RE: Apache-Soap and Tomcat 3.3

2001-11-15 Thread David Brunkow

Thanks for the response.

I only want my web application to respond to SOAP requests.  The soap files
are in my web app.  The problem is, they still have to be in the Server
classpath.  My Toplink classes won't work if they are in the Server
classpath, so says experience and the Toplink vendor.  That means, I can't
use soap and toplink together. Why in the world the Soap people have allowed
this restriction is beyond me.  The Tomcat path is only for the running of
the server, why you need to add classes to it, to run my application is just
plain wrong.

Dave



-Original Message-
From: Tom Drake [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 13, 2001 4:25 PM
To: Tomcat Users List
Subject: Re: Apache-Soap and Tomcat 3.3


David:

Another solution is to simply deploy the apache web-application into the
same context as your own. This means that you have to merge web.xml
files, but it's otherwise pretty straightforward.

This means that only your web-application will be able to respond to
SOAP requests, however.

I've implemented Apache SOAP both ways.

- Original Message -
From: David Brunkow [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Tuesday, November 13, 2001 3:35 PM
Subject: Apache-Soap and Tomcat 3.3


|
|
| Does anyone have Apache-Soap working with Tomcat 3.3? Unless you jar your
| app and put it in %TOMCAT_HOME%\lib\common\ I don't think it should work.
| I'm having all kinds or problems with classes could not be found on just
the
| samples.
|
| Thanks,
|
| Dave


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Apache-Soap and Tomcat 3.3

2001-11-13 Thread David Brunkow



Does anyone have Apache-Soap working with Tomcat 3.3? Unless you jar your
app and put it in %TOMCAT_HOME%\lib\common\ I don't think it should work.
I'm having all kinds or problems with classes could not be found on just the
samples.

Thanks,

Dave

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]




Apparent ClassLoader, ClassNotFoundException when using Apache Soap and Toplink

2001-11-12 Thread David Brunkow

Tomcat 3.2 on NT 4.0.
Apache Soap 2.2, http://xml.apache.org/soap/
Toplink 3.0.5

The root of this entire problem seems to be that the Apache Soap
services/classes cannot be found, ClassNotFoundException, unless the classes
are explicitly in the classpath tomcat.bat, startup, classpath. So says the
installation notes.  

Now, make sure you have the jar files from the lib directory of
this distribution on your classpath and start up tomcat. Also, you will want
to have on the classpath any of your code that you want to deploy as
services
http://xml.apache.org/soap/docs/index.html
 

This is a problem when using a package such as Toplink, which requires these
classes to not be in the classpath because the webapp cannot find them. 
The object, 'com.cis.business.AddressModel'
 of class, 'class java.lang.String' could not be converted to
 'class java.lang.Class',
INTERNAL EXCEPTION: java.lang.ClassNotFoundException:
This makes sense, the webapp classes should not have to be in the tomcat
path. What if there are conficts between two apps. These classes should be
in the webapp path, as Toplink assumes.

Given these restictions, we cannot recieve a transaction through soap, and
insert it into the database.

Bottom Line:
With soap classes in the classppath, it can't find our business object
classes which aren't in the path.
With soap classes in the classpath and our business objects in the path, it
still cannot find the business objects because of Toplink problems.
Without soap classes in path, it can't find the soap services.

That said, I'll do what I have to in order to get this to work.  Anybody
know how? or have any suggestions other than prayer.

Thanks,

Dave Brunkow


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]