[seam-issues] [JBoss JIRA] Assigned: (SEAM-41) org.jboss.weld.exceptions.AmbiguousResolutionException in seam-booking example on Glassfish 3.0.1

[Shane Bryzak (JIRA)]

     [ https://issues.jboss.org/browse/SEAM-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Bryzak reassigned SEAM-41:
--------------------------------

    Assignee: Dan Allen


> org.jboss.weld.exceptions.AmbiguousResolutionException in seam-booking example on Glassfish 3.0.1
> -------------------------------------------------------------------------------------------------
>
>                 Key: SEAM-41
>                 URL: https://issues.jboss.org/browse/SEAM-41
>             Project: Seam 3
>          Issue Type: Bug
>          Components: Shared Examples
>         Environment: Seam3 CR2, glassfish 3.0.1
>            Reporter: Marek Schmidt
>            Assignee: Dan Allen
>             Fix For: 3.0.0.Final
>
>
> The seam-booking example in the CR2 distribution doesn't work on glassfish 3.0.1. After applying workarounds for known issues, the application deploys, but any attempt to login will produce:
> Caused by: org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318 Cannot resolve an ambiguous dependency between [org.jboss.weld.bean-/home/maschmid/java/glassfish3.0.1/glassfish/domains/domain1/applications/seam-booking/-ProducerMethod-org.jboss.seam.servlet.http.ImplicitHttpServletObjectsProducer.method getHttpSession(), org.jboss.weld.bean-weld-ProducerMethod-org.jboss.weld.servlet.HttpSessionManager.method getSession()]
> There is an apparent conflict between weld 1.0.1-SP3 in glassfish 3.0.1 and seam servlet, as both contain HttpSession producers.

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