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.war\templates\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.loadIfNecessary(JspServlet.java:251) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.java: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?

Error encountered processing a template:
/portlets/html/hello.jsporg.apache.jasper.JasperException:
C:\WebSphere\AppServer\installedApps\jetspeed14b2.ear\jetspeed.war 
\templates\jsp\portlets\html\hello.jsp(3,77)
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 necessary changes
in 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 properties
files in the hope that I could at least get a JSP portlet running in WAS
before flipping over to using JSP as the default template format.  I end
up with the same error though.

I should note that I have successfully run jetspeed in Tomcat (versions
3.1, 3.2, 3.3.1a, 4.x) without problem.

If you can think of anything else, we would appreciate it.  If there is
more 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 containers


will not recognize JSP pages that are within the WEB-INF. Make sure that
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 1.4b[2, 3, 4,
or the cvs head] autonomously running under WAS 4.0.6.  We have several
work-arounds that allow us to get it running with a bit of help, such as
precompiling all of the JSP, but we would much prefer to just add new
jsp-based portlets and have them run without going through extra steps.
This would grealy simplify the dev/deploy cycle for us.  The primary
problem we are getting is about the taglib not being  found.  Here are
the first few lines of the exception:

Error encountered processing a template:
/portlets/html/hello.jsporg.apache.jasper.JasperException:
C:\WebSphere\AppServer\installedApps\jetspeed14b2.ear\jetspeed.war\WEB-
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


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]










Reply via email to