I am new here, and new J2EE deployment issues. Forgive
me if these observations are naive.
I gather from recent complaints on this list that
deployment of struts WARs into J2EE environments (with the WARs
packaged into EAR files) is not working as expected. The
struts.jar isn't getting cpath'ed from the demo apps WEB-INF/lib at
deployment time, or gets put in some sub-directory of WEB-INF/lib, where it is
not found.
But, the struts demos do work OK on stand-alone Tomcat (if you use Xerces and avoid JAXP). One workaround people try is to put struts.jar into the j2ee
server's CLASSPATH, but this is a bad idea because j2ee is an "embedded
environment", ie, a total platform into which apps are installed
dynamically. Anyway, juking the CLASSPATH just causes other
problems (in "example" for example).
(Rough summary of various threads.)
I am seeing this too. I my case the problems are on the
freebee j2eesdk1.2.1 server that I downloaded from Sun. This may be
related to the WL and iPlanet problems that others have reported. (Except
that you paid good money for that software and you are getting excellent support
from your vendor, right? No annoyance issues, right?)
The Sun Bug Report I have posted below seems
relevant to these problems. I kept thinking that Sun must know about
(and would quickly fix ??) such an obvious problem in their own SDK
implementation. So I kept searching their site for such a fix.
Apparently not. Perhaps deadlines are tight at Sun.
Anyway, .....
This particular Bug Report is quite old and is
listed as closed. But, skeptic that I am, I am not convinced that it was
fixed anywhere but on Tomcat. And it could be that various
commercial implementations of j2ee (inlcuding the Sun "reference") employed
workarounds for this bug, which ended up as regressions.
Also, what does "javaxservlet:api 3.0beta" mean in this
context, given that the latest Servlet API I know of is Release
2.3.
Dan Connelly (who is not Dan Connolly,
W3C, but likes his ideas anyway)
|