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

Tomas Remes resolved SEAMFACES-164.
-----------------------------------

    Fix Version/s: 3.1.0.Beta4
       Resolution: Out of Date


running:
mvn clean package -Pjbossas6
mvn clean package -Pglassfish

and deploying example works fine.
                
> Unable to deploy short.ly example to glassfish 3.1 and JBossAS 6
> ----------------------------------------------------------------
>
>                 Key: SEAMFACES-164
>                 URL: https://issues.jboss.org/browse/SEAMFACES-164
>             Project: Seam Faces
>          Issue Type: Bug
>          Components: Build & Distribution
>    Affects Versions: 3.0.1
>         Environment: Glassfish 3.1 or JBoss AS 6
>            Reporter: John Asermely
>            Priority: Critical
>             Fix For: 3.1.0.Beta4
>
>
> Build the faces-short.ly using netbeans to generate the faces-short.ly.war 
> file.  
> When deployed to JBoss AS6 using the JBoss admin console we get the following 
> error:
> java.lang.RuntimeException: Error instantiating class 
> org.jboss.seam.faces.context.FacesAnnotationsAdapterExtension
>         at 
> org.jboss.weld.util.ServiceLoader.prepareInstance(ServiceLoader.java:282) 
> [:6.0.0.Final]
>         at 
> org.jboss.weld.util.ServiceLoader.loadService(ServiceLoader.java:238) 
> [:6.0.0.Final]
>         at 
> org.jboss.weld.util.ServiceLoader.loadServiceFile(ServiceLoader.java:194) 
> [:6.0.0.Final]
>         at org.jboss.weld.util.ServiceLoader.reload(ServiceLoader.java:157) 
> [:6.0.0.Final]
>         at org.jboss.weld.util.ServiceLoader.iterator(ServiceLoader.java:346) 
> [:6.0.0.Final]
> ...
> Caused by: java.lang.NoClassDefFoundError: javax/faces/bean/RequestScoped
>         at 
> org.jboss.seam.faces.context.FacesAnnotationsAdapterExtension.<init>(FacesAnnotationsAdapterExtension.java:39)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) [:1.6.0_24]
>         at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>  [:1.6.0_24]
>         at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>  [:1.6.0_24]
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 
> [:1.6.0_24]
>         at 
> org.jboss.weld.util.ServiceLoader.prepareInstance(ServiceLoader.java:273) 
> [:6.0.0.Final]
>         ... 70 more
> Caused by: java.lang.ClassNotFoundException: javax.faces.bean.RequestScoped 
> from 
> BaseClassLoader@3d989dea{vfs:///Users/asermelj/Applications/jboss-6.0.0.Final/server/default/deploy/blah.war}
>         at 
> org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:480)
>  [jboss-classloader.jar:2.2.0.GA]
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [:1.6.0_24]
>         ... 76 more
> When we deploy the application to Glassfish 3.1, with the update 1.1.1 
> version of weld, we get the error:
> WARNING: Failed to locate BeanManager using any of these providers:
> org.jboss.seam.solder.beanManager.BeanManagerUnavailableException: Failed to 
> locate BeanManager using any of these providers:
>  at 
> org.jboss.seam.solder.beanManager.BeanManagerLocator.getBeanManager(BeanManagerLocator.java:91)
>  at 
> org.jboss.seam.faces.event.SeamPreNavigationHandler.handleNavigation(SeamPreNavigationHandler.java:37)
>  at 
> com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:130)
> A interesting point is that the application will run fine in Glassfish if it 
> is run though netbeans.

--
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

        
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues

Reply via email to