[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9232) JBoss 7: JSF 2 apps stop working

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Mon Jun 27 11:26:23 EDT 2011


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

Max Rydahl Andersen commented on JBIDE-9232:
--------------------------------------------

yes, for M3 we will as a *minimum* exclude the jsf 1.x api.

And thanks for finding the issue - we'll do *something* for M3, but for M2 we will have to live with this annoying bug unfortunately ;(

> JBoss 7: JSF 2 apps stop working
> --------------------------------
>
>                 Key: JBIDE-9232
>                 URL: https://issues.jboss.org/browse/JBIDE-9232
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.3.0.M1
>            Reporter: Juergen Zimmermann
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.M3
>
>
> I'm using JBossTools 3.3_stable_branch.aggregate-Update-2011-06-18_05-30-41-H2.
> Now I tried the latest Jenkins Build 1267 of JBoss 7 and I'm getting a classpath issue regarding JSF 2: JBoss Tools is including 
> * jsf-api-1.2_13.jar from modules/javax/faces/api/1.2
> * jboss-jsf-api_2.0_spec-1.0.0.Final.jar from modules/javax/faces/api/main
> It looks like the 1.2 stuff is included earlier in the classpath, so that e.g. ExternalContext.getFlash(), ExternalContext.invalidateSession() or Application.createComponent(FacesContext,String,String) are not available.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list