Generating service component definition language from metadata

A Service Component Architecture (“SCA”) generator configured to use data in a Metadata repository to generate files that can be used by an SCA server, comprising:

• an instruction analyzing module configured to analyze input instructions and to determine the Metadata repository from the input instructions;
• a matching module configured to match a service identifier received with the input instructions to service metadata stored in the Metadata repository;
• a retrieving module configured to retrieve service parameters for the matched service;
• a tree generating module configured to generate a parser tree based on the retrieved service parameters;
• and
• an output file generation module configured to recursively walk through the parser tree and to generate target output files;
• wherein the target output files generated by the output generation module are configured so that the SCA server can access services that have associated service metadata stored in the Metadata repository.

A computer-implemented method for using data in a Metadata repository to generate files that can be used by a Service Component Architecture (“SCA”) server, comprising:

• analyzing input instructions input by a user via a command line interface and determining the Metadata repository from the input instructions, wherein the Metadata repository is one or more of a runtime, a stored repository file or an input repository file received with the input instructions;
• matching a service identifier received with the input instructions to service metadata stored in the Metadata repository and retrieving service parameters for the service, wherein the service identifier is a service name;
• generating a parser tree based on the retrieved service parameters starting with a root directory, followed by a service group, the service and the service parameters;
• and
• recursively walking through the parser tree and generating target output files including a composite file, a component file, an abstract base class header file, and a skeletal implementation class header file;
• wherein the target output files are configured so that the SCA server can access services that have associated service metadata stored in the Metadata repository.