SOAP 1.2 binding

Hello,
My question: Why BPEL is not using SOAP 1.2 name space "http://www.w3.org/2003/05/soap-envelope", instead its using soap 1.1 "http://schemas.xmlsoap.org/soap/envelope/" ?
I am developing BPEL on 10.1.3.1.
My WSDL file contain
<service name="PMIXRequestService">

<port name="PMIXRequestSOAP12Port"
binding="tns:PMIXRequestSOAP12Binding">
<wsoap12:address location="http://...."/>
</port>
</service>
<binding name="PMIXRequestSOAP12Binding" type="tns:PMIXRequestService">
<wsoap12:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="SendRequest">
<wsoap12:operation soapAction="SendRequest"
soapActionRequired="false"/>
<input>
<wsoap12:body use="literal"/>
</input>
<output>
<wsoap12:body use="literal"/>
</output>
</operation>
</binding>
SOAP envelop look like:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body xmlns:ns1="http://ijis.org/jxdm/3.0.3/PMIX">
<ns1:PMPRequest>
</ns1:PMPRequest>
</soap:Body>
</soap:Envelope>
When I invoke it, I am getting a Null pointer exception. Log entry:
<2007-05-03 09:33:41,705> <DEBUG> <default.collaxa.cube.engine.deployment> <LockManager::release> Released lock for PMIXRequestService-1.0
<2007-05-03 09:34:31,304> <DEBUG> <default.collaxa.cube.ws> SOAPRequestProvider
java.lang.NullPointerException
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProviderHelper.getSOAPAction(SOAPRequestProviderHelper.java:431)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:231)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:129)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
At some point I used to get the following error:
07/05/02 16:46:01 Caused by: oracle.j2ee.ws.saaj.soap.SOAPVersionMismatchRuntimeException: Envelope namespace must be: http://schemas.xmlsoap.org/soap/envelope/ is http://www.w3.org/2003/05/soap-envelope
07/05/02 16:46:01      at oracle.j2ee.ws.saaj.soap.SOAPDoc.createRootElement(SOAPDoc.java:98)
07/05/02 16:46:01      at oracle.j2ee.ws.saaj.soap.SOAPDoc.createNodeFromType(SOAPDoc.java:44)
07/05/02 16:46:01      at oracle.j2ee.ws.saaj.soap.SOAPPartImpl$SOAPPartDocument.createNodeFromType(SOAPPartImpl.java:593)
07/05/02 16:46:01      at oracle.xml.parser.v2.XMLDocument.createElement(XMLDocument.java:2122)
07/05/02 16:46:01      at oracle.xml.parser.v2.DocumentBuilder.startElement(DocumentBuilder.java:262)
07/05/02 16:46:01      at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1288)
07/05/02 16:46:01      at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
07/05/02 16:46:01      at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
07/05/02 16:46:01      at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
07/05/02 16:46:01      at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
07/05/02 16:46:01      ... 57 more
Thanks for your help.
If I use default binding, SOAP 1.1 with name space "http://schemas.xmlsoap.org/soap/envelope/", this works just fine.

Hi Samantha
I believe that this is applicable in XI 3,0 from SP 20.
king regards

Similar Messages

Java.lang.NullPointerException in 8.1 with soap doc literal binding

hi,
scenario:
1) web service with soap doc literal binding on external server. web service
is expecting a complex input argument
2) generate web service control in weblogic 8.1 (sp1) workshop
3) wrote jws file to use the web service control
4) run test and hit the following call stack
NOTE: this is only encountered when the web service is expecting a complex input
argument. if the web service is expecting a simple input argument, it works fine
java.lang.NullPointerException at com.bea.xml.marshal.AtomicValueMPlan.marshal(AtomicValueMPlan.java:90)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:337) at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307) at
com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349) at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307) at
com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349) at com.bea.xml.marshal.MethodMPlan.marshal(MethodMPlan.java:260)
at com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:386)
at com.bea.wlw.runtime.jws.call.SoapCall.<init>(SoapCall.java:150) at com.bea.wlw.runtime.jws.call.SoapHttpCall.<init>(SoapHttpCall.java:61)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:559)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420) at
com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy8.DocLitQueryByExample(Unknown Source) at doc_lit_bs.bs_doc_litControlTest.DocLitQueryByExample(bs_doc_litControlTest.jws:31)
is there a workaround to the problem?

http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.webservices&item=4270
Bolei wrote:
>
hi,
scenario:
1) web service with soap doc literal binding on external server. web service
is expecting a complex input argument
2) generate web service control in weblogic 8.1 (sp1) workshop
3) wrote jws file to use the web service control
4) run test and hit the following call stack
NOTE: this is only encountered when the web service is expecting a complex input
argument. if the web service is expecting a simple input argument, it works fine
java.lang.NullPointerException at com.bea.xml.marshal.AtomicValueMPlan.marshal(AtomicValueMPlan.java:90)
at com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:337) at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307) at
com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349) at com.bea.xml.marshal.MarshalContext.writeElementObjectOrHref(MarshalContext.java:426)
at com.bea.xml.marshal.BaseMPlan.writeValueUsingStrategy(BaseMPlan.java:307) at
com.bea.xml.marshal.BaseMPlan.marshal(BaseMPlan.java:349) at com.bea.xml.marshal.MethodMPlan.marshal(MethodMPlan.java:260)
at com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:386)
at com.bea.wlw.runtime.jws.call.SoapCall.<init>(SoapCall.java:150) at com.bea.wlw.runtime.jws.call.SoapHttpCall.<init>(SoapHttpCall.java:61)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:559)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:359)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:420) at
com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:393) at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:387)
at $Proxy8.DocLitQueryByExample(Unknown Source) at doc_lit_bs.bs_doc_litControlTest.DocLitQueryByExample(bs_doc_litControlTest.jws:31)
is there a workaround to the problem?

SOAP over JMS binding

Hi Experts,
Is it possible to expose as a SOAP over JMS binding webservice from XI (from SAP platform)?
Regards
Sara

I have similar situation.
R/3->XI->java message server
XI and message server exchange SOAP envelope using JMS. (SOAP over JMS)
XI posts SOAP message in queue & in inbound case would pickup SOAP message from JMS queue.
My question: When using a SOAP adapter, it does work of stripping SOAP envelope/ header? Do we need to handle it in xslt when a message is picked up from external message queue(from message server)? In other words how to handle SOAP message in inbound case?
Thanks,
sachin
PS: Points will be awarded for useful answer

WSDL / SOAP http get binding

Hello,
i am looking for information regarding HTTP Get binding for SOAP. I have looked at the wsdl 1.1 specification which provides some information concerning that binding (http://www.w3.org/TR/wsdl#_http) and also in SOAP 1.2 (http://www.w3.org/TR/soap12-part0/#L26854). However all this is not precise enough.
In particular, i am wondering whether the serialization of SOAP request (from its definition in a wsdl) using http get is clearly formalized somewhere (in a specification). If any, what are the limitations and constraints, for instance, does it support complex types defined in the WSDL. Are there implementations currently available?
Thanks,
Cyrille

Hello,
Which kind of Web Services are you building in JDeveloper?
- JAX-RPC (J2EE 1.4)
- Oracle Web Service stack (J2EE 1.3)
What is your targetted environment?
Oracle does not support Document style Web Services in Oracle Web Service stack (J2EE 1.3), it has to be done programmatically.
However the JAX-RPC stack does support, and it is the default, Document style Web Services and you can right click on the Web Service node to edit the service.
Regards
Tugdual Grall

Web reference WSDL not conforming to SOAP standard

I built a web service based on the BAPI_FLIGHT_GETLIST function module using the "create web service" wizard. The generated web service endpoint is active in SOAMANAGER transaction.
When I try to generate a proxy class in Visual Studio 2005 using the "Add web reference" tool the service method is shown as expected in the preview window. However, when I click the "Add Reference" button I get the following error message:
Custom tool warning: DiscoCodeGenerator unable to initialize code generator.
No code generated.
The Solution Explorer window shows the Web Reference object generated with components Reference.map, Reference.cs and a WSDL file; however the Reference.cs proxy class has no code in it and there are no objects for the method parameters.
When running the WSDL.exe program from the command line, the following error message is generated:
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Warning: This web reference does not conform to WS-I Basic Profile v1.1.
SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementation guidelines that recommend how a set of core Web services specifications should be used together to develop interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
For more details on the WS-I Basic Profile v1.1, see the specification at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
Warning: no classes were generated.
Warnings were encountered. Review generated source comments for more details.
I've seen several documents that step through this process that work fine. Has anyone seen this issue before and found a solution?
I'm running NW2004s with SP14 on Windows Server 2003 R2. Clients are VS2005 on both XP & Vista - same result on both client environments.
Thanks,
Dorian.

Hi,
I'm not familiar with the tools you described to create the Web Service aboved SAP BAPI's, but i have 2 ideas which you can start with.
I am part of the team developed the "ESE for .NET" and on the last step of our tool we are using VS API to "Add Web Reference".
We have noticed 2 ocaasions that might interest you:
1. Can you please verify that the WSDL contains the "wsdl:binding" part ?
   according to the error message you described you are missing the binding part.
   As you know WSDL of .NET Web Service combined of 5 major sections: "wsdl:types, "wsdl:message, "wsdl:portType, "wsdl:binding" & "wsdl:service".
   .NET proxy generation can't be executed on a WSDL based on a Service Definition only, it must have the "wsdl:binding" part which always comes only with
   the End Points WSDL from SAP services.
2. Can you send me the WSDL file by email ? [email protected]
3. Another important issue for Runtime of the Services - SAP Web Service schema is a little different than MS schema, you should look for "parameters" inside the WSDL and change it to "paramter".
Hope this information will help you,
Nadav

OBPM BPM Studio support for SOAP 1.2 based Proxy services (OSB)

Hi,
I tried to import proxy services from OSB (as external resource). The proxy service is based on the SOAP 1.2 WSDL standard. When BPM studio introspective SOAP1.2 based proxy services, it is givng the following warninigs. Bacause of this i am unable to create a service object. Please help.
Regards,
Pandu
Introspecting...
downloading /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
parsing /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
[Warning] unknown tag 'header' from 'http://schemas.xmlsoap.org/wsdl/soap12/'.
[Warning] unknown tag 'header' from 'http://schemas.xmlsoap.org/wsdl/soap12/'.
checking /sbresource?PROXY/RoutingAndMessagingService/proxy/OnRampService
parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlmessages%2Futilityservices%2Froutingandmessagingservice%2FRoute
analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlmessages%2Futilityservices%2Froutingandmessagingservice%2FRoute
parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlheaders%2FHeaderSchema
analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdlheaders%2FHeaderSchema
parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FHeaderTypes
analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FHeaderTypes
parsing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FSimpleTypes
analyzing http://localhost:7002/sbresource?PROXY%2FRoutingAndMessagingService%2Fproxy%2FOnRampService%3ASCHEMA%2FSchemas%2Finternal%2Fwsdltypes%2Fcommon%2FSimpleTypes
http://www.michaelpage.com/wsdltypes/common/SimpleTypesv1.0 compiled
http://www.michaelpage.com/wsdltypes/common/HeaderTypesv1.0 compiled
http://www.michaelpage.com/wsdlheaders/Headerv1.0 compiled
http://www.michaelpage.com/wsdlmessages/utilityservices/Routev1.0 compiled
[Warning] The binding 'OnRampServiceSOAP' with type 's2:OnRampServicePort'is unsupported. Components will not be generaded for this binding..
'http://www.michaelpage.com/wsdl/utilityservices/routingandmessagingservice/OnRampServicev1.0/' was parsed.
Analyzing dependecies for module 'WS.OnRampService'...
Analyzing dependecies for module 'WS.OnRampService'...
Analyzing Components
Storing Instrospected Types
Introspection completed. Errors: 0, Warnings: 3.

Pandu,
OBPM 10g doesn't support SOAP 1.2 binding.
Edited by: 4dyomi on Nov 20, 2009 11:41 AM
Edited by: 4dyomi on Nov 20, 2009 11:42 AM

Is my webservise supporting SOAP 1.2

With JDeveloper 10.1.3.4.0
- created a class with name MyClass
- I created a webservice with name MyWebService as:
- J2EE 1.4 (JAX-RPC) Web Service
- Published the MyClass component with a HelloWorls method
- Checked the “Autogenerate Service Endpoint Interface”
- Checked the” SOAP 1.2 Binding”
- SOAP Message Format: Document/Wraped
- Checked the “Enabel REST Access to SOAP Ports”
- Checked the “Generate Schema with Qualified Elemnts”
A client of my WS that is calling my WS from a .NET client is telling me that my WS is not supporting SOAP 1.2, My oc4j is also reporting the error :
oracle.j2ee.ws.common.soap.fault.SOAP11VersionMismatchException: Version Mismatch.
My .NET customer have seen my “oracle-webservice.xml” and the wsdl file and tell me that we are using wrong “SOAP envelope” schema “http://schemas.xmlsoap.org/soap/envelope/”. The right one should be : http://www.w3.org/2003/05/soap-envelope/
What is this? I did check the “SOAP 1.2 Binding” when generating my WS, what more is it to do, to create a WS with SOAP 1.2 with JDeveloper?
Thanks
Per Jørgen Vigdal

Well, that link is for the late-2011 model, the OP has an early-2011 model.
Look here for detailed info on his computer:
http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.0- 15-early-2011-unibody-thunderbolt-specs.html
However the answer is the same, you have SATA3 in the main bay.
The problems are in the optical bay, as your motherboard supports sata3 also for it, but the cable and shielding are not good enough for SATA3 speed. So, if you place a SATA3 SSD in the optical bay, it is going to perform erratically.
No problems instead placing your original HD in the optical bay, as it is a SATA2 disk.
The only mechanical HD featuring a SATA3 interface are the newest hybrid drives from Seagate, size 750 Gb and up. These cannot be mounted in the optical bay...

Soap 1.2 in NetBeans 6.1

I have a BPEL process (NetBeans 6.1 CAPS) calling a Visual Studio 2008 web service. It's a simple string in, string out scenario.
There are a few posts on the web that claim to consume .net web service from BPEL using the most recent binding components from OpenESB.
I downloaded the most recent version but still have an issue where the CASA project detects 2 ports. It appears the .Net WSDL creates two ports for each operations, standard soap and soap 1.2.
Any idea what version of the SOAP/HTTP binding component supports Soap 1.2 binding in JBI?
Thanks
(Cross post form CAPS forums - it's probably better suited here)

Posting question to "[email protected]" would get quick response
You need to special version, the instalation you have should suffice.
Composite Application build (CASA editor) connects ports automatically only if there is only one consumer and one provider for given WSDL port type. In your scenario there are two, so there is ambiguity. So it would fail with WARNING.
If you navigate to "Service Assembly" node under Composite Application and double click it opens CASA editor. You would notice BPEL partner link is not connected to SOAP endpoint. You need to connect manually, save it and build the project.
If you deploy the SA this time and run the project it should work fine.
If this is not the case please file an issue at https://open-esb.dev.java.net/servlets/ProjectIssues

OSB: Soap 1.1 and Soap 1.2

Hello i am tasked with a wsdl file that contains two port types one with soap 1.1 and the other with soap 1.2
Now I need both the soap 1.1 and soap 1.2 to be available to the end user
however in osb when creating the proxy service i am forced to choose either hte soap 1.1 binding or the soap 1.2 binding... will i have to create two separate proxy services for each or is there a way to have it where one proxy service can support both soap types?

How come a SOAP 1.2 request can go through the whole flow even though the local PS and provider BS I chose the SOAP 1.1 ports?Make your PS_3 as Any XML Service proxy service and the select Local Transport.
come a SOAP 1.2 request can go through the whole flow even though the local PS and provider BS I chose the SOAP 1.1 ports?Your PS_3 can accept both SOAP1.1 and SOAP1.2 as it's based on Any XML service.
Regards,
Abhinav

Flex sending corrupt SOAP request

I've created a PHP5 SOAP webservice and am trying to call a
method from flex. I get a fault from the Flex app that says
faultString="HTTP request error"
faultCode="Server.Error.Request"
The SOAP request received by the server is as follows (which
I think explains why the server responded with an error):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body/>
</SOAP-ENV:Envelope>
It is missing all the body parameters. What could cause an
empty request like this?
The relevant AS:
public var _webServiceLoaded:Boolean = false; // flag noting
when wsdl has been loaded
public var _myService:WebService = new WebService();
public function initWS():void {
_myService.wsdl = "
http://foreignserver.com/seminar_service.wsdl";
_myService.loadWSDL();
_myService.echoArgs.addEventListener("result",
echoResultHandler);
_myService.addEventListener("fault", faultHandler);
_myService.addEventListener('load',WSLoad);
public function send_attendee_email():void {
_myService.echoo("qwerty"); // should just return the same
string we send; echoo spelled with extra o
And my wsdl:
<?xml version="1.0"?>
<definitions
xmlns="
http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:tns="
http://foreignserver.com/seminar_service.php"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/"
xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/"
targetNamespace="
http://foreignserver.com/seminar_service.php">
<message name="echooInput">
<part name="echo" type="xsd:string"/>
</message>
<message name="send_attendee_emailInput">
<part name="sem_date" type="xsd:string"/>
<part name="sem_first" type="xsd:string"/>
<part name="sem_last" type="xsd:string"/>
<part name="sem_title" type="xsd:string"/>
<part name="sem_company" type="xsd:string"/>
<part name="sem_phone" type="xsd:string"/>
<part name="sem_email" type="xsd:string"/>
<part name="pdf_filename" type="xsd:string"/>
</message>
<message name="echooOutput">
<part name="return" type="xsd:string"/>
</message>
<message name="send_attendee_emailOutput">
<part name="return" type="xsd:string"/>
</message>
<portType name="seminarPortType">
<operation name="echoo">
<input message="tns:echooInput"/>
<output message="tns:echooOutput"/>
</operation>
<operation name="send_attendee_email">
<input message="tns:send_attendee_emailInput"/>
<output message="tns:send_attendee_emailOutput"/>
</operation>
</portType>
<binding name="seminarBinding"
type="tns:seminarPortType">
<soap:binding xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
style="rpc" transport="
http://schemas.xmlsoap.org/soap/http"/>
<operation xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="echoo">
<input xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
<operation xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="send_attendee_email">
<input xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/">
<soap:body xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
use="encoded" encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="seminarService">
<port xmlns:default="
http://schemas.xmlsoap.org/wsdl/soap/"
name="seminarPort" binding="tns:seminarBinding">
<soap:address xmlns="
http://schemas.xmlsoap.org/wsdl/soap/"
location="
http://foreignserver.com/seminar_service.php"/>
</port>
</service>
</definitions>

This behavior (empty SOAP request sent to server) stemmed
somehow from my wsdl file. I'm uncertain what the specific problem
was, but when I rebuilt the wsdl from scratch using a different
model, the SOAP request from Flex was properly formed.

Does Flex Builder 3 have support for Soap 1.2?

Does Flex Builder 3 Data Services support Soap 1.2?
I'm using Flex Builder v3.0.205647. I'm trying to import a
Web Service (WSDL) through the Data Services...but I'm seeing that
Soap 1.2 is not supported (only Soap 1.1). Are there any plug-ins
and/or updates that would allow me to connect to a Soap 1.2
service? If not, is this planned for the future?
Thanks!

Pandu,
OBPM 10g doesn't support SOAP 1.2 binding.
Edited by: 4dyomi on Nov 20, 2009 11:41 AM
Edited by: 4dyomi on Nov 20, 2009 11:42 AM

Problem to generate classes from a gsoap server's wsdl with wsimport

Hello,
I trie for a long time to generate my client classes from a wsdl file with wsimport. The wsdl file was generated by gsoap.
Here, the wsdl file :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="form"
targetNamespace="https://enterprise-name-masked.com/form.wsdl"
xmlns:tns="https://enterprise-name-masked.com/form.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="generic"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/2004/08/xop/include"/>
<import namespace="http://www.w3.org/2004/11/xmlmime"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>
<simpleType name="service">
   <restriction base="xsd:string">
    <enumeration value="service-none"/>
    <enumeration value="service-ident"/>
    <enumeration value="service-pool"/>
    <enumeration value="service-hwr"/>
    <enumeration value="service-form"/>
    <enumeration value="service-document"/>
   </restriction>
</simpleType>
<simpleType name="result-code">
   <restriction base="xsd:string">
    <enumeration value="ok"/>
    <enumeration value="already-exists"/>
    <enumeration value="not-found"/>
    <enumeration value="cant-connect"/>
    <enumeration value="exception"/>
    <enumeration value="bad-conversion"/>
    <enumeration value="bad-values"/>
    <enumeration value="session-not-found"/>
    <enumeration value="initialization-failed"/>
   </restriction>
</simpleType>
<complexType name="result">
   <sequence>
     <element name="code" type="generic:result-code" minOccurs="1" maxOccurs="1"/>
     <element name="details" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
</schema>
<schema targetNamespace="form"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/2004/08/xop/include"/>
<import namespace="http://www.w3.org/2004/11/xmlmime"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>
<simpleType name="area-type">
   <restriction base="xsd:string">
    <enumeration value="area-type-text"/>
    <enumeration value="area-type-numeric"/>
    <enumeration value="area-type-date"/>
    <enumeration value="area-type-checkbox"/>
    <enumeration value="area-type-slider"/>
    <enumeration value="area-type-draw"/>
    <enumeration value="area-type-identifier"/>
   </restriction>
</simpleType>
<simpleType name="format">
   <restriction base="xsd:string">
    <enumeration value="A5"/>
    <enumeration value="A4"/>
    <enumeration value="A3"/>
    <enumeration value="A2"/>
    <enumeration value="A1"/>
    <enumeration value="A0"/>
   </restriction>
</simpleType>
<complexType name="area">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="x" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="y" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="width" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="height" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="comments" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="area-type" type="form:area-type" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-string">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="string" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-integer">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="integer" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-range">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="lower" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="upper" type="xsd:double" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="areas">
   <sequence>
     <element name="areas" type="form:area" minOccurs="0" maxOccurs="unbounded"/>
     <element name="string-areas" type="form:area-with-string" minOccurs="0" maxOccurs="unbounded"/>
     <element name="integer-areas" type="form:area-with-integer" minOccurs="0" maxOccurs="unbounded"/>
     <element name="range-areas" type="form:area-with-range" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="group">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="areas" type="form:areas" minOccurs="1" maxOccurs="1"/>
     <element name="groups" type="form:group" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="background">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="md5" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="mime" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="num-page" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="pattern-type">
   <sequence>
     <element name="print-once" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
     <element name="has-identifier" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="page">
   <sequence>
     <element name="num-page" type="xsd:int" minOccurs="1" maxOccurs="1"/>
     <element name="format" type="form:format" minOccurs="1" maxOccurs="1"/>
     <element name="is-portrait" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
     <element name="background" type="form:background" minOccurs="1" maxOccurs="1"/>
     <element name="areas" type="form:areas" minOccurs="1" maxOccurs="1"/>
     <element name="groups" type="form:group" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document-new">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="pattern-type" type="form:pattern-type" minOccurs="1" maxOccurs="1"/>
     <element name="form-pages" type="form:page" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document">
   <sequence>
     <element name="uuid" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="pattern-type" type="form:pattern-type" minOccurs="1" maxOccurs="1"/>
     <element name="form-pages" type="form:page" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document-info">
   <sequence>
     <element name="uuid" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="page-count" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="Data">
   <sequence>
     <element ref="xop:Include" minOccurs="1" maxOccurs="1"/>
   </sequence>
     <attribute ref="xmime4:contentType" use="optional"/>
</complexType>
<complexType name="login-response">
   <sequence>
     <element name="result" type="generic:result" minOccurs="1" maxOccurs="1"/>
     <element name="session" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>

<element name="login" type="xsd:string"/>

<element name="password" type="xsd:string"/>

<element name="result" type="generic:result"/>

<element name="uuid" type="xsd:string"/>

<element name="session" type="xsd:string"/>

<element name="aform" type="form:document-new"/>

<element name="form" type="form:document"/>

<element name="md5" type="xsd:string"/>

<element name="data" type="form:Data"/>

<element name="exists" type="xsd:boolean"/>

<element name="backgrounds" type="form:background"/>

<element name="forms" type="form:document"/>

<element name="forms-info" type="form:document-info"/>
</schema>
</types>
<message name="login">
<part name="login" element="form:login"/>
<part name="password" element="form:password"/>
</message>
<message name="uuid-response">
<part name="result" element="form:result"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="quit">
<part name="session" element="form:session"/>
</message>
<message name="response">
<part name="result" element="form:result"/>
</message>
<message name="new-form">
<part name="session" element="form:session"/>
<part name="aform" element="form:aform"/>
</message>
<message name="free-form">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="get-form">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="document-response">
<part name="result" element="form:result"/>
<part name="form" element="form:form"/>
</message>
<message name="get-file">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
</message>
<message name="data-response">
<part name="result" element="form:result"/>
<part name="data" element="form:data"/>
</message>
<message name="set-file">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
<part name="data" element="form:data"/>
</message>
<message name="file-exists">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
</message>
<message name="exists-response">
<part name="result" element="form:result"/>
<part name="exists" element="form:exists"/>
</message>
<message name="list-form-backgrounds">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="list-backgrounds-response">
<part name="result" element="form:result"/>
<part name="backgrounds" element="form:backgrounds"/>
</message>
<message name="list-forms">
<part name="session" element="form:session"/>
</message>
<message name="list-forms-response">
<part name="result" element="form:result"/>
<part name="forms" element="form:forms"/>
</message>
<message name="list-forms-info">
<part name="session" element="form:session"/>
</message>
<message name="list-forms-info-response">
<part name="result" element="form:result"/>
<part name="forms-info" element="form:forms-info"/>
</message>
<portType name="formPortType">
<operation name="login">
<documentation>Service definition of function form__login</documentation>
<input message="tns:login"/>
<output message="tns:uuid-response"/>
</operation>
<operation name="quit">
<documentation>Service definition of function form__quit</documentation>
<input message="tns:quit"/>
<output message="tns:response"/>
</operation>
<operation name="new-form">
<documentation>Service definition of function form__new_form</documentation>
<input message="tns:new-form"/>
<output message="tns:uuid-response"/>
</operation>
<operation name="free-form">
<documentation>Service definition of function form__free_form</documentation>
<input message="tns:free-form"/>
<output message="tns:response"/>
</operation>
<operation name="get-form">
<documentation>Service definition of function form__get_form</documentation>
<input message="tns:get-form"/>
<output message="tns:document-response"/>
</operation>
<operation name="get-file">
<documentation>Service definition of function form__get_file</documentation>
<input message="tns:get-file"/>
<output message="tns:data-response"/>
</operation>
<operation name="set-file">
<documentation>Service definition of function form__set_file</documentation>
<input message="tns:set-file"/>
<output message="tns:response"/>
</operation>
<operation name="file-exists">
<documentation>Service definition of function form__file_exists</documentation>
<input message="tns:file-exists"/>
<output message="tns:exists-response"/>
</operation>
<operation name="list-form-backgrounds">
<documentation>Service definition of function form__list_form_backgrounds</documentation>
<input message="tns:list-form-backgrounds"/>
<output message="tns:list-backgrounds-response"/>
</operation>
<operation name="list-forms">
<documentation>Service definition of function form__list_forms</documentation>
<input message="tns:list-forms"/>
<output message="tns:list-forms-response"/>
</operation>
<operation name="list-forms-info">
<documentation>Service definition of function form__list_forms_info</documentation>
<input message="tns:list-forms-info"/>
<output message="tns:list-forms-info-response"/>
</operation>
</portType>
<binding name="form" type="tns:formPortType">
<SOAP:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="login">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="quit">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="new-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="free-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="get-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="get-file">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="set-file">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="file-exists">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-form-backgrounds">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-forms">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-forms-info">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
</binding>
<service name="form">
<documentation>gSOAP 2.7.10 generated service definition</documentation>
<port name="form" binding="tns:form">
<SOAP:address location="https://enterprise-name-masked.com/cgi-bin/form.fcgi"/>
</port>
</service>
</definitions>And here, you can find the generated errors :
wsimport -s Sources -b http://www.w3.org/2004/08/xop/includ
e -b http://www.w3.org/2004/11/xmlmime form.wsdl
parsing WSDL...
[WARNING] src-resolve: Cannot resolve the name 'xmime4:contentType' to a(n) 'attribute declaration' component.
line 215 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] s4s-elt-invalid-content.1: The content of 'Data' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.
line 215 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] src-resolve.4.2: Error resolving component 'generic:result'. It was detected that 'generic:result' is in namespace 'generic', but components
from this namespace are not referenceable from schema document 'file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP
/WSImport/Test/Form/form.wsdl#types?schema2'. If this is the incorrect namespace, perhaps the prefix of 'generic:result' needs to be changed. If this
is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Re
cherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2'.
line 230 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] src-resolve: Cannot resolve the name 'xop:Include' to a(n) 'element declaration' component.
line 213 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] Ignoring SOAP port "form": it uses non-standard SOAP 1.2 binding.
You must specify the "-extension" option to use this binding.
line 533 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl
[WARNING] Service "form" does not contain any usable ports. try running wsimport with -extension switch.
line 531 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl
generating code...
compiling code...Could you tell me how to correctly generate my classes in this case ?
Thank you.
Edited by: morphet on May 30, 2008 6:12 AM

Alchemista,
Not sure if you were able to solve your problem..but I was trying to do exactly what you were trying to do.. access a datasource from a simple Java client. However, you cannot do so by simply writing the Java class and running it. The simple Java client has to be deployed as a J2EE Application Client. The following tutorial shows how to create a J2EE Application Client using the non-J2EE Java class you have written.
http://developer.java.sun.com/developer/technicalArticles/J2EE/appclient
The article talks about accessing EJBs from a J2EE App. Client.. but since you only want to access the DataSource, just skip all the screens until it asks you to register the JNDI DataSource resources...
Let me know if you have any questions. You can email me at [email protected]
I hope this helps.

WSIF calling EJB 3.0 beans, with JAXB 2.0.2 as the JavaSerializer

I'm working with SOA suite (10.1.3.1.0 [build #0 ]), and I am trying to allow my BPEL processes to call my EJB 3.0 stateless session beans via WSIF.
This works fine when I am passing primitives (strings, dates and so-forth) between BPEL and my EJB's using WSIF.
However I want to be able to pass my 'business objects" across the BPEL/EJB boundary directly. I started off by following the BPEL cookbook article "Using WSIF for Integration" which was usefull in showing how to use JAXB 1.x generated classes across the BPEL/EJB boundary.
However in the project I am working on we want to use JAXB 2.0 as it allows us to create an XML schmea binding directly from our existing "business objects".
So I am using the knowlege gained in the article mentioned above to implement a custom JavaSerializer for my bpel process that will use JAXB 2.0. My custom JavaSerilizer is being invoked correctly, when I invoke my BPEL process, but it is unable to load the correct JAXB (2.0.2) classes - it keeps getting the JAXB 1.0 classes that come standard with oracle.
My debug code that prints out the classloaders for my serializers (and parent classloaders) reports the following:
06/09/05 11:18:18 CustomSerializer.serialize
06/09/05 11:18:18 Classloader =oracle.bpel.common:10.1.3
06/09/05 11:18:18 Classloader =api:1.4.0
06/09/05 11:18:18 Classloader =jre.extension:0.0.0
06/09/05 11:18:18 Classloader =jre.bootstrap:1.5.0_06
The Jaxb classes it is loading a coming from classloader:
06/09/05 11:18:18 JAXBContext classloader =oracle.xml:10.1.0_2
My question is how do I get the JAXB 2.0 classes in my classpath?
Thanks,
Dave Oram

Hello,
About WSIF, we are currently working on a WSIF-EJB30 binding that will allow you to direclty annotate the session ben and get the EJB exposed as SOAP and WSIF binding out of the box.
This will be available in OracleAS 10.1.3.1 production.
Regards
Tugdual Grall

PL/SQL Web Service porblem with parameters

Hi,
I'm pretty new to this so I apologise in advance if this is just something I'm doing wrong, but I'm really struggling to understand what's going wrong (and I could find any threads suggesting any one else was having the same problem.
I am using jdeveloper version 10.1.3.3 and am trying to create a web service from a pl/sql package. The problem occurs when I have more than 1 input parameter and I get the following message in the 'Web Services' tab :-
Generating WSDL and mapping file
WARNING: OWS-00037 No method found in SEI: esab_dev_tf_geo_appl.Ws
WSDL and mapping file generation failed for the following reason:
Interface esab_dev_tf_geo_appl.Ws: Invalid Method
Method public abstract esab_dev_tf_geo_appl.WsUser_add_Out esab_dev_tf_geo_appl.Ws.add(java.lang.Integer,java.lang.Integer) throws java.rmi.RemoteException: BARE mode is not supported for zero or multiple non-SOAPHeader parameter
This did work yesterday morning and I had a web service that actually worked, but in making some minor changes to the pl/sql package and trying to re-generate the web service it now fails every time. Any ideas?
This is a basic package spec. that fails:
create or replace
PACKAGE SL_TEST AS
PROCEDURE ADD
No_1 IN INTEGER,
No_2 IN INTEGER,
No_3 OUT INTEGER,
No_4 OUT VARCHAR2
end sl_test;
I should have mentioned, the options I had selected were as follows:-
J2EE 1.4 (JPAX-RPC) Web Service
SOAP 1.1 Binding
SOAP 1.2 Binding
Document/Literal
Generate Schema with Qualified Elements
Thanks.
Shaun.
Message was edited by:
user625274

Shaun,
I was able to reproduce your problem.
It goes away if you choose RPC/Literal instead of Document/Literal.
I'm not a WS guru by any means - perhaps someone else can comment on why this happens?
John

Missing Port Information - HELP!

Hi, i built a dynamic client to work with my webservice. Both were built using the JWSP1.2. Bellow is the error i get. It happens only if i call the getAll WS method (this method receives a String parameter and returns a Source Type Object) . Does anyone have any idea about what's happening? Could someone show me the way? Really appreciate
[java] WSDLstring = http://localhost:8080/cm/ContextManager?WSDL
[java] java.rmi.ServerException: Missing port information
[java] at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:382)
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:234)
[java] at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:64)
[java] at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:346)
[java] at com.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:102)
[java] at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:74)
[java] at $Proxy0.getAll(Unknown Source)
[java] at contextclient.CMClient.getConnection(Unknown Source)
[java] at contextclient.CMClient.main(Unknown Source)
Tks in advance,
Rodrigo.

The WSDL code is right here. It was generated by the ant builder wich follows the JWSDP 1.2
<definitions xmlns:tns="http://localhost:8080/cm/ContextManager" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns2="http://java.sun.com/jax-rpc-ri/internal" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://localhost:8080/cm/ContextManager" name="ContextManager">
     <types>
          <schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal" xmlns:tns="http://java.sun.com/jax-rpc-ri/internal" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <simpleType name="text_xml">
                    <restriction base="string"/>
               </simpleType>
          </schema>
     </types>
     <message name="ContextManagerIF_getAll">
          <part name="String_1" type="xsd:string"/>
     </message>
     <message name="ContextManagerIF_getAllResponse">
          <part name="result" type="ns2:text_xml"/>
     </message>
     <message name="ContextManagerIF_getFullDOM">
          <part name="Source_1" type="ns2:text_xml"/>
     </message>
     <message name="ContextManagerIF_getFullDOMResponse">
          <part name="result" type="ns2:text_xml"/>
     </message>
     <message name="ContextManagerIF_teste">
          <part name="String_1" type="xsd:string"/>
     </message>
     <message name="ContextManagerIF_testeResponse">
          <part name="result" type="ns2:text_xml"/>
     </message>
     <portType name="ContextManagerIF">
          <operation name="getAll" parameterOrder="String_1">
               <input message="tns:ContextManagerIF_getAll"/>
               <output message="tns:ContextManagerIF_getAllResponse"/>
          </operation>
          <operation name="getFullDOM" parameterOrder="Source_1">
               <input message="tns:ContextManagerIF_getFullDOM"/>
               <output message="tns:ContextManagerIF_getFullDOMResponse"/>
          </operation>
          <operation name="teste" parameterOrder="String_1">
               <input message="tns:ContextManagerIF_teste"/>
               <output message="tns:ContextManagerIF_testeResponse"/>
          </operation>
     </portType>
     <binding name="ContextManagerIFBinding" type="tns:ContextManagerIF">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="getAll">
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </output>
               <soap:operation/>
          </operation>
          <operation name="getFullDOM">
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </output>
               <soap:operation/>
          </operation>
          <operation name="teste">
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/cm/ContextManager"/>
               </output>
               <soap:operation/>
          </operation>
     </binding>
     <service name="ContextManager">
          <port name="ContextManagerIFPort" binding="tns:ContextManagerIFBinding">
               <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
          </port>
     </service>
</definitions>
Regards,
Rodrigo.

SOAP 1.2 binding

Similar Messages

Maybe you are looking for