Method and apparatus for generating a code bridge

1. A method for generating a code bridge between a client application and a target application, comprising:

generating a metadata file defining exposed interfaces for the client application and the target application;

creating a schema defining the code bridge using the metadata file; and

generating source code for the code bridge using the schema,

wherein the code bridge enables the client application to invoke a method on the target application, and

wherein the client application is written in a first programming language and the target application is written in a second programming language.

2. The method of claim 1 , further comprising:

deploying the code bridge using a binary component derived from the source code.

3. The method of claim 1 , wherein generating the metadata file comprises using a compiler.

4. The method of claim 1 , wherein generating the metadata file comprises using an introspection tool.

5. The method of claim 1 , wherein generating the metadata file comprises using a code descriptor database.

6. The method of claim 1 , wherein the schema uses Extensible Mark-up Language to define the code bridge.

7. The method of claim 1 , wherein creating the schema comprises using a metadata conversion tool.

8. The method of claim 1 , wherein creating the schema comprises using a component-design editor.

9. The method of claim 1 , wherein creating the schema comprises using an automation tool.

10. The method of claim 9 , wherein the automation tool comprises functionality for parameter usage and parameter conflict resolution.

11. The method of claim 9 , wherein the automation tool comprises functionality to automatically generate the schema using default rules.

12. The method of claim 9 , wherein the automation tool comprises functionality to flag a portion of the metadata that the automation tool cannot process.

13. The method of claim 9 , wherein the automation tool comprises functionality to review and refine an automatically generated schema file.

14. The method of claim 1 , wherein generating source code for the code bridge uses an extensible stylesheet language template and an extensible stylesheet language processor.

15. The method of claim 1 , further comprising: generating a descriptor for the code bridge using the schema.

16. The method of claim 2 , further comprising:

generating a descriptor containing configuration information for the code bridge using the schema; and

generating a build configuration file containing rules for the code bridge using the schema.

17. The method of claim 16 , wherein the binary component is generated using the source code, the descriptor, and the build configuration file.

18. A method for generating a code bridge between a client application and a target application, comprising:

generating a metadata file defining exposed interfaces for the client application and the target application;

creating a schema defining the code bridge using the metadata file;

generating source code for the code bridge using the schema; and

deploying the code bridge using a binary component derived from the source code,

wherein the code bridge enables the client application to invoke a method on the target application, and

wherein the client application is written in a first programming language and the target application is written in a second programming language.

19. A method for generating a reusable code bridge component, comprising:

generating a first schema defining an exposed interface for a target application;

generating a second schema defining an exposed interface for a first client application;

generating a target-side code bridge component using the first schema and the second schema;

generating a first client-side code bridge component using the first schema and the second schema; and

bridging the target application and first client application using the first client-side code bridge component and the target-side code bridge component.

20. The method of claim 19 , further comprising:

generating a third schema defining an exposed interface for a second client application;

generating a second client-side code bridge component using the first schema and the third schema; and

bridging the target application and the second client application using the second client-side code bridge component and the target-side code bridge component.

21. The method of claim 19 , wherein the first schema comprises Extensible Mark-up Language.

22. The method of claim 19 , wherein the second schema comprises Extensible Mark-up Language.

23. The method of claim 20 , wherein the third schema comprises Extensible Mark-up Language.

24. The method of claim 19 , wherein generating the first client-side code bridge component comprises an extensible stylesheet language template and an extensible stylesheet language processor.

25. The method of claim 19 , wherein generating the target-side code bridge component comprises an extensible stylesheet language template and an extensible stylesheet language processor.

26. The method of claim 20 , wherein generating the second client-side code bridge component comprises an extensible stylesheet language template and an extensible stylesheet language processor.

27. An apparatus for generating a code bridge between a client application and a target application, comprising:

means for generating a metadata file defining exposed interfaces for the client application and the target application;

means for creating a schema defining the code bridge using the metadata file; and

means for generating source code for the code bridge using the schema,

wherein the code bridge enables the client application to invoke a method on the target application, and

wherein the client application is written in a first programming language and the target application is written in a second programming language.

28. An apparatus for generating a code bridge between a client application and a target application, comprising:

means for generating a metadata file defining exposed interfaces for the client application and the target application;

means for creating a schema defining the code bridge using the metadata file;

means for generating source code for the code bridge using the schema; and

means for deploying the code bridge using a binary component derived from the source code,

wherein the code bridge enables the client application to invoke a method on the target application, and

wherein the client application is written in a first programming language and the target application is written in a second programming language.

29. An apparatus for generating a reusable code bridge component, comprising:

means for generating a first schema defining an exposed interface for a target application;

means for generating a second schema defining an exposed interface for a first client application;

means for generating a target-side code bridge component using the first schema and the second schema;

means for generating a first client-side code bridge component using the first schema and the second schema;

means for bridging the target application and first client application using the first client-side code bridge component and the target-side code bridge component;

means for generating a third schema defining an exposed interface for a second client application;

means for generating a second client-side code bridge component using the first schema and the third schema; and

means for bridging the target application and the second client application using the second client-side code bridge component and the target-side code bridge component.