Alex If you pipeline is call from a coplet with the cocoon pseudo protocol, you don't need this action, because the portal object model is already in memory. This action is useful only if you need to access coplet attributes from another pipeline. You need to say which coplet instance you will use. Bookmark a portal is not a piece of cake. Hopefully the new portal engine, comes since Dec 2003, comes with a powerful bookmark/history feature. History, here, is the capability to retrieved a previous page viewed, with the following URL http://localhost:8080/MyWebSite/portal/bookmark?history=n, where n the portal-action number. On each page viewed the portal store all coplets attributes. For example, if you have a coplet that display a document based on a docId, put in in attribute, instead of read it from the request parameter. If you go backward your history, you will see the right coplet content. Laurent
> Hi Laurent, > > I can probably convert my coplets to be inside a > single match -- I was hoping to awoid rework and stick > with my old model. By the way, can you explain how > portal-object-model action works? Also you have > mentioned something about portal history in one of > your previous e-mails, what is it? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
