Re: War deploy; maven archetypes problems; web.xml filtering
Re: War deploy; maven archetypes problems; web.xml filtering
- Subject: Re: War deploy; maven archetypes problems; web.xml filtering
- From: Henrique Prange <email@hidden>
- Date: Mon, 26 Oct 2009 11:48:51 -0200
Hi Greg,
Mr. G Brown wrote:
Hi,
I had maven 2.0.9--it does not work with servlets; everything else was ok.
I don't recall any servlet specific problem related with this version of
Maven. Anyway, Maven 2.0.9 is more than 1 year old. :)
I upgraded to 2.2.1, and now the non-wonder servlets work. I still have
a problem with archetype built wonder projects.
The wo maven bootstrap doesn't install
the <artifactId>JavaWOJSPServlet_client</artifactId> for WO 5.3, into
the local repository, if I recall, I had to manually do this.
I've created the issue WOL-1123 to report this problem.
Tomcat and jetty both give errors with stuff like:
javax.servlet.UnavailableException: Error initializing
ERXServletAdaptor: ${mainclass}
at
It seems the ${mainclass} variable still hasn't been filtered correctly.
Could you try to manually replace the variables in your web.xml file and
check if the application works?
I should upgrade to 5.4, it is time. It may be that
the ERXServletAdaptor only works with 5.4?
ERXServletAdaptor is compatible with both.
Attached is a warwonder.zip project, built by the archetype with wonder.
I've installed WO 5.3.3 on my machine. I've run the application
successfully using 'mvn clean jetty:run-war'.
Cheers,
Henrique
_______________________________________________
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