Portlet TLDs need to be configured in j2-admin's web.xml
--------------------------------------------------------
Key: JS2-1204
URL: https://issues.apache.org/jira/browse/JS2-1204
Project: Jetspeed 2
Issue Type: Bug
Components: Admin Portlets
Affects Versions: 2.2.1
Reporter: Woonsan Ko
Assignee: Woonsan Ko
Priority: Minor
Fix For: 2.2.2
When j2-admin app is deployed, the portlet TLD configurations are not added in
web.xml automatically because it already has Jetspeed container servlet
settings. However, this hasn't made any problem in Tomcat because Tomcat seems
to load all TLDs in JAR from every accessible classloader; this behavior is
slightly different from the JSP 2.0 Spec, where only jars in /WEB-INF/lib are
to be looked up. (The pluto portlet tag lib jar file is deployed onto the
shared lib path currently. I guess this was to conform the portlet spec,
"portlet container must provide an implementation of portlet tags", which may
be another issue.)
Also, in other servlet container platforms where the automatic deployment
option is not available, the missing TLD configurations in j2-admin's web.xml
has made problems.
So, at least, I think j2-admin should have the portlet TLD configurations by
default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
