My situation is not this type.I using CachedURICoplet to use my application.
Roy Huang ----- Original Message ----- From: "Christian Mayrhuber" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 30, 2004 7:15 PM Subject: Re: cl:links in cachingURI coplet ? > On Wednesday 30 June 2004 04:40, roy huang wrote: > > Hi Chris, > > I meet the similar situation.I don't understand "calling your pipeline > > from outside the portal".How to define a pipeline called in a portal ? And > > what need to do if I call a pipeline outside a portal? Can you describe it > > more in detail? Thanks > > If the PortalGenerator calls a coplet pipeline the portal environment is > already set up. That means coplet:#, coplet:attributes/MYATTR, portalName, > etc. is available. > If you directly call a coplet via the cocoon:/ protocol > (cocoon://PATH_TO_PORTAL/coplets/mycoplet/ or cocoon:/pipeline-in-my-coplet) > the portal environment is unkown, thus the CopletTransformer does not know > for which coplet to generate link events. > In this case you have to specify the portalName and copletId sitemap > parameters. > > -- > lg, Chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
