1 2 3 Previous Next 42 Replies Latest reply on Oct 26, 2009 9:19 PM by atamhank

    Seam 2.1.1.GA

    Norman Richards Expert

      Seam 2.1.1.GA is now out.  Please use this thread for questions or problems related to the release! 


        • 1. Re: Seam 2.1.1.GA
          Romain Cherchi Newbie

          Great !


          How can I know which version of hibernate search is shipped with Seam 2.1.1.GA ?

          • 2. Re: Seam 2.1.1.GA
            Dan Allen Master

            You can find it in build/root.pom.xml. The version specified for Hibernate is 3.2.4.sp1.

            • 3. Re: Seam 2.1.1.GA
              Dan Allen Master

              I discovered a problem with hot deploy in seam-gen WAR projects. The -ds.xml file is being copied to the server with overwrite=true, which forces a redeploy of the datasource and confuses any active entity managers (conversations still active that use persistence). To fix this problem, overwrite=true should be removed from line 258 of seam-gen/build-scripts/build-war.xml and 259 of seam-gen/build-scripts/build.xml (or in the build.xml of projects already created). (Be sure to close the XML bracket appropriately).


              For better or for worse, we have found another hole in our testing of seam-gen, so we will be sure to patch it up for the next go around.

              • 4. Re: Seam 2.1.1.GA
                Dan Allen Master

                Actually, it's not just active entity managers. The redeploy of the datasource messes up the entity manager factory, so I think it affects any persistence operations following the redeploy.

                • 5. Re: Seam 2.1.1.GA
                  Christos Vasilakis Newbie

                  Hi Dan,


                  tried seam-gen on 2.1.1.GA on jboss 5.0.0 GA and seam explode always redeploys the project instead of hot deploy. I haven't touched anything on the project just tried seam explode and then again seam explode. The project is war based.


                  Don't know if its a jboss 5 problem. Later I will try 4.2.3 and see.


                  Regards,
                  Christos


                  • 6. Re: Seam 2.1.1.GA
                    george smith Newbie

                    Using jboss tool/jboss5.0/jboss seam2.1.1
                    create a seam web ear.
                    cannot be deployed


                    Caused by: java.lang.IllegalArgumentException: Exception setting property org.jboss.seam.core.init.jndiPattern on component org.jboss.seam.core.init.  Expression @jndiPattern@ evaluated to null.


                    Even after copy comp

                    • 7. Re: Seam 2.1.1.GA
                      george smith Newbie
                      Using jboss tool/jboss5.0/jboss seam2.1.1 create a seam web ear. cannot be deployed


                      after copy components.xml, remove log-level entry,
                      change web modules to depend on all jars in this project, clean all,
                      still cannot deploy this application, but much less error now.



                      20:38:11,265 INFO  [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=rapDatasource' from JNDI name 'java:rapDatasource'
                      20:38:11,343 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=rapDatasource' to JNDI name 'java:rapDatasource'
                      20:38:11,343 WARN  [HDScanner] Failed to process changes
                      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                      *** CONTEXTS IN ERROR: Name -> Error

                      vfsfile:/C:/Java/jboss-5.0.0.GA/server/default/deploy/rap-ear.ear/ -> org.jboss.deployers.spi.DeploymentException: URL vfsfile:/C:/Java/jboss-5.0.0.GA/server/default/deploy/rap-ear.ear/rap.war/ deployment failed


                              at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
                              at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665)
                              at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
                              at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                              at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
                              at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
                              at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
                              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
                              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
                              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                              at java.lang.Thread.run(Unknown Source)
                      • 8. Re: Seam 2.1.1.GA
                        george smith Newbie
                        how do we solve this issue? deploy a ear file.
                        seam 2.1.1ga /jboss 5/ jboss tool
                        Caused by: java.lang.RuntimeException: Error loading element Identity with component name null and component class null
                             at


                        21:03:01,937 INFO  [Initialization] reading /WEB-INF/components.xml
                        21:03:01,968 ERROR [[/rap]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
                        java.lang.RuntimeException: error while reading /WEB-INF/components.xml
                             at org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:231)
                             at org.jboss.seam.init.Initialization.create(Initialization.java:134)
                             at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:35)
                             at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
                             at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
                             at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367)
                             at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146)
                             at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
                             at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
                             at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
                             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                             at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                             at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                             at java.lang.reflect.Method.invoke(Unknown Source)
                             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
                             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
                             at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
                             at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
                             at $Proxy36.start(Unknown Source)
                             at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
                             at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
                             at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
                             at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
                             at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
                             at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                             at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
                             at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
                             at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
                             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                             at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
                             at org.jboss.system.ServiceController.start(ServiceController.java:460)
                             at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
                             at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
                             at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
                             at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
                             at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
                             at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
                             at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                             at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
                             at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
                             at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                             at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                             at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
                             at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
                             at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
                             at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
                             at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
                             at org.jboss.Main.boot(Main.java:209)
                             at org.jboss.Main$1.run(Main.java:547)
                             at java.lang.Thread.run(Unknown Source)
                        Caused by: java.lang.RuntimeException: Error loading element Identity with component name null and component class null
                             at org.jboss.seam.init.Initialization.installComponentsFromXmlElements(Initialization.java:352)
                             at org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:227)
                             ... 61 more
                        • 9. Re: Seam 2.1.1.GA
                          Arshad Mahmood Newbie
                          Hi,

                          The @JndiPattern@ error is being caused by components.xml in your WAR. I assume you have a version that is assuming some sort of ant build as ant rewrites with the appropriate value from build.properties.

                          Since, I don't use jboss tools I am not sure what is the best way to cope with this. The easist way is to to manually edit the components.xml and update the @JndiPattern@ to something like <name of your ear>/#{ejbName}/local.

                          Regards.
                          • 10. Re: Seam 2.1.1.GA
                            Arshad Mahmood Newbie

                            Hi,


                            The error you are getting is fairly generic and I struggled with it for quite a while.


                            Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener


                            My first suggestion is to take a detailed look at your generated EAR. In particular look for the jboss-seam.jar, is it there and declared as an EJB. Also, you don't have multiple copies hanging around (e.g. one in the EAR and then one in WEB-INF/lib in the WAR).


                            In my (limited) experience is most cases this is a JAR issue, or the settings in your web.xml.


                            Regards.

                            • 11. Re: Seam 2.1.1.GA
                              george smith Newbie
                              Thanks for your replies.

                              jndipattern null is solved by copying components.properties to web-inf\classes directory.

                              But Error loading element Identity with component name null and component class null  could not be solved.

                              Seems the components.xml does not contain any component name element.
                              • 12. Re: Seam 2.1.1.GA
                                george smith Newbie

                                The whole project is created by jboss tool. Followed the chapter 3 of the seam tutorial


                                Just use the ear instead of war.


                                • 13. Re: Seam 2.1.1.GA
                                  cyberanto Newbie

                                  You have to copy the file security.drl from your -ejb project to the deployment directory on the server for your ejb project ... plus all the other files in the root of your ejb project (including the meta-ing directory)


                                  Unfortunately, while you can get to the home page than, it still will give you errors on subsequent pages: multiple jboss-seam jar file are in the servers tmp directory and cause more than one phase listeners to be deployed ...


                                  Have not figured out yet how to avoid that

                                  • 14. Re: Seam 2.1.1.GA
                                    Xinhua Gu Newbie

                                    Hi, all


                                    seems that in 2.1.1.GA @PostConstruct does not work anymore with seam interceptor.....


                                    please help

                                    1 2 3 Previous Next