Method for providing a pluggable custom data binding system
View Patent ↗The present invention is directed to a pluggable custom data binding system and method utilizing a generic data structure exchanged between a run-time system and a user define binding logic in Web Service Applications. The custom data binding system may replace the existing mappings for XML schema types. The custom binder is a function that works with the pairing of a particular XML schema type and Java type. The custom binder may define an interface including serialize and de-serialize methods to convert between Java objects and SOAPElements. After the custom binder is plugged into the run-time system, this custom binder may interact with the run-time system through use of SOAPElement. The custom binding provider may aggregate related custom binders to support particular custom data bindings. The custom binding provider may be created for a specific application that has a few XML schema types that are not supported by the JAX-RPC specification.
1. A method of mapping Java types to extended markup language schema types, comprising:
mapping at least one markup language schema to at least one Java type to define at least one custom binder associated with the markup language schema/Java type pair, wherein mapping of the at least one markup language schema to the at least one Java type is unsupported by Java Application Programming Interface for XML-based Remote Procedure Call (JAX-RPC);
receiving at least one Java object employing the at least one Java type;
selecting a custom binder according to the at least one Java type of the at least one Java object;
serializing the Java object employing the at least one Java type to a Simple Object Access Protocol (SOAP)Element generic data structure via the custom binder; and
serializing the SOAPElement to a SOAP message employing the at least one markup language schema.
2. The method as described in claim 1 , wherein the at least one markup language schema is in accordance with an extensible markup language.
3. The method as described in claim 1 , wherein the custom binder is implemented by a binding provider.
4. The method as described in claim 3 , wherein the binding provider aggregates a plurality of custom binders to support a particular application.
5. A method of mapping extended markup language schema types to Java types, comprising:
mapping at least one markup language schema to at least one Java type to define at least one custom binder associated with the markup language schema/Java type pair, wherein mapping of the at least one markup language schema to the at least one Java type is unsupported by Java Application Programming Interface for XML-based Remote Procedure Call (JAX-RPC);
receiving a Simple Object Access Protocol (SOAP) message employing the markup language schema;
selecting a custom binder according to the at least one markup language schema of the SOAP message;
de-serializing the SOAP message to a SOAPElement; and
de-serializing the SOAPElement to a Java object having the at least one Java type via the custom binder.
6. The method as described in claim 1 , wherein the at least one markup language schema is in accordance with an extensible markup language.
7. The method as described in claim 1 , wherein the custom binder is implemented by a binding provider.
8. The method as described in claim 7 , wherein the binding provider aggregates a plurality of custom binders to support a particular application.