Soap Service Registration Problem

When i try to register the sample helloWorld soap application i get the following problem...
install_service:
Copying SOAP service classes to d:\iplanet\ias6\ias/APPS/soap-services/samples/s
oap/helloworld.
Registering SOAP service with Apache SOAP container.
[java] Ouch, the call failed:
[java] Fault Code = SOAP-ENV:Server.Exception:
[java] Fault String = try to access method org.apache.soap.server.http.Se
rverHTTPUtils.readEnvelopeFromRequest(Ljavax/xml/parsers/DocumentBuilder;Ljava/l
ang/String;ILjava/io/InputStream;Lorg/apache/soap/transport/EnvelopeEditor;Ljava
x/servlet/http/HttpServletResponse;Lorg/apache/soap/rpc/SOAPContext;)Lorg/apache
/soap/Envelope; from class org.apache.soap.server.http.RPCRouterServlet
Iam using iAS6.5, xerces 1.4.3, soap2.2.
Advacnced thanks for your help

Hi,
Did you solve this problem?
I'm also trying to get Soap 2.2 working in iAS 6.5.
I've no trouble installing soap, and I can deploy a sample
soap service, but I have not been able to call the
service... seems the soap server cannot find the implementing
class when receiving the rpcRouter request. I've tried just about
everything except packaging the sample code into the soap.jar
file... which I assume would work.
all this tested just fine against soap in tomcat

Similar Messages

Web service registration problem

Hi,
I must use a web service in MII transaction.
There is no problem about registration of web service In Ms-VisualStudio.Net environment , But problem in MII.
After registration in VS.Net there is generated an .xsd file near .wsdl file.
Is the problem with .xsd file MII can not bring it?
Thanks.

I inserted .xsd into .wsdl

Problem in service registration?

Hi all.
I created two midlets: one for a server and one for a client
My midlet works very well on WTK: client find devices and find the service. so the client can connect to the server and i can send some messages to the server.
But I have a problem in real test on Nokia 6630 and Nokia Communicator too.
I think service Registration doesn't work. Clients find devices but they don't find the service on the server. I don't understand: midlet works well on WTK and doesn't work on real devices!
Have you any idea?

I inserted .xsd into .wsdl

Unable to change ESB Soap Service endpoint

Hi people , i have a problem,
after creating a soap service , register de esb service on DefaultSystem, i want to call externally using
"http://host:port/esb/wsil/DefaultSystem/<name of soap service>?wsdl
everithing works ok , but when i try to change from Jdeveloper the enpoint URL , ESB seems to keep using the old URL in :
http://host:port/event/DefaultSystem/<name of soap service>?WSDL ..
If i check on esb control i can se the new "WSDL URL" on the Definition tab of this soap service. But internally in the WSDL generated by the ESB endpoint it keeps using the OLD URL
causing obviously a:
"SOAPException: Message send failed: Connection refused"
if i make that resource unavailable after the change
The question is .. why i cant change the endpoint url ????
theres is any WSDL cache or something like in Oracle BPEL PM ??
i need to restart (i dont try yet )
please ill wait for any suggestions
PS: im using ESB 10.1.3.3.0 Build:PCBPEL_10.1.3.3.0_GENERIC_070615.0525

Hi
I have similar problems and nobody seems to know the solution. Changing the virtual host and port in ESB console does not resolve the problem thoroughly. It's changing the end point entry but living the namespace URL of the WSDL with old value, for instance my address was: http://localhost.localdomain:8889/ .....servicename?WSDL.
This prevents it from proper invoking by external clients, you can reach the end point and use the test page but you can't read its wsdl file without adjusting its address by hand.
I found one solution, it's reinstalling the OAS from scratch and pass the proper name of the server when prompted but what the kind of solution is that? This is obviously deployment problem, the original wsdl file prepared in JDeveloper is used to generate the final wsdl file exposed to external clients but which is the configuration file responsible for that and why the esb console don't change the namespace url too while changing end point?
This is the bug indeed because it's impossible to resolve from console level.

Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

hello colleagues,
In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
Error,
Connect Diagnostics Agent
The table does not contain any data
Agent availables in all SLD
SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
Thanks

OK, then pls follow below steps;
- Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
- Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
- If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
Let me know the results.
Regards,
Vivek

SOAP wdsl generation problem j developer

hi im having a problem with wsdl file generated from jdeveloper.
I expose a pl/sql function as a web service. I can then conect to the soap url with a web browser and sucessfull publish data to the db from this , but if i take the wsdl file from jdeveloper in to a soap test client (magoo) i get an error, on anything that trys to post data back to the DB ???
the error is
No Deserializer found to deserialize a ':emp' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
im not using BPEL (which i know has some soap problems)
THIS IS THE SOAP MESSAGE THE WSDL FILE GENERATES
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:m='MyWebService-v9' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:ns1='http://oadev11/Company.xsd' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
<soapenv:Body soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
<m:addemp>
<emp>
<eid xsi:type='xsd:int'>7</eid>
<efirstname xsi:type='xsd:string'>mr</efirstname>
<elastname xsi:type='xsd:string'>magoo</elastname>
<addr>
<street xsi:type='xsd:string'>granby grove</street>
<city xsi:type='xsd:string'>southampton</city>
<state xsi:type='xsd:string'>uk</state>
<zip xsi:type='xsd:string'>so</zip>
</addr>
<salary xsi:type='xsd:double'>1000</salary>
</emp>
</m:addemp>
</soapenv:Body>
</soapenv:Envelope>
this returns an error,
No Deserializer found to deserialize a ':emp' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
ive tested the client with the googlesearchapi wsdl file, so the client is working ok, I think there might be a problem with the wsdl file generation. can anyone sugest what this might be?
conecting directly to the soap service url and submitting xml suggested by the interface, adds the entry to the databse and works fine
<emp xmlns:ns1="http://oadev11/Company.xsd"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:oadev11_EmployeeUser">
<eid xsi:type="xsd:int">7</eid>
<efirstname xsi:type="xsd:string">MR</efirstname>
<elastname xsi:type="xsd:string">MAGGO</elastname>
<addr xsi:type="ns1:oadev11_AddressUser">
<street xsi:type="xsd:string">Granby grove</street>
<city xsi:type="xsd:string">southampton</city>
<state xsi:type="xsd:string">uk</state>
<zip xsi:type="xsd:string">SO</zip>
</addr>
<salary xsi:type="xsd:double">1000</salary>
</emp>
This sucessfuly ads the entry to the databse any ideas please?

Hi,
Action parameter is always under Opertaion tag of your wsdl. In your case it is
Action = rpc/http://siebel.com/CustomUI:ATDDQMatchWS
<operation name="ATDDQMatchWS">
<soap:operation soapAction="rpc/http://siebel.com/CustomUI:ATDDQMatchWS"/>
<input>
<soap:body use="literal" namespace="http://siebel.com/CustomUI"/>
</input>
<output>
<soap:body use="literal" namespace="http://siebel.com/CustomUI"/>
</output>
</operation>
It looks to me you are trying to invoke RC encoded webservice which is not supported in XI.
Reward points if find useful
Thanks
Amit

ESB SOAP Service Error - Mutiple levels of SOAP invocation.

Hi,
Does anyone have a solution to this problem,
We are on SOA 10.1.3.1.
I am trying to design hierarchial invocation of services, where one ESB service calling another ESB service and so on...
Example There are 3 ESB Projects A, B and C. Project A calls B; B calls C.
A -> B -> C
In project B, I added SOAP service to directly reference/invoke service C which is already deployed. On execution, service B is successfully able to call service C. No issues.
I did similar execise, In project A, I added SOAP service to directly invoke service B (which is internally calling service C). Deployment is successfully. On execution from service A, I am getting following error.
Does anyone have a solution to this problem ?
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</faultcode><faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:790)
at java.util.HashMap$ValueIterator.next(HashMap.java:817)
at oracle.tip.esb.server.common.wsif.WSIFInvokerResponse.getFirstFaultElement(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.handleFault(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
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.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
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.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
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.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
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.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:790)
at java.util.HashMap$ValueIterator.next(HashMap.java:817)
at oracle.tip.esb.server.common.wsif.WSIFInvokerResponse.getFirstFaultElement(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.handleFault(Unknown Source)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
... 20 more
</faultstring><faultactor></faultactor></env:Fault></env:Body></env:Envelope>

Your usecase should be no problem. The error java.util.NoSuchElementException seems to indicate you are refering a non existing element somewhere. Are you sure the service gets invoked with the correct message content? From the enterprise manager website you can increase the logging of esb. Go to your esb oc4j container, administration, Logger Configuration. Search for soap loggers and increase the log level. You should now see the entire xml soap messages in the log.xml file.
Kind Regards,
Andre Jochems

ESB Soap Service invoking mutiple operations of a WSDL

Hi,
we have a requirement where in we have to call mutiple opeartions of a WSDL.
We tried developing this using ESB, where in we used many soap services invoking different operations of thw WSDL and a routing service which will decide on which SOAP service (Opeartion of WSDL) to invoke.
But we just want to check if there any way that we can call many operations of the same WSDL using the same soap service.
Any pointers on this.
Thanks in advance.
santu

Your usecase should be no problem. The error java.util.NoSuchElementException seems to indicate you are refering a non existing element somewhere. Are you sure the service gets invoked with the correct message content? From the enterprise manager website you can increase the logging of esb. Go to your esb oc4j container, administration, Logger Configuration. Search for soap loggers and increase the log level. You should now see the entire xml soap messages in the log.xml file.
Kind Regards,
Andre Jochems

Session management thru SOAP services

          Hi I am trying to deploy our application in a clsutered environment. Previsouly
          I had some problems with http session replication. That problems were solved but
          now I have another problem.
          Our application has multiple clients, some are browser based and some are swing
          based that use our SOAP services.
          all browser based clients use httpsession for session management, since weblogic
          replicates the httpsession, we have no problem clustering http webapps. But SOAP
          services has no access to httpsession.
          We have implemented our own session management (we cache the app specific session
          objects) so that SOAP services works fine (SOAP services doesn't have access to
          httpsession, so we could not use httpsession for session management). Each method
          in our soap services takes a sessionid and we get the session objects (not http
          session objects but our app specific session objects) based on the sessionid.
          But now that our application is clustered, the session cache mechanism doesn't
          work since its not replicated thru out the clusters.
          I thought I could use stateful session beans to cache the sessions, but how do
          I cache the SFSB thru out the session w/o sending any references to the SFSB to
          the client. I know I can send the Handle reference to the client but We cannot
          change the SOAP API now. The only information client has is the session id.
          My question is: How do I use SFSB w/o changing my soap services method paramaters.
          My SOAP method looks like methodName(String sessionid, ..............)
          I could use a clustered cache but we can't buy anything in the current situation.
          Any help would be appreciated.
          Praveen


Well, does the DSM log have any details? (see [Note 529924|https://service.sap.com/sap/support/notes/529924] on how to view the logs)
My guess is that you are using different protocols between the dispatcher and a backend system: they both have to use HTTP or both use HTTPS (as described in the same note). That would also explain why the URL for the direct connection to the portal doesn't present the error, if that URL has the same protocol as the backend.
Regards,
Sean

Shared services registration failed in HFM 11.1.1.3

We have installed the following products on the following
servers
1) Shared services server Repository : Oracle 11g installed
in 64 - bit Enterprise Linux.
2) 64 Bit HFM Installation in Windows 2003 Server.
3) Shared services installation done in Windows 2003 32-bit
OS.
4) IIS is up & running in the same (Windows 2003 Server- 64
Bit) where HFM is installed.
5) Also the shared services is accessible by using the URL
( in the Windows 2003 Server- 32 Bit)
**We are facing a problem with during the Web server configuration for HFM & shared services registration.**
the following system installers are also used :
1) V17382-01 (64 BIT SYSTEM INSTALLER)
2) V17397-01 (64 BIT FOUNDATION SERVICES 1)
3) V17369-01 (64 BIT FOUNDATION SERVICES 2)
4) V17370-01 (64 BIT FOUNDATION SERVICES 3)
5) V17372-01 (64 BIT FOUNDATION SERVICES 4)
Thanks in advance!!!

Sorry to have forgotten one more installable:
6) V17365-01.zip ( 64 Bit HFM installable)
Also if the ISS server is running in the 32-bit mode , does it affect the EPM configuration??
How do i check whether the IIS server is running in the 32 bit Mode or 64 - bit Mode.

EJB calling SOAP service

I'm experiencing a problem on 61.sp3.
I have an EJB that utilizes an API toolkit to access SOAP services on a
Tomcat server. The SOAP service sends back a SOAP exception which is
correct in what I am asking
in to do. However, the weblogic app server is returning a SOAP
exception to my EJB rather than passing the SOAP exception to the API
toolkit that I am using to make my SOAP calls.
Has anyone seen something like this?
Sandy Mustard

I did it (wsdl2java).
But I am working with jaxrpc.jar and axis.jar.
What my EJB does is:
java.xl.rpcCall call;
try {
    java.xl.rpc.ServiceFactory serviceFactory = java.xl.rpcServiceFactory.newInstance();
    Service service = serviceFactory.createService(new QName("", "hello"));
    QName qName = new QName("http://www.w3.org/2001/XMLSchema", "Array");
    TypeMapping service.getTypeMappingRegistry().getDefaultTypeMapping();
    typeMapping.register(ArrayList.class, qName,
                        new ArraySerializerFactory(),
                        new ArrayDeserializerFactory());
    call = service.createCall();
    } catch (ServiceException e) {
        cat.error(e.printStackTrace());
    try {
        call.setTargetEndpointAddress("http:/localhost:81");
    } catch (JAXRPCException e) {
        cat.error(e.printStackTrace());
    call.setProperty(Call.SESSION_MAINTAIN_PROPERTY, Boolean.TRUE);
    call.setProperty(Call.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
    call.setOperationName(new QName("", "hello"));
    try {
        return call.invoke(new Object[]{});
    } catch (RemoteException e1) {
        cat.error(e.printStackTrace());
    }Now I have another error which varies, it's quite disturbing me.
It goes from 'NoClassDefFound' to 'Linkage' errors...
Unexpected Error:
java.lang.NoClassDefFoundError: javax/xml/rpc/encoding/TypeMapping
and
Unexpected Error:
java.lang.LinkageError: loader constraints violated when linking javax/xml/rpc/encoding/SerializerFactory class
I get similar errors if I force the serviceFactory to be an instance of org.apache.axis.client.ServiceFactory.
Apparently I cannot make such remote calls within an only thread (?)
GNeidisch

Invoke remote SOAP Servlet using ESB SOAP Service component

Hello
I am new to ESB and JDeveloper as well, have been working with Eclipse since now. I have the following problem I can not solve at this time.
I have a SOAP Servlet running on Apache Tomcat 5, which I can call from simple JAVA code using the URL http://localhost:8080/omar/registry/soap
The servlet is defined/described within Tomcat using the web.xml file like:
<servlet>
<servlet-name>
ebxmlrr-soap-receiver-servlet
</servlet-name>
<servlet-class>
org.freebxml.omar.server.interfaces.soap.RegistrySOAPServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
I have already made a web service, which I have deployed on Oracle Application Server (using the SOA suite). In the web service I have wrapped a simple JAVA class which uses the SOAPConnection class to connect to http://localhost:8080/omar/registry/soap and sends a simple SOAP message successfully.
My question is, can I use the http://localhost:8080/omar/registry/soap URL directly from an ESB SOAP Service to send messages to the SOAP Servlet (not to use the web service in Oracle Application Server, but to connect directly to the SOAP Servlet on Tomcat) ?
Regards
Zolt

I have found a WSDL file provided to test the SOAP service I have mentioned before.
The content of the WSDL looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://omarebxmlrrwsdlnew/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="StandaloneTestService" targetNamespace="http://omarebxmlrrwsdlnew/">
     <types/>
     <message name="StandaloneTest_sendMessage">
          <part name="Message" type="xsd:string"/>
     </message>
     <message name="StandaloneTest_sendResponse">
          <part name="Response" type="xsd:string"/>
     </message>
     <portType name="StandaloneTestPortType">
          <operation name="sendMessage" parameterOrder="Message">
               <input message="tns:StandaloneTest_sendMessage"/>
               <output message="tns:StandaloneTest_sendResponse"/>
          </operation>
     </portType>
     <binding name="StandaloneTestBinding" type="tns:StandaloneTestPortType">
          <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="sendMessage">
               <soap:operation/>
               <input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://omarebxmlrrwsdlnew/"/>
               </input>
               <output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://omarebxmlrrwsdlnew/"/>
               </output>
          </operation>
     </binding>
     <service name="StandaloneTestService">
          <port name="StandaloneTestPort" binding="tns:StandaloneTestBinding">
               <soap:address location="http://localhost:8080/omar/registry/soap"/>
          </port>
     </service>
</definitions>
Where the address specifies the address of the SOAP service
When I try to use this WSDL inside an ESB SOAP Service I get the following error:
The selected porttype is using a message that is invalid for ESB because it is multi-part or has a simple type.
The message StandaloneTest_sendMessage in operation sendMessage of porttype StandaloneTestPortType is invalid.
Please select another porttype or fix the wsdl.
How can I get pass by this error, what is wrong with the WSDL file ?

SOAP service quality sporadic

(cross-posting to reach a broader audience)
http://forums.bea.com/bea/thread.jspa?threadID=400000749
I have a proxy service inside ALSB 2.5 deployed as a web service, and periodically synchronous requests to the web service return blank messages. No error message inside AquaLogic or WebLogic, and no error message in the SOAP message itself. The HTTP headers are passed, but no processed message is included.
I figured the next plan of action would be to ask over here in the WebLogic section.
I am using a standard HTTP POST command. (as defined under the SOAP section here: http://edocs.bea.com/wls/docs92/webserv/overview.html#Standards)

Currently it's a rudimentary flow that changes a field in an xml document. When using a standalone SOAP client the results are 100%. When accessing the SOAP service via my application it works 100%, until I start accessing it over and over again. Sometimes I get the proper response and sometimes only the HTTP header is returned. The problem increases with load.
I didn't know if there's an issue with the proxy service and the webservice getting out of sync when traffic increases or what. Previously the proxy service was accessed using a queue, and this was not an issue.

SOAP Service not loaded: WSDL Exception

MII: 12.0.3
OS: Win2k3 64bit
JDK: 1.4.2_18
Trying to load a web service and i keep getting this error which i'm having a hard time finding out the problem.
SOAP service could not be loaded. WSDLException (at /Rowsets): faultCode=INVALID_WSDL: Expected element 'definitions'
I loaded the WSDL path in IE and it comes up fine. The targetNamespace="http://tempuri.org" and xmlns:wsdl="http://schemas.xmlsoap.org/wsdl
If anyone has any suggestions or help please let me know....
Thank You

Nevermind.....Figured it out.
Turns out the target system was on a domain while the client box accessing it was NOT on a domain.
Changed the URL reference to the IP address instead of the server name and it worked.
- Thanks

SOAP service could not be loaded: premature end of file

Hi,
I am trying to call some web services using the Web Service action in the logic editor, but I am always getting some errors. For instance, for an online service (e.g. http://webservices.imacination.com/distance/Distance.jws) I am getting:
"SOAP service could not be loaded: Premature end of file."
I've tried 3 different web services that are available out there, and no result. I've laso tried writing it like this:
http://webservices.imacination.com/distance/Distance.jws/ or
http://webservices.imacination.com/distance/Distance.jws?wsdl
, but the result was the same.
I've also tried a web service that's currently deployed on my machine, using Tomcat. Here, I'm getting some slightly different errors:
http://localhost:8080/epcis-repository-0.2.0/capture/
SOAP service could not be loaded: the element type "HR" must be terminated by the matching end-tag "</hr>"
http://localhost:8080/epcis-repository-0.2.0/capture or
http://localhost:8080/epcis-repository-0.2.0/capture?wsdl
SOAP service could not be loaded: WSDLEXception (at /html): faultCode=INVALID_WSDL: Expected element 'definitions'.
As a note, this web service that I have deployed locally is also available online (http://demo.accada.org/epcis/capture), and if I try out this one, the error is again:
SOAP service could not be loaded: Premature end of file.
As far as I could tell, the /epcis/capture webservice is document/literal, so I don't think this should be a problem. I have read other posts about people having similar problems, but I could not find the answer to my problem...
Can anyone please help?
Thanks in advance!
Angela

Hi,
Thanks a lot, everyone, for your answers! Yes, the firewall and the "rpc/encoded" encoding might explain why the first two web services did not work...
However, it does not explain why the web service installed locally does not work, since it is "document/literal" encoded, as far as I could tell..... And unfortunately, this one is the one that I need to connect to (the others I was only using for testing). Again, this is the error message that I get:
SOAP service could not be loaded: WSDLEXception (at /html): faultCode=INVALID_WSDL: Expected element definitions'.
Parts of the wsdl file are copied bellow, and I can't see anything wrong with it (certainly no <definitions/> missing):
<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:epcis="urn:epcglobal:epcis:xsd:1" xmlns:epcisq="urn:epcglobal:epcis-query:xsd:1" xmlns:epcglobal="urn:epcglobal:xsd:1" xmlns:impl="urn:epcglobal:epcis:wsdl:1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:epcglobal:epcis:wsdl:1">
<wsdl:binding name="EPCISServiceBinding" type="impl:EPCISServicePortType">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="getQueryNames">
      <wsdlsoap:operation/>
      <wsdl:input>
        <wsdlsoap:body use="literal"/>
      </wsdl:input>
      <wsdl:output>
        <wsdlsoap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
As a side note, I now get the same error message if I try to connect from outside the company's firewall to the same web service available on the internet (http://demo.accada.org/epcis/capture?wsdl).
Does anyone have any more ideas?
Thank you once again in advance!
Angela

Soap Service Registration Problem

Similar Messages

Maybe you are looking for