It looks like you are looking for cohesion.
In the class menupanel.java I must reference PageXXXX
In the class PageXXXX.java I must reference MenuPanel

menupanel can to be an parameter to PageXXX; PageXXX can to be abstract and
have an abstract method :
abstract protected Page
getPageToSetOnReturnOnCase1Case2And3(PossibleParameter p);

noted that in the examples there is a circular reference between Checkout
page and Index page
on the example the objects has an reference to the other type class. And the
class object do not has an reference those objects. I don't see it as
circular reference.

Are circular references unavoidable with Wicket?
do they are unavoidable in java, in object oriented paradigm? Is this the
correct question?

Is there a best practive to avoid this situation?
When I avoid an circular reference, I make a choice between a several
possible solutions, the on I get depends on the class objectives


On Wed, Sep 23, 2009 at 7:21 AM, Giovanni Cuccu
<giovanni.cu...@cup2000.it>wrote:

> Hi all,
>        I'm developing a wicket application and I'm facing a problem.
> I built a menupanel that shows the menu to access the various aplication
> pages; since the panel needs to show the pages it contains a list of links
> that when clicked simply do the the following
>        setResponsePage(new PageXXXX());
> In the class menupanel.java I must reference PageXXXX
> In the class PageXXXX.java I must reference MenuPanel
> At the end I have a circular reference between manupanel and the various
> PageXXXX and I don't like it.
> While reading wicketInAction I noted that in the examples there is a
> circular reference between Checkout page and Index page. Are circular
> references unavoidable with Wicket? Is there a best practive to avoid this
> situation?
> Thanks,
>        Giovanni
>
>
> --
> Giovanni Cuccu
> Via del Borgo di S. Pietro, 90/c - 40126 Bologna
> e-mail: giovanni.cuccu _at_ cup2000.it
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to