1 Reply Latest reply on Mar 25, 2013 1:23 PM by wdfink

    4.2.3 migration to last good build

    ric2001

      I'm trying to deploy an app that works fine in 4.2.3 to the last AS 7 stable build (Feb 23). I've included all the jars from the lib dir of 4.2.3 with my app and I've excluded a few of the subsystems:

       

      <subsystem name="jaxrs" />

      <subsystem name="webservices" />

      <subsystem name="ejb3" />

      <subsystem name="ee" />

      <subsystem name="security" />

      <subsystem name="jpa" />

      <subsystem name="jsf" />

       

      My goal is to run the app with minimal or no modifications.  I'm not sure if it's possible to exclude all the built-ins of AS 7 as to not create conflicts.  Right now, I'm getting the following:

       

      Servlet CXFServlet threw load() exception: org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are:

      PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'serviceBeans' threw exception; nested exception is java.lang.NoSuchMethodError: javax.ws.rs.Path.limited()Z

      at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:104) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.AbstractPropertyAccessor.setPropertyValues(AbstractPropertyAccessor.java:59) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1127) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:862) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:423) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:249) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:155) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:246) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:291) [spring-beans-2.0.8.jar:2.0.8]

      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) [spring-context-2.0.8.jar:2.0.8]

      at org.apache.cxf.transport.servlet.CXFServlet.loadAdditionalConfig(CXFServlet.java:161) [cxf-2.1.2.jar:2.1.2]

      at org.apache.cxf.transport.servlet.CXFServlet.updateContext(CXFServlet.java:129) [cxf-2.1.2.jar:2.1.2]

      at org.apache.cxf.transport.servlet.CXFServlet.loadSpringBus(CXFServlet.java:101) [cxf-2.1.2.jar:2.1.2]

      at org.apache.cxf.transport.servlet.CXFServlet.loadBus(CXFServlet.java:70) [cxf-2.1.2.jar:2.1.2]

      at org.apache.cxf.transport.servlet.AbstractCXFServlet.init(AbstractCXFServlet.java:90) [cxf-2.1.2.jar:2.1.2]

      at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

      at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

      at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

      at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Final.jar:7.2.0.Final]

      at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:154) [jboss-as-web-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]

      at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:58) [jboss-as-web-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]

      at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:91) [jboss-as-web-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]

      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_12]

      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_12]

      at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_12]

      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_12]

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_12]

      at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_12]

      at org.jboss.threads.JBossThread.run(JBossThread.java:122)

       

      In the server.log, I can see that all my jars are added to my module.  Again, it gets deployed under 4.2.3 without any issues.

       

      I understand that there's a migration guide that should be followed to conform to the latest specs but, if my application is self-contained (i.e., I don't need what JBoss provides), should it be possible to deploy it?

       

      This is my first exposure to AS 7 so excuse the newbie question.  Any pointers and suggestions are appreciated.

       

      Thanks,

      Ric

        • 1. Re: 4.2.3 migration to last good build
          wdfink

          If you remove this subsystems I suppose that the application will not work. You might have the classes included to have no issues with classloading.

          But I suppose that the application will not correct deployed. i.e. if you remove the ee and ejb3 subsystem ejb applications might not work, nevertheless whether you add the whole as4/lib directory or not.

           

          It depends on the application what you need to change.

          You should share a bit of details to get helpful answers.