Title: RE: Tomcat in Linux
It plumbs the same, by my reckoning ;-)
--- bhw
-Original Message-
From: Yiet, Richard Liyong [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 11:05 AM
To: [EMAIL PROTECTED]
Subject: Tomcat in Linux
Hi,
I am trying to run Tomcat stan
Title: RE: Error while trying to deploy service
You'll need your commandline classpath including all the JARs from Axis (as well as the servlet jar, if memory serves).
If you wish to continue your attempts at running through java code, your "current working directory" is the one in which you
Title: RE: ResultSet arguments
Yes. If you establish your complex datatypes (the row from your ResultSet) as a JavaBean (with getters and setters), then Axis will use it's generic Bean serialization/deserialization routines to build the SOAP/XML.
When you use the wsdl.exe tool in .NET (or ho
Title: RE: ResultSet arguments
I guess I did something similar. But, I never thought to try and serialize the ResultSet, per se. I created serializable value objects that represented the contents of a "row" in the ResultSet and my WebService returns an array of these.
--- bhw
-Origina
Title: nightly drops missing
I
think your error is related to the "empty" type of your nestedException
element. I think that the {http://www.w3.org/2001/XMLSchema} string is
just the default namespace with no class following it.
Anyone?
---
bhw
-Original Message-From: Volkman
Title: RE: EJBs deployed as webservices continued
Russell, et al.
I am using JBoss as my EJB server, but I have a decoupled Tomcat-4.1.12 installation hosting Axis. I think that (minus a few Sun RI vs. JBoss issues) the problem domain is nearly identical. I can appreciate your pain in get
o one last question... Is this all a shortcoming in the XML/SAX
parser or expected behavior when shipping bad data across the web-service-wire
(it *DID* work for the EJB call)?
---
bhw
-Original Message-From: Brian Ward
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, October 29, 2002
Title: org.xml.sax.SAXParseException: Illegal XML character
I'm encountering a deserialization error. I have some strings (which contain some some xml-unfriendly characters) that I am trying to return from an axis deployed web service. The service itself seems to be fine, but I'm encounterin
