You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-user@portals.apache.org by "Chamberlain James O. CONTR J9C998" <Ja...@je.jfcom.mil> on 2004/03/05 16:02:59 UTC
Question on taglib tld placement
Any reason why the portlet taglib tld file is not bundled into the pluto
jar? If it was included in the jar then it would not be necessary map it
in the portlet's web.xml. I like to test my portlets in different
containers which requires me to include the portal container's specific
tld in my portlet webapp. It would be nice if I didn't have to do this
step. Any reason why this is a bad idea?
Regards,
James
Re: Question on taglib tld placement
Posted by Ken Weiner <kw...@unicon.net>.
+1 from me too. Also, as I posted a while ago on this list, I think
some kind of support for deployment should go into the container since
the deployment requirements are uniquely defined by the container (the
way in which web.xml should get re-written with wrapper servlet
definitions).
-Ken
Martin Cooper wrote:
> +1 for packaging the TLD inside the jar. I can't think of any reason not to
> do this, and it does make for simpler deployment.
>
> --
> Martin Cooper
>
>
> "Chamberlain James O. CONTR J9C998" <Ja...@je.jfcom.mil> wrote
> in message
> news:1D317DC2764EAA4F8F52741F125A827B28DB2D@postman.j9.root2k.local...
> Any reason why the portlet taglib tld file is not bundled into the pluto
> jar? If it was included in the jar then it would not be necessary map it
> in the portlet's web.xml. I like to test my portlets in different
> containers which requires me to include the portal container's specific
> tld in my portlet webapp. It would be nice if I didn't have to do this
> step. Any reason why this is a bad idea?
>
> Regards,
>
> James
====
This message and any attachments are confidential. Unauthorized use
or disclosure of this message is strictly prohibited, and this message
must be destroyed immediately if received by an unauthorized recipient.
====
Re: Question on taglib tld placement
Posted by Joseph Ottinger <jo...@enigmastation.com>.
Um... isn't the pluto .jar file supposed to be placed outside of a webapp?
Wouldn't this affect the referencing of the .tld?
On Fri, 5 Mar 2004, Martin Cooper wrote:
> +1 for packaging the TLD inside the jar. I can't think of any reason not to
> do this, and it does make for simpler deployment.
>
> --
> Martin Cooper
>
>
> "Chamberlain James O. CONTR J9C998" <Ja...@je.jfcom.mil> wrote
> in message
> news:1D317DC2764EAA4F8F52741F125A827B28DB2D@postman.j9.root2k.local...
> Any reason why the portlet taglib tld file is not bundled into the pluto
> jar? If it was included in the jar then it would not be necessary map it
> in the portlet's web.xml. I like to test my portlets in different
> containers which requires me to include the portal container's specific
> tld in my portlet webapp. It would be nice if I didn't have to do this
> step. Any reason why this is a bad idea?
>
> Regards,
>
> James
>
>
>
>
-----------------------------------------------------------------------
Joseph B. Ottinger http://enigmastation.com
IT Consultant joeo@enigmastation.com
Editor-in-Chief - Java Developer's Journal josephottinger@sys-con.com
Re: Question on taglib tld placement
Posted by Martin Cooper <ma...@apache.org>.
+1 for packaging the TLD inside the jar. I can't think of any reason not to
do this, and it does make for simpler deployment.
--
Martin Cooper
"Chamberlain James O. CONTR J9C998" <Ja...@je.jfcom.mil> wrote
in message
news:1D317DC2764EAA4F8F52741F125A827B28DB2D@postman.j9.root2k.local...
Any reason why the portlet taglib tld file is not bundled into the pluto
jar? If it was included in the jar then it would not be necessary map it
in the portlet's web.xml. I like to test my portlets in different
containers which requires me to include the portal container's specific
tld in my portlet webapp. It would be nice if I didn't have to do this
step. Any reason why this is a bad idea?
Regards,
James
Re: Question on taglib tld placement
Posted by Stefan Hepper <st...@hursley.ibm.com>.
Jason Novotny wrote:
>
> I wonder if this is an issue I've encountered with Tomcat 4. We have
> a gridsphere-ui-tags.jar that includes the portlet tags plus our own
> user interface tags and it has to be placed in every webapp/WEB-INF/lib
> directory of the webapp that uses it-- for some reason about a year ago
> I discovered you couldn't just put them in shared/lib and have the
> webapp find them. I hope Tomcat 5 has fixed this.
>
> Jason
>
Yes, tomcat 5 has fixed this.
Stefan
Re: Question on taglib tld placement
Posted by Jason Novotny <no...@aei.mpg.de>.
I wonder if this is an issue I've encountered with Tomcat 4. We have
a gridsphere-ui-tags.jar that includes the portlet tags plus our own
user interface tags and it has to be placed in every webapp/WEB-INF/lib
directory of the webapp that uses it-- for some reason about a year ago
I discovered you couldn't just put them in shared/lib and have the
webapp find them. I hope Tomcat 5 has fixed this.
Jason
Stefan Hepper wrote:
> Chamberlain James O. CONTR J9C998 wrote:
>
>> Any reason why the portlet taglib tld file is not bundled into the pluto
>> jar? If it was included in the jar then it would not be necessary map it
>> in the portlet's web.xml. I like to test my portlets in different
>> containers which requires me to include the portal container's specific
>> tld in my portlet webapp. It would be nice if I didn't have to do this
>> step. Any reason why this is a bad idea?
>> Regards,
>>
>> James
>>
>>
>>
>
> I've no objections against bundle the tld with the pluto jar, however
> I think the issue was with tomcat 4 that still needed that you copy
> the tld file into the portlet web app at deployment time-
>
> I don't understand why you need to include the tld in the portlet app.
> The spec was written specifically the way that this is not required to
> allow each portal vendor to provide its own tld implementation.
>
> Stefan
>
>
Re: Question on taglib tld placement
Posted by Stefan Hepper <st...@hursley.ibm.com>.
Chamberlain James O. CONTR J9C998 wrote:
> Any reason why the portlet taglib tld file is not bundled into the pluto
> jar? If it was included in the jar then it would not be necessary map it
> in the portlet's web.xml. I like to test my portlets in different
> containers which requires me to include the portal container's specific
> tld in my portlet webapp. It would be nice if I didn't have to do this
> step. Any reason why this is a bad idea?
>
> Regards,
>
> James
>
>
>
I've no objections against bundle the tld with the pluto jar, however I
think the issue was with tomcat 4 that still needed that you copy the
tld file into the portlet web app at deployment time-
I don't understand why you need to include the tld in the portlet app.
The spec was written specifically the way that this is not required to
allow each portal vendor to provide its own tld implementation.
Stefan