base64QName = new QName(soapEncURI, "base64");
mapTypes(soapEncURI, base64QName, byte[].class, base64Ser,
base64Ser);
On 24 Jun 2003 at 17:57, Richard Bolen wrote:
> I followed the directions in the documentation which say to patch the
> Constants.java file to change the curren
I followed the directions in the documentation which say to patch the
Constants.java file to change the current schema to the 1999 schema. I
did this but the RPCRouterServlet for a StatelessSessionBean provider
continued to use the 2001 schema. Is there anything I can change via a
config file? I
FYI -
My session issues have nothing to do with SOAP faults. I was stepping on the target
object URI attribute of the Call object causing it to lose it's EJB ID.
Rich
Does handling a fault affect maintaining sessions? I'm having some problems
maintaining user sessions after a fault is re
Does handling a fault affect maintaining sessions? I'm having some problems
maintaining user sessions after a fault is returned from the server. Does a fault
reset some of the attributes of the Call object?
thanks -
Rich
Ri
h is insufficient to change parsers. You need to
set the system property javax.xml.parsers.DocumentBuilderFactory.
To see which parser you are actually using, do a System.out on the
javax.xml.parsers.DocumentBuilderFactory object returned by the static
newInstance() method.
For us, weblog
;t
change the xml parser I was using so what could it be?
Is there a workaround for this? i.e.: not setting a namespace in the call object?
any help is greatly appreciated.
Rich
-Original Message-
From: Richard Bolen
Sent: Wednesday, May 22, 2002 10:21
To: SOAP Users Mail
Did you ever find a solution to this issue? I'm having the same problem.
Thanks,
Rich
-Original Message-
From: Jim Cross [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 09:24
To: [EMAIL PROTECTED]
Subject: IllegalArgumentException in processing server exceptions on
client side
I'm getting the following SOAPException from SOAP when it is parsing what appears to
be a valid Fault element:
SOAPException in soapMethodCall: A 'http://schemas.xmlsoap.org/soap/envelope/:Fault'
element must contain a: 'faultcode' element.
Here's the Fault response (captured from the TCPMoni
It's the official release version. It's version 2.4.4 of JBoss. If I remember
correctly, they've changed the config format from 2.4.1 to 2.4.4 so that may be why
you get errors.
It just http://www.jboss.org for the download.
Rich
-Original Message-
From: Tiago Fernandes Thomaz [mail
got the error
for several threads: Error: Connection refused;
Any ideas?
Tiago Fernandes Thomaz
-Original Message-
From: Richard Bolen [mailto:[EMAIL PROTECTED]]
Sent: sexta-feira, 12 de Abril de 2002 18:23
To: SOAP Users Mailing List (E-mail)
Subject: SOAP under heavy load - per
Is there any good source for information on using Apache SOAP under heavy load? My
service needs to support 50-100 concurrent client sessions (which really isn't that
heavy of a load).
My service is a SOAP front end for EJB's running on JBoss with Tomcat 4.0.1 as the
servlet engine for SOAP
I'm trying to load test our SOAP service and when I get to a certain number of clients
I get a
SOAPException: Parser already in use
error. Has anyone seen this? Is there some configuration that can be done to avoid
this error? I'm running on Tomcat 4.0.1.
Thanks,
Rich
---
I'm including soap.war in a .ear file that contains my entire application. I'd like
my soap services to be automatically deployed when the .ear file is deployed.
How can I do this?
Can I just include my soap deployment descriptors in my ear file somewhere? Or do I
need to create a Deployed
I'm working on a project where we need to allow different versions of a
client and a server to work together. Our deployment pattern is very
complex and we will have different server versions and different client
versions all trying to interoperate. We're using SOAP as the communication
mechanis
14 matches
Mail list logo
