On Oct 23, 2005, at 10:57 PM, Igor Vaynberg wrote:
There are two problems with creating a spring web page factory:
1) pages get serialized and you don't want to serialize all the
enjected
deps along with it, so you need a mechanism that reinjects the
dependencies
whenever a page is activated - or whenever a page references
another page
that has been serialized. This can be difficult to achieve
transparently and
can get expensive.
All Wicket needs to do is provide an extension point. I'm sure it is
already in there actually.
2) to use the page factory your pages can only have the default or
PageParameter constructors. This prevents you from doing things like
setResponsePage(new EditUserPage(userId));
I understand the problem. I think AOP in combination with either
Annotations or a definition in the spring context is a solution here.
No need for a factory then. I don't like to add more infrastructure.
Only if it is hidden.
S.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
