This content has been marked as final. Show 2 replies
Please apply the Debug Flag "-Dweblogic.webservice.verbose=true" If possible then Both End Client and Server End. U will see the complete Soap Message on Server Side...It will help us the Understand that Why WebLogic Client is not able to send Proper SOAPMessage.
Please specify that How you Generated ClientSide Artifacts...Using WebLogic provided "ClientGen" Utility or ...some other utility.
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Dec 19, 2009 2:12 PM
I generted the Client artifacts on Weblogic Workshop and I'm using it on a JPD file, I did it with the Web Service Control Wizard on Workshop.
I don't know what you mean with that flag, I already put a handler on the Web Service control to look at the soap message * @jc:handler operation="com.oracle.mslv.mip.logger.ConsoleLoggingHandler"
But If i take that soap msg and send it by soap ui to the same service it works perfectly.
I do not have access to the CRM Weblogic Platform. Should i put that flag on the weblogic that is running my JPD?