Capgemini / 2001
Java objects ↔ XML: the MetaSolv–Cygent integration
A utility using the Java Reflection API translated Java objects to XML and XML back into Java objects at the boundary between telecom CRM and order-management systems.
Java objects ↔ XML, in both directions
- Java objectsApplication representation
- Java Reflection APIObject ↔ XML conversion
- XML transactionsIntegration representation
The utility used the Java Reflection API to work with Java objects.
Read the complete architecture & boundaries
MetaSolv–Cygent integration: the diagram shows the confirmed bidirectional conversion, without assigning an unconfirmed role or transport to either product.
- Inspect the object. The utility used the Java Reflection API to work with Java objects.
- Convert to XML. Java objects were converted into XML for the integration boundary.
- Reconstruct the object. XML was converted back into Java objects using the same utility.
THE PROBLEM
What needed to change.
The MetaSolv–Cygent integration needed Java application objects and XML transactions to work across a telecom CRM and order-management/backend boundary.
MY CONTRIBUTION
Where I came in.
I wrote a utility using the Java Reflection API to convert Java objects into XML and reconstruct Java objects from XML.
The team connected the telecom CRM and order-management/backend systems using XML transactions.
THE APPROACH
How it came together.
- Inspect Java objects through the Java Reflection API.
- Convert Java objects into XML transactions.
- Convert incoming XML back into Java objects.
- Use the utility within the MetaSolv–Cygent integration effort.
THE OUTCOME
What the work made possible.
The utility provided conversion in both directions between Java objects and XML for the integration. No throughput or business-impact metric is claimed.
Technical & implementation detail
Technologies described in this account: Java, XML, Java Reflection API.
Java Reflection supported the object/XML conversion utility. MetaSolv and Cygent are the system names confirmed in this review. The diagram shows the conversion boundary; it does not assign each product to a specific endpoint or invent the transport, schema mapping or deployment topology.