If you use Cocoon as your portal then you configure "Cocoon portlets"
(coplets). Typically, these are configured with the pipeline they are
to execute to render the portlet content.
If you want to invoke Cocoon pipelines from some other portal then they
need to be invoked as JSR-168 portlets via the CocoonPortlet.
Ralph
Goetzmann Bertrand wrote:
Thank you Ralph,
About your last sentence : "You do not need CocoonPortlet to use Cocoon pipelines
within the portal", does this concern Cocoon as a portal or using Cocoon pipelines
in an other portal ?
Regards.
Bertrand.
-----Message d'origine-----
De : Ralph Goers [mailto:[EMAIL PROTECTED]
Envoyé : mardi 24 janvier 2006 23:27
À : [email protected]
Objet : Re: Questions about Cocoon and the Portlet API
Yes, Cocoon can be a portlet container.
Yes, CocoonPortlet allows you to use Cocoon in some other portal.
You do not need CocoonPortlet to use Cocoon pipelines within the portal.
HTH
Ralph
Goetzmann Bertrand said:
Hi,
I have simple questions about relation between Cocoon and the portlet
API :
- Does Cocoon can act as a portlet container ?
- The org.apache.cocoon.portlet.CocoonPortlet class seems to be a
portlet : does a cocoon portlet can be deployed in a compliant portlet
container, in order to have a complete Cocoon application included in
a portlet ?
Thank you.
Regards.
Bertrand Goetzmann.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
