You can put your business logic elsewhere.
Say:
1. Project Wicket GUI
2. Project Business Logic
Minimum business logic into wicket gui or gui constructors.
**
Martin
2010/8/14 Brown, Berlin [GCG-PFS] berlin.br...@primerica.com:
What is the best practice for where to put business logic in Wicket.
At first, I had put logic in the page constructor, but now I have
learned a little bit about the Lifecycle of a page, the serialization of
the page. So putting any kind of logic there didn't seem like a good
idea.
I placed logic in the action buttons onSubmit methods and form onSubmit
methods.
Placing any logic here in the onSubmits methods are OK, but sometimes it
is difficult to find all the dependent objects.
I gues I am used to a Struts MVC approach, where you have one Page
action and then communicate with all of your dependent objects (say a
form bean with all of the data);
With Wicket, I see these issues:
1. When will the page constructor get invoked (should any kind of
business logic be placed here?)
2. Where and when will the onSubmit/onUpdate action methods get invoked
(should any business logic be placed here and are all the dependent
objects available)
Berlin Brown
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
