This content has been marked as final. Show 7 replies
Seems to be a problem in serialization??? What do I do?
When I invoke the web service from a web proxy client, this is the stack trace:
Process exited with exit code 0.
Does it give good output/return valid when you run the java...instead of the service.
I wouldn't know. Control never reaches my implementation code.
I'm trying to invoke searchAirline.
From the stack trace:
Control enters the main function of the web proxy
Then to the web proxy client's searchAirline method
Then goes to the stub code and calls a send
The stub reads the fault element to try to deserialize it
After going through a bunch of method calls in the deserialization stack, it fails while calling SearchAirline_fault_LiteralSerializer.doDeserialize
Everything that's executed in the stack trace is generated by the wizard.
It doesn't even reach my implementation code.
hmm and searchAirline is some public service...or a local service which you developed too.
It's a local service I developed.
Starting from a valid WSDL, I used the "Java Web Service from WSDL" project wizard to generate a web service with all the default options. I put in simple, dummy implementation code to return dummy values - no processing, no fancy stuff. Everything seemed to go fine - no errors, no warnings. Just messages saying "Successful".
I deployed the service onto my local server. Again, everything went fine.
The service showed up as deployed on my server.
I then tried to invoke the service through the application server control and hit the nullpointerexception with no stack trace.
I then created a web proxy client, again using the wizard. using all default options.
When I ran the web proxy client from within JDeveloper, I got a (the same?) nullpointerexception, but this time with a stack trace that seemed to lead to generated code that was supposed to do deserialization.
I've tried everything I possible can including reinstalling the SOA suite and JDeveloper. All I'm trying to do is prove to my customer that Oracle actually works.
Oracle fails at even something as simple as creating, deploying and running a Java web service out of an existing/legacy WSDL.
Has anyone ever created a Java web service from an existing/legacy WSDL using Oracle ESB/JDeveloper?
Does Oracle itself even acknowledge that it works?
I get something similar that I was just about to ask the forum about.
I'm running SOA Suite 10.1.3.1.0. on w
I've been given wsdls by a standards body and implementing the services as routing services in ESB (with some BPEL behind doing some stuff).
Won't go into the long version, but what I've found is that my request response routing service turns into a one way message if I do an "Apply" in any of the console tabs (e.g. Definition or Properties).
Then my interface goes cactus. I have to redeploy from JDev and I'm back in business again. And then I stay away from "Apply" in the console.
Seems to happen to SOAP invocation services too. This is a bit awkward as you may want to change or specify the end point location property.
Hope this helps you and would appreciate comments from anyone else as I've only just identified this as my issue.