Over in Jakarta Commons, there has been some discussion over the last
couple of months about proposing the creation of a new Jakarta subproject,
tentatively named Webapp Commons. This came about as a result of proposals
to add servlet filters and other handy webapp-building widgets as Jakarta
Commons components, and the recognition that these do not really fit the
charter of Jakarta Commons.
So the idea was floated of creating a new Webapp Commons subproject that
would have just such a charter - commonly used widgets for building web
applications, including filters, listeners, and other such utility code.
What does this have to do with Jakarta Taglibs? Well, there was also a
discussion recently on the degree to which Taglibs is alive, and more
importantly, healthy. I think everyone here would agree that the community
here is not as healthy as it could be, with only a small number of taglibs
really being developed, and many languishing.
So a suggestion was made that Jakarta Taglibs could morph into a part of
the new WebApp Commons subproject. Not only would this bring it together
with other webapp-building components, but it has the potential to bring
fresh blood to Taglibs and revitalise the community.
What say you, Taglibs developers? Would this community be interested in
becoming a part of a larger Webapp Commons community, and sharing ideas
and code on more than just tag libraries?
Personally, I am very much +1 on this proposal.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
