I wouldn't recommend trying to do it via WSRP. I would recommend
looking at http://wiki.apache.org/cocoon/CocoonAppAsJSR168Portlet.
Ralph
On Nov 4, 2009, at 11:42 PM, Paul Adriaenssens wrote:
We would like to expose parts of our cocoon 2.1.11 application as
portlets and consume them in a LifeRay portal application.
The cocoon application is deployed in a JOnAS (+Tomcat) J2EE server,
while the LifeRay environment runs on a different host in the same
LAN.
Is this realistic, what would be possible, what not?
Kind regards,
Paul
Andreas Kuehne wrote:
Hi Jos,
I would like to know about anything that's possible !
Always prefer to do a PortLet in Cocoon ...
Greetings
Andreas
----- Original Message ----
From: Jos Snellings <[email protected]>
To: [email protected]
Sent: Thu, October 29, 2009 1:50:50 PM
Subject: Re: cocoon 2.1 as WSRP producer?
Mmm, do you need all of the spec?
validation caching? authentication?
What do you really need?
Jos
On Thu, 2009-10-29 at 10:29 +0000, Paul Adriaenssens wrote:
Hi,
We have already read the documentation, but it only speaks about
consuming WSRP portlets. We want to integrate our Cocoon
application with Liferay, and therefore Coccoon 2.1.11 needs to be
WSRP-enabled as producer. Does anybody know if this is possible?
Thanks,
Best regards,
Paul Adriaenssens
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
