--- [EMAIL PROTECTED] wrote:
> For maintainable code, look at the patterns I went
> into. If you are writing a very large application,
they
> will make your application easier to debug and
maintain
> in the future.
It's not so much that I'm unfamiliar with writing
large applications but that the
Sent: Friday, November 16, 2007 5:10 PM
To: Struts Users Mailing List
Subject: RE: Pass Javabeans
Wow, that was a lot of code.
The expurgated version is that in Struts 1 there are
two basic ways to do it: put the bean into a scope,
generally request or session, or set properties on
your Actio
Wow, that was a lot of code.
The expurgated version is that in Struts 1 there are
two basic ways to do it: put the bean into a scope,
generally request or session, or set properties on
your ActionForm (which itself is either request- or
session-scoped).
d.
--- [EMAIL PROTECTED] wrote:
> I would
I would look into the following Patterns:
BusinessDelegate , SessionFacade
For Database connectivity with EJBs you should also look at
servicelocator.
Typically what I do is:
Have an action:
To retrieve data from a database -- I pass all necessary
interface parameters to a BusinessDe
4 matches
Mail list logo
