I am not
sure that splitting it up in 10 classes would be necessarily cleaner.
However I am open to suggestions.
Ivelin
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 28, 2002 8:28 AM
Subject: Antwort: Re: Creating dynamic content u
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 29, 2002 6:47 AM
Subject: Re: Antwort: Re: Creating dynamic content using JSP like Tag
implementation
> From: "Nicola Ken Barozzi" <[EMAIL PROTECTED]>
> > From: "Konstantin Piroumian" <
From: "Nicola Ken Barozzi" <[EMAIL PROTECTED]>
> From: "Konstantin Piroumian" <[EMAIL PROTECTED]>
>
> > Anyway, I'd like to see your extension in scratchpad.
> >
> > Team, do we need a vote for this?
>
> There is no need for a vote to use the scratchpad.
> That's why it's called scratchpad ;-)
Ye
From: "Konstantin Piroumian" <[EMAIL PROTECTED]>
> Anyway, I'd like to see your extension in scratchpad.
>
> Team, do we need a vote for this?
There is no need for a vote to use the scratchpad.
That's why it's called scratchpad ;-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
> Hi,
>
> yes, I think you already described the benefits:
> - Easily add new elements.
> - Modular.
> - No "if else" cascade in startElement and endElement.
> - only one Transformer needed in a pipeline for different
transformation.
This also looks very similar to the TreeProcessor that
Hi,
yes, I think you already described the benefits:
- Easily add new elements.
- Modular.
- No "if else" cascade in startElement and endElement.
- only one Transformer needed in a pipeline for different transformation.
In our "WorldAccount" project we already had implemented a "TextTa
Ivelin,
we have for the moment no implementation of a IteratorTag. I thought often
about an implementation and I think that we can implement it similarly as in the
current
JSP Jakarta taglib Implemtierung (http://jakarta.apache.org/taglibs/). If you
are interested, look at the current CVS "jaka
