Re: 1.1 and Adding a new tag to JSP

[Paul Siegmann <pauls@euronet.nl>]

Wes Biggs wrote:
> 
> In JSP 1.1, adding a new tag that would perform HTML encoding should be
> trivial, at which point you could do something like:
> <encode>Blah blah <%= foo.getBar() %> blah</encode>

I like this approach better.
but shouldn't that be <gnujsp:encode>...</gjnusjp:encode> or something?

> IMHO, the tag extension specification is very immature, and it provides
> only a glimmer of insight into how these things should actually be
> implemented (I have my own ideas, but I don't work for JavaSoft...)

maybe you should send them to the gnujsp-spec-comments address.
that way we could all benefit from them.

> Paul, I think you're wise to aim for 1.0 compliance right now given the
> state of the 1.1 spec.

The only reason I'm only implementing the 1.0 spec is because of the amount of
work involved. After I have a semi-workable 1.0 implementation or before that
if I'm confident enought with the design I'll start implementing 1.1 features.
One of the reasons for the current Dom-tree approach is that it will be really
easy (trivial) to implement the tag extension mechanism.

>  Still, I am foolish enough to try to implement
> tag extensions as an experimental branch off the experimental branch, if
> there's any interest.

The current parser fails on <jsp:...> ... </jsp:...> tags.
Could you either fix that first of wait until I've fixed it?

>  The basic changes to your excellent reworking of
> the parser would be to have it work with a set of
> TagLibrary/TagInfo/TagAttributeInfo objects as well as the hardcoded
> "jsp:*" tags
> (though the standard JSP libary could be an instance/subclass of TagLibrary).  I think this can be accomplished
> quite cleanly.

yes, keep talking baby.

> Based on these parsing instructions, the parser would
> create Tag and NodeData items as members of the generated servlet and
> reference them when needed in _jspService().

cool. I should spend some more time on the 1.1 specs.

> The tough part is actually making a sensible implementation based on the
> confused APIs JavaSoft is churning out.

which also differ from the javadocs. :-(
see for instance JspEngineInfo. is it getSpecificationInfo or
getImplementationInfo?

> I went ahead and coded up
> compilable but mostly nonfunctioning classes for everything in
> javax.servlet.jsp.tagext, which hopefully I will get improve upon soon.
> If anyone wants a snapshot, or wants to append it to classpathx-servlet,
> let me know.

I do. just send it to me and I'll add it.

regards,
			Paul

PS
really like your regexp classes. used them a lot on several projects with
great succes. thanks.