wood burning stoves 2.0*
The moose likes Websphere and the fly likes Webservices - URGENT Information needed !!! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Webservices - URGENT Information needed !!!" Watch "Webservices - URGENT Information needed !!!" New topic
Author

Webservices - URGENT Information needed !!!

aanchal mathur
Greenhorn

Joined: Sep 13, 2001
Posts: 29
Hi,

I have been trying to urgently find out if MS Soap is compatible with Websphere 5.1 . I have a vb client which needs to access the Java Web Service deployed under my Websphere 5.1 Application Server. I tried but on TCPMON i could c all garbage values in the request. does this mean i cannot use MSSoap client with the Websphere based webservice.

aanchal.
[ June 01, 2004: Message edited by: aanchal mathur ]
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Yes they are compatible. This is where WS-I compliance comes in. If you write a WS-I compliant Web Service in WAS (which is the default) then you will be able to access it from a Microsoft client.

Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
aanchal mathur
Greenhorn

Joined: Sep 13, 2001
Posts: 29
Hi Kyle,

Thanx for a quick Reponse. Since i am new with Webservices you may need to guide me a little further with the WS-I compliancy. The Java Webservice was already existin and working with the Oracle9ias App server. i.e VB 6.0 Client was talkin to the Webservice deployed on Oracle9ias App server successfully. I made no changes to the WebService and instead using the EJB2WebService tool provided by IBM generated the various files needed by Websphere inorder to deploy it as a Webservice.
The Deployment shows success on Webpshere with the following message "And now the Servcies..." , so i am assuming from this message that the Servcie has been deployed successully.

When i access the Service frmo a Java Client using Apache Soap i can c the correct response on TCPMON , but on the comman prompt i get the followin error :


[SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to deserialize a ' <a href="http://soap.ejb.businessobjects.a2g.infocorpnow.com:querySessionBean</b rel="nofollow">" target="_blank">http://soap.ejb.businessobjects.a2g.infocorpnow.com:querySessionBean


Next when i call the same service from a VB utility runnin MS Soap toolkit 3.0 , i get the following error on TCPMON :

[CDATA[org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0xfffe) was found in the prolog of the document.[/B]




And in the Websphere System.out log file i get the following error :



WebServicesFault
faultCode: Server.generalException
faultString: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0xfffe) was found in the prolog of the document.
faultActor: null
faultDetail:

org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0xfffe) was found in the prolog of the document.
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:150)
at com.ibm.ws.webservices.engine.SOAPPart.getSOAPEnvelope(SOAPPart.java:773)
at com.ibm.ws.webservices.engine.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:640)
at com.ibm.ws.webservices.engine.Message.getSOAPEnvelope(Message.java:451)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCSOAPHandler.checkSOAPSemantics(JAXRPCSOAPHandler.java:218)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCSOAPHandler.invokeServerRequestHandler(JAXRPCSOAPHandler.java:188)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$1.invoke(JAXRPCHandler.java:214)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:195)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:61)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:253)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:840)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:341)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:443)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Caused by: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0xfffe) was found in the prolog of the document.
at sax.SAX2DocumentEntityParserBase.reportFatalError(Unknown Source)
at com.ibm.xml.b2b.scan.WFCDocumentScannerSupport.reportFatalError(Unknown Source)
at com.ibm.xml.b2b.scan.latin.LatinWFCDocumentScanner.scanDocument(Unknown Source)
at sax.latin.LatinWFCSAX2DocumentEntityParser.scanDocument(Unknown Source)
at util.DocumentEntityParserBase.parse(Unknown Source)
at sax.SAX2DocumentEntityParserBase.parseEntity(Unknown Source)
at sax.SAX2DocumentEntityParserBase.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at com.ibm.ws.webservices.engine.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:251)
at com.ibm.ws.webservices.engine.SOAPPart.getSOAPEnvelope(SOAPPart.java:742)
... 34 more


Please help me in identifyin wats the problem and how can it be rectified.
thanx
aanchal.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Webservices - URGENT Information needed !!!