[weld-issues] [JBoss JIRA] Issue Comment Edited: (WELD-510) Support for Portlet 2.0

Brian Leathem (JIRA) jira-events at lists.jboss.org
Wed Jul 6 01:24:24 EDT 2011


    [ https://issues.jboss.org/browse/WELD-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612568#comment-12612568 ] 

Brian Leathem edited comment on WELD-510 at 7/6/11 1:23 AM:
------------------------------------------------------------

It's a shame that what seems like a relatively simple fix is being held up by waiting for the testing infrastructure in place.

This issue is becoming more of a concern as one of the considerations on the table for JSR-344 is to consider using CDI as the managed bean facility for JSF.  Until CDI/Weld can run everywhere where JSF currently runs (in this case portlets), then the existing JSF bean management facility is (@ManagedBean/@ManagedProperty) required.

Can we move forward with a fix, and come back to the test as a separate issue when the testing infrastructure is ready to support it?

      was (Author: bleathem):
    It's a shame that what seems like a relatively simple fix is being held up by waiting for the testing infrastructure in place.

This issue is becoming more of a concern as one of the considerations on the table for JSR-344 is to consider using CDI as the managed bean facility for JSF.  Until CDI/Weld can run everywhere where JSF currently runs (in this case portlets), then the existing JSF bean management facility is (@ManagedBean/@ManagedProperty) required.

Can we move forward with a fix, and come back to this issue when the testing infrastructure is ready to support it?
  
> 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.2.Final
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list