DTO is a design that can be not only in J2EE.
I like the idea that Wicket can manipulate directly domain objects but
not to give many objects to wicket page's.
I like that
public class APage extends WebPage {
public APage(ADomainBean bean) {.. }
But not
public class APage extends
On Thu, 29 Nov 2007, Gervais wrote:
DTO is a design that can be not only in J2EE.
I like the idea that Wicket can manipulate directly domain objects but
not to give many objects to wicket page's.
When doing real remoting DTOs might make sense. With Wicket
pages I don't quite see how would
Hi wicketers,
I use Wicket since 2 weeks. Before wicket i have worked on many projects
(Swing or Web apps) and try to find the best architecture.
Now i'm learning Wicket and i have a big problem. I dont'like Data
Transferts Objects.
Many forms use more than one Bean, so i have asked you in a
Hi Gervais
Im not sure if you have understood the idea of the
CompoundPropertyModel(CPM). You pass a simple domain class to it and it
uses property expressions to retireve what ever requested. For example
if you set a CPM on a page you may add a label using this new
Label(label) this will
Hi,
A have already understand the idea of the CPM. But i think it is boring
to write another class just for handling some properties or beans.
But now i have read Core J2EE Patterns - Transfer Object[1] and DTO
can give me more than just handling some properties or beans. Now i
like Data
On Wed, 28 Nov 2007, Gervais wrote:
A have already understand the idea of the CPM. But i think it is boring
to write another class just for handling some properties or beans.
But now i have read Core J2EE Patterns - Transfer Object[1] and DTO
can give me more than just handling some
