Generating Service Component Definition Language from Metadata

1. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processor, cause the processor to perform a process that uses data in a metadata repository to generate files that can be used by a Service Component Architecture (SCA) server, the process comprising: analyzing input instructions and determining the metadata repository from the input instructions, wherein the metadata repository comprises an architecture; matching a service identifier received with the input instructions to service metadata stored in the metadata repository and retrieving service parameters for a service; generating a parser tree based on the retrieved service parameters, wherein generating the parser tree starting with a root directory, followed by a service group, the service, one or more buffer definitions per the service and the service parameters; and recursively walking through the parser tree and generating target output files based on the parser tree, wherein the target output files comprise 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 without requiring information regarding the architecture.

2. The non-transitory computer readable medium of claim 1 , wherein the metadata repository comprises at least one of: a runtime, a stored repository file or an input repository file received with the input instructions.

3. The non-transitory computer readable medium of claim 1 , wherein the target output files further comprise at least one Extensible Markup Language Schema Definition schema for complex data types.

4. The non-transitory computer readable medium of claim 1 , wherein the metadata repository is a Tuxedo® Metadata Repository.

5. A Service Component Architecture (SCA) server, comprising: a memory configured to store one or more modules; a processor configured to execute the one or more modules; an instruction analyzing module configured to analyze input instructions and to determine the metadata repository from the input instructions, wherein the metadata repository comprises an architecture; 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 a service; a tree generating module configured to generate a parser tree based on the retrieved service parameters, wherein generating the parser tree starting with a root directory, followed by a service group, the service, one or more buffer definitions per the service and the service parameters; and an output file generation module configured to recursively walk through the parser tree and to generate target output files based on the parser tree, wherein the target output files comprise a composite file, a component file, an abstract base class header file, and a skeletal implementation class header file; 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 without requiring information regarding the architecture.

6. The SCA server of claim 5 , wherein the target output files further comprise at least one Extensible Markup Language Schema Definition schema for complex data types.

7. The SCA server of claim 5 , wherein the metadata repository comprises at least one of: a runtime, a stored repository file or an input repository file received with the input instructions.

8. The SCA server of claim 5 , wherein the metadata repository is a Tuxedo® Metadata Repository.

9. 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 comprises one or more of a runtime, a stored repository file or an input repository file received with the input instructions, and wherein the metadata repository comprises an architecture; matching a service identifier received with the input instructions to service metadata stored in the metadata repository and retrieving service parameters for a 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, one or more buffer definitions per the service and the service parameters; and recursively walking through the parser tree and generating target output files based on the parser tree, the target output files comprising 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 without requiring information regarding the architecture.

10. The computer-implemented method of claim 9 , wherein the target output files further include at least one Extensible Markup Language (XML) Schema Definition (XSD) schema for complex data types.

11. The computer-implemented method of claim 9 , wherein the metadata repository is a Tuxedo® Metadata Repository.