On Wed, 09 Oct 2002, Will Jaynes wrote:
It seems to me that the problem is that you are trying to do everything
in the JSP without benefit of using an Action. The Action is where this
kind of processing should take place. (Some developers would push it
further, into Business Objects, but
Well, if you insist :-) Remember that you can include Java in a JSP, so
after defining your form and the db bean you can write any Java that you
want.
jsp:useBean id=myForm type=myPackage.MyForm /
jsp:useBean id=dbBean type=myPackage.DbBean /
%
dbBean.setSelectionCriteria(
Will Jaynes [EMAIL PROTECTED] wrote:
Well, if you insist :-) Remember that you can include Java in a JSP, so
after defining your form and the db bean you can write any Java that you
want.
jsp:useBean id=myForm type=myPackage.MyForm /
jsp:useBean id=dbBean type=myPackage.DbBean /
%
So the form bean is in the session, right. If the db bean is going to be
able to get at the form then you'll need to pass the session object to
the db bean, then use the session object's getAttribute method to get
the form. But you don't want to go there...
Markus Herrmann wrote:
Will
Hello Struts users,
i have a JSP whose form data is stored in an ActionForm bean (as it should be).
The ActionForm bean sets the form data to default values (e.g. it gets todays
date). The JSP not only displays the form, but also displays data which comes
from a DB bean. In the JSP I use the
It seems to me that the problem is that you are trying to do everything
in the JSP without benefit of using an Action. The Action is where this
kind of processing should take place. (Some developers would push it
further, into Business Objects, but they would still be called from the
Action.)
6 matches
Mail list logo
