On Oct 6, 2009, at 4:59 PM, Matt Wringe wrote:
Portlet TLDs on the JBoss AS version of GateIn was not working, so I
had
to renable the patch to specify the portlet war which contains the
portlet TLDs. [I don't know why the patch was missing, if there was a
reason for its absence please let me know]
It works differently in tomcat (to not say more conveniently), as
tomcat takes any TLD that it finds in the lib directory.
This means we have a patch to the
deployers/jbossweb.deployers/web.xml
to specify the jar containing the tlds (see
http://www.jboss.org/community/wiki/GlobalTLDs)
it would be nice in JBoss AS to have a better way to add global TLD
that do not require a patch of a file because we also have to keep the
web.xml file in our JBoss patch directory. Would it be possible to
have something that goes in that direction, like a deployment
descriptor that would be found by JBoss deployers and we would only
have to have the correct declaration in the JBoss patch directory.
> <init-param>
> <description>Portlet standard tlds</description>
> <param-name>tagLibJar2</param-name>
> <param-value>../../deploy/exoplatform.ear/pc-portlet-2.1.0-
> Beta1.jar</param-value>
> </init-param>
Can we change the jar name to be unversioned so that when the version
changes it doesn't break this?
you mean as a deploy time facility ?
as this jar contains code, maybe it would be best to copy the TLD in
another jar file at deploy time that would have a constant name.
Or can we specify a token instead of
hardcoding the jar name?
Or does anyone know a better way to add the tlds to the portlets on
JBoss AS?
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev