jQuery in Action, 2nd edition
The moose likes Web Services and the fly likes Weblogic 10 -    operation Name part of request XML  Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "Weblogic 10 -    operation Name part of request XML  " Watch "Weblogic 10 -    operation Name part of request XML  " New topic
Author

Weblogic 10 - operation Name part of request XML

Aditya Kumar
Ranch Hand

Joined: Oct 31, 2006
Posts: 46
Hi,

In weblogic 10.3, We have created a web service from the WSDL. All is OK but the problem that we are facing is that the request XML has the request object encapsulated within the transaction Name tag. For example, if the operation name is getNumericId, the request xml (from the wsdl test page) is coming out to be: <getNumericId><requestXML></getNumericId>.

Because of this, the clients are facing an issue. Is there a way to remove the transaction name from the request XML? Because when I use xmlSpy to create a soap request from the WSDL, it creates the XML without the operation name preceding it and that is assumed to be the standard request structure as per the WSDL shared with the clients.

From what I understand, the WSDL that we use to create the Jws from has differences with the endpoint WSDL that is generated by weblogic. Is this a known issue? How do I resolve this?

Please help!

Aditya
ps: a copy of this message has also been posted at oracle forums
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Weblogic 10 - operation Name part of request XML
 
Similar Threads
Deployment time NameNotFoundException
Creating Custom wsdl definition
Strange behavior with input parameter valuse during web service invocation
Problem when create client for web services because of XSD import url
Problem with arrays of primitive types