[
https://jira.jboss.org/jira/browse/SOAG-47?page=com.atlassian.jira.plugin...
]
Gary Brown commented on SOAG-47:
--------------------------------
Approaches:
1) Simple xsd types can be directly mapped to their equivalent Java types, e.g. xsd:string
to java.lang.String
No disadvantages to this.
2) In the CDL, it is possible to specify a namespace against a prefix, and then use the
prefix with the type/element local part when referring to the type. It would be possible
to use a different type of namespace, categorised by the URL scheme, e.g. namespace
"java:org.jboss.example.purchasing" and prefix "purchasing" could
reference a Java package, with the Java class being then used in conjunction with the
prefix, e.g. "puchasing:Order"
Advantage is that it is simple and direct.
Disadvantage is that it binds the choreography to Java types.
3) We need some way to map an XML namespace + localpart to a Java class:
a) Use JAXB annotations on the Java class to link back to the XML namespace/localpart
(e.g. using the XmlRootElement annotation).
Advantage: This does not impact the choreography, which can remain independent of the
implementation types used
Disadvantage: Requires Java classes to define the annotation - which would be impossible
for third party classes, and also may have a performance issue on the tools, as it may be
necessary to scan all of the classes in jars associated with the project, to identify any
that have the relevant annotation
b) Custom mapping file - would need to understand the relationship between the
choreography file and the mapping file (i.e. how will the generator locate the mapping
file?)
Advantages: simple
Disadvantages: ???
Options (1) and (2) can be implemented regardless of what mechanism is supported for (3).
Handle both XML and Java types between choreography and jboss-esb.xml
descriptions
----------------------------------------------------------------------------------
Key: SOAG-47
URL:
https://jira.jboss.org/jira/browse/SOAG-47
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 1.0 CR1
Reporter: Gary Brown
Assignee: Gary Brown
Currently CDL specifies XML elements/types for messages and variables.
However jboss-esb.xml actions may be dealing with XML or Java objects on the pipeline.
Also state variables associated with the business object type could be Java or XML.
Need to decide how the types should be recorded in the choreography, and how they should
be mapped to types in the generated jboss-esb.xml and supporting Java classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira