Carsten Ziegeler wrote:
Ralph Goers wrote:
Also, I thought you were proposing adding the events to the url as
well? If you are not, then I believe all we are discussing is whether
nav items are in the url or in a request parameter. That just becomes a
question of which we think is "prettier".
Yepp, this is more or less my point :)
Under the covers the
implementation has to be pretty similar. IMO, which isn't worth much in
this case, the url you provided above is kind of ugly. Also, what is
the page/index.html about?
Think of a forrest site done with the portal, you have some navigation
coplets,
perhaps some news coplets and the big area is the content copletshowing
the current document. Clicking a link from the navigation toggles the
content inside the content coplet. CHanging the content is done via
events, the id of the content coplet is "page" and index.html is the
document to display.
Unfortunately, I have no familiarity with forrest, but I think I
understand. IIUC, you are basically saying that page/index.html is data
for the target of the nav. I'm not crazy about this syntax, but
whatever floats your boat. Since it seems the functionality is pretty
much the same between the two then the best option is to divorce the
functionality from how it appears in the request. Then everybody can
just do their own thing.
Ah, ok, now you mentioned that you need marshalling in order to
get JSR 168 portlets running. I have several JSR 168 portlets running
without marshalling. Do you have a test case where this doesn't work,
cause I think it should work without marshalling.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33091
Unfortunately, I don't have a portlet handy that demonstrates this. I
guess you can try doing a page reload with your portlets and see what
happens.
Ralph
Carsten
