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 pro
a simple way to decouple the menu from the pages is to mount all the
pages and pass the mount urls into the menu instead of the page
classes.
that way you wont have any imports other then java.lang.String
-igor
On Fri, Sep 25, 2009 at 12:06 AM, Giovanni Cuccu
wrote:
> I have no problem other th
Best solution is "ignore circular dependencies" ;)
**
Martin
2009/9/25 Giovanni Cuccu :
> 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
>
>> what is the actual probl
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
what is the actual problem you are having with this other then "i dont like it"?
-igor
On Wed, Sep 23, 2009 at 3:21 AM,
Hi Giovanni,
I absolutely understand what you mean. I recently refactored some Swing
GUI code and also tried to remove the circular references.
The menu bar of the app's main frame needed a reference to this frame in
order to show a modal dialog on it.
The frame embeds the menu bar and therefo
what is the actual problem you are having with this other then "i dont like it"?
-igor
On Wed, Sep 23, 2009 at 3:21 AM, Giovanni Cuccu
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 aplicatio
Thanks for the response,
I try to clarify my point of view.
Before using wicket I don't remember that my classes were cross
references, I always paid attention that if class A references Class B
Class B can't reference Class A (even in imports).
After starting wicket development I've see
It looks like you are looking for cohesion.
In the class menupanel.java I must reference Page
In the class Page.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
getPageToSetOnReturn
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