Cactus and Portlet
Hello, I've been looking for portlet support within Cactus. I didn't find anything related to it on the Cactus web page... but consulting the mailing list showed me that two guys (Vincet Massol and John Rousseau) have been working on it... Can anybody tell me (perhaps you, Vincent or John) if a Portlet-Cactus API is available now? Cheers Vladimir Altuna - EDIFIXIO
RE: Cactus and Portlet
Hi Valdimir, -Original Message- From: Vladimir Altuna [mailto:[EMAIL PROTECTED] Sent: vendredi 10 juin 2005 16:43 To: cactus-user@jakarta.apache.org Subject: Cactus and Portlet Hello, I've been looking for portlet support within Cactus. I didn't find anything related to it on the Cactus web page... but consulting the mailing list showed me that two guys (Vincet Massol and John Rousseau) have been working on it... Can anybody tell me (perhaps you, Vincent or John) if a Portlet-Cactus API is available now? No it's not. I remember John and another person a long time before were interested in that topic but I don't believe there has been progress (I haven't seen it as least). Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cactus and portlet integration
Hi Oleg, (cc-ing the Cactus user list so that everyone interested can participate) I'd say it's not possible as is simple because a Portlet is NOT a Servlet. It has a different specification and a different lifecycle. That said, it would be relatively easy to build a PortletTestCase and associated objects. For now your best solution is to use mock objects and functional testing. Thanks -Vincent _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: mercredi 11 mai 2005 13:58 To: [EMAIL PROTECTED] Subject: cactus and portlet integration Hi Vincent! Looked through the Cactus site, and noticed your 1 year old discussion concerning integration of Cactus and Portlets. It didn't answer the question how to do the actual integration, and whether it is possible now. Right now we are looking for some tool to test Portlet applications, do you know if Cactus is capable of that? Thanks in advance!
RE: cactus and portlet integration
Hi Oleg, (cc-ing the Cactus user list so that everyone interested can participate) I'd say it's not possible as is simple because a Portlet is NOT a Servlet. It has a different specification and a different lifecycle. That said, it would be relatively easy to build a PortletTestCase and associated objects. For now your best solution is to use mock objects and functional testing. Thanks -Vincent _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: mercredi 11 mai 2005 13:58 To: [EMAIL PROTECTED] Subject: cactus and portlet integration Hi Vincent! Looked through the Cactus site, and noticed your 1 year old discussion concerning integration of Cactus and Portlets. It didn't answer the question how to do the actual integration, and whether it is possible now. Right now we are looking for some tool to test Portlet applications, do you know if Cactus is capable of that? Thanks in advance!
RE: cactus and portlet integration
Vincent, The most difficult part of portlet cactus testing is the portlet application URL, that is changing from deployment to deployment. So, the question was more about automating the task of identifying the correct URL for the tested portlet app, not implementation of the test. We work with WebSphere, probably it's not a general portlet issue, but just IBM portal implementation that makes our life so hard. I'm not sure about that, would be glad to have any info on that. Thanks! --- sincerely yours, Oleg Mikheev Gemini Systems SPB Vincent Massol [EMAIL PROTECTED] 11-05-05 16:09 To [EMAIL PROTECTED] cc 'Cactus Users List' cactus-user@jakarta.apache.org Subject RE: cactus and portlet integration Hi Oleg, (cc-ing the Cactus user list so that everyone interested can participate) I?d say it?s not possible as is simple because a Portlet is NOT a Servlet. It has a different specification and a different lifecycle. That said, it would be relatively easy to build a PortletTestCase and associated objects. For now your best solution is to use mock objects and functional testing. Thanks -Vincent From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: mercredi 11 mai 2005 13:58 To: [EMAIL PROTECTED] Subject: cactus and portlet integration Hi Vincent! Looked through the Cactus site, and noticed your 1 year old discussion concerning integration of Cactus and Portlets. It didn't answer the question how to do the actual integration, and whether it is possible now. Right now we are looking for some tool to test Portlet applications, do you know if Cactus is capable of that? Thanks in advance!
RE: cactus and portlet integration
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] systems.ru] Sent: mercredi 11 mai 2005 15:24 To: [EMAIL PROTECTED] Cc: 'Cactus Users List' Subject: RE: cactus and portlet integration Vincent, The most difficult part of portlet cactus testing is the portlet application URL, that is changing from deployment to deployment. So, the question was more about automating the task of identifying the correct URL for the tested portlet app, not implementation of the test. We work with WebSphere, probably it's not a general portlet issue, but just IBM portal implementation that makes our life so hard. I'm not sure about that, would be glad to have any info on that. Sorry but I don't know anything about Portlets :-) That said if the URL is something that is container-specific it shouldn't be an issue. We could make it a Cactus property in the Cactus framework and the URL would be set automatically in the Ant and Mavne integrations for example. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cactus and portlet integration
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] systems.ru] Sent: mercredi 11 mai 2005 15:24 To: [EMAIL PROTECTED] Cc: 'Cactus Users List' Subject: RE: cactus and portlet integration Vincent, The most difficult part of portlet cactus testing is the portlet application URL, that is changing from deployment to deployment. So, the question was more about automating the task of identifying the correct URL for the tested portlet app, not implementation of the test. We work with WebSphere, probably it's not a general portlet issue, but just IBM portal implementation that makes our life so hard. I'm not sure about that, would be glad to have any info on that. Sorry but I don't know anything about Portlets :-) That said if the URL is something that is container-specific it shouldn't be an issue. We could make it a Cactus property in the Cactus framework and the URL would be set automatically in the Ant and Mavne integrations for example. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
