0 Replies Latest reply on Jan 7, 2010 4:55 PM by daniele campanini

    Multiple seam application on websphere 7

    daniele campanini Newbie

      Hi,
      I developed two applications with seam and I need to run both on websphere 7. When i try o access to one of them i got a exception like this:



      com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is com.ibm.websphere.ejbcontainer.AmbiguousEJBReferenceException: The short-form default binding 'org.jboss.seam.transaction.LocalEjbSynchronizations' is ambiguous because multiple beans implement the interface : app1 jboss-seam-WS.jar EjbSynchronizations, app2 jboss-seam-WS.jar EjbSynchronizations. Provide an interface specific binding or use the long-form default binding on lookup.
              at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:1014)
              at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:175)
              at com.ibm.ws.naming.urlbase.UrlContextImpl.processBoundObjectForLookup(UrlContextImpl.java:1736)
              at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1249)
              at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1225)
              at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1276)
              at javax.naming.InitialContext.lookup(InitialContext.java:455)
              at org.jboss.seam.Component.instantiateSessionBean(Component.java:1385)
              at org.jboss.seam.Component.instantiate(Component.java:1349)
              at org.jboss.seam.Component.newInstance(Component.java:2102)
              ... 59 more
      Caused by:  The short-form default binding 'org.jboss.seam.transaction.LocalEjbSynchronizations' is ambiguous because multiple beans implement the interface :



      What's wrong?!?


      thank you in advance