I had once tried using DOM as Object Parts in the WSIFMessage without anythis looks like a bug. unfortunately this code in WSIFOperation_ApacheAxis is not easy to follow.
success.
I checked the code of WSIFOperation_ApacheAxis
Inside function "invokeRequestResponseOperation" api isMessaging(inMsg) is
called which returns true in case the WSIFMessage Parts are DOM Elements.
This then sets the operation style to AXIS_STYLE_MESSAGE (thus oes the AXIS
Call invoke for 'messaging') even if the actual WebService is RPC or DOC
style.
Any recommendations on how DOM can be used.please file a bug in jira:
http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10462
and if you have some time to debug it and resolve it please submit a patch (follow instructions from http://wiki.apache.org/old/AxisProjectPages/SubmitPatches except that use Jira instead of bugzilla - could not fix it as page is "immutable" :( )
thanks,
alek
-----Original Message-----
From: Aleksander Slominski [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 10:42 AM
To: [EMAIL PROTECTED]
Subject: Re: WSIF and JROM
Christian wrote:
Hello,i think JROM is no longer supported and it never was open source anyway. try to use DOM Element instead to construct exactly what XML you want to send.
How is it possible to use JROM Serializer/Desializer with the DynamicInvoaction.class from the WSIF examples. I just want to map an complex data type to JROMComplexType for the input wsdl message part.
HTH,
alek
-- The best way to predict the future is to invent it - Alan Kay
