Re: Oracle V2 parser doesn't like unqualfied 'fault' elements

This error is thrown by the soap client libraries, not the Oracle JAXP implementation. If this is indeed the XML returned by the server: SOAP-ENV:Fault faultcodeSOAP-ENV:Server/faultcode faultstringservice 'urn:test:echo2' unknown/faultstring faultactor/winxml/rpcrouter/faultactor

AW: Server Event Notification To Clients

Title: RE: Server Event Notification To Clients Well, I think that's one ofthe points JMS can't do. We are using it in a local network. That'swhySOAP is better. -Ursprüngliche Nachricht-Von: Tony Jeffery [mailto:[EMAIL PROTECTED]]Gesendet: Dienstag, 5. März 2002 16:41An:

RE: Soap client threads

Title: Soap client threads Each client thread should create a new instance of the client side SOAPobject...you should have no problems here... (Make sure that you are not using the same SOAP object across threads...that would cause synchronization problems). Java does allow you to have

Re: AW: Soap client threads

I think for the SOAP toolkit that's no problem. But does Java allow many sockets open from many threads? YES.

Re: weblogic6.1 and soap2.2

Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before weblogic.jar in server's classpath.(See attached file: patchCR058220.jar) regards, Ruben

Re: weblogic6.1 and soap2.2

Ruben, thanks, it work. where can I find some info on this patch? -Gus On Wed, 2002-03-06 at 07:59, [EMAIL PROTECTED] wrote: Hi Gus, this seems a problem with the ServletOutputStreamImpl class in weblogic. I found a patch that solves the problem (find it attached), just place it before

Re: weblogic6.1 and soap2.2

Hi Gus, no idea, I tried to find the Patch from Bea support for a long time but I get no response, just know that it works and I think they solved the problem in sp2. Ruben

Re: Oracle V2 parser doesn't like unqualfied 'fault' elements

here's the header for that message, should have included in original posting. ?xml version='1.0' encoding='UTF-8'? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance; xmlns:xsd=http://www.w3.org/1999/XMLSchema;

Re: weblogic6.1 and soap2.2

Ruben, Thanks. On Wed, 2002-03-06 at 09:12, [EMAIL PROTECTED] wrote: Hi Gus, no idea, I tried to find the Patch from Bea support for a long time but I get no response, just know that it works and I think they solved the problem in sp2. Ruben

JBoss and SOAP service deployment

I'm stumped trying to get my first service deployed. Can anyone please lend me a hand. I'm trying to rpc the sample interest ejb for JBoss. Soap 2.2, JBoss 2.2.4 and Tomcat 4.0.1... and using the servicemanagerclient for deployment. FullContextFactoryName - I'm using:

base64binary

Hello everybody! I have a problem and hope somebody can help me. I have .NET client and Java Apache Soap Web Service. One method has an input parameter byte[] (public String setArrayByte(byte[] param) and another one - returns byte[] (public byte[] getArrayByte(String param). When the client