B
Bryan Althaus
Has anyone gotten JSTL working under WebSphere 5.0? If so could you
explain what JARs you needed to copy into the WAR file? Did you need
to do anything to avoid clashes with the JAR files that ship with WAS?
I'm currently porting an application from WebLogic 6.1 to WebSphere
5.0. Under WL, I can take the Apache Jarkta Standard Taglibs
(http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html) and
install the JARS in WEB-INF/lib and all works fine. If I do the same
thing with WebSphere 5.0, I get clashes with the JAR files (xalan.jar,
etc.).
We use JSTL's Xtags (http://jakarta.apache.org/taglibs/doc/xtags-doc/intro.html)
to do XSL transformation and this tends to reply on the XML JAR's
heavily.
Any help would be greatly appreciated as this is the only thing
keeping the port from being completed.
Regards,
Bryan
P.S. I notice 5.0.2 comes with a new Web Services Pack but relies on
JDK 1.4 and I'd rather not go down that path (we have a few java
applet clients which don't run under JDK 1.4).
explain what JARs you needed to copy into the WAR file? Did you need
to do anything to avoid clashes with the JAR files that ship with WAS?
I'm currently porting an application from WebLogic 6.1 to WebSphere
5.0. Under WL, I can take the Apache Jarkta Standard Taglibs
(http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html) and
install the JARS in WEB-INF/lib and all works fine. If I do the same
thing with WebSphere 5.0, I get clashes with the JAR files (xalan.jar,
etc.).
We use JSTL's Xtags (http://jakarta.apache.org/taglibs/doc/xtags-doc/intro.html)
to do XSL transformation and this tends to reply on the XML JAR's
heavily.
Any help would be greatly appreciated as this is the only thing
keeping the port from being completed.
Regards,
Bryan
P.S. I notice 5.0.2 comes with a new Web Services Pack but relies on
JDK 1.4 and I'd rather not go down that path (we have a few java
applet clients which don't run under JDK 1.4).