Also, it would be nice for servers to be able to implement
bean-pooling. If I have a "page" lifespan bean, that means
one bean is created per page.... it would be more efficient
if the server could pool these beans.
The specification could define a method... say "public void
reinit()" that, if present in the bean would allow the server
to pool the bean. The server would call reinit() prior to
reusing the bean.
The pooling mechanism makes sense only for "page" lifespan
beans, since you can detect when the page is done.
Pooling will become more important as JSP begins to support
EJB. Pooling stateless Session beans would dramatically
improve performance, since communication with the EJB server
may take place over a network.
-eric
> Mark Minnoye wrote:
>
> Is there -or shouldn't there- be a tag to call a different constuctor
> than the defaultconstructor of a bean. For example a bean with the
> constructor :
> public aBean(int i){ //get the values of that bean with key i from a
> dbase}
>
> and then in the JSP-page:
> <usebean name="myBean" type="aBean" lifespan="session">
> <setoncreate="int"> // ofcourse setoncreate is not a good example
> since it already exists
> </usebean>
>
> Mark
===========================================================================
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".
