Hi,
We have (in our team) the same thoughts :). We treat circular
references between packages as an error (bad architecture design) and
we use an automatic test case for all projects to check if there are
any cycles in packages. So project with such cycles does not pass the
tests.
It can be a problem in Wicket, when you are using base navigation
concept: setResponsePage(...). In my opinion, to use Wicket in more
complicated projects, it is good to first prepare a navigation
abstraction layer above the core Wicket mechanisms, and do not use
page class references directly (we are using actions for this, the
concept very similar to Delphi actions).
So instead write something like this:
Customer customer = customerModel.getObject();
new BookmarkablePageLink("someId", CustomerViewPage.class, new
PageParameters("id=" + customer.getId()));
I can write:
new ActionLink("someId", new ObjectAction(ActionType.INSPECT,
customerModel, Customer.class)));
and the rest is done "behind the scenes". Then the whole "circular
references" problem will gone :).
--
Daniel
On Fri, Sep 25, 2009 at 9:06 AM, Giovanni Cuccu
<giovanni.cu...@cup2000.it> wrote:
> I have no problem other than "i dont like it", but since I don't like it I'd
> like to know if someone else had the same thoughts I had and what was the
> conclusion.
> Giovanni
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
