Hi all,
I think Webapp Commons is a great idea. I'm no Apache committer but I'd be 
more than happy to contribute these two little reusable components:

http://purl.org/net/flavio/xslt-servlet.html
http://purl.org/net/flavio/http-headers-filter.html

They are licensed under the Apache license 2.0 and the dependencies are from 
Jakarta Commons.

Regards,
Flavio


On Sunday 19 June 2005 19:26, Martin Cooper wrote:
> On Sun, 19 Jun 2005, Glenn Nielsen wrote:
> > My initial reaction to this proposal is positive. I will hold off
> > on giving a +1 until there has been time for more discussion and
> > a more formal proposal.
> >
> > Other than taglibs how many other existing components are there for
> > Webapp Commons?
>
> There are a couple of components in the Jakarta Commons sandbox that would
> move over to a Webapp Commons. It has also been suggested that some
> add-ons from projects such as Tomcat could move there. And at least one
> non-committer has expressed interest in contributing things like filters
> and listeners.
>
> > Would Webapp Commons widgets be restricted to specific web application
> > frameworks or would it be wide open?
>
> I think the general idea is that it would be for framework-independent
> components. Anything that's intended for a specific framework would be
> more appropriately developed along with the framework rather that in
> Webapp Commons.
>
> --
> Martin Cooper
>
> > Regards,
> >
> > Glenn
> >
> > On Tue, Jun 14, 2005 at 08:53:47AM -0700, Martin Cooper wrote:
> >> 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]
> >
> > ----------------------------------------------------------------------
> > Glenn Nielsen             [EMAIL PROTECTED] | /* Spelin donut madder    |
> > MOREnet System Programming               |  * if iz ina coment.      |
> > Missouri Research and Education Network  |  */                       |
> > ----------------------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to