what is the messagerouter servlet - instructions didn't tell me to set oneup did they?

Hi I am setting up apache soap rpcrouter and messagerouter servlets in web sphere - all works fine except: I point browser at: http://localhost:port/soap/servlet/rpcrouter and I get the page that tells me that router doesn't use post command - all well and good. Then I point at:

Re: Jasper and Exception SOLVED PARTIALLY

I have solved the problem by installing Sun's JWSDP (Java Web Services Development Pack 1.0.01). It consists Tomcat, Ant and others. After that I have just installed soap 2.3 WAR file in %JWSDP%\webapps folder and soap.jar in %JAVA_HOME%\jre\lib\ext. It is a partially solution because of I am

Re: what is the messagerouter servlet - instructions didn't tell me toset one up did they?

I am not certain exactly what instructions you are following. I know that the soap.war file contains a web.xml that both rpcrouter and messagerouter servlets. Things work as expected on my Tomcat-based deployments (sorry, I don't have WebSphere.) Scott Nichol - Original Message -

Re: Jasper and Exception SOLVED PARTIALLY

soap.jar in %JAVA_HOME%\jre\lib\ext is a very bad idea. This has been the cause of problems for many, many people. If you look at Tomcat's class loader information at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html, you will find that jars in lib/ext are loaded by the

Re: NoClassDefFoundError: javax/servlet/http/HttpServlet

Yes, putting soap.jar in lib/ext causes problems for Tomcat because of the boundaries between class loaders. Because classes in soap.jar depend on classes in upstream class loaders (e.g. classes in servlet.jar), class loading problems occur if soap.jar is in lib/ext. Scott Nichol -

Bean-to-XML Serializer

We will be using SOAP 2.3. For most users we need to conver to/from SOAP to java bean format. However, for a few users, we will need to convert from the java bean to either DOM or literal-XML. Is there a way to do this? I see the beanserializer will go from SOAP to bean and back, but how do

Re: Bean-to-XML Serializer

Hi, You could look at JROM (http://www.alphaworks.ibm.com/tech/jrom) too. JROM is a java representation of XML which is more convenient than DOM for many applications, has a SOAP serializer and deserializer and a JROM-2-Bean, Bean-2-JROM convertor. JROM2DOM and DOM2JROM are being developed

Announcing Axis 1.0!

I'm pleased to announce the Apache SOAP engine known as Axis just had it's first release. Performance, interoperability, and JAX RPC compliance have been significant focuses of this effort. You can download it at http://xml.apache.org/axis/dist/1_0/. - Sam Ruby -- To unsubscribe, e-mail:

Re: what is the messagerouter servlet - instructions didn't tellme to set one up did they?

Hi I am setting up apache soap rpcrouter and messagerouter servlets in web sphere - all works fine except: I point browser at: http://localhost:port/soap/servlet/rpcrouter and I get the page that tells me that router doesn't use post command - all It should say it doesn't

serializer and deserializer for byte[]

Hi, We have been using apache soap 2.2 successfully in many of our web applications over the past one year with websphere 3.5.4. When I tried to add a new soap call(Element saveItemWithDocuments(int userID, Hashtable itemDocuments, Element itemElement)), i was getting errors, which i came to

Catching a comm error

Hello: This has probably been answered before. If there is something in an archive, please point me there and I'll read it. I was wondering what happens if the SOAP response never gets back to the client that invoked the SOAP Call. In other words, the Java method that the SOAP RPC router called

Re: Catching a comm error

There is no way for the service to know that a particular response has been successfully returned to the client. Note that even if the servlet writes all the output to the response stream without error, it cannot be certain that the client application receives it. In fact, I doubt you can even

Re: Catching a comm error

I guess I better have a method exposed on my web service that the client can call to ask about previous requests or maybe retry the same request X times before giving up. Anyway, I'll need to do something on the client end. At least the client will get a SOAP Fault indicating some sort of error

Re: Catching a comm error

If you really need a handshake, I think you are right to take the approach of having your service expose that functionality. Scott Nichol - Original Message - From: Wyn Easton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 07, 2002 5:34 PM Subject: Re: Catching a comm

Re: Catching a comm error

I think that you may be off track by having the client call and ask the server. Remember, in the client side code, the call will only complete without a SOAP fault if everything worked fine. So the client always knows whether the whole SOAP transaction worked or not. The real issue is whether