[weld-dev] Fwd: [JBoss JIRA] (WELD-510) Support for Portlet 2.0

[Pete Muir]

Guys, We still don't have portlet support? Ales, can you work with Marko on this as you are close to each other?

Begin forwarded message:

> From: "Adam Michalik (JIRA)" <jira-events at lists.jboss.org>
> Subject: [JBoss JIRA] (WELD-510) Support for Portlet 2.0
> Date: 20 April 2012 19:13:17 GMT+05:30
> To: pmuir at bleepbleep.org.uk
> 
> 
>    [ https://issues.jboss.org/browse/WELD-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12686068#comment-12686068 ] 
> 
> Adam Michalik edited comment on WELD-510 at 4/20/12 9:41 AM:
> -------------------------------------------------------------
> 
> I have attached a test project.
> 
> Steps to reproduce:
> 1) Download Liferay Portal Community Edition 6.1.0 CE budled with Tomcat from http://www.liferay.com/downloads/liferay-portal/available-releases
> 2) Unpack to - let's call it - ${LIFERAY_HOME}
> 3) Start Liferay with {LIFERAY_HOME}/tomcat-xxx/bin/startup.sh
> 4) Go to http://localhost:8080 to finish setup
> 5) Unzip the attached project, run mvn package
> 6) Copy the war file to ${LIFERAY_HOME}/deploy
> 7) Log in as the admin user and add the weld-510 portlet
> 8) Observe stacktrace in Liferay's logs ({LIFERAY_HOME}/tomcat-xxx/logs/catalina.out)
> 
> The portlet works fine without Weld:
> 1) In web.xml disable the WeldCrossContextFilter filter and filter-mapping
> 2) In HelloWorld class toggle from @Model to @ManagedBean
> 3) run mvn package -P!weld
> 4) deploy to Liferay
> 5) The portlet appears fine
> 
>      was (Author: hattifnat):
>    Steps to reproduce:
> 1) Download Liferay Portal Community Edition 6.1.0 CE budled with Tomcat from http://www.liferay.com/downloads/liferay-portal/available-releases
> 2) Unpack to - let's call it - ${LIFERAY_HOME}
> 3) Start Liferay with {LIFERAY_HOME}/tomcat-xxx/bin/startup.sh
> 4) Go to http://localhost:8080 to finish setup
> 5) Unzip the attached project, run mvn package
> 6) Copy the war file to ${LIFERAY_HOME}/deploy
> 7)Log in as the admin user and add the weld-510 portlet
> 8) Observe stacktrace in Liferay's logs ({LIFERAY_HOME}/tomcat-xxx/logs/catalina.out)
> 
> The portlet works fine without Weld:
> 1) In web.xml disable the WeldCrossContextFilter filter and filter-mapping
> 2) In HelloWorld class toggle from @Model to @ManagedBean
> 3) run mvn package -P!weld
> 4) deploy to Liferay
> 5) The portlet appears fine
> 
>> Support for Portlet 2.0
>> -----------------------
>> 
>>                Key: WELD-510
>>                URL: https://issues.jboss.org/browse/WELD-510
>>            Project: Weld
>>         Issue Type: Feature Request
>>   Affects Versions: 1.0.1.Final
>>           Reporter: Neil Griffin
>>           Assignee: Marko Strukelj
>>           Priority: Blocker
>>            Fix For: 1.1.3.Final
>> 
>>        Attachments: weld-510.zip
>> 
>> 
>> There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue.
>> Original Post:
>> http://www.portletfaces.org/community/forums/-/message_boards/message/43041#_19_message_43038
>> Here is a simple stacktrace of the problem:
>> Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment
>> at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119)
>> at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener
>> The code for the bridge API is here:
>> http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.bridge.api/
>> The code for the bridge IMPL is here:
>> http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.bridge.impl/
>> And the code for a sample portlet is here:
>> http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-application-portlet/
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
>