Ted,
go get JRun and have a look at its Tagglets; JRun's JSP parser allows to
associate Servlets with new tags; this seems an excellent idea and an
example of how to do it.
I wish JSP 1.0 would have something like this - I don't want my own
JSP-pages having to
create all the <select>..<option>..</option>..</select> stuff etc, but
rather delegate this to some utility classes. And I don't want my _data_
beans to do that. Maybe taglets could be a way for this. Having utility
beans be able to refer to data beans would also help.
bye,
Werner
> -----
> Betreff: Re: JSP Spec enhancment
>
> Uh, what extensible tags?
> We developers listening to this list haven't heard a thing about plans for
> extensible tags (or did I miss something?).
> If an extensible tag mechanism is going to be part of the next
> release then
> that's great but we would also like to know what's going on.
>
> ted stockwell
>
> > -----Original Message-----
> > From: Abhishek Chauhan [SMTP:[EMAIL PROTECTED]]
> > Sent: Friday, March 05, 1999 2:29 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: JSP Spec enhancment
> >
> > Steve,
> >
> > With the advent of extensible tags in JSP such features get out of the
> > scope of the JSP spec, and into that of extensible tags. JSP would
> > come with a set of standard tags that would be available on all JSP
> > implementations.
> >
> > Extensible tags will allow JSP users / Tag Library Providers to
> > provide custom tags that look and feel just like regular JSP tags.
> > The tag provider would be able to implement whatever behaviour they
> > want out of the tag. In particular, I think it is possible to
> > implement your suggestion as a custom tag.
> >
> > -abhishek
> >
> > steve barrett wrote:
> > > I would like to something that provided the following features:
> > > 1) Swing components could be placed within the page using something
> > > like <input .. BEAN TYPE="JTable">
> > >
> > > 2) These components shared an applet context so any behavior you could
> > > get from an applet could be coded (scripted would be too good to be
> > > true)
> > > a) data validation logic where emptiness, or date
> > > validation, or amount checking could be done
> > > b) business logic - examples:
> > > 1. where components would be disabled because
> > > a radio button was not selected
> > > 2. if there was a zip code then city/state could
> > > be set
> > > 3. if some field held the int value 9 then some
> > > other field had to be blank or perhaps an
> > > int value 1-5
> > >
> > > 3) some kind of application bean that could provide access to session
> > > beans from multiple browser windows
> > >
> > > Can any of this already be done?
> >
>
> ==================================================================
> =========
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
