with Struts.
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 21, 2001 8:03 AM
Subject: Re: [EJB] Design Patterns (was JavaReport ...)
What I'm working on now are patterns for Struts development that can be
used with or without Enterprise
PROTECTED]
Sent: Thursday, June 21, 2001 8:03 AM
Subject: Re: [EJB] Design Patterns (was JavaReport ...)
What I'm working on now are patterns for Struts development that can be
used with or without Enterprise Beans. As mentioned, the J2EE blueprints
are mostly about development patterns
The ActionForm beans can contain nested references, so you could just
set some other bean to it, then refer to myBean.propertyThis and
myBean.propertyThat. Of course, the other bean would have to have
standard String accessor and mutators, which is where it starts to fall
down. The other beans
-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 9:04 AM
To: [EMAIL PROTECTED]
Subject: Re: [EJB] Design Patterns (was JavaReport ...)
The ActionForm beans can contain nested references, so you could just
set some other bean to it, then refer to myBean.propertyThis
Why is it that each bean (includeing the containing bean) could not have
BOTH String get/set and also native type get/set?
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 21, 2001 9:03 AM
Subject: Re: [EJB] Design Patterns
They could. This is especially convenient when your value object bean
contains a RowSet, since the *String versions are already built in. So,
you end up with something like
thisForm.set(
thisValue.getItemString(),
thisValue.getDonorString(),
On Thu, 21 Jun 2001, Jonathan wrote:
Why is it that each bean (includeing the containing bean) could not have
BOTH String get/set and also native type get/set?
You can only do this if you use different property names for the same
property. Otherwise, you'll get compile errors on
7 matches
Mail list logo
