> Yes, the "best practice" I have in mind is that the bundle that
> contains the
> PAGE that you want to LINK TO, registers the MenuItem for that
> Page. And that
> the bundle that own the Page where the Link will show up,
> instantiates and
> manages the Menu. ("Manage" in this context is primarily
> identification and
> rendering.)
>
> So, I don't think we are on different pages (pun intended) on this
> one. I
> perhaps need better explaination in the docs and the example will
> show what I
> mean in better detail.
Nice pun. He he.
This sounds good.
There's only one thing that I find a bit confusing. IIUC, your
meaning of "page" differs from the wicket meaning of "page". In
wicket, IIUC, each new page has it's own strategy for loading a
"border", which includes the css. In other words, a Page is a special
kind of Component that provides additional resources beyond what most
Components provide.
In pax-wicket, a "page" can be any component.
Anyway, this is a bit confusing to mere mortals such as myself. Can
we think about changing the name from "page" to something else? Like
maybe PaxComponent or whatever?
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
