Thanks for the help! I successfully have js14b4 running under WAS 4.0.5. Setting up the directory with these libraries in it and adding it to the server classpath was the trick.
Thanks again, George
Mark Orciuch wrote:
You need to change the app server classpath NOT the system classpath (don't replace any .jar files). Modify the classpath for app server running your jetspeed webapp to point to xalan-2.3.1, xml-apis, crimson-1.1.3 from jetspeed distribution and xerces shipped with WAS. You may want to copy the first 3 .jar files to a separeate folder and reference it from there.
Best regards,
Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/
-----Original Message----- From: gbs [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 11:50 AM To: Jetspeed Users List Subject: Re: WebSphere 4.0.6 and Jetspeed 1.4b*
I tried replacing WAS's xerces with 2.02, but the server wouldn't start. So, just for fun, I changed the system-level classpath to start with jetspeed's lib directory, and WAS does start but I get the same error. I question whether changing the system-level classpath had any effect.
I next decided to irritate the system by wholly removing the tld file to see if I get a different error. Interestingly, the error did change to the following:
Error encountered processing a template: /portlets/html/hello.jsporg.apache.jasper.JasperException: C:\WebSphere\AppServer\installedApps\jetspeed14b4.ear\jetspeed.war \templates\jsp\portlets\html\hello.jsp(3,69) JSPG0103E: Unable to open taglibrary /templates/jsp/tld/template.tld : JSPG0127E: Could not locate TLD META-INF/taglib.tld at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java:874) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNeces sary(JspServlet.java:251) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(Jsp Servlet.java:279) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:503) at .....
So without a tld, the error is that WAS can't locate the tld file (as compared to 'openning' it in the first error). This leads me to believe that the problem truly is a xml parsing issue as you had mentioned, but I am at a loss as to how to fix it. Do you have additional suggestions I might try?
Thanks, George
Weaver, Scott wrote:
It looks to be some sort of XML parsing error. Is there anywayyou can use a different version of Xerces other than the one
Websphere uses?
ar\templat*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
-----Original Message----- From: gbs [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 11:57 AM To: Jetspeed Users List Subject: Re: WebSphere 4.0.6 and Jetspeed 1.4b*
Yes (although I have made the config changes in a jetspeed 1.4b4 installation):
Error encountered processing a template:
/portlets/html/hello.jsporg.apache.jasper.JasperException:
C:\WebSphere\AppServer\installedApps\jetspeed14b4.ear\jetspeed.w
essary(Jspes\jsp\portlets\html\hello.jsp(3,69)
JSPG0103E: Unable to open taglibrary /templates/jsp/tld/template.tld :
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at
org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java:874) at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNec
spServlet.Servlet.java:251)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(J
necessary changesjava:279) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java:503) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:651) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.engine.webapp.StrictServletInstance.doService
Weaver, Scott wrote:
So now the error looks like this?\templates\jsp\portlets\html\hello.jsp(3,77)
Error encountered processing a template: /portlets/html/hello.jsporg.apache.jasper.JasperException: C:\WebSphere\AppServer\installedApps\jetspeed14b2.ear\jetspeed.war
JSPG0103E: Unable to open taglibrary /templates/jsp/tld/template.tld : org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at .....
*===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
-----Original Message----- From: gbs [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 11:43 AM To: Jetspeed Users List Subject: Re: WebSphere 4.0.6 and Jetspeed 1.4b*
Scott,
I've moved /WEB-INF/templates to /templates, made the
propertiesin TR.p and JR.p, updated the web.xml, and changed the JSP taglib
statements in the hello.jsp portlet to reflect the new location. I've
also left the default template type as velocity (=vm) in the
running in WASfiles in the hope that I could at least get a JSP portlet
format. I endbefore flipping over to using JSP as the default template
(versionsup with the same error though.
I should note that I have successfully run jetspeed in Tomcat
If there is3.1, 3.2, 3.3.1a, 4.x) without problem.
If you can think of anything else, we would appreciate it.
containersmore info you would like to get from me, let me know and I'll try to provide it.
Thanks, George
Weaver, Scott wrote:
Hi George,
Try moving the templates directory outside of WEB-INF. Some
1.4b[2, 3, 4,thatwill not recognize JSP pages that are within the WEB-INF. Make sure
JSP pages reflect this change when linking in the taglib.
Hth, *===================================* * Scott T Weaver * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] * *===================================*
-----Original Message----- From: gbs [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 1:27 AM To: [EMAIL PROTECTED] Subject: WebSphere 4.0.6 and Jetspeed 1.4b*
A team I am working with has been trying to get Jetspeed
help, suchseveralor the cvs head] autonomously running under WAS 4.0.6. We have
work-arounds that allow us to get it running with a bit of
just add newas
precompiling all of the JSP, but we would much prefer to
found. Here aresteps.jsp-based portlets and have them run without going through extra
This would grealy simplify the dev/deploy cycle for us. The primary
problem we are getting is about the taglib not being
ed.war\WEBthe first few lines of the exception:
Error encountered processing a template:
/portlets/html/hello.jsporg.apache.jasper.JasperException:
C:\WebSphere\AppServer\installedApps\jetspeed14b2.ear\jetspe
----------
INF\templates\jsp\portlets\html\hello.jsp(3,77) JSPG0103E: Unable to open taglibrary /WEB-INF/templates/jsp/tld/template.tld : org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at .....
We appreciate any help,
Thanks, George
------------------------------------------------------------
[EMAIL PROTECTED]To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
