OTD based on XSD problem (__TYPE__ auto-added) - JCAPS 5.1.2

Hi all,

when creating a new OTD based on an XSD extra (unwanted) fields are automatically added, with the name __TYPE__ . The javaName is X__TYPE__ .

I also created a webservice based on the same schemas. I imported the WSDL and set it up to run in a BP. When I look at the schema definitions created by importing the WSDL it is exactly as defined in the XSD.

The problem is that when I map a business rule (in the Business Rule Designer) which maps the input message (based on the schemas in the imported wsdl) to a JCD (which uses the OTD with the extra __TYPE__ field as its input) I can't drag the top level element from the left to the right to automap all the fields!

How can I either:

a) create the OTD based on XSD and stop it from creating the __TYPE__ fields.

b) in the BP Designer get it to automap by just dragging the top level element (despite the extra __TYPE__ fields everything else is identical).

I have not found any documentation on this issue and have looked in several forums for an answer, without success.

Hopefully I have been clear and there's an easy answer...

Kind regards,

Stijn.

[1177 byte] By [StijnMa] at [2007-11-27 4:16:08]
# 1

Hi all,

I have found a workaround to get an exact OTD based on a given XSD - one that doesn't contain the __TYPE__ nonsense.

I found a post (this one: http://eai.ittoolbox.com/groups/technical-functional/seebeyond-l/xsd-object-vs- xsd-object-type-definition-difference-1157772 ) which gave me a good tip on how to go about circumventing the normal OTD wizard.

Still, if anyone has anymore insights into the problem, I would gladly like to hear about it!

Kind regards,

Stijn.

StijnMa at 2007-7-12 9:22:36 > top of Java-index,Java Enterprise System,Java Composite Application Platform Suite -- General Discussion...