Bundle frameworks, not jars and yes, it's in the classpath.

Bill



On Feb 3, 2009, at 3:59 PM, Mike Schrag wrote:

are you using jar frameworks or bundle frameworks? is the erxservletadaptor.jar in your classpath?

On Feb 3, 2009, at 3:53 PM, William Hatch wrote:

New project using recent wonder for 5.4, absolute latest pre hotness WOLips, eclipse 3.3 and wo 5.4; tomcat 5.5.xxxx

Building a simple, war gives the famous ERXServletAdaptor exception on container deploy. I'm struggling for words to express how much I despise this error

My web.xml contains the appropriate declaration specifying er.extensions.jspservlet.ERXServletAdaptor as class for WOServletAdaptor
Classpath looks good.

I've googled this to death, and the only thing that seems like a reasonable explanation is the discrepancy between spec 2.2 and 2.3

The odd thing is that some new projects will work, and I won't see this error. I'm trying to get my head around what the magical variant is here. Any ideas? Anybody willing to share their working, web.xml from a recent new project?

Thanks.


Bill



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected] )
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/mschrag%40mdimension.com

This email sent to [email protected]


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects- [email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/wkhatch%40me.com

This email sent to [email protected]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to