Web Services from WSDL file

Hi there. I am new for Java Web Services.
I'm trying to generate a web service from a .wsdl file. This file includes a references to other .xsd files
and that's the problem.
First I've tried with JBuilder 9 but it gave me some problems with some element definitions from xsd file (such as those elements defined as 'choice'): there were generated some classes with repeated elements (such as variables and methods), some classes with strange names (it was added a 'TypeN' label to the name of the class), etc.
Then I've tried with Sun One Studio 5. It didn't support 'include' tags in the wsdl file.
Later I've tried with Weblogic Workshop but an error with an internal class of Weblogic was generated.
Can anyone tell me what editor could I use to generate the Java Web Services?
Thanks!

https://jax-rpc.dev.java.net/whitepaper/1.1/index-part2.html explains in detail how to develop, deploy and invoke a web service starting from a WSDL.
Let me know if you have any specific questions.
Thanks,
-Arun

Similar Messages

Error creating web service from WSDL in 11.1.2.0.0

Hello,
I have just installed JDeveloper 11.1.2.0.0. I tried to test a web service created (and successfully tested) in 11.1.1.5.0. The service is deployed to internal WebLogic server but when I call "Test Web Service" this is the error I get:
The Web Service Tester cannot be invoked, because the WSDL document of the selected service cannot be read.
java.lang.IllegalStateException: SSLContextImpl is not initialized
     at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
     at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
     at java.lang.ThreadLocal.get(ThreadLocal.java:131)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLDirect(CachedWSDLReader.java:471)
     at oracle.jdevimpl.webservices.tcpmonitor.ServiceTester$3.run(ServiceTester.java:262)
     at java.lang.Thread.run(Thread.java:662)
Then I tried to create a new project and Java web service from WSDL, but on the second step of the "Java Web Service from WSDL" wizard when I select WSDL file from the disk and click "Next" I get
java.lang.IllegalStateException: SSLContextImpl is not initialized
java.lang.IllegalStateException: SSLContextImpl is not initialized
     at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
     at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
     at java.lang.ThreadLocal.get(ThreadLocal.java:131)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:484)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:455)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.fetchWSDL(SpecifyWsdlPanel.java:1050)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$1.run(SpecifyWsdlPanel.java:364)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
I performed fresh install of this new JDeveloper version in new Middleware home with all the default options and this is the first thing I tried.
Any hints?
Thanks,
Bruno

Hi Vishal,
no, I don't see any HTTPS security settings defined. The thing is that this worked just fine in 11.1.1.5.0 version. I installed 11.1.2.0.0 and the first thing I tried was testing this web service. Right away I get this error. I also tried creating Web Service Client Proxy for this web service and I get the same exception. I looks to me that this happens when wizard tries parsing WSDL...
But, I got another error when I opened "Java Web Service Editor" for this web service and selected "Methods":
NPE in o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel:702
Performing action (35) Project Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService.jpr, VegaService.jpr, DMSVegaAdapter.jws ) ]
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:02 AM IndexFacade runQuery
INFO: Having to guess workspace
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:28 AM IndexFacade runQuery
INFO: Having to guess workspace
Performing action (23) Find... [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (56) Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService, VegaService.jpr, DMSVegaAdapter.jws ) ]
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:09:32 AM IndexFacade runQuery
INFO: Having to guess workspace
java.lang.NullPointerException
java.lang.NullPointerException
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.populateListImpl(SelectMethodsPanel.java:702)
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.access$600(SelectMethodsPanel.java:82)
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel$4$1.run(SelectMethodsPanel.java:603)
j.a.event.InvocationEvent.dispatch(InvocationEvent.java:209)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:642)
j.a.EventQueue.access$000(EventQueue.java:85)
j.a.EventQueue$1.run(EventQueue.java:603)
j.a.EventQueue$1.run(EventQueue.java:601)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.a.EventQueue.dispatchEvent(EventQueue.java:612)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
j.a.Dialog$1.run(Dialog.java:1046)
j.a.Dialog$3.run(Dialog.java:1098)
j.security.AccessController.doPrivileged(Native Method)
j.a.Dialog.show(Dialog.java:1096)
j.a.Component.show(Component.java:1585)
j.a.Component.setVisible(Component.java:1537)
j.a.Window.setVisible(Window.java:842)
j.a.Dialog.setVisible(Dialog.java:986)
o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
o.i.dialogs.WizardLauncher.runDialog(WizardLauncher.java:55)
o.i.panels.TDialogLauncher.showDialog(TDialogLauncher.java:225)
o.ji.webservices.wizard.jaxrpc.WebServicesEditor.showDialog(WebServicesEditor.java:313)
o.ji.webservices.WebServicesAddin.findAndInvokeWizard(WebServicesAddin.java:1672)
o.ji.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:870)
o.i.controller.IdeAction$ControllerDelegatingController.handleEvent(IdeAction.java:1469)
o.i.controller.IdeAction.performAction(IdeAction.java:662)
o.i.controller.IdeAction.actionPerformedImpl(IdeAction.java:1140)
o.i.controller.IdeAction.actionPerformed(IdeAction.java:617)
jx.s.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
jx.s.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
jx.s.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
jx.s.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
jx.s.AbstractButton.doClick(AbstractButton.java:357)
jx.s.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
jx.s.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
j.a.Component.processMouseEvent(Component.java:6289)
jx.s.JComponent.processMouseEvent(JComponent.java:3267)
j.a.Component.processEvent(Component.java:6054)
j.a.Container.processEvent(Container.java:2041)
j.a.Component.dispatchEventImpl(Component.java:4652)
j.a.Container.dispatchEventImpl(Container.java:2099)
j.a.Component.dispatchEvent(Component.java:4482)
j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
j.a.LightweightDispatcher.processMouseEvent(Container.java:4238)
j.a.LightweightDispatcher.dispatchEvent(Container.java:4168)
j.a.Container.dispatchEventImpl(Container.java:2085)
j.a.Window.dispatchEventImpl(Window.java:2478)
j.a.Component.dispatchEvent(Component.java:4482)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:644)
j.a.EventQueue.access$000(EventQueue.java:85)
j.a.EventQueue$1.run(EventQueue.java:603)
j.a.EventQueue$1.run(EventQueue.java:601)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
j.a.EventQueue$2.run(EventQueue.java:617)
j.a.EventQueue$2.run(EventQueue.java:615)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.a.EventQueue.dispatchEvent(EventQueue.java:614)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
j.a.EventDispatchThread.run(EventDispatchThread.java:122)
Regards,
Bruno

Trouble Creating Web Service from WSDL in 9.2

I am following the guide at: http://edocs.bea.com/wls/docs92/webserv/setenv.html#wp214576 for creating a web service from wsdl using Ant. When i run the "wsdlc" task, it creates a Jar with source files but no class files. This seems odd.
So, i have to then manually unjar, compile, and re-jar it to work? And what about using the types in an IDE like Eclipse? I have to un-jar the source files and include them in my project? This makes no sense. Why not have the ant task compile the classes in the jar?

I am following the guide at: http://edocs.bea.com/wls/docs92/webserv/setenv.html#wp214576 for creating a web service from wsdl using Ant. When i run the "wsdlc" task, it creates a Jar with source files but no class files. This seems odd.
So, i have to then manually unjar, compile, and re-jar it to work? And what about using the types in an IDE like Eclipse? I have to un-jar the source files and include them in my project? This makes no sense. Why not have the ant task compile the classes in the jar?

"java Web Service from WSDL" just hands me a SOAPElement, no java mappings

Another beginner question. I've used jdev and built a WSDL starting from a somewhat complex xsd. I've used the wizard "Java Web Service From WSDL" taking defaults. It seems to correctly generate class files for all my xsd types. It produces a fancy looking java-wsdl-mapping.xml But the generated stub service implementation just gets handed a SOAPElement object. Why generate all that mapping stuff and then make me parse the incoming data myself with SOAPElement methods? How am I supposed to make use of the mapping work that the wizard seems to have done for me?
Thanks,
Steve

Dear Tugdual,
Thanks for your intrest in my issue. I narrowed it down to the following type in my xsd
<complexType name="PersonInfoType">
<sequence >
<element name="FamilyName" type="string"/>
<element name="IndividualName" type="string"/>
<element name="SpouseName" type="string"/>
<element name="BirthDate" type="dateTime"/>
</sequence>
</complexType>
This works fine - the "WebSerice From WSDL" wizard "knows" how to generate a class for PersonInfoType (with geters and seters) as well as useful stub implementation:
public class PersonInfoImpl {
public PersonInfoType processPersonInfo(String entityCode) {
return null;
However, if I make my type multiple occuring (to represnt e.g. rows from a db)
<complexType name="PersonInfoType">
<sequence maxOccurs="unbounded" >
<element name="FamilyName" type="string"/>
<element name="IndividualName" type="string"/>
<element name="SpouseName" type="string"/>
<element name="BirthDate" type="dateTime"/>
</sequence>
</complexType>
Now the Web Service generator runs, but just doesn't generate any PersonInfoType class at all. For a stub implementation it genertes the following:
public class PersonInfoImpl {
public SOAPElement processPersonInfo(String entityCode) {
return null;
Now I'm stuck with the container just expecting from me a Soap Object and I have to build all the pieces myself with no java mappings to my xsd at all. Not very useful.
Is there another xml structure I can use to represent data rows that is better supported by the wizard?
Thanks,
Steve

Error when generating a Web Service from WSDL (Weblogic Workshop)

Hi,
I am using weblogic workshop 10 for implementing web services and its was working fine. But now when I try to generate a web service from WSDL its crashing with the following error;
Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
org.eclipse.core.runtime.CoreException: Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws(JwsFromWsdlBuilder.java:107)
     at com.bea.workshop.webservices.ui.wizards.jwsfromwsdl.GenerateJwsFromWsdlWizard$1.execute(GenerateJwsFromWsdlWizard.java:133)
     at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
     at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
org.eclipse.core.runtime.CoreException[4]: com.bea.workshop.webservices.core.gen.WebServicesException:
     at com.bea.workshop.webservices.core.gen.GenerationScript.runAnt(GenerationScript.java:154)
     at com.bea.workshop.webservices.core.gen.GenerationScript.createJWS(GenerationScript.java:98)
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws0(JwsFromWsdlBuilder.java:135)
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws(JwsFromWsdlBuilder.java:98)
     at com.bea.workshop.webservices.ui.wizards.jwsfromwsdl.GenerateJwsFromWsdlWizard$1.execute(GenerateJwsFromWsdlWizard.java:133)
     at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
     at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
     at org.eclipse.ant.core.AntRunner.problemLoadingClass(AntRunner.java:445)
     at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:417)
     at org.eclipse.ant.core.AntRunner.run(AntRunner.java:362)
     at com.bea.workshop.webservices.core.gen.GenerationScript.runAnt(GenerationScript.java:152)
     ... 8 more
I have checked my ANT_HOME and its pointing to the correct location bea\tools\eclipse32\eclipse\plugins\org.apache.ant_1.6.5 and the AntMain classs is present in this path: org.apache.tools.ant.launch.AntMain
If anyone has any idea on this please suggest a solution.
Thanks in advance
-AKJ

Yes, I assume you are talking about ANT_HOME:
see this Screenshot which shows my current settings
[http://i43.tinypic.com/nbrec6.jpg|http://i43.tinypic.com/nbrec6.jpg]
Regards
-AKJ

When to use Java Web Service from WSDL, Webservice proxy, Web Service DataControl -- JDeveloper 11.1.1.7

Hi Experts!
I am having confusion among these 3 services provided in Oracle ADF. When to use and what service needs to be used?
Once we generate Webservice WSDL. With the WSDL we have 3 options in Jdeveloper to invoke this service.
1. Java Web Service From WSDL.
2. Web Service proxy,
3. Web Service Data Control.
Can anyone give us some brief description of these 3 services when do we need to use and which service is to be used for which scenario ?
Please give me your valuable inputs.
Thanks & Regards,
Guravaiah Tata.

Hi,
Can you share your WSDL.
You can send it to me at [email protected]
-Vishal

Parameter names change when generating web service from WSDL

Hi,
I have a problem with BEAs web services that I'm hoping someone can help me with.
I have a
WSDL file, and from that I want to generate a web service implementation and a
web service
client. In the WSDL file, I have a message defined like this:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="data"/>
</message>
I generate the server using the server using the wsdl2service Ant task, I implement
the necessary classes, and I deploy it. When I access the deployed web service,
the parameter name has changed, from "data" to "bytes". If I access the WSDL file
of the deployed web service, it says:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="bytes"/>
</message>
This happens for all parameters, string parameters are renamed to "string", base64Binary
parameters are renamed to "bytes", etc...
This poses a problem to me, because if I generate a web service client from the
original WSDL file, it will not be able to talk to my web service. Is there any
way of forcing a web service generated from a WSDL file to keep the parameter
names of the original WSDL file?
Any help in this is greatly appreciated.
Regards,
Petter

From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
Here are sample of bare-style :
<xsd:element name="getPupilAddressResponse" type="xsd:string"/>
<xsd:element name="getPupilAddressRequest" type="xsd:int"/>
Wrapped will looks like that:
<xsd:element name="getSENLevelResponse">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
<xsd:element name="RecordCount" type="xsd:int">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Hope this helps,
Eric

Unable to create web service from wsdl that contains xsd as import

I have written a WSDL and tried to create the web services by weblogic workshop.
Prior to that I have created the war file and able to deploy them properly. Also able to access any wsdl by hitting the server.
But when I am trying to create the web services by weblogic workshop its throwing error as "URL is not well formed" for those XSDs which I have imported in my WSDL. I have kept all my XSDs and WSDLs in the same folder.
The WSDL has given below :
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:intf="http://soapheader.ibm.com" xmlns:impl="http://soapheader.ibm.com" xmlns:MessageContext="MessageContext" xmlns:AlertUpdateRequest="AlertUpdateRequest" xmlns:AlertFetchResponse="AlertFetchResponse" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapheader.ibm.com">
     <import namespace="MessageContext" location="http://localhost:7001/WebApplicationWeb/gss/xsd/MessageContext.xsd"/>
     <import namespace="AlertUpdateRequest" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertUpdateRequest.xsd"/>
     <import namespace="AlertFetchResponse" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertFetchResponse.xsd"/>
     <wsdl:types>
          <schema elementFormDefault="qualified" targetNamespace="http://ggg.com" xmlns="http://www.w3.org/2001/XMLSchema">
          </schema>
     </wsdl:types>
     <wsdl:message name="alertUpdateRequest">
          <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertUpdateResponse">
          <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertFetchRequest">
          <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:message name="alertFetchResponse">
          <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
          <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
     </wsdl:message>
     <wsdl:portType name="AlertUpdateService">
          <wsdl:operation name="getAlertUpdate">
               <wsdl:input name="alertUpdateRequest" message="intf:alertUpdateRequest"/>
               <wsdl:output name="alertUpdateResponse" message="intf:alertUpdateResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:portType name="AlertFetchService">
          <wsdl:operation name="getAlert">
               <wsdl:input name="alertUpdateRequest" message="intf:alertFetchRequest"/>
               <wsdl:output name="alertUpdateResponse" message="intf:alertFetchResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="AlertUpdateServiceSoapBinding" type="intf:AlertUpdateService">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getAlertUpdate">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:header message="intf:alertUpdateRequest" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:header message="intf:alertUpdateResponse" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:binding name="AlertFetchServiceSoapBinding" type="intf:AlertFetchService">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getAlert">
               <wsdlsoap:operation/>
               <wsdl:input>
                    <wsdlsoap:header message="intf:alertFetchRequest" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <wsdlsoap:header message="intf:alertFetchResponse" part="request_header" use="literal"/>
                    <wsdlsoap:body parts="parameters" use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="AlertUpdateServiceService">
          <wsdl:port name="AlertUpdateService" binding="intf:AlertUpdateServiceSoapBinding">
               <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertUpdateService"/>
          </wsdl:port>
     </wsdl:service>
     <wsdl:service name="AlertFetchServiceService">
          <wsdl:port name="AlertFetchService" binding="intf:AlertFetchServiceSoapBinding">
               <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertFetchService"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>

Hi,
From your description I am assuming that you are using JAX-WS, if not get back to me as I might have another bug to look at.
The problem is that the annotation @Oneway needs to be added to the methods in java files for this to work correctly. You can either do this manually or use the PI in the code editor. I have raised bug 6266513 to track the fact this annotation is not written out properly. I have logged bug 6266556 to track the nillable=true and extranious elements you will see when you do add @Oneway.
Thanks for the quality of your bug report, and we would of course welcome any other feedback good or bad you would like to give us.
Gerard Davison
JDeveloper Web Services Team

Java Web Service from WSDL

I got the following error generating from a TALEO WSDL file:
Error creating model from WSDL: Two declarations cause a collision in the Object Factory Class.
The WSDL file from TALEO is very large - 16000 + lines. and the error does not point specifically to the offending declarations(if any). I downloaded Apache Axis2 and successfully used wsdl2java.bat to generate from the same wsdl file. This is perplexing, especially since I am just learning how to create a web service call.
Dean Geary

Dear Tugdual,
Thanks for your intrest in my issue. I narrowed it down to the following type in my xsd
<complexType name="PersonInfoType">
<sequence >
<element name="FamilyName" type="string"/>
<element name="IndividualName" type="string"/>
<element name="SpouseName" type="string"/>
<element name="BirthDate" type="dateTime"/>
</sequence>
</complexType>
This works fine - the "WebSerice From WSDL" wizard "knows" how to generate a class for PersonInfoType (with geters and seters) as well as useful stub implementation:
public class PersonInfoImpl {
public PersonInfoType processPersonInfo(String entityCode) {
return null;
However, if I make my type multiple occuring (to represnt e.g. rows from a db)
<complexType name="PersonInfoType">
<sequence maxOccurs="unbounded" >
<element name="FamilyName" type="string"/>
<element name="IndividualName" type="string"/>
<element name="SpouseName" type="string"/>
<element name="BirthDate" type="dateTime"/>
</sequence>
</complexType>
Now the Web Service generator runs, but just doesn't generate any PersonInfoType class at all. For a stub implementation it genertes the following:
public class PersonInfoImpl {
public SOAPElement processPersonInfo(String entityCode) {
return null;
Now I'm stuck with the container just expecting from me a Soap Object and I have to build all the pieces myself with no java mappings to my xsd at all. Not very useful.
Is there another xml structure I can use to represent data rows that is better supported by the wizard?
Thanks,
Steve

Problem in writing a client web service from WSDL document

Hi,
I wrote a web service using .Net and a WSDL document. I tried after that to generate a client web service using Jdeveloper. but, the methode generated by Jdeveloper (in the stub) does not represente the original methode.
<?xml version = '1.0' encoding = 'windows-1252'?>


<definitions
name="CreditCard"
targetNamespace="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard"
xmlns:ns1="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard/schema">
<types>
<schema
targetNamespace="http://tempuri.org/jdeveloper/generated/CreditCard/CreditCard/schema"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"/>
</types>
<message name="Validate0Request">
<part name="cardNumber" type="xsd:string"/>
<part name="lngDate" type="xsd:long"/>
</message>
<message name="Validate0Response">
<part name="return" type="xsd:boolean"/>
</message>
<portType name="CreditCardPortType">
<operation name="Validate">
<input name="Validate0Request" message="tns:Validate0Request"/>
<output name="Validate0Response" message="tns:Validate0Response"/>
</operation>
</portType>
<binding name="CreditCardBinding" type="tns:CreditCardPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="Validate">
<soap:operation soapAction="" style="rpc"/>
<input name="Validate0Request">
<soap:body use="encoded" namespace="CreditCard.CreditCard" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="Validate0Response">
<soap:body use="encoded" namespace="CreditCard.CreditCard" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="CreditCard">
<port name="CreditCardPort" binding="tns:CreditCardBinding">
<soap:address location="http://localhost:8888/FirstSample-CreditCard-context-root/CreditCard.CreditCard"/>
</port>
</service>
</definitions>
Here The methode Validate consume two parameters : string and long
the generated stub look like :
public Vector Validate(Element requestElem) throws Exception
There is some one who have a solution ?
---------------------------------------

My guess is that it is because .NET defaults to generating a document style interface whereas JDeveloper defaults to generating an RPC style interface. The end result is that JDeveloper wraps the document interface in something that looks document like - thus your client. To see how to handle this right now, check out this sample - you have to parse the XML:
http://otn.oracle.com/tech/webservices/htdocs/series/net/content.html
In the preview of JDeveloper 9.0.3 which is due quite soon - next few weeks roughly (crossing my fingers) - JDeveloper will wrap .NET document based Web services in a much more elegant wrapper - giving you exactly what you are looking for - a method called Validate rather than a vector of Elements.
What I don't understand in your sample, however, is that you have WSDL generated from JDeveloper versus WSDL generated from .NET. Did you also do an implementation of the validate method in Java too?
Mike.

How to get contents of Soap Over JMS web service's wsdl file

Hi,
Is there a way to get the soap over jms webservice's wsdl file in browser? if yes please provide me the details how to get it.
OR how can i get the contensts of WSDL file for soap over jms wsdl file.
thanks in advance.

I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
Have you already found an answer to this?

XMLBean generation from WSDL file

I have used workshop for weblogic 9.2 to generate web service from wsdl files. The problem is however, that the (XmlBean) code generated from the <wsdl:fault name="..... /> does not genetate a "Throwable" object. The resulting methods produced by the Web Services -> Generate Web Service... menu option produces code that cannot be compiled, because the (generated) throws clause uses an object that is not derived from Throwable.
Has anyone else had these symptoms? is there a fix?
Thanks
Alan

Have you tried pulling the schema out of the wsdl and putting it in a xsd file and see if it validates?
Otherwise, have you tried removing the xmlns:"" from <WL5G3N0:definitions xmlns:"".
Edited by: C.Stodden on Oct 11, 2012 8:52 AM

Calling a web service from a portal application / SOAP Action

Hallo,
Ich möchte aus einer Portal Applikation auf einen Web Service zugreifen.
Dafür habe ich mit dem Wizard "Portal Service from Wsdl file - Client side"
eine Portal Service erzeugt, auf den ich dann zugreife.
Leider wird dabei ein Fehler ausgegeben (Stacktrace-Ausschnitt s.u.).
Ich habe ein Posting zu dem Fehler hier im SDN gefunden, leider hatte dort niemand eine Antwort. Vielleicht hat inzwischen jemand eine Idee?
Das Feld soapaction ist in der soapconfig.xml leer angegeben (soapaction="").
Es ändert aber nichts an der Fehlermeldung, wenn ich dort etwas eintrage.
Ein weiterer Gedanke ist, dass die soapaction, die wenn ich es richtig verstehe eine URL auf die web service methode enthalten soll, im Grunde dynamisch sein sollte, da der Web Service lokal in dem Portal läuft, auf dem die Applikation gerade deployed ist. Auf den Web Service wird mit WebDynPro erfolgreich zugegriffen (dynamisch). Meine Vermutung ist, dass hier das Problem liegt und es entweder mit diesem Wizard nicht möglich ist oder ein Bug vorliegt.
Also ist die Frage: Wie erzeuge ich dasselbe für eine Portal-Applikation?
Ich hoffe, dass mir jemand mit einer Antwort oder Hinweisen wo man weiterforschen kann, weiterhelfen kann.
Freundliche Grüße,
Daniel Dehnhard
Stacktrace:
Component finished with error: (com.sapportals.portal.prt.service.soap.exception.PRTFaultEnvelopeVersion)
java.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.processParams(PRTSOAPBodyElement.java:253)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.init(PRTSOAPBodyElement.java:190)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.(PRTSOAPBodyElement.java:56)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.init(PRTSOAPBody.java:94)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.(PRTSOAPBody.java:36)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.init(PRTSOAPEnvelope.java:113)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.(PRTSOAPEnvelope.java:54)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.processSOAPMessage(PRTSOAPMessage.java:58)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.(PRTSOAPMessage.java:40)
at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:180)
at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
at de.enviam.ep.egk.km.webservicewrapper.Z_EP_EM_EGK_CustomerGroupToCRMData.getCustomerGroup2CrmDataByGPNr(Z_EP_EM_EGK_CustomerGroupToCRMData.java:218)
at de.enviam.ep.egk.km.imp.EPImpSchedulerTask.resolveGroupId(EPImpSchedulerTask.java:764)

Hi,
I am accessing a web service from a Portal Component through a Portal Web Service. First i created a web service, then a portal web service which is made to access the wsdl file of the web service. Now i access the Portal Web Service from a Portal Component. Now i am getting an error as,
Exceptionjava.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
The code which i wrote in component is below
String text = "word";
FuncHelloResponse res=new FuncHelloResponse();
FuncHello fn= new FuncHello() ;
fn.setName(text);
res= ( (INewPortal) PortalRuntime.getRuntimeResources().getService(INewPortal.KEY)).FuncHello(fn);
response.write(res.getResponse());
Can any one solve this problem?

Call web service from portal/soap config .xml error

Hi all,
I am trying to call a web service from our portal. Setup is as follows:
-Generate proxy classes and deploy it as a portal service
I created this service using the wizard (Portal service from wsdl file client side) in NWDS.
-Portal component which uses the portal service.
When I try to run the application in the portal, I get the following exception:
java.lang.IllegalStateException: Error in soapconfig.xml: The method mail of com.sap.portal.prt.soap.proxy.Alias portal service is not found..
How can I solve this?
Her is my xml file:
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
     <property name="SharingReference" value="com.sap.portal.runtime.application.soap"/>
</application-config>
<components>
    <component name="callwebproxy">
      <component-config>
        <property name="ClassName" value="com.portal.erbS.callwebproxy"/>
      </component-config>
      <component-profile/>
    </component>
    <component name="org_opach">
      <component-config>
        <property name="ClassName" value="com.test.org_opach"/>
      </component-config>
      <component-profile/>
    </component>
</components>
<services>
    <service alias="com.sap.portal.prt.soap.proxy.Alias" name="ProxyClass">
      <service-config>
        <property name="className" value="com.sap.portal.wsdl.webservices.service.connector.ProxyClass">
        </property>
        <property name="startup" value="false"/>
        <property name="WebEnable" value="false"/>
        <property name="Webproxy" value="true"/>
        <property name="SecurityZone" value="com.sap.portal.wsdl.webservices.service.connector/DefaultSecurity"/>
      </service-config>
      <service-profile>
        <property name="SystemAlias" value="Default_system_Alias"/>
      </service-profile>
    </service>
</services>
</application>
reza

Hi,
Check your soapconfig.xml
Your method should be defined there. If it's not there, then you're sure to get this error.
For every method (in Webservice) that you call from your Portal Service, you should have it defined here.
Remember, this is autogenerated.
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <portal-webservices version="6,0,3" application-name="TestWS">
- <portal-webservice name="com.company.mod.TestWS">
- <webservice-method soapaction="" authenticated="false" styleenconding="RPC" javasignature="public abstract byte[] com.company.mod.TestWS.getValue(java.lang.String)" name="getValue">
- <webservice-parameter defaultjavatype="java.lang.String" enconding="encoded" targetnamespace="http://www.w3.org/2001/XMLSchema" nillable="false" xmlattribute="false" required="true" ID="0" name="value">
<webservice-type wsdltype="xsd:string" javatype="java.lang.String" />
</webservice-method>
</portal-webservice>
</portal-webservices>
Regards,
JP

Generate web services form WSDL as part of build process

Hi, I am using Jdev drop7build2.
I have wsdl and schema types. From Jdeveloper we can generate webservices using "web services from WSDL". But I want to generate web services as part of my build process.
Is it possible to do this as part of build process ? any ant tasks or API etc ?
Thanks
-Siva

Arrrgggg
Drop 7 is an Oracle-internal build, as far as I know.
You should be asking on an internal Oracle list.
John

Web Services from WSDL file

Similar Messages

Maybe you are looking for