javaxml.jar, war deploys, and sanity vs serenity
javaxml.jar, war deploys, and sanity vs serenity
- Subject: javaxml.jar, war deploys, and sanity vs serenity
- From: William Hatch <email@hidden>
- Date: Tue, 07 Jul 2009 23:35:34 -0400
WTF????????????
I have three apps, all deployed under the same container. they all
have the same classpaths. two of them deploy, one does not with that
miserable, make-you-want-to-kill error WOServletAdaptor
Unavailable.... All of these are built on a remote host using ant from
the shell on a CentOS box. That part works fine. In a recent post,
Mike makes mention of this jar hosing you, and I'd say it does, but
not all the time. If you keep sudo touching the damned war, eventually
it deploys. Why is this not a consistent error? What can be done to
make this stop, and what can be done so that one can never have to
speak it's name again? I mean clearly, you shouldn't have javaxml.jar
in your classpath and all that, but is there an easy way to prevent it
from getting there period? I'd rather suffer with some compiler errors
up front if it'd help. Thanks for letting me vent...;-) My future hair
line thanks you in advance for any solid suggestions that lead to a
more serene place
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden