Re: [gatein-dev] Make portlet_2_0.tld manageable in GateIn BOM
hi,
I have a couple of minor concerns (before making up my mind):
1/ are the BOM today compatible with all versions of GateIn or are they still JBoss AS7
specific ?
2/ keep in mind that the TLD is vendor specific because it contains links to the actual
portlet container codebase.
For example:
<name>param</name>
<tag-class>org.gatein.pc.portlet.impl.jsr286.taglib.URLParameter286Tag</tag-class>
<body-content>empty</body-content>
I don't know how that will behave in IDE.
On May 13, 2013, at 3:10 PM, Peter Palaga <ppalaga(a)redhat.com> wrote:
Hi *,
Background
----------
ATM, the tag library descriptor for http://java.sun.com/portlet_2_0
resides in org.gatein.pc:pc-portlet. Therefore customers using the
portlet_2_0 taglib in their JSPs need to depend on
org.gatein.pc:pc-portlet so that their IDEs (including Eclipse and
NetBeans) can provide validation and content assist for the related tags.
Problem
-------
The customers need to manage the version of org.gatein.pc:pc-portlet
themselves which is unconfortable and a little bit error prone.
Solution Proposal
-----------------
The customers are supposed to import GateIn BOM in their projects, so it
would be handy for them to get some kind of help from there. Namely,
there could be an artifact managed in GateIn BOM that would contain
portlet_2_0.tld.
We can either
(a) use an artifact that is already there, e.g. gatein-api
or
(b) perhaps create a new dedicated artifact.
Bolek said that he prefers (a) rather than (b). Any comments?
Best,
Peter
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev