Web service - Client Proxy - SOAP error

Hi All,
I created a custom web service/port and Client proxy.
While I test the Client proxy with Logical port via SE80, I am getting error message related to SOAP.
Error text:
SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Error when processing Web service call
Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Am I missing any configuration?
THanks,
Chirag

Hi,
I got the same error with using the configuration tool LPCONFIG after implementing -> with SOAMANAGER everything worked allright directly just create a port with that tool.
Maybe tha will help you also - for your problem.
Regards,
Jeroen Cosijnse

Similar Messages

Web Service - Client Proxy generation error

Hi All,
I tried creating a client proxy using an URL provided to me and followed the steps using the wizard. I end up in getting the following error messages. Could anyone throw some light on resolving this? I do not have any idea about what WSDL is. Any help is highly appreciated. Not able to attach the WSDL code here.
Below is the error message upon client proxy creation:
Proxy-Generierung: Fehler aufgetreten
Exception occurred in library handler
Not implemented
Thanks
Srini
Edited by: Srinivasan Karunakaran on Oct 22, 2010 11:11 PM

Resolved through SAP Help. Refer SAP note# 0001403271.

Web service client proxy thread safe?

Is the jax-ws web service client proxy and port objects thread safe in Weblogic 10.3.4?
Been searching through the docs but can't find any info on this.

I have searched and it seems that with cxf it's safe to do something like this.
Nobody knows if this is safe using metro?

ABAP Web Service client proxy - generation problems

Hi!
I tried to create an ABAP web service client proxy for many different web services -
for instance some of that listed at <a href="http://www.xmethods.net/">http://www.xmethods.net/</a> .
Almost on 99% of the WSDLs the client proxy generation failed.
For istance "<extension> not supported", or "<message...> must have at least one part",... .
Could anybody tell me what restrictions are to web services you can create a
ABAP client proxy for ?
In the SAP Web AS Java Stack there is no problem at all to generate a
client proxy for almost all of the xmethod-WebServices !
Is the ABAP Web Service proxy generation for production use ?
Regards
Frank Ruggaber

Resolved through SAP Help. Refer SAP note# 0001403271.

JDeveloper Web Service Client/Proxy Basic Authentication

Hi I recently migrated a 10g Web Service to an 11g Web Service that uses basic authentication.
I then generated the client/proxy using the WSDL for my consumer application in JDeveloper 11g. however I cannot find any functions that will allow me to set the username and password to access the web service.
For instance, in 10g Client, I simply had to this:
myPort = new SoapHttpPortClient();
myPort.setUsername("username");
myPort.setPassword("password");
I am not sure how I do the same in the generated Web Service client in 11g.
Thanks in advance.

Thanks Frank. I was able to get it to work!
I did google it but I always add "jdeveloper 11g" in my searches so that must be why this did not come up. :) Thanks again!

Web Service Client encoding style error

Hi all,
I have a created a java static stub client (created with wscompile from the wsdp). If I run the client I receive the following error
"unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/..."
I am using a delphi web service server, the encoding style is set to "http://schemas.xmlsoap.org/soap/encoding/"
My server simply echos a string with the method name "echoString"
Where do I go from here?
Does the xmlns tag in the "config-wsdl.xml" have anything to do with it?
Complete error :
java.rmi.RemoteException: Runtime exception; nested exception is:
unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:248)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:230)
at staticstub.IMyEmailWebService_Stub.echoString(IMyEmailWebService_Stub.java:68)
at DelphiClass.main(DelphiClass.java:25)
Caused by: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.encoding.SOAPDeserializationContext.verifyEncodingStyle(SOAPDeserializationContext.java:159)
at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:150)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:134)
at staticstub.IMyEmailWebService_Stub._deserialize_echoString(IMyEmailWebService_Stub.java:173)
at staticstub.IMyEmailWebService_Stub._readFirstBodyElement(IMyEmailWebService_Stub.java:157)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:158)
Thank you in advance
Garth

Looks like the server is not using the correct encoding. I suggest using a packet sniffer so you can actually see the SOAP message to verify that. Apache Axis has a tcpmon utility that works very nicely.

10.1.3.3 JDev web service client proxy: Issue with XSD:anySimpleType

Hi,
One of our Web services XSD elementss has "anySimpleType" as the type:
<xsd:element name="Value" type="xsd:anySimpleType" minOccurs="0" nillable="true"/>
The client proxy is generated using JDev 10.1.3.3. We observed that the corresponding Java object is created with "String" data type:
protected java.lang.String value;
exp.setValue("100");
We need to be able to pass arguments with other simple types as well (E.g. Decimal). We tried changing the auto generated code, but weren't successful.
Any pointers in this regard are much appreciated.
Thanks,
Phani

Hi all,
can anyone please respond to my issue. Its sort of urgent.
thanks,

Testing a Static Web Service Client Proxy

Hi all,
I have followed all the steps for Database Web Service Callout Utilitiy 10.1.3.1 but stuck at this point.
C:\OraHome_3>jpub -u dbws@lokal3 -sysuser sys@lokal3 -proxywsdl=http://localhost:8888/javacallout/javacallout?WSDL -endpoint=htt
p://localhost:8888/javacallout/javacallout
tmp\src\genproxy\HttpSoap11ClientJPub.java
plsql_wrapper.sql
plsql_dropper.sql
plsql_grant.sql
plsql_revoke.sql
Executing plsql_dropper.sql
Executing plsql_wrapper.sql
Error executing plsql_wrapper.sql. Please run that script in DBWS.
Executing plsql_grant.sql
Error connecting as SYSDBA. Please load the file in question manually. For autom
atic loading into remote databases or through thin drivers, please set up the pa
ssword file for remote SYS connection according to Oracle JDBC Developer's Guide
Error executing plsql_grant.sql: null. Please run that script as SYSDBA.
Error detecting dbwsclient.jar in the database: ORA-12560: TNS:protocol adapter
error
. Please load sqlj/lib/dbwsclient.jar if it has not been loaded.
Error connecting as SYSDBA. Please load the file in question manually. For autom
atic loading into remote databases or through thin drivers, please set up the pa
ssword file for remote SYS connection according to Oracle JDBC Developer's Guide
Error granting loading permission: null
Loading plsql_proxy.jar
SQL Error while connecting with oci8 driver to default database: ORA-12560: TNS:
protocol adapter error
Any ideas?
Regards,
Onur

Hi,
I got the same error with using the configuration tool LPCONFIG after implementing -> with SOAMANAGER everything worked allright directly just create a port with that tool.
Maybe tha will help you also - for your problem.
Regards,
Jeroen Cosijnse

HTTP Analyzer help for web service client in 11g

I am using jDev 11.1.1.3.0 to build a web service client (proxy) to a potential vendor's web service. I've used the Http Analyzer before but I'm having trouble configuring it for a WS proxy. I just want to see the SOAP stream between my client and the web service. I used the Web Service Proxy wizard to create the Java code, but the web service provider has kept some of the contract in the WSDL private so that I had to manually generate the meat and potatoes of the Java code. I need to be able to see the SOAP my Java code is sending.
I have tried to configure the Http Analyzer to listen on it's own localhost and port with a forward rule to forward the request to the real WS, but I cannot figure out how to get the client to send it's requests to localhost instead of the actual WS.
Actually, I did figure it out, but then the request fails as it apparently tries to connect to the real WSDL before actually sending the request and cannot find a WSDL at the localhost URL. Here's the error:
Exception in thread "main" javax.xml.ws.WebServiceException: {http://localhost:8099}CatalogRequest is not a valid service. Valid services are: {http://[actual URL here]}CatalogRequest
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:249)
I have also tried to configure the Http Analyzer to somehow 'sniff' the actual URL by listening on the actual URL and port, but either I cannot get the Analyzer to see the request or it fails because the Analyzer is using the same port the request is trying to use.
Can someone explain how to configure the Http Analyzer to see the SOAP stream for a Web Client Proxy?

Hi, I'm just using the default setup for HTTP Analyzer and having no problem using it.
Just make sure to run the HTTP Analyzer first before running or starting your app server (Integrated weblogic Server).

Web service as another web service client - problem in JavaEE SE?

Hello,
I observed strange behaviour with OpenESB, Glassfish (build 33) and following scenario:
I need to call web service from another web service. When I use simple schema:
web service client -> web service (as EJB) -> another Web service
everything works. But I would like to use JBI/ESB, so:
web service client -> HTTP SOAP BC -> JAVAEE SE -> web service (as EJB) -> another Web service
the following exception prevents success:
com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class cz.muni.fi.yucca.client.jbiws.gamanager.Calculate is not fou
nd. Have you run APT to generate them?
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:254)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:550)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:497)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:339)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:225)
at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:584)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:287)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:270)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:263)
at javax.xml.ws.Service.getPort(Service.java:92)
at cz.muni.fi.yucca.client.jbiws.gamanager.GAManagerService.getGAManagerPort(GAManagerService.java:51)
When I call both services separately they work correctly, when I don't use JBI it works correctly too.
Should anybody help me solving this problem?
Thanks in advice, Vlado

Fine,
I've found out that this problem is caused by different classloaders assigned to directly (EJBClassloader) and through-JBI (improperly configured URLClassloader) called web services.
I've moved my question to GlassFish forum (http://forums.java.net/jive/thread.jspa?threadID=24901&tstart=0) beacause of it's "technical" nature.
Despite this, any help is welcome:-)

Problem using WSDL from SAP in IBM's RAD for generating web service client

When importing a WSDL from the ABAP stack on a SAP 6.40 system into IBM's RAD tool for generating a web service client there are errors with the soap fault classes that get generated. The WSDL declares the types for the faults with WebServiceName.RfcException and these have elements of name, text, and message. When the tools see this in the WSDL they generate classes that extend the Java exeception class and this causes an error because the "message" name conflicts with the standard java exception message. Has anyone else ran into this problem? It seems like a basic problem many java tools for generating web service client proxies would have because the soap faults get turned into java exceptions. This name conflict of the java exception with the WSDL fault definition means that code always needs to be adjusted and cannot simply use the classes that are generated from the WSDL. Anyone run across this or a similar problem in the java environment using the SAP WSDL?
Aaron

Hi,
Hello again .
Have you tried your service using soapui ?
You can use your WSDL as input .
In order to eliminate eclipse problem try this service:(I just did)
http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
Regards.
package main;
import java.io.FileInputStream;
import java.rmi.RemoteException;
import java.util.Properties;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
public class Main {
public static void main(String[] args) {
try {
   final Properties properties = new Properties();
   properties.load(new FileInputStream("properties.ini"));
   System.getProperties().putAll(properties);
} catch (final Exception exception) {
   exception.printStackTrace();
new Main();
public Main() {
try {
   final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
   final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
   for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
    System.out.println(tCountryCodeAndName.getSName());
} catch (final RemoteException exception) {
   exception.printStackTrace();

Web Service Client: Project Additional Classpath contributor not working?

I've created a simple web service client/proxy and it works when debugging and running in JDeveloper 10.1.3.3
I created a deployment profile that includes "Project Additional Classpath". The preview does not show any of the jar dependencies being included and the client application does not run because it is missing the dependencies.
Am I missing something simple here? I've searched forever on this with no luck (it's now 2am!)
Help is much appreciated

Frank,
Thank you for your reply. The funny thing is that I had known how to do this in the past.
I have to say. The layout of that screen just is not intuitive.
First, if you select file groups\project output\Contributors and select "Project Additional Path" you would think that you'd either get to select the class libraries there or at least in the filters screen.
Second, the new button on the lower left, beneath the tree control when selecting the File Groups node is an arrangement I havn't seen used in any other application. Usually when you select a tree node, the right side window would have a tool bar over an arrangement of the sub-nodes/folders and you would click new on that tool bar. The new button goes completely unnoticed where it is. I'm sure it's nothng once you get used to it but for a noob like me, it wasn't apparent
I took a brief look at 11g and it seems they're changing some of the screens so perhaps this stuff will become more intuitive.
Thank you for your help.

Weblogic 10.3: web service client enable HTTP/HTTPS connection reuse?

hi all,
i am writing an client app to call a web service, through a client proxy generated by jdeveloper/weblogic.
My question is:
for the weblogic web service client proxy, is it possible to enable HTTP/HTTPS connection reuse/pooling?
i see there is many connection created when calling the web service (by command netstat)?
thank you.
lsp

anybody can help?
thanks

Error while invoking web services from Proxy services in OSB

I have a Proxy Service of message type in Oracel Service Bus 10gR3 and it passes the incoming messages from a JMS Queue to Business Service of Web Services type. This Web Service is hosted in Glass Fish v3 and it's binding style is RPC. The JRE used in both the servers are 1.6.0_20. The JMS message is of Text type. The Web Services at the Glass Fish throws MessageCreationException for any content of the JMS message. However, it works fine if Business Service's test client is invoked from the OSB'S Admin Console. However, the same will not work if Proxy Service's test client is called.
The detailed exception stack is given below :
Thanks for the help.
- Raj
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
     at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:318)
     at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:92)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:501)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:285)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:143)
     at org.glassfish.webservices.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:116)
     at org.glassfish.webservices.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
     at org.glassfish.webservices.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:196)
     at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:127)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sun.grizzly.http.servlet.FilterChainImpl.doFilter(FilterChainImpl.java:195)
     at com.sun.grizzly.http.servlet.FilterChainImpl.invokeFilterChain(FilterChainImpl.java:139)
     at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:376)
     at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:329)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
     at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:175)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:129)
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:354)

Let me explain what I am trying to achieve. Our application receives data from multiple sources - from mainframe using FTP, JMS Queue and BPM application using Web Services. The data from all these sources are sending to a Web Service running in GlassFish V3. To handle this I have created three Proxy Services and one Business Service on OSB. The Business Service is of type Web Service using the same WSDL from the target Web Service.
The Proxy Services are configured as follows:
Proxy 1 (type - Messaging service) listens to the JMS Queue and receives JMS Text Message -> Business Service(B1) (Web Service).
Proxy 2 (type - Messaging service Polls files from the FTP Server -> Business Service(B1) (Web Service).
Proxy 3 (type - Web service) is invoked by the BPM application and sends a String -> Business Service(B1) (Web Service).
All the Proxies route to the same Business Service - B1 which calls the Web Service in GlassFish. The only Proxy that works fine is Proxy 3 which is created using the same WSDL of the Web Service. In the other two proxies it thows the same exception in GlassFish as I mentioned before.
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
Is this configuration correct to achieve my requirements?
Once again thanks for the help.
- Raj

Web service client error

Hello,
I created new Web service client using WL 8.1, axis 1.4 , JDK 1.4.2 . The Service is hosted by my vendor and it's on asp/.net.
I used axis to create stub implemetation and when i invoke the service , i get the following error . I googled out the error and i see lot of them complain this as an axis issue.
Does anyone faced this error before ? or found an workaround for this?
Error message :-
2009-09-16 15:11:52,299] [DEBUG] [org.apache.axis.utils.XMLUtils] - Failed to set EntityResolver to null on DocumentBuilder
java.lang.NullPointerException
     at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEntityResolver.java:61)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryDocumentBuilder.java:168)
     at org.apache.axis.utils.XMLUtils.releaseDocumentBuilder(XMLUtils.java:252)
     at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:342)
Thanks in advance.
Thanks,
Subu

You made proxy client not a client.
I think u did not make any mistake to generate the proxy client but most probably ur web service-- message format is not rpc/encoded. Check it. hope u will succeed

Web service - Client Proxy - SOAP error

Similar Messages

Maybe you are looking for