Kurt Williams wrote:
> True, in *Java* a bean and property can be any object, but to set it
> from a JSP <USEBEAN><SETFROM...></USEBEAN> tag, the property must be a
> string. Unless you place a JSP scriptlet <%... %> and set the bean
> property using Java, there is no way to set a bean's property to another
> bean. There's no way using tags alone to set a bean's property to
> reference another bean. The folks designing our pages have a tough
> enough time with all the HTML tags, let alone asking them to learn Java.
> We need support in the bean tags themselves for setting bean properties
> to reference beans, not just strings. Thus the new tag suggestion
> <SETFROMBEAN PROPERTYNAME="propertyName" BEANNAME="beanName">.
>
Take a look at IBM's BML (bean markup language). Sooner or later you will also
want
set properties, then to invoke methods with parameters, maybe even connect
event listeners.
Since the subject is "wish list":
In 0.92 they have a "processRequest()" method - and it is great, since you
can do
here whatever you can't do with the <bean> tag.
One big missing piece: you need a method "init(Servlet s)", that will let the
"JSPBean"
know what servlet it is working for ( or an extra Servlet parameter passed to
processRequest()).
It is very important to have access to ServletContext, log(), etc.
I assume the "correct" model is to have JSP pages with minimal Java, and
JSPBeans with all the "smart"
processing. It will not hurt to have processRequest() take also a
ServlerResponse parameter -
so it can set response headers for example.
Regards,
Costin
===========================================================================
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".
