• RELEVANCY SCORE 5.24

    DB:5.24:Di Of Spring-Beans Without Annotations? dx






    Is it possible to inject Spring-beans into EJB without the @Spring-annotation using XML-descriptor instead?Regards,Michael

    DB:5.24:Di Of Spring-Beans Without Annotations? dx


    Unfortunately no. Currently we only support annotations.But as our EJB impl is moving towards Microcontainer injection,things should be come trivial to support.

  • RELEVANCY SCORE 3.67

    DB:3.67:Making Spring Beans Into Seam Components Via Annotations? 8x






    Is there any way to make a Spring bean into a Seam component using annotations? All of the examples in the Seam reference doc assume the Spring beans are configured via XML, but newer versions of Spring don't require that. Thanks.

    DB:3.67:Making Spring Beans Into Seam Components Via Annotations? 8x


    Is there any way to make a Spring bean into a Seam component using annotations? All of the examples in the Seam reference doc assume the Spring beans are configured via XML, but newer versions of Spring don't require that. Thanks.

  • RELEVANCY SCORE 3.10

    DB:3.10:Configuring Spring Beans In Seam mk





    Hi,
    I have one query regarding configuring spring beans into jBPM work flows and Seam Framework. I have read about integrating the Spring beans into Seam. I wanted to know whether is there any other way i can achieve this. i.e. without integrating spring into seam. Is it possible just to configure beans into SEAM and access it.
    Any Help would be highly appreciated.
    Thanks.

    DB:3.10:Configuring Spring Beans In Seam mk

    Thanks the reply. I wanted to know one more thing, whether can i define spring beans as seam POJO component in component.xml

  • RELEVANCY SCORE 2.98

    DB:2.98:Jbossesb Filters - Using Spring Context On Filters d3



    I want to use a federated enterprise component that offers some security services (like auditing, for example). This component can be easy plugged using a Spring ApplicationContext to load all beans and required configurations.I would like to know if there is a way using the JBossESB Filters, to load this component without create the application context by hand, something like the AbstractSpringAction for creation of Spring aware Actions.Thanks,Pedro Igor

    DB:2.98:Jbossesb Filters - Using Spring Context On Filters d3


    At first glance it should be possible, though nothing out-of-the-box as yet. I'll take a look.

  • RELEVANCY SCORE 2.97

    DB:2.97:Java.Lang.Abstractmethoderror: Gettextcontent zc


    Hi,

    I've an application that has been build using hibernate, spring and icefaces and when I update my application using UPDATE button the application could not restart (or if it's stopped doesn't restart)

    I always need to restart the whole server to get it running. (I'm been using Weblogic 9.2) here is the stack trace

    deployment request with ID '1246006508862' for task '97'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.AbstractMethodError: getTextContent
    at com.sun.faces.config.processor.AbstractConfigProcessor.getNodeText(AbstractConfigProcessor.java:140)
    at com.sun.faces.config.processor.FactoryConfigProcessor.processFactories(FactoryConfigProcessor.java:148)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:125)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1610)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2751)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:334)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:162)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    It's look like the dom xml implementation is not well found

    java.lang.AbstractMethodError: getTextContent
    at com.sun.faces.config.processor.AbstractConfigProcessor.getNodeText(AbstractConfigProcessor.java:140)
    at com.sun.faces.config.processor.FactoryConfigProcessor.processFactories(FactoryConfigProcessor.java:148)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:125)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)

    Here'is the full list of jar I've

    aopalliance-1.0.jar
    asm-1.5.3.jar
    axis.jar
    backport-util-concurrent-2.2.jar
    cglib-2.1_3.jar
    commons-beanutils-1.8.0.jar
    commons-codec-1.3.jar
    commons-collections-3.2.jar
    commons-dbcp-1.3.0.jar
    commons-digester-1.8.jar
    commons-discovery-0.2.jar
    commons-el-1.0.jar
    commons-fileupload-1.2.jar
    commons-lang-2.3.jar
    commons-logging-1.1.1.jar
    commons-logging-api-1.1.jar
    commons-pool-1.3.jar
    dom4j-1.6.1.jar
    el-ri.jar
    hibernate-3.2.6.ga.jar
    hibernate-annotations-3.3.1.GA.jar
    hibernate-commons-annotations-3.0.0.ga.jar
    icefaces-comps.jar
    icefaces-facelets.jar
    icefaces.jar
    jaas.config
    jaxrpc.jar
    jsf-api-1.2.jar
    jsf-impl-1.2.jar
    jsp-api-2.1-6.0.2.jar
    jstl.jar
    jta-1.0.1B.jar
    junit-4.6.jar
    log4j-1.2.15.jar
    merlina-7.1.0.jar
    out.txt
    persistence-api-1.0.jar
    saaj.jar
    spring-aop-2.5.5.jar
    spring-aspects-2.5.5.jar
    spring-beans-2.5.5.jar
    spring-context-2.5.5.jar
    spring-core-2.5.5.jar
    spring-jdbc-2.5.5.jar
    spring-orm-2.5.5.jar
    spring-tx-2.5.5.jar
    spring-web-2.5.5.jar
    wsdl4j.jar
    xercesImpl.jar
    xml-apis.jar

    DB:2.97:Java.Lang.Abstractmethoderror: Gettextcontent zc

    Hi,

    I've an application that has been build using hibernate, spring and icefaces and when I update my application using UPDATE button the application could not restart (or if it's stopped doesn't restart)

    I always need to restart the whole server to get it running. (I'm been using Weblogic 9.2) here is the stack trace

    deployment request with ID '1246006508862' for task '97'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.AbstractMethodError: getTextContent
    at com.sun.faces.config.processor.AbstractConfigProcessor.getNodeText(AbstractConfigProcessor.java:140)
    at com.sun.faces.config.processor.FactoryConfigProcessor.processFactories(FactoryConfigProcessor.java:148)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:125)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1610)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2751)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:334)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:162)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    It's look like the dom xml implementation is not well found

    java.lang.AbstractMethodError: getTextContent
    at com.sun.faces.config.processor.AbstractConfigProcessor.getNodeText(AbstractConfigProcessor.java:140)
    at com.sun.faces.config.processor.FactoryConfigProcessor.processFactories(FactoryConfigProcessor.java:148)
    at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:125)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:203)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)

    Here'is the full list of jar I've

    aopalliance-1.0.jar
    asm-1.5.3.jar
    axis.jar
    backport-util-concurrent-2.2.jar
    cglib-2.1_3.jar
    commons-beanutils-1.8.0.jar
    commons-codec-1.3.jar
    commons-collections-3.2.jar
    commons-dbcp-1.3.0.jar
    commons-digester-1.8.jar
    commons-discovery-0.2.jar
    commons-el-1.0.jar
    commons-fileupload-1.2.jar
    commons-lang-2.3.jar
    commons-logging-1.1.1.jar
    commons-logging-api-1.1.jar
    commons-pool-1.3.jar
    dom4j-1.6.1.jar
    el-ri.jar
    hibernate-3.2.6.ga.jar
    hibernate-annotations-3.3.1.GA.jar
    hibernate-commons-annotations-3.0.0.ga.jar
    icefaces-comps.jar
    icefaces-facelets.jar
    icefaces.jar
    jaas.config
    jaxrpc.jar
    jsf-api-1.2.jar
    jsf-impl-1.2.jar
    jsp-api-2.1-6.0.2.jar
    jstl.jar
    jta-1.0.1B.jar
    junit-4.6.jar
    log4j-1.2.15.jar
    merlina-7.1.0.jar
    out.txt
    persistence-api-1.0.jar
    saaj.jar
    spring-aop-2.5.5.jar
    spring-aspects-2.5.5.jar
    spring-beans-2.5.5.jar
    spring-context-2.5.5.jar
    spring-core-2.5.5.jar
    spring-jdbc-2.5.5.jar
    spring-orm-2.5.5.jar
    spring-tx-2.5.5.jar
    spring-web-2.5.5.jar
    wsdl4j.jar
    xercesImpl.jar
    xml-apis.jar

  • RELEVANCY SCORE 2.93

    DB:2.93:Jboss Ws Cxf Client Istantiated From A Spring Context Without Spring Libraries In Common/Lib 77



    Hi all, I am a newbie in jboss ws

    I am developing a "headless" jboss/web application which is loaded and started by means of a spring application context;

    which in turn is loaded by a spring ContextLoaderListener configured in the web.xml;

    the application connects to external devices and communicates with remote applications using web services (client and service);

    the spring libraries are not deployed in the common/lib directory (Jboss-6.1.0-Final)

    when instantiating the client proxy to a remote web service,

    I receive a (well known) exception thrown during the execution of the the javax.xml.ws.Service constructor:

    java.lang.NoClassDefFoundError: org/springframework/beans/BeansException

    at org.jboss.wsf.stack.cxf.client.configuration.JBossWSBusFactory.getSpringBusFactory(JBossWSBusFactory.java:120)

    the exception in due to the missing spring jars in the common/lib directory, while the spring libraries are available in the current thread context classpath.

    After examination of the classes

    org.jboss.wsf.stack.cxf.client.ProviderImpl and

    org.jboss.wsf.stack.cxf.client.configuration.JbossWSBusFactory,

    I inserted the following code, before the invocation of the javax.xml.ws.Service constructor (through an extending class):

    BusFactory busFactory = BusFactory.newInstance();

    if (busFactory instanceof JBossWSBusFactory)

    BusFactory.setThreadDefaultBus(((JBossWSBusFactory)busFactory).getNonSpringBusFactory().createBus());

    MyService service = new MyService(..

    where MyService extends javax.xml.ws.Service.

    and now the service client is istantiated ok.

    Required (provided scope) jars in the compilation classpath,

    from directory %JBOSS_HOME%/ client:

    cxf-api.jar, cxf-rt-core.jar, jbossws-cxf-client.jar

    My question:

    can the same result be achieved with modification of the jboss ws cxf ... configuration files ?

    thanks to all,

    Luigi

    DB:2.93:Jboss Ws Cxf Client Istantiated From A Spring Context Without Spring Libraries In Common/Lib 77


    Well Richard, the changed configuration is consistent wth the fact that the spring libraries are not deployed in jboss libs.

    As soon as possible I will try to put the modified jbossws-cxf-factories.jar in the classpath of the war application, in order to further decouple the application from the host jboss

    (I still don't know if it will work, due to the ClassLoader problems ..)

    Thank you very much.

    by Luigi

  • RELEVANCY SCORE 2.91

    DB:2.91:Issue Using A4j:Mediaoutput With Spring 2.0 Beans fp



    Dear RichFaces Developer Team,I ran into technical issues using the a4j:mediaOutput tag with Spring Beans instead of Managed JSF Beans on a JSPX page. The relevant part of the page looks like this:

    a4j:repeat value="#{paintBean.imageData}" var="imageTile"

    a4j:outputPanel layout="block" style="left: #{imageTile.left}px; top: #{imageTile.top}px; width: #{paintBean.tileWidth}px; height: #{paintBean.tileHeight}px"

    a4j:mediaOutput createContent="#{paintBean.paint}" element="img" mimeType="image/png" shape="rect" standby="loading..." value="#{imageTile}" /

    /a4j:outputPanel

    /a4j:repeat

    DB:2.91:Issue Using A4j:Mediaoutput With Spring 2.0 Beans fp


    Dear RichFaces Developer Team,I ran into technical issues using the a4j:mediaOutput tag with Spring Beans instead of Managed JSF Beans on a JSPX page. The relevant part of the page looks like this:

    a4j:repeat value="#{paintBean.imageData}" var="imageTile"

    a4j:outputPanel layout="block" style="left: #{imageTile.left}px; top: #{imageTile.top}px; width: #{paintBean.tileWidth}px; height: #{paintBean.tileHeight}px"

    a4j:mediaOutput createContent="#{paintBean.paint}" element="img" mimeType="image/png" shape="rect" standby="loading..." value="#{imageTile}" /

    /a4j:outputPanel

    /a4j:repeat

  • RELEVANCY SCORE 2.90

    DB:2.90:Whcih On Is Better For Distributed Application (Spring Pojos Vs Ejb ) ? cp


    Hi All,

    I want to develop a distributed standalone application in which I have used the following technologies

    Presentation Layer : Swings
    Business Layer : Spring POJOs
    Persistence Layer : Spring DAO

    I will deploy the business logic in remote location then I will connect to the business components through
    RMI.(without using EJB we can't get the middleware services, spring already provides some middleware services
    like transcations and security but I think it is not providing load balancing)

    If I use spring POJOs instead of EJB shall I get any benifits?
    If I use spring POJOs how load balance the applicaton?
    If we make multiple requests to the ejb container, multiple ejb objects will be created in order to provide the service in case stateless session beans. Is there any similar kind of service in spring POJOs?

    Can I use spring for distributed standalone applications ?(I want Spring POJOs with middle ware services).

    Is Spring best suitable for developing distributed standalone application?

    Please suggest me which technologies are best to implement the distributed applications.(For standalone applications)

    Thanks in advance
    krishna

    DB:2.90:Whcih On Is Better For Distributed Application (Spring Pojos Vs Ejb ) ? cp

    Nothing to do with the welblogic.
    This problem is related to set context path in ur xml file.

  • RELEVANCY SCORE 2.89

    DB:2.89:Fxcontainer Open Source Javafx Dependency Injection Framework Is Available mz



    What is FxContainer?

    FxContainer is the only IoC container that is built using JavaFX and specifically meant for JavaFX applications to provide Dependency Injection.

    Why FxContainer?

    The world is already filled with dozens of IoC containers. Do we need another one? That is the question I pondered a lot before setting out to write a DI/IoC container in JavaFX

    I looked at Spring, Guice and others as to how to apply them successfully for JavaFX

    1. Spring supports XML and Annotation based Dependency Injection. Guice supports Annotation and binding provider API based DI. Both support Constructor and Setter Injection.

    2. Unfortunately for us, JavaFX does not support Annotations. JavaFX also does not support constructor injection. So we are left with XML based setter injection.

    3. However setter injection feels artificial for JavaFX programming style (where variables are initialized during allocation. Variables are generally declared public-init)

    4. In addition, Setter Injection introduces atleast one known side effect that can cause certain type of JavaFX objects not to work correctly. (More details here: [http://weblogs.java.net/blog/srikanth/archive/2010/06/12/wiring-javafx-objects-spring-tread-caution])

    5. A minimal Spring DI requires 3-4 jars that can add up and exceed 1 MB.

    FxContainer solves all these problems and introduces Init Injection - the style that is natural to JavaFX language. FxContainer is very Spring-like in xml configuration and you will feel very much at home if you know Spring.

    Useful Links

    1. Project Website [https://fxobjects.dev.java.net/]
    2. Download [https://fxobjects.dev.java.net/files/documents/11182/152368/fxcontainer-1.0.zip]
    3. Technical overview of FxContainer [http://weblogs.java.net/blog/srikanth/archive/2010/08/21/fxcontainer-ioc-container-written-javafx-javafx-applications]
    4. 10 minute overview presentation [http://www.slideshare.net/skshenoy/javafx-dependency-injection-with-fxcontainer]

    Srikanth Shenoy
    ObjectSource

    DB:2.89:Fxcontainer Open Source Javafx Dependency Injection Framework Is Available mz


    What is FxContainer?

    FxContainer is the only IoC container that is built using JavaFX and specifically meant for JavaFX applications to provide Dependency Injection.

    Why FxContainer?

    The world is already filled with dozens of IoC containers. Do we need another one? That is the question I pondered a lot before setting out to write a DI/IoC container in JavaFX

    I looked at Spring, Guice and others as to how to apply them successfully for JavaFX

    1. Spring supports XML and Annotation based Dependency Injection. Guice supports Annotation and binding provider API based DI. Both support Constructor and Setter Injection.

    2. Unfortunately for us, JavaFX does not support Annotations. JavaFX also does not support constructor injection. So we are left with XML based setter injection.

    3. However setter injection feels artificial for JavaFX programming style (where variables are initialized during allocation. Variables are generally declared public-init)

    4. In addition, Setter Injection introduces atleast one known side effect that can cause certain type of JavaFX objects not to work correctly. (More details here: [http://weblogs.java.net/blog/srikanth/archive/2010/06/12/wiring-javafx-objects-spring-tread-caution])

    5. A minimal Spring DI requires 3-4 jars that can add up and exceed 1 MB.

    FxContainer solves all these problems and introduces Init Injection - the style that is natural to JavaFX language. FxContainer is very Spring-like in xml configuration and you will feel very much at home if you know Spring.

    Useful Links

    1. Project Website [https://fxobjects.dev.java.net/]
    2. Download [https://fxobjects.dev.java.net/files/documents/11182/152368/fxcontainer-1.0.zip]
    3. Technical overview of FxContainer [http://weblogs.java.net/blog/srikanth/archive/2010/08/21/fxcontainer-ioc-container-written-javafx-javafx-applications]
    4. 10 minute overview presentation [http://www.slideshare.net/skshenoy/javafx-dependency-injection-with-fxcontainer]

    Srikanth Shenoy
    ObjectSource

  • RELEVANCY SCORE 2.85

    DB:2.85:Persistence Strategy For Seam + Spring 9p



    Hi,for a new application, I plan to use use a layered architecture based one seam + spring + hibernate.The spring example in Seam 2.0 shows how to use JpaTemplate to implement data access. I have a couple of questions:1.) It is still possible to use classical Hibernate POJO + Mapping file, but I will not be able to use Hibernate metadata validation. Right?2.) If I choose to use JPA, do I have to make the hibernate class EJB entity beans with @Entity? What is exactly the difference between Hibernate annotation and JPA (beside different configuration files) and EJB3 entity beans?3.) What is the best way to handle PersistenceContext or HibernateSession? Configure and manage it in Seam? But how can I get them injected into my Spring DAOs without using Seam annotation?Any feedback is appreciated.Dapeng

    DB:2.85:Persistence Strategy For Seam + Spring 9p


    Hi,for a new application, I plan to use use a layered architecture based one seam + spring + hibernate.The spring example in Seam 2.0 shows how to use JpaTemplate to implement data access. I have a couple of questions:1.) It is still possible to use classical Hibernate POJO + Mapping file, but I will not be able to use Hibernate metadata validation. Right?2.) If I choose to use JPA, do I have to make the hibernate class EJB entity beans with @Entity? What is exactly the difference between Hibernate annotation and JPA (beside different configuration files) and EJB3 entity beans?3.) What is the best way to handle PersistenceContext or HibernateSession? Configure and manage it in Seam? But how can I get them injected into my Spring DAOs without using Seam annotation?Any feedback is appreciated.Dapeng

  • RELEVANCY SCORE 2.83

    DB:2.83:Jboss 6 Deployment Issue: Javax.Naming.Namenotfoundexception Jdbc Not Bound a1



    I am having the following deployment issue for JBoss 6 for my Struts 2, Spring 3, JPA 2 WAR file.

    DEPLOYMENTS IN ERROR:

    Deployment "persistence.unit:unitName=EDRVS.war#edrvs" is in error due to the following reason(s): javax.naming.NameNotFoundException: jdbc not bound

    persistence.xml follows:

    ?xml version="1.0" encoding="UTF-8"?

    persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"

    persistence-unit name="edrvs" transaction-type="RESOURCE_LOCAL"

    providerorg.hibernate.ejb.HibernatePersistence/provider

    non-jta-data-sourcejdbc/OracleDS/non-jta-data-source

    classgov.doleta.edrvs.model.Code/class

    classgov.doleta.edrvs.model.Errorcheck/class

    classgov.doleta.edrvs.model.Fileimportlog/class

    classgov.doleta.edrvs.model.Filerecordlayout/class

    classgov.doleta.edrvs.model.Filerecordlayoutelement/class

    classgov.doleta.edrvs.model.Recordxerrorcheck/class

    classgov.doleta.edrvs.model.State/class

    classgov.doleta.edrvs.model.TmpfileuploadWia/class

    classgov.doleta.edrvs.model.Reportquarter/class

    classgov.doleta.edrvs.model.Userreportingoption/class

    exclude-unlisted-classes/

    properties

    property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect" /

    property name="hibernate.format_sql" value="true"/

    property name="hbm2ddl.auto" value="update"/

    property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/

    property name="hibernate.archive.autodetection" value="class"/

    /properties

    /persistence-unit

    /persistence

    oracle-ds.xml follows:

    ?xml version="1.0" encoding="UTF-8"?

    !-- ===================================================================== --

    !-- --

    !-- JBoss Server Configuration --

    !-- --

    !-- ===================================================================== --

    !-- See http://www.jboss.org/community/wiki/Multiple1PC for information about local-tx-datasource --

    !-- $Id: oracle-ds.xml 97536 2009-12-08 14:05:07Z jesper.pedersen $ --

    !-- ==================================================================== --

    !-- Datasource config for Oracle originally from Steven Coy --

    !-- ==================================================================== --

    datasources

    local-tx-datasource

    jndi-namejdbc/OracleDS/jndi-name

    connection-urljdbc:oracle:thin:@192.48.52.155:1521:orcl/connection-url

    driver-classoracle.jdbc.driver.OracleDriver/driver-class

    user-namebrafai/user-name

    passwordbr9900/password

    !-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool --

    !--valid-connection-checker-class-nameorg.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker/valid-connection-checker-class-name--

    !-- Checks the Oracle error codes and messages for fatal errors --

    exception-sorter-class-nameorg.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter/exception-sorter-class-name

    !-- sql to call when connection is created

    new-connection-sqlsome arbitrary sql/new-connection-sql

    --

    !-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered--

    check-valid-connection-sqlselect * from dual;/check-valid-connection-sql

    !-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --

    metadata

    type-mappingOracle11g/type-mapping

    /metadata

    /local-tx-datasource

    /datasources

    web.xml follows:

    ?xml version="1.0" encoding="UTF-8"?

    web-app id="starter" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"

    display-nameStruts 2 - Maven Archetype - Starter/display-name

    context-param

    param-namecontextConfigLocation/param-name

    param-valueclasspath*:applicationContext*.xml/param-value

    /context-param

    !-- Filters --

    filter

    filter-nameaction2-cleanup/filter-name

    filter-classorg.apache.struts2.dispatcher.ActionContextCleanUp/filter-class

    /filter

    filter

    filter-namesitemesh/filter-name

    filter-classcom.opensymphony.module.sitemesh.filter.PageFilter/filter-class

    /filter

    filter

    filter-nameaction2/filter-name

    filter-classorg.apache.struts2.dispatcher.FilterDispatcher/filter-class

    /filter

    filter-mapping

    filter-nameaction2-cleanup/filter-name

    url-pattern/*/url-pattern

    /filter-mapping

    filter-mapping

    filter-namesitemesh/filter-name

    url-pattern/*/url-pattern

    /filter-mapping

    filter-mapping

    filter-nameaction2/filter-name

    url-pattern/*/url-pattern

    /filter-mapping

    !-- Listeners --

    listener

    listener-classorg.springframework.web.context.ContextLoaderListener/listener-class

    /listener

    !-- Servlets --

    servlet

    servlet-namedwr/servlet-name

    servlet-classuk.ltd.getahead.dwr.DWRServlet/servlet-class

    init-param

    param-namedebug/param-name

    param-valuetrue/param-value

    /init-param

    /servlet

    servlet

    servlet-namejspSupportServlet/servlet-name

    servlet-classorg.apache.struts2.views.JspSupportServlet/servlet-class

    load-on-startup5/load-on-startup

    /servlet

    servlet-mapping

    servlet-namedwr/servlet-name

    url-pattern/dwr/*/url-pattern

    /servlet-mapping

    !-- Welcome file lists --

    welcome-file-list

    welcome-fileindex.jsp/welcome-file

    welcome-filedefault.jsp/welcome-file

    welcome-fileindex.html/welcome-file

    /welcome-file-list

    resource-ref

    descriptionMyDataSource/description

    res-ref-namejdbc/OracleDS/res-ref-name

    res-typejavax.sql.DataSource/res-type

    res-authContainer/res-auth

    /resource-ref

    /web-app

    jboss-web.xml follows:

    jboss-web

    resource-ref

    res-ref-namejdbc/OracleDS/res-ref-name

    res-typejavax.sql.DataSource/res-type

    jndi-namejava:jdbc/OracleDS/jndi-name

    /resource-ref

    /jboss-web

    Spring applicationContext.xml follows:

    ?xml version="1.0" encoding="UTF-8"?

    beans xmlns="http://www.springframework.org/schema/beans"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:aop="http://www.springframework.org/schema/aop"

    xmlns:tx="http://www.springframework.org/schema/tx"

    xsi:schemaLocation="

    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd

    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd

    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd"

    !-- Example of SAF2 action instantiated by Spring --

    bean id="helloWorldAction" class="gov.doleta.edrvs.action.HelloWorldAction" /

    bean id="indexAction" class="gov.doleta.edrvs.action.IndexAction" /

    !-- Enable JPA Support --

    bean

    class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor" /

    !-- Define EntityManagerFactory and Datasource --

    bean id="entityManagerFactory"

    class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"

    property name="persistenceUnitName" value="edrvs" /

    property name="dataSource" ref="dataSource" /

    property name="jpaVendorAdapter"

    bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"

    property name="database" value="ORACLE" /

    property name="showSql" value="true" /

    /bean

    /property

    /bean

    bean id="dataSource"

    class="org.springframework.jdbc.datasource.DriverManagerDataSource"

    property name="driverClassName" value="oracle.jdbc.driver.OracleDriver" /

    property name="url" value="jdbc:oracle:thin:@192.48.52.155:1521:orcl" /

    property name="username" value="brafai" /

    property name="password" value="br9900" /

    /bean

    !-- Define Transaction Manager --

    bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager"

    property name="entityManagerFactory" ref="entityManagerFactory" /

    /bean

    tx:annotation-driven transaction-manager="transactionManager" /

    !-- Define the FileImportLogDao --

    bean id="FileImportLogDao" class="gov.doleta.edrvs.dao.FileImportLogDaoImpl" /

    !-- Define the FileImportLogService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="FileImportLogService" class="gov.doleta.edrvs.service.FileImportLogServiceImpl"

    property name="FileImportLogDao" ref="FileImportLogDao" /

    /bean

    !-- Define the StateDao --

    bean id="StateDao" class="gov.doleta.edrvs.dao.StateDaoImpl" /

    !-- Define the StateService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="StateService" class="gov.doleta.edrvs.service.StateServiceImpl"

    property name="StateDao" ref="StateDao" /

    /bean

    !-- Define the WIASourceDao --

    bean id="WIASourceDao" class="gov.doleta.edrvs.dao.WIASourceDaoImpl" /

    !-- Define the WIASourceService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="WIASourceService" class="gov.doleta.edrvs.service.WIASourceServiceImpl"

    property name="WIASourceDao" ref="WIASourceDao" /

    /bean

    !-- Define the FileRecordLayoutElementDao --

    bean id="FileRecordLayoutElementDao" class="gov.doleta.edrvs.dao.FileRecordLayoutElementDaoImpl" /

    !-- Define the FileRecordLayoutElementService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="FileRecordLayoutElementService" class="gov.doleta.edrvs.service.FileRecordLayoutElementServiceImpl"

    property name="FileRecordLayoutElementDao" ref="FileRecordLayoutElementDao" /

    /bean

    !-- Define the CodeDao --

    bean id="CodeDao" class="gov.doleta.edrvs.dao.CodeDaoImpl" /

    !-- Define the CodeService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="CodeService" class="gov.doleta.edrvs.service.CodeServiceImpl"

    property name="CodeDao" ref="CodeDao" /

    /bean

    !-- Define the ErrorCheckDao --

    bean id="ErrorCheckDao" class="gov.doleta.edrvs.dao.ErrorCheckDaoImpl" /

    !-- Define the ErrorCheckService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="ErrorCheckService" class="gov.doleta.edrvs.service.ErrorCheckServiceImpl"

    property name="ErrorCheckDao" ref="ErrorCheckDao" /

    /bean

    !-- Define the RecordXErrorCheckDao --

    bean id="RecordXErrorCheckDao" class="gov.doleta.edrvs.dao.RecordXErrorCheckDaoImpl" /

    !-- Define the RecordXErrorCheckService --

    !-- enable the configuration of transactional behavior based on annotations --

    bean id="RecordXErrorCheckService" class="gov.doleta.edrvs.service.RecordXErrorCheckServiceImpl"

    property name="RecordXErrorCheckDao" ref="RecordXErrorCheckDao" /

    /bean

    /beans

    Any help is appreciated. I can run my Maven Spring Service JUnit tests without problems and get data to/from the Oracle DB

    but when I try to deploy to JBoss I have the issue above.

    Jeff Sanders

    DB:2.83:Jboss 6 Deployment Issue: Javax.Naming.Namenotfoundexception Jdbc Not Bound a1


    By default JBoss AS datasources are bound to java: namespace, so change your persistence.xml from:

    non-jta-data-sourcejdbc/OracleDS/non-jta-data-source

    to

    non-jta-data-sourcejava:jdbc/OracleDS/non-jta-data-source

  • RELEVANCY SCORE 2.83

    DB:2.83:Ejb3 Entity Bean, Pojo, Without Annotations xc


    Hello,
    I develop an application where the EJB3 is used.
    According to some advises got from the net, POJO classes are used as entity beans and they contain some EJB3 annotations like @Entity, @Id, @GeneratedValue, @ManyToMany etc. The application server is JBOSS.

    To manage and communicate with the server side, a web GUI was created.
    It communicates with server by means of EJB3 interface (@Remote).
    At the moment I'm introducing a web interface (webservice) for one of a server side interfaces.
    Doing this I realized, that the output parameter (an entity bean (POJO)) hardly depends on all the packages that support all the annotations stuff that is used in it.
    Therefore, the web service client must be aware of them (when it uses the POJO declaration for the unmarchalling).

    My question is:
    How is it possible to stay in the frame of the EJB3 model (beans, persisting) and get rid of annotations in POJO?
    What is (if any) the standard practice for such a case? (POJO Inheritance, XML descriptions, etc...) ?

    Merci.

    Edited by: dendroid66 on Mar 9, 2009 2:36 AM

    DB:2.83:Ejb3 Entity Bean, Pojo, Without Annotations xc

    this situation bothered me extremely as well. you can solve it one of two ways.

    as the previous poster mentioned, you can separate your entities from your DTO's. this is nice in a lot of ways because the ideal objects for over-the-wire usage may be very different from the ideal objects for your database model. the downside of this approach is that you may end up duplicating a lot of work.

    the alternative, is using xml files to describe your entities. this is still supported in ejb3, although it is not obvious from a lot of the documentation. annotations were meant to remove the need for xml config files, but almost everything you can do with annotations is still possible via xml configuration (in fact, you can combine the two, doing some configuration with annotations and some with xml, where xml based configuration will override annotation based configuration). check out documentation on "orm.xml" for details. the upside of this solution is it removes annotations from your entities. the downside is that it can be a little more work to manage than annotation based configuration.

  • RELEVANCY SCORE 2.83

    DB:2.83:Cdi: Get A List Of Matching Beans md



    Hi,

    can I get a list of beans matching given annotations, using anotations?

    I mean, can I convert this
    java.util.SetBean? myBeans = getBeans(Foobar.class, annotation1, ann2, ...);

    DB:2.83:Cdi: Get A List Of Matching Beans md

    can I get a list of beans matching given annotations, using anotations?
    I mean, can I convert this
    java.util.SetBean? myBeans = getBeans(Foobar.class, annotation1, ann2, ...);

    to this?

    @Inject @Anno1 @Anno2 java.util.SetBean? myBeans;

    Or any plans for it?

    I think you're looking for:

    * http://docs.jboss.org/cdi/api/1.0-SP4/javax/enterprise/inject/Instance.html

  • RELEVANCY SCORE 2.82

    DB:2.82:Seam Spring Example md



    Hi togetherI would try out the Seam Spring example. After restart of my tomcatinstance the following messages occures:15:39:50,538 DEBUG [PluggableSchemaResolver] Loading schema mappings from [META-INF/spring.schemas]15:39:50,538 DEBUG [PluggableSchemaResolver] Loaded schema mappings: {http://www.springframework.org/schema/aop/spring-aop-2.0.xsd=org/springframework/aop/config/spring-aop-2.0.xsd, http://www.springframework.org/schema/util/spring-util.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd, http://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd, http://www.springframework.org/schema/jee/spring-jee.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://www.springframework.org/schema/beans/spring-beans.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang-2.0.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx-2.0.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/aop/spring-aop.xsd=org/springframework/aop/config/spring-aop-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool-2.0.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/jee/spring-jee-2.0.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd}15:39:50,538 DEBUG [PluggableSchemaResolver] Loading schema mappings from [META-INF/spring.schemas]15:39:50,538 DEBUG [PluggableSchemaResolver] Loaded schema mappings: {http://www.springframework.org/schema/aop/spring-aop-2.0.xsd=org/springframework/aop/config/spring-aop-2.0.xsd, http://www.springframework.org/schema/util/spring-util.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd, http://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd, http://www.springframework.org/schema/jee/spring-jee.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://www.springframework.org/schema/beans/spring-beans.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang-2.0.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx-2.0.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/lang/spring-lang.xsd=org/springframework/scripting/config/spring-lang-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/aop/spring-aop.xsd=org/springframework/aop/config/spring-aop-2.0.xsd, http://www.springframework.org/schema/tx/spring-tx.xsd=org/springframework/transaction/config/spring-tx-2.0.xsd, http://www.springframework.org/schema/tool/spring-tool-2.0.xsd=org/springframework/beans/factory/xml/spring-tool-2.0.xsd, http://www.springframework.org/schema/jee/spring-jee-2.0.xsd=org/springframework/ejb/config/spring-jee-2.0.xsd, http://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd}15:39:50,538 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]15:39:50,553 DEBUG [DefaultDocumentLoader] Using JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl]15:39:50,553 DEBUG [PluggableSchemaResolver] Trying to resolve XML entity with public id [null] and system id [http://www.springframework.org/schema/beans/spring-beans-2.0.xsd]15:39:50,569 DEBUG [PluggableSchemaResolver] Found XML schema [http://www.springframework.org/schema/beans/spring-beans-2.0.xsd] in classpath: org/springframework/beans/factory/xml/spring-beans-2.0.xsd15:39:50,694 DEBUG [PluggableSchemaResolver] Trying to resolve XML entity with public id [null] and system id [http://www.jboss.com/products/seam/spring-seam-1.2.xsd]15:40:11,679 WARN [XmlBeanDefinitionReader] Ignored XML validation warningorg.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.jboss.com/products/seam/spring-seam-1.2.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.warning(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:351) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefiniCould anyone help me?Thanks Andi

    DB:2.82:Seam Spring Example md


    Well, the exception mentions "http://www.jboss.com/products/seam/spring-seam-1.2.xsd" as a System Id. So it would probably be in the applicationContext.xml file?http://www.jboss.com/products/seam/spring-seam-1.2.xsdshould behttp://jboss.com/products/seam/spring-seam-1.2.xsdandhttp://www.jboss.com/products/seam/spring-seamshould behttp://jboss.com/products/seam/spring-seam

  • RELEVANCY SCORE 2.82

    DB:2.82:Jndi Naming Issue pd



    I'm migrating an application to JBOSS7 and as you can see in the log below, the ServerMessageService is ok but Ive still error which says : javax.naming.NameNotFoundException: 2-bpm2-server/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService

    19:17:07,597 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named ServerMessageService in deployment unit subdeployment "2-bpm2-server.jar" of deployment "bpm2.ear" are as follows:

    java:global/bpm2/2-bpm2-server/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService

    java:app/2-bpm2-server/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService

    java:module/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService

    java:global/bpm2/2-bpm2-server/ServerMessageService

    java:app/2-bpm2-server/ServerMessageService

    java:module/ServerMessageService

    19:17:08,388 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.subunit."bpm2.ear"."2-bpm2-server.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."bpm2.ear"."2-bpm2-server.jar".INSTALL: Failed to process phase INSTALL of subdeployment "2-bpm2-server.jar" of deployment "bpm2.ear"

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

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

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

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]

    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to install management resources for org.jboss.as.ee.component.ComponentConfiguration[name= Bpm1Topic1Bean class=com.tt.airman.bpm2.server.mdb.Bpm1Topic1Bean]

    at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:79)

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

    ... 5 more

    Caused by: org.jboss.as.controller.PathElement$OperationClientIllegalArgumentException: JBAS014719: Invalid value specification Bpm1Topic1Bean

    at org.jboss.as.controller.PathElement.init(PathElement.java:91)

    at org.jboss.as.controller.PathElement.pathElement(PathElement.java:70)

    at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.getComponentAddress(EjbManagementDeploymentUnitProcessor.java:124)

    at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.installManagementResource(EjbManagementDeploymentUnitProcessor.java:104)

    at org.jboss.as.ejb3.deployment.processors.EjbManagementDeploymentUnitProcessor.deploy(EjbManagementDeploymentUnitProcessor.java:76)

    ... 6 more

    19:17:09,261 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-8) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmsMessageService': Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: 2-bpm2-server/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService -- service jboss.naming.context.java.app.bpm2.2-bpm2-server."ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService"

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:546) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:872) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:423) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

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

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

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]

    Caused by: javax.naming.NameNotFoundException: 2-bpm2-server/ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService -- service jboss.naming.context.java.app.bpm2.2-bpm2-server."ServerMessageService!com.tt.airman.bpm2.shared.service.IServerMessageService"

    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)

    at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)

    at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_26]

    at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:122) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:109) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean.afterPropertiesSet(LocalStatelessSessionProxyFactoryBean.java:86) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    ... 20 more

    DB:2.82:Jndi Naming Issue pd


    You can download the source and build 7.2.0.Final yourself from: https://github.com/wildfly/wildfly/tree/7.2.0.Final

  • RELEVANCY SCORE 2.80

    DB:2.80:Adding @Webservices To An Existing .War km


    Hello
    I've a J2EE web application based on Spring/Struts/Hibernate, that I usually deploy as a .war on Tomcat.
    All the required .jar are included in the WEB-INF/lib of the .war

    I did succeed in creating an .ear file that simply includes the .war and I can deploy it on Weblogic. It works!

    I now wish to expose some webservices from the application using the standard @Webservice @Webmethod etc annotations.

    On another application server (SAP Netweaver Java AS) I just created a plain java class, annotated them with @Webservice @Webmethod and I've said it extends SpringBeanAutowiringSupport
    In this way spring injects into that class the service beans that will implement the business logic of the webservices using all the features I already have in the original application and it's absolutely great and easy.
    And SAP Netweaver finds at runtime the @Webservice annotations and exposes automatically all of them!

    I thought that on Weblogic the solution was similar. but it is not.

    After deploying an application annotated with @Webservice I did notice that Weblogic did not recognized automatically the webservices.
    So after reading a lot of documentation I am finally trying to play with "jswc" and task (and even with "wsdlc") but with no success.

    It seems that jswc create an indipendent .war for just the webservice, but I wish to put the webservice into the same .war where it is running the struts/spring application!

    I would accept of course of having two different .war (one for the struts/spring application and one for the tiny application just exposing the webservice)
    But the problem is that in the second war (where there is the @Webservice annotated class) I didn't find any way to use some service singleton beans that Spring manages on the other .war

    And, about the JPA entity classes, they are defined and compiled in the Struts/Spring application .war, how can I use those classes in the second .war????

    A solution could be to move all the .jar from the struts/spring .war to the .ear containers, and I should compile all my custom .java into a .jar and put it in the .ear container so that both application can access the same classes, JPA entities services and so on (but even this very difficult solution failed!)

    What's the best way to approach this problem?

    Thank you

    DB:2.80:Adding @Webservices To An Existing .War km

    Hello
    I've a J2EE web application based on Spring/Struts/Hibernate, that I usually deploy as a .war on Tomcat.
    All the required .jar are included in the WEB-INF/lib of the .war

    I did succeed in creating an .ear file that simply includes the .war and I can deploy it on Weblogic. It works!

    I now wish to expose some webservices from the application using the standard @Webservice @Webmethod etc annotations.

    On another application server (SAP Netweaver Java AS) I just created a plain java class, annotated them with @Webservice @Webmethod and I've said it extends SpringBeanAutowiringSupport
    In this way spring injects into that class the service beans that will implement the business logic of the webservices using all the features I already have in the original application and it's absolutely great and easy.
    And SAP Netweaver finds at runtime the @Webservice annotations and exposes automatically all of them!

    I thought that on Weblogic the solution was similar. but it is not.

    After deploying an application annotated with @Webservice I did notice that Weblogic did not recognized automatically the webservices.
    So after reading a lot of documentation I am finally trying to play with "jswc" and task (and even with "wsdlc") but with no success.

    It seems that jswc create an indipendent .war for just the webservice, but I wish to put the webservice into the same .war where it is running the struts/spring application!

    I would accept of course of having two different .war (one for the struts/spring application and one for the tiny application just exposing the webservice)
    But the problem is that in the second war (where there is the @Webservice annotated class) I didn't find any way to use some service singleton beans that Spring manages on the other .war

    And, about the JPA entity classes, they are defined and compiled in the Struts/Spring application .war, how can I use those classes in the second .war????

    A solution could be to move all the .jar from the struts/spring .war to the .ear containers, and I should compile all my custom .java into a .jar and put it in the .ear container so that both application can access the same classes, JPA entities services and so on (but even this very difficult solution failed!)

    What's the best way to approach this problem?

    Thank you

  • RELEVANCY SCORE 2.79

    DB:2.79:Not Able To Load Spring Transaction Xsd For Spring Db Object(S) Initialise Used Under Switcyard Project 9z



    Did anyone tried to initializing db facade with transaction using spring context files from switcyard project/cotext?

    We face below exception, mostly looking up of xsd file from classpath related.

    14:48:16,834 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (http-/135.254.229.83:8443-1) Loading XML bean definitions from URL [file:/opt/aor/conf//aa/db/spring-task-manager.xml]

    14:49:19,862 WARN [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (http-/135.254.229.83:8443-1) Ignored XML validation warning: org.xml.sax.SAXParseException; systemId: classpath:org/springframework/transaction/config/spring-tx-2.0.xsd; lineNumber: 12; columnNumber: 150; schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/tool/spring-tool-2.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema.

    at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) [xercesImpl-2.9.1-redhat-4.jar:]

    at org.apache.xerces.util.ErrorHandlerWrapper.warning(Unknown Source) [xercesImpl-2.9.1-redhat-4.jar:]

    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.9.1-redhat-4.jar:]

    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.9.1-redhat-4.jar:]

    The http reference defined in spring namespace are not loadable first as we don't enable internet and so we tried using classpath references as second option. Still when enabling spring transaction for DB, we are not able to load tx xsd which internally refers tools xsd. Is there a way to initialise spring without this xsd lookup/read complexity. Below is our sample namespace pointing details on spring context file

    ?xml version="1.0" encoding="UTF-8"?

    CLASSPATH

    beans default-init-method="beanInit" default-destroy-method="beanDestroy"

    xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:context="http://www.springframework.org/schema/context"

    xmlns:jee="http://www.springframework.org/schema/jee" xmlns:tx="http://www.springframework.org/schema/tx"

    xmlns:tool="http://www.springframework.org/schema/tool"

    xsi:schemaLocation="http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans-4.0.xsd

    http://www.springframework.org/schema/context classpath:org/springframework/context/config/spring-context-4.0.xsd

    http://www.springframework.org/schema/tx classpath:org/springframework/transaction/config/spring-tx-2.0.xsd

    http://www.springframework.org/schema/tool classpath:org/springframework/beans/factory/xml/spring-tool-2.0.xsd"

    OR INTERNET

    beans default-init-method="beanInit" default-destroy-method="beanDestroy"

    xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:context="http://www.springframework.org/schema/context"

    xmlns:jee="http://www.springframework.org/schema/jee" xmlns:tx="http://www.springframework.org/schema/tx"

    xmlns:aop="http://www.springframework.org/schema/aop"

    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd

    http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd

    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd

    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd

    http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.0.xsd"

    .

    It will be good, if switchyard deployment reads below spring fw configuration/reference files?

    META-INF/spring.schemas

    META-INF/spring.handlers

    DB:2.79:Not Able To Load Spring Transaction Xsd For Spring Db Object(S) Initialise Used Under Switcyard Project 9z


    Seems We need to keep the combined spring.schemas spring.handlers under Service projects META-INF to make spring transaction work under jboss switchyard project;

    module xmlns="urn:jboss:module:1.0" name="org.springframework.401"

    resources

    resource-root path="spring-beans-4.0.1.RELEASE.jar"/

    resource-root path="spring-core-4.0.1.RELEASE.jar"/

    resource-root path="spring-jdbc-4.0.1.RELEASE.jar"/

    resource-root path="spring-orm-4.0.1.RELEASE.jar"/

    resource-root path="spring-test-4.0.1.RELEASE.jar"/

    resource-root path="spring-tx-4.0.1.RELEASE.jar"/

    resource-root path="spring-context-4.0.1.RELEASE.jar"/

    resource-root path="spring-context-support-4.0.1.RELEASE.jar"/

    resource-root path="spring-expression-4.0.1.RELEASE.jar"/

    resource-root path="spring-dao-2.0.8.jar"/

    resource-root path="spring-aop-4.0.1.RELEASE.jar"/

    resource-root path="aopalliance-1.0.jar"/

    resource-root path="."/

    /resources

    dependencies

    module name="org.apache.commons.logging"/

    module name="javax.persistence.api"/

    module name="javax.jms.api"/

    module name="javax.api"/

    module name="org.hibernate"/

    module name="com.mysql"/

    /dependencies

    /module

    Mission Accomplished for the day!

  • RELEVANCY SCORE 2.77

    DB:2.77:Injection Vs. Get Bean Via Application Context x8


    Hi all,

    I'm quite new to JSF and Spring and theres one question that bothers me. I use JSF together with Spring and all the managed beans are created via the spring framework.

    It ist possible to inject the spring beans (dao) into the managed beans but you can also access the beans via:

    ApplicationContext ctx = FacesContextUtils.getWebApplicationContext(FacesContext.getCurrentInstance());
    ctx.getBean(....

    Which is the best method and what are the advantages/disadvatages of each method.

    Regards
    Matt

    DB:2.77:Injection Vs. Get Bean Via Application Context x8

    I was under the impression that Spring's defualt initialization is eager, not lazy? In any case, if bean is marked as lazy, and is not instantiated yet, BeanFactory will create a new instance.

  • RELEVANCY SCORE 2.77

    DB:2.77:Jboss-Spring With Spring 2.0-Rc1 Noclassdeffounderror a8



    Hi,I've tried to setup JBoss-Spring Integration version 4, jboss-spring-jdk5.deployer with JBoss4.0.4GA, and have found that it uses Spring 2.0-m3 jars.So I've deleted those jars and put the all-in-one spring.jar in place, from version 2.0-rc1 of the Spring framework.Then when I've tried deploying the example app. (JBoss-Spring.ear), JBoss threw a "java.lang.NoClassDefFoundError: org/springframework/beans/factory/xml/DefaultXmlBeanDefinitionParser" exception.I've checked the contents of the new spring.jar, and it seems that DefaultXmlBeanDefinitionParser was removed indeed.Is there a way to configure the Integration to work with the latest release of the Spring Framework?Thanks Regards,David

    DB:2.77:Jboss-Spring With Spring 2.0-Rc1 Noclassdeffounderror a8


    SpringDeployer compatible with Spring2.0 final.http://www.jboss.org/index.html?module=bbop=viewtopicp=3979096

  • RELEVANCY SCORE 2.76

    DB:2.76:Spring 3 + Jbpm 4.4 + Hibernate 3.3 + Jpa + Jta Integration Error. 3s



    All,

    I have been able to make some progress in terms of integrating my current project with jbpm, based on the link below:

    http://captaincaveman.posterous.com/jbpm-43-spring-3-jboss-jpa-jta-configuration

    With minor modifications, the set up was pretty much close. However, after all the configuration changes are done, I do face this error during server start-up.

    [7/4/11 19:38:05:491 IST] 00000011 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\was70profile1\logs\ffdc\server1_57ff57ff_11.07.04_19.38.05.3343817305385213655618.txt com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated 1341[7/4/11 19:38:05:506 IST] 00000011 webapp E com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E: Exception caught while initializing context: {0} java.lang.NoClassDefFoundError: org.jbpm.api.ProcessEngineat java.lang.Class.getDeclaredFieldsImpl(Native Method)at java.lang.Class.getDeclaredFields(Class.java:550)at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:372)at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:320)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:798)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:493)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1707)at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:380)at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:299)at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1122)at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:725)at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1266)at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4582)at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4760)at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplicationDynamically(ApplicationMgrImpl.java:1271)at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2043)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:439)at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:382)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:653)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:615)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1177)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)at java.lang.reflect.Method.invoke(Method.java:611)at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:49)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)at java.lang.reflect.Method.invoke(Method.java:611)at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:256)at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1085)at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:966)at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1332)at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1225)at com.ibm.ws.management.remote.AdminServiceForwarder.invoke(AdminServiceForwarder.java:334)at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1438)at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1276)at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1371)at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)at javax.management.remote.rmi._RMIConnectionImpl_Tie.invoke(_RMIConnectionImpl_Tie.java:750)at javax.management.remote.rmi._RMIConnectionImpl_Tie._invoke(_RMIConnectionImpl_Tie.java:158)at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)at com.ibm.rmi.iiop.ORB.process(ORB.java:513)at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)Caused by: java.lang.ClassNotFoundException: org.jbpm.api.ProcessEngineat java.net.URLClassLoader.findClass(URLClassLoader.java:434)at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:150)at java.lang.ClassLoader.loadClass(ClassLoader.java:653)at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:90)at java.lang.ClassLoader.loadClass(ClassLoader.java:619)at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:541)at java.lang.ClassLoader.loadClass(ClassLoader.java:619)... 77 more

    [7/4/11 19:38:05:538 IST] 00000011 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Web Module NAPSWeb has been bound to default_host[*:9081,*:80,*:9444,*:5063,*:5062,*:443].[7/4/11 19:38:05:553 IST] 00000011 ApplicationMg A WSVR0221I: Application started: NAPS[7/4/11 19:38:05:553 IST] 00000011 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=NAPS in BLA WebSphere:blaname=NAPS started.[7/4/11 19:38:06:147 IST] 0000001f FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\was70profile1\logs\ffdc\server1_19071907_11.07.04_19.38.06.1471603185250462490371.txt com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet 208[7/4/11 19:38:06:163 IST] 0000001f servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper run [Servlet Error]-[class java.lang.ClassNotFoundException: com.ibm.etools.utc.servlet.InitializeServlet]: java.lang.ClassNotFoundException: class java.lang.ClassNotFoundException: com.ibm.etools.utc.servlet.InitializeServletat java.beans.Beans.instantiate(Beans.java:190)at java.beans.Beans.instantiate(Beans.java:75)at com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run(ServletWrapper.java:1909)at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(ServletWrapper.java:1900)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:730)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3933)at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:275)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

    I do have the jbpm.jar file in the classpath (it's in the WEB-INF\lib folder.)

    This is bit of a suprise to me. Has anybody faced similar problem?

    System configuration:

    RAD 7.5 and WAS 7.0.0.15 Test Environment on Windows XP SP3.

    DB server: SQL Server.

    I added the following to my already working spring applicationContext.xml file:

    !-- Added for JBPM START --
    !--
    Activates a load-time weaver for the context. Any bean within the context that
    implements LoadTimeWeaverAware (such as LocalContainerEntityManagerFactoryBean)
    will receive a reference to the auto-detected load-time weaver.
    --
    !-- context:load-time-weaver aspectj-weaving="on" /--

    !--
    Turn on AspectJ @Configurable support. As a result, any time you
    instantiate an object, Spring will attempt to perform dependency
    injection on that object. This occurs for instantiation via the "new"
    keyword, as well as via reflection. This is possible because AspectJ
    is used to "weave" Roo-based applications at compile time. In effect
    this feature allows dependency injection of any object at all in your
    system, which is a very useful feature (without @Configurable you'd
    only be able to dependency inject objects acquired from Spring or
    subsequently presented to a specific Spring dependency injection
    method). Roo applications use this useful feature in a number of
    areas, such as @PersistenceContext injection into entities.
    --
    context:spring-configured /
    !--
    This declaration will cause Spring to locate every @Component,
    @Repository and @Service in your application. In practical terms this
    allows you to write a POJO and then simply annotate the new POJO as an
    @Service and Spring will automatically detect, instantiate and
    dependency inject your service at startup time. Importantly, you can
    then also have your new service injected into any other class that
    requires it simply by declaring a field for your service inside the
    relying class and Spring will inject it. Furthermore, this turns on
    @Autowired, @PostConstruct etc support. These annotations allow you to
    use common Spring and Java Enterprise Edition annotations in your
    classes without needing to do any special configuration. The most
    commonly used annotation is @Autowired, which instructs Spring to
    dependency inject an object into your class.
    --
    context:component-scan base-package="com.test" /

    !-- enables interpretation of the @Required annotation to ensure that dependency injection actually occurs --
    bean class="org.springframework.beans.factory.annotation.RequiredAnnotationBeanPostProcessor"/
    !--
    Activates various annotations to be detected in bean classes: Spring's
    @Required and @Autowired, as well as JSR 250's @PostConstruct,
    @PreDestroy and @Resource (if available) and JPA's @PersistenceContext
    and @PersistenceUnit (if available).
    --
    context:annotation-config
    transaction-manager="transactionManager" /
    !--
    Instruct Spring to retrieve and apply @AspectJ aspects which are
    defined as beans in this context.
    --
    !-- aop:aspectj-autoproxy proxy-target-class="true" /--

    !--
    The JNDI Hibernate session factory will not work for jBPM 4.4 as jBPM is expecting
    a Spring LocalSessionFactoryBean. So we specify our mappings here. This will only
    be used by jBPM. Spring will still inject the container managed persistence unit
    anywhere you use @PersistenceContext.
    --
    !-- jee:jndi-lookup id="sessionFactory" jndi-name="java:/SquareOneHibernateSessionFactory" / --
    bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
    !-- property name="configLocation" value="classpath:/jbpm/jbpm.hibernate.cfg.xml" / --
    property name="dataSource" ref="dataSource" /
    property name="mappingResources"
    list
    valuejbpm.repository.hbm.xml/value
    valuejbpm.execution.hbm.xml/value
    valuejbpm.history.hbm.xml/value
    valuejbpm.task.hbm.xml/value
    valuejbpm.identity.hbm.xml/value
    /list
    /property
    !--
    Hibernate properties needed to configure the session factory to use JTA.
    This will ensure that jBPM can participate in the application's JTA transactions.
    --
    property name="hibernateProperties"
    props
    prop key="hibernate.transaction.factory_class"org.hibernate.transaction.CMTTransactionFactory/prop
    prop key="hibernate.transaction.manager_lookup_class"org.hibernate.transaction.WebSphereTransactionManagerLookup/prop
    prop key="hibernate.dialect"org.hibernate.dialect.SQLServerDialect/prop
    prop key="hibernate.connection.datasource"java:jdbc/my_dataSource/prop
    prop key="jta.UserTransaction"java:comp/UserTransaction/prop
    prop key="hibernate.hbm2ddl.auto"false/prop
    !-- prop key="hibernate.default_schema"dbo/prop--
    /props
    /property
    /bean

    !-- jBPM beans.
    Based on the jBPM provided way of creating a Spring process engine set up.
    This can also be done by calling the Process engine methods with parameters directly.
    However this is the most appropriate way of initializing jBPM.
    --
    !-- util:properties id="my_jbpm_config" location="classpath:/resources/my.jbpm.cfg.xml"/--
    bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper"
    property name="jbpmCfg" value="/WEB-INF/resources/my.jbpm.cfg.xml"/
    /bean

    bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" scope="singleton"/
    !-- Added for JBPM END --

    Any pointers will be of great help.

    Thanks,
    Ayusman

    Also...

    I just wanted to do the following with in the web-application.. to verify that I atleast have the handle to jbpm from with in spring...


    @Autowired
    private static ProcessEngine processEngine;
    .
    .
    .
    .
    .
    public void foo()
    {

    log.debug("START jbpm processing...");
    if (null != processEngine )
    {
    RepositoryService rs = processEngine.getRepositoryService();
    ExecutionService es = processEngine.getExecutionService();
    TaskService taskService = processEngine.getTaskService();
    DeploymentQuery dq = rs.createDeploymentQuery();
    log.debug("Deployment count: "+dq.count());
    ProcessInstanceQuery piq = es.createProcessInstanceQuery();
    log.debug("Total number of process instances is: "+ piq.count());
    }
    else
    {
    log.error("Process engine object is null");
    }
    log.debug("END jbpm processing...");

    }


    just incase it matters

    DB:2.76:Spring 3 + Jbpm 4.4 + Hibernate 3.3 + Jpa + Jta Integration Error. 3s


    All,

    I have been able to make some progress in terms of integrating my current project with jbpm, based on the link below:

    http://captaincaveman.posterous.com/jbpm-43-spring-3-jboss-jpa-jta-configuration

    With minor modifications, the set up was pretty much close. However, after all the configuration changes are done, I do face this error during server start-up.

    [7/4/11 19:38:05:491 IST] 00000011 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\was70profile1\logs\ffdc\server1_57ff57ff_11.07.04_19.38.05.3343817305385213655618.txt com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated 1341[7/4/11 19:38:05:506 IST] 00000011 webapp E com.ibm.ws.webcontainer.webapp.WebApp notifyServletContextCreated SRVE0283E: Exception caught while initializing context: {0} java.lang.NoClassDefFoundError: org.jbpm.api.ProcessEngineat java.lang.Class.getDeclaredFieldsImpl(Native Method)at java.lang.Class.getDeclaredFields(Class.java:550)at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.findPersistenceMetadata(PersistenceAnnotationBeanPostProcessor.java:372)at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessMergedBeanDefinition(PersistenceAnnotationBeanPostProcessor.java:320)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyMergedBeanDefinitionPostProcessors(AbstractAutowireCapableBeanFactory.java:798)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:493)at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:1707)at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:380)at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:299)at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:100)at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:166)at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:731)at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:616)at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:376)at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:668)at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1122)at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1319)at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:610)at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:944)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:725)at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1266)at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4582)at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4760)at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplicationDynamically(ApplicationMgrImpl.java:1271)at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2043)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:439)at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:382)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:653)at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:615)at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1177)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)at java.lang.reflect.Method.invoke(Method.java:611)at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:49)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)at java.lang.reflect.Method.invoke(Method.java:611)at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:256)at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1085)at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:966)at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1332)at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1225)at com.ibm.ws.management.remote.AdminServiceForwarder.invoke(AdminServiceForwarder.java:334)at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1438)at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1276)at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1371)at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)at javax.management.remote.rmi._RMIConnectionImpl_Tie.invoke(_RMIConnectionImpl_Tie.java:750)at javax.management.remote.rmi._RMIConnectionImpl_Tie._invoke(_RMIConnectionImpl_Tie.java:158)at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)at com.ibm.rmi.iiop.ORB.process(ORB.java:513)at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)Caused by: java.lang.ClassNotFoundException: org.jbpm.api.ProcessEngineat java.net.URLClassLoader.findClass(URLClassLoader.java:434)at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:150)at java.lang.ClassLoader.loadClass(ClassLoader.java:653)at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:90)at java.lang.ClassLoader.loadClass(ClassLoader.java:619)at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:541)at java.lang.ClassLoader.loadClass(ClassLoader.java:619)... 77 more

    [7/4/11 19:38:05:538 IST] 00000011 webcontainer I com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Web Module NAPSWeb has been bound to default_host[*:9081,*:80,*:9444,*:5063,*:5062,*:443].[7/4/11 19:38:05:553 IST] 00000011 ApplicationMg A WSVR0221I: Application started: NAPS[7/4/11 19:38:05:553 IST] 00000011 CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=NAPS in BLA WebSphere:blaname=NAPS started.[7/4/11 19:38:06:147 IST] 0000001f FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\was70profile1\logs\ffdc\server1_19071907_11.07.04_19.38.06.1471603185250462490371.txt com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet 208[7/4/11 19:38:06:163 IST] 0000001f servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper run [Servlet Error]-[class java.lang.ClassNotFoundException: com.ibm.etools.utc.servlet.InitializeServlet]: java.lang.ClassNotFoundException: class java.lang.ClassNotFoundException: com.ibm.etools.utc.servlet.InitializeServletat java.beans.Beans.instantiate(Beans.java:190)at java.beans.Beans.instantiate(Beans.java:75)at com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run(ServletWrapper.java:1909)at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(ServletWrapper.java:1900)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:730)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3933)at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:275)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

    I do have the jbpm.jar file in the classpath (it's in the WEB-INF\lib folder.)

    This is bit of a suprise to me. Has anybody faced similar problem?

    System configuration:

    RAD 7.5 and WAS 7.0.0.15 Test Environment on Windows XP SP3.

    DB server: SQL Server.

    I added the following to my already working spring applicationContext.xml file:

    !-- Added for JBPM START --
    !--
    Activates a load-time weaver for the context. Any bean within the context that
    implements LoadTimeWeaverAware (such as LocalContainerEntityManagerFactoryBean)
    will receive a reference to the auto-detected load-time weaver.
    --
    !-- context:load-time-weaver aspectj-weaving="on" /--

    !--
    Turn on AspectJ @Configurable support. As a result, any time you
    instantiate an object, Spring will attempt to perform dependency
    injection on that object. This occurs for instantiation via the "new"
    keyword, as well as via reflection. This is possible because AspectJ
    is used to "weave" Roo-based applications at compile time. In effect
    this feature allows dependency injection of any object at all in your
    system, which is a very useful feature (without @Configurable you'd
    only be able to dependency inject objects acquired from Spring or
    subsequently presented to a specific Spring dependency injection
    method). Roo applications use this useful feature in a number of
    areas, such as @PersistenceContext injection into entities.
    --
    context:spring-configured /
    !--
    This declaration will cause Spring to locate every @Component,
    @Repository and @Service in your application. In practical terms this
    allows you to write a POJO and then simply annotate the new POJO as an
    @Service and Spring will automatically detect, instantiate and
    dependency inject your service at startup time. Importantly, you can
    then also have your new service injected into any other class that
    requires it simply by declaring a field for your service inside the
    relying class and Spring will inject it. Furthermore, this turns on
    @Autowired, @PostConstruct etc support. These annotations allow you to
    use common Spring and Java Enterprise Edition annotations in your
    classes without needing to do any special configuration. The most
    commonly used annotation is @Autowired, which instructs Spring to
    dependency inject an object into your class.
    --
    context:component-scan base-package="com.test" /

    !-- enables interpretation of the @Required annotation to ensure that dependency injection actually occurs --
    bean class="org.springframework.beans.factory.annotation.RequiredAnnotationBeanPostProcessor"/
    !--
    Activates various annotations to be detected in bean classes: Spring's
    @Required and @Autowired, as well as JSR 250's @PostConstruct,
    @PreDestroy and @Resource (if available) and JPA's @PersistenceContext
    and @PersistenceUnit (if available).
    --
    context:annotation-config
    transaction-manager="transactionManager" /
    !--
    Instruct Spring to retrieve and apply @AspectJ aspects which are
    defined as beans in this context.
    --
    !-- aop:aspectj-autoproxy proxy-target-class="true" /--

    !--
    The JNDI Hibernate session factory will not work for jBPM 4.4 as jBPM is expecting
    a Spring LocalSessionFactoryBean. So we specify our mappings here. This will only
    be used by jBPM. Spring will still inject the container managed persistence unit
    anywhere you use @PersistenceContext.
    --
    !-- jee:jndi-lookup id="sessionFactory" jndi-name="java:/SquareOneHibernateSessionFactory" / --
    bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
    !-- property name="configLocation" value="classpath:/jbpm/jbpm.hibernate.cfg.xml" / --
    property name="dataSource" ref="dataSource" /
    property name="mappingResources"
    list
    valuejbpm.repository.hbm.xml/value
    valuejbpm.execution.hbm.xml/value
    valuejbpm.history.hbm.xml/value
    valuejbpm.task.hbm.xml/value
    valuejbpm.identity.hbm.xml/value
    /list
    /property
    !--
    Hibernate properties needed to configure the session factory to use JTA.
    This will ensure that jBPM can participate in the application's JTA transactions.
    --
    property name="hibernateProperties"
    props
    prop key="hibernate.transaction.factory_class"org.hibernate.transaction.CMTTransactionFactory/prop
    prop key="hibernate.transaction.manager_lookup_class"org.hibernate.transaction.WebSphereTransactionManagerLookup/prop
    prop key="hibernate.dialect"org.hibernate.dialect.SQLServerDialect/prop
    prop key="hibernate.connection.datasource"java:jdbc/my_dataSource/prop
    prop key="jta.UserTransaction"java:comp/UserTransaction/prop
    prop key="hibernate.hbm2ddl.auto"false/prop
    !-- prop key="hibernate.default_schema"dbo/prop--
    /props
    /property
    /bean

    !-- jBPM beans.
    Based on the jBPM provided way of creating a Spring process engine set up.
    This can also be done by calling the Process engine methods with parameters directly.
    However this is the most appropriate way of initializing jBPM.
    --
    !-- util:properties id="my_jbpm_config" location="classpath:/resources/my.jbpm.cfg.xml"/--
    bean id="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper"
    property name="jbpmCfg" value="/WEB-INF/resources/my.jbpm.cfg.xml"/
    /bean

    bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" scope="singleton"/
    !-- Added for JBPM END --

    Any pointers will be of great help.

    Thanks,
    Ayusman

    Also...

    I just wanted to do the following with in the web-application.. to verify that I atleast have the handle to jbpm from with in spring...


    @Autowired
    private static ProcessEngine processEngine;
    .
    .
    .
    .
    .
    public void foo()
    {

    log.debug("START jbpm processing...");
    if (null != processEngine )
    {
    RepositoryService rs = processEngine.getRepositoryService();
    ExecutionService es = processEngine.getExecutionService();
    TaskService taskService = processEngine.getTaskService();
    DeploymentQuery dq = rs.createDeploymentQuery();
    log.debug("Deployment count: "+dq.count());
    ProcessInstanceQuery piq = es.createProcessInstanceQuery();
    log.debug("Total number of process instances is: "+ piq.count());
    }
    else
    {
    log.error("Process engine object is null");
    }
    log.debug("END jbpm processing...");

    }


    just incase it matters

  • RELEVANCY SCORE 2.75

    DB:2.75:Annotated Configuration Vs Xml Configuration zx


    I have to decide whether to move ahead and use Annotations for an application for a major enhancement task.
    XML configurations can be replaced with annotations for the following items:
    1. Spring related (EJB configurations, bean configurations (layers of dependent java classes getting injected))
    2. Hibernate related (getting rid of HBM XMLs)

    But, developers are not that keen to move ahead with the annotation thing, since during development they will have to re-compile every time there is a minor configuration change.
    Now, what I can foresee is that when the application is in production, there will be few (maybe none) configuration changes. So the XML files stay unchanged anyways and beats the no-need-to-re-compile logic!

    And yes, Client wants to shift to the latest and greatest of Spring and Hibernate. So just giving them new third party jars packaged with the application without introducing the usage of the new features, seem to be irrelevant!

    So how do I balance both ends and decide, keeping the developers at ease during development phase? Will it be a good idea to migrate from XMLs to Annotations as a separate developmental activity once the business enhancements are taken care of?

    Sorry if I was not able to express myself clearly. Please do revert in that case as well.

    DB:2.75:Annotated Configuration Vs Xml Configuration zx

    But, developers are not that keen to move ahead with the annotation thing, since during development they will have to re-compile every time there is a minor configuration change.That 'reason' doesnt make any sense whatsoever. Recompilation happens severa times a day in development shops, as new changes are pulled in from the source control system. IDEs do the recompilation for you automatically. The attitude seems to match work practices that are about thirty years out of date.

  • RELEVANCY SCORE 2.75

    DB:2.75:Bean Destroy Methods When Undeploying f9



    Hi:I am using jboss 4.2. I just started using the jboss spring deployer to deploy my spring application. Some of the spring beans my application are configured with destroy-method callback as described here (http://static.springframework.org/spring/docs/2.0.x/reference/beans.html#beans-factory-lifecycle-disposablebean).When I shutdown jboss, I see in the log that there is a line about destroying the singleton beans:2008-07-14 11:28:19,418 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@17c7988: defining beans [my app beans]But I don't think the destroy methods of the beans are invoked (added some log messages but they didn't show up in the log).How should I configure my app for the spring deployer to call the lifecycle methods like init and destroy?Thanks,Ken

    DB:2.75:Bean Destroy Methods When Undeploying f9


    "tkyung" wrote:Is there a downside for making this a prototype bean?This is more of a Spring question, so you should really ask there. But I think this is what happens here is that if a bean is prototype, Spring doesn't track it anymore, so nothing happens on shutdown - since it's out of Spring's scope. What you should really use is, SpringDeployer's hierarchy notion: - http://java.sys-con.com/read/180386.htm Since we'd like to hot deploy many different Spring archives, each of them must be uniquely represented in our environment. For that purpose, JNDI will be used as a registry for these deployments. But where can we get our local JNDI name? By default, this JNDI name is obtained from the archive's file name: name.spring or name-spring.xml. But since it's also possible for each bean factory to have parent bean factory, there should be a way to define this parent's name too. This can be done in Spring's beans xml descriptor in description tag as shown in Listing 3.We are parsing this description tag and looking for a regular expression pattern of 'BeanFactory=(name)' and 'ParentBeanFactory=(name)' so see Listing 4.Every time a Spring component is undeployed, we get the corresponding Bean factory through the URL string key in our bean factory map. We remove the map entry, destroy the bean factory singletons, and unbind it from JNDI. When undeploying components be careful of the bean factory hierarchy; don't undeploy some other component's parent bean factory. When shutting down, JBossAS undeploys components in reverse order, which is the right behavior for our child-parent bean factory hierarchy.And then you can access other context's bean directly.

  • RELEVANCY SCORE 2.75

    DB:2.75:Can You Merge Multiple Annotations In One? pm



    Many of my beans are annotated like this:
    @Stateful
    @Scope(...)
    @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
    @Conversational(ifNotBegunOutcome="main")
    @Name("...")

    DB:2.75:Can You Merge Multiple Annotations In One? pm


    FYI, I want to introduce annotation refactoring using meta-annotations in the next rev of EJB3. I will be proposing this formally to Sun quite soon, and I hope to get it into the JSR proposal.So you could do something like this:
    @Stateless
    @Transaction(NOT_SUPPORTED)
    public @interface Action {}

  • RELEVANCY SCORE 2.75

    DB:2.75:Spring!!! pc



    A reminder of spring.

    DB:2.75:Spring!!! pc


    I cannot wait for it to get here !!!


  • RELEVANCY SCORE 2.74

    DB:2.74:Spring Annotations, Component-Scanning, Autowiring - And Blueprint? 37



    A newbie question... I am exploring a possibility of repackaging an existing Spring project as OSGi bundles. My modules have Spring-annotated classes (e.g. @Component-annotated) with @autowired- and @Value-annotated properties, etc. If I understand correctly, to export some of my shared beans as OSGi services (defined in one bundle) I would need to create service definitions in the bundle's Blueprint configuration XML(s), not in Spring. (Assuming I am using Aries.) I do realize that the Blueprint spec came out of of Spring DM and is itself a dependency-injection container for OSGi. Does this mean that I should be using Blueprint/Aries instead of Spring, not with it? Does this mean I would have to redefine all the client beans (that live in other bundles and need to be injected with the references to those shared "services") as Blueprint beans? Does this mean I can no longer rely on Spring auto-wiring, component scanning, etc? Or will I be able to use "regular" Spring contexts together with Blueprint?

    I wouldn't want to a) have to change my implementation just because I am packaging the artifacts differently now, b) give up on familiar and convenient Spring features - for whatever reasons. An old tutorial I found on the Internet (from 2009) demonstrates the usage of Spring DM with separate configuration files for regular Spring and OSGi service definitions per bundle. That makes a lot of sense, it allows reusing regular Spring definitions for testing and any non-OSGi stuff. I have tried something similar with Blueprint/Aries, but, evidently, the Blueprint-context objects are not seen by my Spring beans. Am I missing something? I'm exploring a new territory here, and any up-to-date tutorials seem to be sparse. So, I'd appreciate any clarifications or advice.

    Many thanks for your help!

    Edited by: constv7 on Oct 30, 2012 8:50 PM

    DB:2.74:Spring Annotations, Component-Scanning, Autowiring - And Blueprint? 37


    Hi,

    Ensure you have

    xmlns:osgi-springdm="http://www.springframework.org/schema/osgi"

    and

    http://www.springframework.org/schema/osgi

    http://www.springframework.org/schema/osgi/spring-osgi.xsd

    in xsi:schemaLocation

    Freeman

  • RELEVANCY SCORE 2.74

    DB:2.74:Use Of Deployed Spring Beans Directly On Webapp 98



    Hello All,I have sort of a very basic question but it doesn't appear on previous posts. Is it possible to use the deployed spring beans directly in a web app without going to the EJB? In the example provided, you have an ear file where the spring pojos are deployed separately from the webapp and the webapp itself uses the EJB beans, now how can it be configured for the webapp to use the pojos without the EJB beans, in the same EAR? I tried to do it and the pojos are deployed successfully (in a .spring file) and the beanfactory is registered to JNDI, but I couldn't find a way to reference those spring beans on my webapp context (deployed on a war file). Any ideas?thanks a lot for your prompt responseSalvador

    DB:2.74:Use Of Deployed Spring Beans Directly On Webapp 98


    Wrong forum - pure Spring (+ Hibernate) stuff - nothing to do with JBoss-Spring integration.

  • RELEVANCY SCORE 2.74

    DB:2.74:Toplink Ignores Jpa Annotations / Porting The Spring Petclinic sz


    As the Petclinic example of the Spring Framework (JPA version) uses
    xml-based mapping files (orm.xml), I tried to create a Petclinic
    version that uses JPA annotations.

    I succeeded with Hibernate as JPA persistence provider, my petclinic
    version with JPA annotations runs fine.

    But when using Toplink as JPA provider, I managed to run the Spring
    Petclinic only successfully when I continue to use the xml-based
    mapping (orm.xml).

    It appears that Toplink completely ignores the JPA annotations ,
    so when I eliminate orm.xml, no mappings are defined. Consequently,
    when running the Petclinic and trying to display all veterinarians,
    Toplink throws the following exception, which isn't surprising:
    oracle.toplink.essentials.exceptions.EJBQLException Exception
    Description: Unknown abstract schema type [Vet]

    When NOT eliminating orm.xml, however, my Petclinic JPA version runs
    fine with Toplink.

    There are some pitfalls I am aware of:

    First of all, my persistence.xml file to define the persistence unit
    has the exclude-unlisted-classes element either uncommented or set to
    "false", so scanning of unlisted-classes should actually not be
    prevented. Also, there is no xml-mapping-metadata-complete/ element
    in my persistence.xml.

    Secondly, when persistence.xml is placed in WEB-INF/classes/META-INF of
    my Petclinic WAR-file, my compiled Java classes are in WEB-INF/classes
    (and not in a separate JAR file placed in WEB-INF/lib).

    My questions:

    How can I configure Toplink Essentials (using Tomcat 6.0.2) and Spring
    2.0 so that it doesn't ignore the JPA annotations placed on Entity
    classes?

    Does anyone perhaps have a small example to demonstrate that Toplink,
    set up by Spring, can read JPA annotations (rather than just xml-based
    mapping files)?

    Any hints would be highly appreciated.

    applicationContext-jpa.xml (placed in WEB-INF): ?xml version="1.0" encoding="UTF-8"?
    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/aop
    http://www.springframework.org/schema/aop/spring-aop-2.0.xsd
    http://www.springframework.org/schema/tx
    http://www.springframework.org/schema/tx/spring-tx-2.0.xsd"

    !-- Configurer that replaces ${...} placeholders with values from a properties file --
    !-- (in this case, JDBC-related settings for the dataSource definition below) --
    bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"
    property name="location" value="/WEB-INF/jdbc.properties"/
    /bean

    !-- Local DataSource that works in any environment --
    !-- Note that DriverManagerDataSource does not pool; it is not intended for production --
    !-- See JPetStore for an example of using Commons DBCP BasicDataSource as alternative --
    !-- See Image Database for an example of using C3P0 ComboPooledDataSource as alternative --
    bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource"
    property name="driverClassName" value="${jdbc.driverClassName}"/
    property name="url" value="${jdbc.url}"/
    property name="username" value="${jdbc.username}"/
    property name="password" value="${jdbc.password}"/
    /bean

    !-- JPA EntityManagerFactory --
    bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"
    property name="dataSource" ref="dataSource"/
    !-- loadTimeWeaver not needed for Hibernate --
    property name="loadTimeWeaver"
    bean class="org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver"/
    /property

    property name="jpaVendorAdapter"
    bean class="org.springframework.orm.jpa.vendor.TopLinkJpaVendorAdapter"
    !-- property name="databasePlatform"
    value="org.springframework.samples.petclinic.toplink.EssentialsHSQLPlatformWithNativeSequence"/ --
    property name="databasePlatform" value="oracle.toplink.essentials.platform.database.MySQL4Platform"/
    property name="generateDdl" value="false"/
    property name="showSql" value="true" /
    /bean
    /property
    /bean

    !-- Transaction manager for a single JPA EntityManagerFactory (alternative to JTA) --
    bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager"
    property name="entityManagerFactory" ref="entityManagerFactory"/
    /bean

    !--
    Instruct Spring to retrieve and apply @AspectJ aspects which are defined
    as beans in this context (such as the UsageLogAspect below).
    --
    aop:aspectj-autoproxy/

    !--
    Simply defining this bean will cause requests to owner names to be saved.
    Spring automatically deploys the @Aspect when AspectJ autoproxying is enabled.
    Note that we can dependency inject this bean like any other bean.
    --
    bean class="org.springframework.samples.petclinic.aspects.UsageLogAspect"
    property name="historySize" value="300"/
    /bean

    !--
    Instruct Spring to perform declarative transaction management automatically
    on annotated classes.
    --
    tx:annotation-driven/

    !--
    PostProcessors to perform resource injection according to the JPA specification
    (@PersistenceContext, @PersistenceUnit).
    --
    bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/

    !--
    PostProcessors to perform exception translation on @Repository classes (from native
    exceptions such as JPA PersistenceExceptions to Spring's DataAccessException hierarchy).
    --
    bean class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/

    !--
    Will automatically be transactional due to @Transactional.
    EntityManager will be auto-injected due to @PersistenceContext.
    PersistenceExceptions will be auto-translated due to @Repository.
    --
    bean id="clinic" class="org.springframework.samples.petclinic.jpa.EntityManagerClinic"/

    /beanspersistence.xml (placed in WEB-INF/classes/META-INF):persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0"

    persistence-unit name="PetClinic" transaction-type="RESOURCE_LOCAL"

    !--
    Prevent annotation scanning. In this app we are purely driven by orm.xml.
    --
    exclude-unlisted-classesfalse/exclude-unlisted-classes

    !--
    Using Spring we don't need the basic required vendor-specific properties like
    the following, which in this sample app are all conveyed in Spring configuration...
    --
    properties
    /properties
    /persistence-unit

    /persistenceSpring version used: 2.0

    Toplink essentials version:
    taken from Spring 2.0 distribution, but version from glassfish-persistence-installer-v2-b25.jar doesn't work either.

    spring-tomcat-weaver.jar placed in ${TOMCAT_HOME}/lib

    Tomcat version used: 6.0.2

    DB:2.74:Toplink Ignores Jpa Annotations / Porting The Spring Petclinic sz

    Hi,

    I had a very similar occurance with Tomcat 5.5.16, and I found that I needed to take my toplink-essentials.jar out of the war/WEB-INF/lib and place it in a Tomcat shared library in order for the annotations to be processed correctly (ie. so that the javax definitions would be properly recognized.)

    As far as I can figure this is due to a classloader issue between Spring's TomcatInstrumentableClassLoader and Tomcat's WebAppLoader...

    Hope this helps.

    Edit: I've been experimenting a bit with Tomcat 6.0.0 and you may also need to place the toplink-essentials.jar explicitly on Tomcat's classpath in catalina bat.

    Message was edited by: more information
    lhillis

  • RELEVANCY SCORE 2.73

    DB:2.73:Jboss-Hibernate Integration x9



    Hello,Hibernate Support included in JBoss and the support of Hibernate in Spring framework seems similar to me.I only want to be sure I didn't miss the point: If I want to manage BMP Entity beans with Hibernate in JBoss, I can make my code cleaner using:JBoss-Hibernate integrationORSpring-Hibernate integrationThese are two alternatives solutions for the same problem: managing Hibernate sessionFactory options and mappings without creating/maintaining lots of plumbing code.Thank you for your help.Denis.

    DB:2.73:Jboss-Hibernate Integration x9


    Hello,Hibernate Support included in JBoss and the support of Hibernate in Spring framework seems similar to me.I only want to be sure I didn't miss the point: If I want to manage BMP Entity beans with Hibernate in JBoss, I can make my code cleaner using:JBoss-Hibernate integrationORSpring-Hibernate integrationThese are two alternatives solutions for the same problem: managing Hibernate sessionFactory options and mappings without creating/maintaining lots of plumbing code.Thank you for your help.Denis.

  • RELEVANCY SCORE 2.71

    DB:2.71:Looking For Instructions For Reverse Engineering Db Schema Using Hibernate Tools p7



    Hi,

    I'm looking for instructions for reverse engineering hibernate domain objects from an existing DB schema using hibernate tools, but I am not finding what I'm looking for. Is there a tutorial or some sort of instructions for how to do this? I have sucessfully installed the jboss tools in eclipse indigo, and that's all good but I am not finding instructions for how to connect to an existing DB and generate hibernate domain objects from it. We're using hibernate as a provider and JPA annotations for the mappings, so I'd like to have it generate mapping via JPA annotations if at all possible. We are not using seam, but rather using Spring DI, but I can create a seam project if that's the only way to do it. Any pointers to a tutorial or other set of instructions would be greatly appreciated!

    DB:2.71:Looking For Instructions For Reverse Engineering Db Schema Using Hibernate Tools p7

    Our video page has this: http://docs.jboss.org/tools/movies/#hibreveng

    docs at http://docs.jboss.org/tools/latest/en/hibernatetools/html_single/index.html outlines the "classic" hibernate tools approach.

  • RELEVANCY SCORE 2.71

    DB:2.71:Mock Facescontext In Spring Application Context? 8m



    Hi All,

    I am working on an app that is using Spring managed beans instead of Faces managed beans.

    I have a problem with a (Spring) @Component that has a @PostConstruct method which accesses session data via

    DB:2.71:Mock Facescontext In Spring Application Context? 8m


    Ok, that's bean code, but can you please post test code so that I can see how Mock objects are being configured there and try to reproduce the problem locally?

  • RELEVANCY SCORE 2.71

    DB:2.71:Weblogic Web Service And Spring x1


    Hi,
    just looking for a simple example of creating a weblogic web service (using annotations, etc) and incorporating that into spring (via ServletEndpointSupport?). Can't seem to find if this is possible or not...
    Thanks.

    DB:2.71:Weblogic Web Service And Spring x1

    Hi,
    just looking for a simple example of creating a weblogic web service (using annotations, etc) and incorporating that into spring (via ServletEndpointSupport?). Can't seem to find if this is possible or not...
    Thanks.

  • RELEVANCY SCORE 2.70

    DB:2.70:No Endpoints In Web Console sm



    I can't see any of my endpoints in console.

    JBoss 7.0.2 with own cxf spring configuration, standalone mode. Example of configuration:

    bean annotations:

    @WebContext(secureWSDLAccess=false)

    @Stateless

    @WebService(endpointInterface=webservice_interface)

    webservice interface annotations:

    @WebService

    jbossws-cxf.xml:

    beans xmlns='http://www.springframework.org/schema/beans'

    xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:beans='http://www.springframework.org/schema/beans'

    xmlns:jaxws='http://cxf.apache.org/jaxws' xmlns:wsa='http://cxf.apache.org/ws/addressing'

    xmlns:jms='http://cxf.apache.org/transports/jms' xmlns:soap='http://cxf.apache.org/bindings/soap'

    xsi:schemaLocation='http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/transports/jms http://cxf.apache.org/schemas/configuration/jms.xsd http://cxf.apache.org/bindings/soap http://cxf.apache.org/schemas/configuration/soap.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd'

    jaxws:endpoint id='BeanName'

    address='/jar-name/BeanName'

    implementor='BeanClassWithPackage'

    serviceName='ns0:BeanNameService'

    xmlns:ns0='http://reversed_bean_package/'

    endpointName='ns1:BeanNamePort'

    xmlns:ns1='http://reversed_bean_package/'

    jaxws:invoker

    bean class='org.jboss.wsf.stack.cxf.JBossWSInvoker' /

    /jaxws:invoker

    /jaxws:endpoint

    /beans

    I can access it by url and it works fine.

    Is it a bug or an unimplemented feature?

    It would be easier if Heiko updates http://community.jboss.org/wiki/SubsystemManagementOperations.

    We would know what to expect and what should we report.

    btw. now I'm not sure if EJB tab with session beans and message driven beans should be filled (it's empty on my server) or it's not implemented yet.

    DB:2.70:No Endpoints In Web Console sm


    Thanks Alessio,

    Since you mentioned EAR archives:

    I'm curious... The JBoss Tools/WTP top-down service creation process appears to force the creation of an "Enterprise App/EAR" project. A dynamic web project gets the EAR project added when the service is added. Is there a way to use the web service creation wizard.and avoid the creation of the EAR project?

    Regards

  • RELEVANCY SCORE 2.70

    DB:2.70:War Accessing A Jar With Jpa Entities,Spring And Persistence.Xml In Jboss-5.1.0.Ga fx



    Hi,

    I am creating a jar as DataLayerService.jar of one of my module - DataLayerService and putting it inside WEB-INF/lib directory of my application TestServiceLayer. Then I am deploying the war of TestServiceLayer namely - TestServiceLayer.war in jboss-5.1.0.GA.

    Contents of my persistence.xml file -

    ?xml version="1.0" encoding="UTF-8"?

    persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0"

    persistence-unit name="bts-72"

    descriptionBts/description

    jta-data-sourcejava:BtsDS/jta-data-source

    properties

    property name="hibernate.show_sql" value="false"/

    property name="jboss.as.jpa.providerModule" value="hibernate3-bundled"/

    property name="javax.persistence.validation.mode"none/property

    /properties

    /persistence-unit

    /persistence

    and the location of persistence.xml file is -

    DataLayerService

    |

    META-INF

    |

    persistence.xml

    And Content fo my service-spring-config.xml -

    ?xml version="1.0" encoding="UTF-8" standalone="no"?

    beans xmlns="http://www.springframework.org/schema/beans" xmlns:p="http://www.springframework.org/schema/p" xmlns:tx="http://www.springframework.org/schema/tx" xmlns:context="http://www.springframework.org/schema/context" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://www.springframework.org/schema/beans

    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

    http://www.springframework.org/schema/tx

    http://www.springframework.org/schema/tx/spring-tx-3.0.xsd

    http://www.springframework.org/schema/context

    http://www.springframework.org/schema/context/spring-context-3.0.xsd"

    !-- bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager" property name="transactionManagerName" value="java:/TransactionManager"/ /bean --

    tx:annotation-driven/

    tx:jta-transaction-manager/

    context:annotation-config/

    !-- bean class="com.gravitant.bms.billing.service.automation.BillImportService" id="billImportService" factory-method="getInstance" /bean --

    !-- bean class="com.gravitant.util.EntityManagerProxyImpl" id="entityManagerProxy"/ bean class="com.gravitant.util.PlanningFindersUtil" id="findersUtil" factory-method="getInstance" property name="entityManagerProxy" ref="entityManagerProxy"/ /bean --

    !-- bean class="com.gravitant.billing.BillDAOImpl" id="billDAO" property name="entityManagerProxy" ref="entityManagerProxy"/ property name="findersUtil" ref="findersUtil"/ /bean bean class="com.gravitant.billing.BillService" id="billService" property name="billDAO" ref="billDAO"/ /bean --

    /beans

    This service-spring-config.xml is located in the classpath of DataLayerService.jar

    In the library of DataLayerService module I have included - ejb3-persistence.jar file.

    I have used annotations @PersistenceContext to include the EntityManager -

    @PersistenceContext

    private EntityManager entityManager;

    In the TestServiceLayer I have the following -

    /WEB-INF/lib directory contains DataServiceLayer.jar.

    In the classpath of TestServiceLayer, I have hibernate.properties and spring-config.xml file -

    Content of hibernate.properties file -

    hibernate.show_sql=false

    hibernate.format_sql=false

    hibernate.cache.use_second_level_cache=true

    hibernate.cache.use_query_cache=true

    hibernate.cache.region.factory_class=net.sf.ehcache.hibernate.EhCacheRegionFactory

    hibernate.cache.provider_configuration_file_resource_path=ehcache.xml

    hibernate.dialect=org.hibernate.dialect.MySQLDialect

    Content of spring-config.xml file

    ?xml version="1.0" encoding="UTF-8" standalone="no"?

    beans xmlns="http://www.springframework.org/schema/beans" xmlns:p="http://www.springframework.org/schema/p" xmlns:tx="http://www.springframework.org/schema/tx" xmlns:context="http://www.springframework.org/schema/context"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:jee="http://www.springframework.org/schema/jee"

    xsi:schemaLocation="http://www.springframework.org/schema/beans

    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

    http://www.springframework.org/schema/tx

    http://www.springframework.org/schema/tx/spring-tx-3.0.xsd

    http://www.springframework.org/schema/context

    http://www.springframework.org/schema/context/spring-context-3.0.xsd

    http://www.springframework.org/schema/jee

    http://www.springframework.org/schema/jee/spring-jee-3.0.xsd"

    tx:annotation-driven/

    tx:jta-transaction-manager/

    context:annotation-config/

    !-- jee:jndi-lookup id="myEmf" jndi-name="persistence/myPersistenceUnit"/ --

    !-- bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/ --

    context:component-scan base-package="com.myapp"/

    !-- bean class="com.gravitant.rest.BillWebService" id="billWebService" property name="billService" ref bean="billService"/ /property /bean --

    /beans

    After creating the war file of TestServiceLayer application if I deploy it in the server, I get the following exception -

    2014-01-05 23:06:18,579 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfszip:/C:/jboss/jboss-5.1.0.GA/server/default/deploy/TestServiceLayer.war/ state=PreReal mode=Manual requiredState=Real

    org.jboss.deployers.spi.DeploymentException: Error during deploy: org.jboss.metadata.jpa.spec.PersistenceUnitMetaData.bts-72

    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)

    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.install(DeployersImpl.java:1098)

    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

    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:702)

    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

    at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

    at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

    at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

    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.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

    at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

    at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

    at org.jboss.Main.boot(Main.java:221)

    at org.jboss.Main$1.run(Main.java:556)

    at java.lang.Thread.run(Unknown Source)

    Caused by: java.lang.NullPointerException

    at java.util.Hashtable.put(Unknown Source)

    at java.util.Hashtable.putAll(Unknown Source)

    at org.jboss.jpa.deployers.PersistenceUnitDeployer.addDependencies(PersistenceUnitDeployer.java:75)

    at org.jboss.jpa.deployers.PersistenceUnitDeployer.deploy(PersistenceUnitDeployer.java:117)

    at org.jboss.jpa.deployers.PersistenceUnitDeployer.deploy(PersistenceUnitDeployer.java:51)

    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)

    ... 30 more

    I am struggling a lot to overcome this exception.

    May be someone can help me with some tips to overcome this exception.

    Thanking in advance

    Chandan

    DB:2.70:War Accessing A Jar With Jpa Entities,Spring And Persistence.Xml In Jboss-5.1.0.Ga fx


    The issue here is your persistence.xml should be in a jar/war file that would be first picked up by your appserver.

    In your case the war is first deployed and because your war needs to be deployed the JPA jar is being deployed.

    The trick here would be move the persistence,xml to the META-INF of your war.Once you have the file here your container will pick up the xml file.

    Or if your creating an ear file using maven specify the jar in your module section of ear plugin

  • RELEVANCY SCORE 2.70

    DB:2.70:Design Framework To Decouple Business Rules From Jsf/Spring Bean 1k


    We use JSF beans in the Presentation layer and Spring beans in the Service layer.
    The JSF Backing beans are designated as XXXBean.java whereas Spring beans are designated as XXXManagerImpl.java and are suppose to implement business rules and then call Spring's ORM Hibernate Template to do the persistence to database.

    The problem is JSF/Spring beans are suppose to implement 20-30 business rules. This will eventually in implementing 20-30 methods in JSF/Spring beans

    So we are thinking to decouple the business rules from manager methods into a separate Interface with Concrete class implementing the Rule

    For example each of the XXXManagerImpl.java will have dependency injection of its co-oresponding XXXRuleManager with each of the rules specified as methods

    Here is the code snippet in manager method
    public Class XXXManagerImpl implements XXXManager
    {
    private XXXRuleManager XXXruleManager;
    //getters/setter methods for XXXRuleManager
    XXXruleManager.applyCreateXXXRules();
    XXXruleManager.applyUpdateXXXRules();
    XXXruleManager.applyDeleteXXXRules();
    XXXruleManager.applyValidateXXXRules();

    //Persistence
    hibernateTemplate.save(object);
    }

    We hope applyCreateXXXRules() will have set of rules and Iterator will iterate thru each of these rules by calling applyRule() methods to create an object

    The goal is to make this draft into design which is extensible when we add/delete new rules. Also when we bring new developers to the team, they should be able to implement the rule without stepping on each other code

    Any pointers/suggestions to make this draft into design will be greatly app

    DB:2.70:Design Framework To Decouple Business Rules From Jsf/Spring Bean 1k

    We use JSF beans in the Presentation layer and Spring beans in the Service layer.
    The JSF Backing beans are designated as XXXBean.java whereas Spring beans are designated as XXXManagerImpl.java and are suppose to implement business rules and then call Spring's ORM Hibernate Template to do the persistence to database.

    The problem is JSF/Spring beans are suppose to implement 20-30 business rules. This will eventually in implementing 20-30 methods in JSF/Spring beans

    So we are thinking to decouple the business rules from manager methods into a separate Interface with Concrete class implementing the Rule

    For example each of the XXXManagerImpl.java will have dependency injection of its co-oresponding XXXRuleManager with each of the rules specified as methods

    Here is the code snippet in manager method
    public Class XXXManagerImpl implements XXXManager
    {
    private XXXRuleManager XXXruleManager;
    //getters/setter methods for XXXRuleManager
    XXXruleManager.applyCreateXXXRules();
    XXXruleManager.applyUpdateXXXRules();
    XXXruleManager.applyDeleteXXXRules();
    XXXruleManager.applyValidateXXXRules();

    //Persistence
    hibernateTemplate.save(object);
    }

    We hope applyCreateXXXRules() will have set of rules and Iterator will iterate thru each of these rules by calling applyRule() methods to create an object

    The goal is to make this draft into design which is extensible when we add/delete new rules. Also when we bring new developers to the team, they should be able to implement the rule without stepping on each other code

    Any pointers/suggestions to make this draft into design will be greatly app

  • RELEVANCY SCORE 2.68

    DB:2.68:Weblogic Classloder Issue With Spring, Hibernate, Ear's And War's ja


    Hi,

    I am using Weblogic10, Hibernate-3.2.5.ga, Spring-2.5.1 and cglib-2.1_3.

    My application is currently being deployed as an ear, containing a jar and a rar. The structure is as follows:

    project.ear
    |- project.jar
    |- project.rar
    |- spring.jar
    |- hibernate.jar
    |- cglib.jar

    My Resource Adapter xml looks as follows:
    ?xml version="1.0" encoding="UTF-8"?
    connector
    xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
    version="1.5"
    display-nameGT_OUT/display-name
    vendor-nameSpring Framework/vendor-name
    eis-typeSpring Connector/eis-type
    resourceadapter-version1.0/resourceadapter-version
    resourceadapter
    resourceadapter-classorg.springframework.jca.context.SpringContextResourceAdapter/resourceadapter-class
    config-property
    config-property-nameContextConfigLocation/config-property-name
    config-property-typejava.lang.String/config-property-type
    config-property-value
    classpath:spring-applicationContext.xml,
    classpath:spring-datasources.xml,
    classpath:spring-messaging.xml,
    classpath:spring-persistence.xml,
    classpath:spring-transactions.xml
    /config-property-value
    /config-property
    /resourceadapter
    /connectorThe spring application contexts live in project.jar. The manifest files for both project.jar and project.rar looks as follows:

    Manifest-Version: 1.0
    Class-Path:
    hibernate-entitymanager-3.3.1.ga.jar
    hibernate-commons-annotations-3.0.0.ga.jar
    hibernate-annotations-3.3.0.ga.jar
    gtout-core-1.0-SNAPSHOT.jar
    concurrent-1.3.4.jar
    javassist-3.3.ga.jar
    hibernate-3.2.5.ga.jar
    cglib-2.1_3.jar
    asm-1.5.3.jar
    asm-attrs-1.5.3.jar
    spring-2.5.1.jarWhen I deploy the EAR, the RAR is correctly loaded and configuration begins via spring. I have an EntityManager defined in a spring file as:

    ?xml version="1.0" encoding="UTF-8"?
    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:p="http://www.springframework.org/schema/p"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"

    bean id="jpaVendorAdapter"
    class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"
    p:databasePlatform="org.hibernate.dialect.HSQLDialect"/

    bean id="entityManagerFactory"
    class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"
    p:dataSource-ref="datasource"
    p:jpaVendorAdapter-ref="jpaVendorAdapter"/

    /beansWhen this bean is being initialized I am receiving the following exception:
    Caused by: net.sf.cglib.core.CodeGenerationException: java.lang.reflect.InvocationTargetException--null
    at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:237)
    at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377)
    at net.sf.cglib.proxy.Enhancer.createClass(Enhancer.java:317)
    at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:127)
    at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43)
    at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162)
    at org.hibernate.tuple.entity.AbstractEntityTuplizer.init(AbstractEntityTuplizer.java:135)
    at org.hibernate.tuple.entity.PojoEntityTuplizer.init(PojoEntityTuplizer.java:55)
    at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping.init(EntityEntityModeToTuplizerMapping.java:56)
    at org.hibernate.tuple.entity.EntityMetamodel.init(EntityMetamodel.java:295)
    at org.hibernate.persister.entity.AbstractEntityPersister.init(AbstractEntityPersister.java:434)
    at org.hibernate.persister.entity.SingleTableEntityPersister.init(SingleTableEntityPersister.java:109)
    at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
    at org.hibernate.impl.SessionFactoryImpl.init(SessionFactoryImpl.java:226)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
    at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730)
    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127)
    at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:221)
    at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:251)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
    ... 59 more
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at net.sf.cglib.core.ReflectUtils.defineClass(ReflectUtils.java:384)
    at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:219)
    ... 80 more
    Caused by: java.lang.NoClassDefFoundError: org/hibernate/proxy/HibernateProxy
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    ... 86 moreI've looked around and noticed that CGLib perhaps runs in different classloader???
    Looking at the stacktrace, it can be seen that Hibernate is on the classpath as some of its classes are being used, which in turn calls cglib. Cglib then tries to call Hibernate but cant find it!? I dont get it ...

    Any help would be great!!

    Cheers

    Ryan

    DB:2.68:Weblogic Classloder Issue With Spring, Hibernate, Ear's And War's ja

    Hi, I got registered to this bea forms, can you help on where to go for posting new blog.

    - -

    Weblogic Consultant

  • RELEVANCY SCORE 2.67

    DB:2.67:Invoking Jboss Eap5 Ejbs From Eap6 kz



    Good morning everybody.

    I'm trying to solve a problem with new EAP6 (RedHat version 7.1.2). My company has a bunch of (almost) new ejb cluster, developed and maintained on EAP5 (RedHat 5.1.1 and 5.1.2). I'd like to suggest migration for the frontends to an EAP6, given the numerous benefits of the new platform.

    This is the situation: usually our frontends use Spring 3 and velocity as development framework, and SimpleRemoteStatelessSessionProxyFactoryBean as abstraction to invoke the ejb layer.

    I've managed to solve problems related to templating injection, but still I'm not able to deploy web frontend. I will try as much to clarify my conf.

    First, the error:

    10:49:53,658 ERROR [org.springframework.web.servlet.DispatcherServlet] (MSC service thread 1-4) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceStatusInterceptor': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private it.cmp.extranetpf.common.util.ServiceListHelper it.cmp.extranetpf.common.interceptors.ServiceStatusInterceptor.serviceListHelper; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceListHelper': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private it.cmp.ejb.service.ServiceGenericEJB it.cmp.extranetpf.common.util.ServiceListHelper.serviceGenericEJB; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [it.cmp.ejb.service.ServiceGenericEJB] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true), @org.springframework.beans.factory.annotation.Qualifier(value=serviceGenericEjb)}

    Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceGenericEjb' defined in ServletContext resource [/WEB-INF/conf/app-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: serviceGenericEjb -- service jboss.naming.context.java.serviceGenericEjb

    Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceGenericEjb' defined in ServletContext resource [/WEB-INF/conf/app-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: serviceGenericEjb -- service jboss.naming.context.java.serviceGenericEjb

    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:285) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1074) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

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

    ...

    And this is the bean definition:

    bean id="serviceGenericEjb" lazy-init="true" class="it.cmp.extranetpf.common.util.EjbFactoryBean"

    property name="jndiName" value="serviceGenericEjb"/

    !--

    property name="jndiName" value="ejb:jndirvinterface/jndirvinterface-ejb//serviceGenericEjb!it.cmp.ejb.service.ServiceGenericEJB"/

    --

    property name="businessInterface" value="it.cmp.ejb.service.ServiceGenericEJB"/

    property name="jndiTemplate"ref bean="remoteBankingJndi"//property

    property name="refreshHomeOnConnectFailure" value="true" /

    /bean

    And finally my jndi.properties:

    java.naming.provider.url=remote://remotehost.hostdomain:4546

    As you can see I tryed also the new romoting solution (jndiName commented out), but still no luck.

    My question is: is there a way to solve this without modifing frontend code (with works smoothly if deployed on EAP5)?

    Thank you very much.

    DB:2.67:Invoking Jboss Eap5 Ejbs From Eap6 kz


    Good morning everybody.

    I'm trying to solve a problem with new EAP6 (RedHat version 7.1.2). My company has a bunch of (almost) new ejb cluster, developed and maintained on EAP5 (RedHat 5.1.1 and 5.1.2). I'd like to suggest migration for the frontends to an EAP6, given the numerous benefits of the new platform.

    This is the situation: usually our frontends use Spring 3 and velocity as development framework, and SimpleRemoteStatelessSessionProxyFactoryBean as abstraction to invoke the ejb layer.

    I've managed to solve problems related to templating injection, but still I'm not able to deploy web frontend. I will try as much to clarify my conf.

    First, the error:

    10:49:53,658 ERROR [org.springframework.web.servlet.DispatcherServlet] (MSC service thread 1-4) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceStatusInterceptor': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private it.cmp.extranetpf.common.util.ServiceListHelper it.cmp.extranetpf.common.interceptors.ServiceStatusInterceptor.serviceListHelper; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceListHelper': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private it.cmp.ejb.service.ServiceGenericEJB it.cmp.extranetpf.common.util.ServiceListHelper.serviceGenericEJB; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [it.cmp.ejb.service.ServiceGenericEJB] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true), @org.springframework.beans.factory.annotation.Qualifier(value=serviceGenericEjb)}

    Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceGenericEjb' defined in ServletContext resource [/WEB-INF/conf/app-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: serviceGenericEjb -- service jboss.naming.context.java.serviceGenericEjb

    Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceGenericEjb' defined in ServletContext resource [/WEB-INF/conf/app-config.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: serviceGenericEjb -- service jboss.naming.context.java.serviceGenericEjb

    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:285) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1074) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

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

    ...

    And this is the bean definition:

    bean id="serviceGenericEjb" lazy-init="true" class="it.cmp.extranetpf.common.util.EjbFactoryBean"

    property name="jndiName" value="serviceGenericEjb"/

    !--

    property name="jndiName" value="ejb:jndirvinterface/jndirvinterface-ejb//serviceGenericEjb!it.cmp.ejb.service.ServiceGenericEJB"/

    --

    property name="businessInterface" value="it.cmp.ejb.service.ServiceGenericEJB"/

    property name="jndiTemplate"ref bean="remoteBankingJndi"//property

    property name="refreshHomeOnConnectFailure" value="true" /

    /bean

    And finally my jndi.properties:

    java.naming.provider.url=remote://remotehost.hostdomain:4546

    As you can see I tryed also the new romoting solution (jndiName commented out), but still no luck.

    My question is: is there a way to solve this without modifing frontend code (with works smoothly if deployed on EAP5)?

    Thank you very much.

  • RELEVANCY SCORE 2.67

    DB:2.67:Boot Strapping Spring Inside Jboss sc



    Hi there, I'm trying to bootstrap Spring and a bunch of spring related beans inside Jboss without using the .spring deployer, because I need to be able to deploy this inside WAS too. My web.xml and spring libraries work inside WAS, but when i put it over onto JBoss, JBoss reads the web.xml and everything appears to be okay, but it never triggers any of the Listeners, even to create them. Am i missing something? I've followed the following: http://www.codechimp.net/?p=22Any help would be greatly appreciated.

    DB:2.67:Boot Strapping Spring Inside Jboss sc


    ...i don't know why listener and don't appear. They are in the xml file, and i just cut and pasted it here.

  • RELEVANCY SCORE 2.67

    DB:2.67:Jackson @Jsonignore Being Ignored In Ejb3.1 Beans Deployed In Jboss As d3



    I have a spring REST controller (.war file) that accesses ejb3.1 entity beans ( jar) in a single ear file.

    I have used the @JsonIgnore annotation in my entity beans to try and ignore certain properties but when spring uses json to serialize the entity instance the ignored properties are present.

    Has anyone faced an issue of @JsonIgnore failing to ignore properties ?

    DB:2.67:Jackson @Jsonignore Being Ignored In Ejb3.1 Beans Deployed In Jboss As d3


    Can you create a simple WAR without Spring and see if it works OOTB (possibly isolating the issue to Spring)?

  • RELEVANCY SCORE 2.66

    DB:2.66:Spring 3.1 Hibernate 4 Infinispan Jndi Problem dj



    Hi,

    I am trying to deploy my aplication to jboss-as 7.1.0.CR1b. But I am not able to configure session factory. My spring configuration like below

    bean id="sessionFactory"
    class="org.springframework.orm.hibernate4.LocalSessionFactoryBean"
    property name="dataSource" ref="dataSource"/
    property name="hibernateProperties"
    props
    prop key="hibernate.dialect"org.hibernate.dialect.MySQLDialect/prop
    prop key="hibernate.hbm2ddl.auto"update/prop
    prop key="hibernate.cache.use_minimal_puts"true/prop
    prop key="hibernate.cache.use_structured_entries"true/prop
    prop key="hibernate.cache.use_second_level_cache"true/prop
    prop key="hibernate.cache.use_query_cache"true/prop
    prop key="hibernate.connection.release_mode"auto/prop
    prop key="hibernate.show_sql"true/prop
    prop key="hibernate.format_sql"false/prop
    prop key="hibernate.transaction.factory_class"org.hibernate.transaction.CMTTransactionFactory/prop
    prop key="hibernate.transaction.manager_lookup_class"org.hibernate.transaction.JBossTransactionManagerLookup/prop
    prop key="hibernate.cache.infinispan.cachemanager"java:jboss/infinispan/hibernate/prop
    prop key="hibernate.cache.region.factory_class"org.hibernate.cache.infinispan.JndiInfinispanRegionFactory/prop
    /props
    /property
    property name="packagesToScan" value="com.granul.domain" /
    /bean

    bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean"
    property name="jndiName" value="java:jboss/datasources/MyDatasourceDS" /
    /bean

    bean id="transactionManager"
    class="org.springframework.transaction.jta.JtaTransactionManager" /

    The exception is like below

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [adminApplicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.cache.CacheException: Unable to retrieve CacheManager from JNDI [java:jboss/infinispan/hibernate]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:848) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:790) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:707) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:478) [spring-beans-3.1.0.RELEASE.jar:]
    ... 36 more
    Caused by: org.hibernate.cache.CacheException: Unable to retrieve CacheManager from JNDI [java:jboss/infinispan/hibernate]
    at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.locateCacheManager(JndiInfinispanRegionFactory.java:75) [hibernate-infinispan-4.0.1.Final.jar:]
    at org.hibernate.cache.infinispan.JndiInfinispanRegionFactory.createCacheManager(JndiInfinispanRegionFactory.java:64) [hibernate-infinispan-4.0.1.Final.jar:]
    at org.hibernate.cache.infinispan.InfinispanRegionFactory.start(InfinispanRegionFactory.java:275) [hibernate-infinispan-4.0.1.Final.jar:]
    at org.hibernate.internal.SessionFactoryImpl.init(SessionFactoryImpl.java:271) [hibernate-core-4.0.1.Final.jar:]
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737) [hibernate-core-4.0.1.Final.jar:]
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1775) [hibernate-core-4.0.1.Final.jar:]
    at org.springframework.orm.hibernate4.LocalSessionFactoryBuilder.buildSessionFactory(LocalSessionFactoryBuilder.java:184) [spring-orm-3.1.0.RELEASE.jar:]
    at org.springframework.orm.hibernate4.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:314) [spring-orm-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) [spring-beans-3.1.0.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) [spring-beans-3.1.0.RELEASE.jar:]
    ... 46 more

    Also my standalone xml attached

    DB:2.66:Spring 3.1 Hibernate 4 Infinispan Jndi Problem dj


    Hi Galder,

    When I removed "hibernate.cache.region.factory_class"

    I saw error:

    Caused by: org.hibernate.cache.NoCachingEnabledException: Second-level cache is not enabled for usage [hibernate.cache.use_second_level_cache | hibernate.cache.use_query_cache]

    at org.hibernate.cache.internal.NoCachingRegionFactory.buildEntityRegion(NoCachingRegionFactory.java:69)

    at org.hibernate.internal.SessionFactoryImpl.init(SessionFactoryImpl.java:347)

    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1740)

    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1778)

    at org.springframework.orm.hibernate4.LocalSessionFactoryBuilder.buildSessionFactory(LocalSessionFactoryBuilder.java:189)

    at org.springframework.orm.hibernate4.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:350)

    at org.springframework.orm.hibernate4.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:335)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452)

    Here is my configure, I use spring bean

    hibernate.dialect=org.hibernate.dialect.MySQLDialect

    hibernate.hbm2ddl.auto=update

    jboss.as.jpa.providerModule=hibernate3-bundled

    hibernate.cache.use_second_level_cache=true

    hibernate.cache.use_query_cache=true

    hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory

    hibernate.transaction.manager_lookup_class=org.hibernate.transaction.JBossTransactionManagerLookup

    hibernate.jta.UserTransaction = UserTransaction

    hibernate.transaction.flush_before_completion=true

    hibernate.transaction.auto_close_session=true

    hibernate.cache.infinispan.cfg=/tmp/infinispan-configs.xml

    hibernate.generate_statistics=true

    hibernate.jdbc.batch_size=30

    shared-cache-mode=ENABLE_SELECTIVE

    Could you please give me some advise?

  • RELEVANCY SCORE 2.66

    DB:2.66:Scope-Related Annotations ap


    I tried googling javax.webbeans.SessionScoped api and nothing. Is there a JavaDoc available for Web Beans?
    Also, in the numberguess src code, I'm seeing these annotations:
    @Named@SessionScoped@ApplicationScoped
    which are very similar to existing Seam annotations:
    @Name@Scope(...)
    This is obviously confusing to a Seam developer. When Web Beans becomes the core of Seam 3, which annotations will be used? I'm guessing the new Web Beans ones...

    DB:2.66:Scope-Related Annotations ap

    http://docs.jboss.org/webbeans/apidocs/1.0.0.ALPHA2/ - we'll still support Seam as a legacy mode in Seam3, not sure how yet.

  • RELEVANCY SCORE 2.66

    DB:2.66:Jandex To Improve Component Scanning Perforamance? c1



    Spring component scanning does something very similar to what JBoss does, it looks for classes with certain annotations. However Spring component scanning can perform quite badly when you have a lot of classes in your deployment.

    I was wondering whether it would be possible to hook into Spring component scanning and make it use the JBoss class scanning infrastructure.

    DB:2.66:Jandex To Improve Component Scanning Perforamance? c1


    Hi Philippe,

    I think that it would be a very valuable addition, performance-wise. I have considered for the Snowdrop roadmap - of course, any contributions on that would be very welcome.

    Cheers,

    Marius

  • RELEVANCY SCORE 2.65

    DB:2.65:Spring And Adf Faces dz


    I saw this on the internet:

    http://www.springone.com/display/SpringOne06/Integrating+Spring+with+the+Oracle+Application+Development+Framework

    It mentions that in 11g you will be able to drag and drop spring managed beans onto a JSF page but I don't see this mentioned in the 11g new features.

    Is this a feature of the Spring plugin?

    Peter.

    DB:2.65:Spring And Adf Faces dz

    Maybe this would help:

    http://www.oracle.com/technology/pub/articles/dikmans-spring-toplink.html

  • RELEVANCY SCORE 2.64

    DB:2.64:Extracting Service. Joining Tables Across Schemas. Using Hib sx



    Hello SeamersI'm doing a pilot Seam application for my employer, which already uses Hibernate and Spring. We like the ease of use, but we are wrestling with some questions.1. We would like to factor out any reusable "business logic" into a service layer, possibly in a different EAR. It is clear that we can access EJBs remotely from Seam, but can we deploy Seam's session beans to a different EAR and access it from the rest of the application. Is it advisable?2. We have concerns about hardcoding the OR-mapping in the Java annotations. Is it possible to use Hibernate xml mappning files for part of the mappings along with the annotations?3. Is it possible to map tables in different schemas to the same network of objects, without hardcoding the schema names in the Java source files?We will be grateful for any input (and RTFM advice as long as it includes page numbers).TKummer

    DB:2.64:Extracting Service. Joining Tables Across Schemas. Using Hib sx


    "kummer" wrote:2. We have concerns about hardcoding the OR-mapping in the Java annotations. Is it possible to use Hibernate xml mappning files for part of the mappings along with the annotations?You can use a mix of hbm.xml files, orm.xml files (JPA/EJB3 xml schema) and annotations. AFAIK you can mix annotations and xml for a class. 3. Is it possible to map tables in different schemas to the same network of objects, without hardcoding the schema names in the Java source files?You should be able to do this using xml

  • RELEVANCY SCORE 2.64

    DB:2.64:Spring Annotations Tx:Annotation-Driven/ 3p



    Hi,

    I am using jboss-eap-4.2 with Spring 3.0 and using annotations. I am using @Transactional annotation on my DAO as shown below :

    @Repository("chatSessionDAO")@Transactionalpublic class ChatSessionDAO extends MercerChatDAO { /** mySessionFactory */ @Autowired @Qualifier("mySessionFactory") private LocalSessionFactoryBean mySessionFactory; /** chatAlertsDO */ @Autowired @Qualifier("chatAlertsDO") private MHRContChatAlertsDO chatAlertsDO; /** * Method to retrieve chat session objects for a particular id * * @param chatSessionQO * @return * @throws MercerException */ public List? retrieveSessionInfo(ChatSessionQO chatSessionQO) throws MercerException { Criteria criteria = null; List? lstReturn = null; try { long chatSessionId = chatSessionQO.getChatSessionId(); Long chatSessionIdLong = new Long(chatSessionId); log.info("creating criteria for chatsession"); SessionFactory sessionFactory = mySessionFactory.getObject(); Session session = sessionFactory.getCurrentSession(); criteria = session.createCriteria(MHRContChatSessionDO.class, "chatSession").add( Restrictions.eq("id", chatSessionIdLong)); if (criteria != null) { lstReturn = processQuery(criteria); } } catch (Exception e) { log.error("error :::", e); throw new MercerException("No transaction"); } return lstReturn; }

    and on starting the server I am getting the following error:

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'chatSessionDAO' defined in file [/local/jboss-eap-4.2/jboss-as/server/mercer02/deploy/mercerhr.ear/mercer.war/WEB-INF/classes/com/mercer/chat/app/dao/ChatSessionDAO.class]: Initialization of bean failed; nested exception is java.lang.VerifyError: (class: com/mercer/chat/app/dao/ChatSessionDAO$$EnhancerByCGLIB$$c2bd3f90$$FastClassByCGLIB$$bc114739, method: invoke signature: (ILjava/lang/Object;[Ljava/lang/ObjectLjava/lang/Object Inconsistent stack height 2 != 1

    I am using tx:annotation-driven/ as follows:

    ?xml version="1.0" encoding="UTF-8"?

    beans xmlns="http://www.springframework.org/schema/beans"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:task="http://www.springframework.org/schema/task"

    xmlns:context="http://www.springframework.org/schema/context"

    xmlns:tx="http://www.springframework.org/schema/tx"

    xsi:schemaLocation="http://www.springframework.org/schema/task

    http://www.springframework.org/schema/task/spring-task-3.0.xsd

    http://www.springframework.org/schema/beans

    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

    http://www.springframework.org/schema/tx

    http://www.springframework.org/schema/tx/spring-tx-3.0.xsd

    http://www.springframework.org/schema/context

    http://www.springframework.org/schema/context/spring-context-3.0.xsd"

    tx:annotation-driven/

    and using JTATransactionManager:

    DB:2.64:Spring Annotations Tx:Annotation-Driven/ 3p


    Thanks for the reply. Any pointers about using classloader isolation for forcing spring to use the CGLIB classes packaged in application.

  • RELEVANCY SCORE 2.64

    DB:2.64:I Want To Add A Spring Technologies Features In My Appliation With Implemenation Of Richfaces. p9



    Hi ,

    I am developing Web application using Richfaces . The flow is like.
    .XHTML --- Managed Beans--Service Layers(Hibernate DB Layer).
    .XHTML --- Managed Beans--Service Layers(Hibernate DB Layer).

    I would like to use of the spring feature into my exiting application which is implementated of richfaces and Hibernate.

    Please suggest to me ,how shall I integrated the spring features in richfaces application.

    Thanks

    DB:2.64:I Want To Add A Spring Technologies Features In My Appliation With Implemenation Of Richfaces. p9


    That's not a RichFaces question, more a generic JSF question. First, think through what Spring features you want to use. Spring has lots of features, and you can pretty much pick which ones you need. Most likely you'll want to use Spring's bean managing capabilities, so you would define your beans in a Spring application context and not the faces-config.xml anymore. You could use Spring's DispatcherServlet or even Spring WebFlow, although you shouldn't decide for the second lightly.

  • RELEVANCY SCORE 2.64

    DB:2.64:Aspectj Can't Find Type Sun.Rmi.Registry.Registryimpl c8



    Hello,

    I'm using 7.1.1.Final and I have the exception below when deploying a Spring AOP application:

    Caused by: org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine modifiers of missing type sun.rmi.registry.RegistryImpl
    [Xlint:cantFindType]
    at org.aspectj.weaver.reflect.ReflectionWorld$ExceptionBasedMessageHandler.handleMessage(ReflectionWorld.java:129) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.Lint$Kind.signal(Lint.java:325) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.MissingResolvedTypeWithKnownSignature.raiseCantFindType(MissingResolvedTypeWithKnownSignature.java:232) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.MissingResolvedTypeWithKnownSignature.getModifiers(MissingResolvedTypeWithKnownSignature.java:104) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.ResolvedType.isInterface(ResolvedType.java:855) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.ResolvedType.getHierarchy(ResolvedType.java:349) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.patterns.KindedPointcut.fastMatch(KindedPointcut.java:126) [aspectjtools-1.6.11.jar:]
    at org.aspectj.weaver.internal.tools.PointcutExpressionImpl.couldMatchJoinPointsInType(PointcutExpressionImpl.java:82) [aspectjtools-1.6.11.jar:]
    at org.springframework.aop.aspectj.AspectJExpressionPointcut.matches(AspectJExpressionPointcut.java:255) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:209) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:263) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.support.AopUtils.findAdvisorsThatCanApply(AopUtils.java:295) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findAdvisorsThatCanApply(AbstractAdvisorAutoProxyCreator.java:117) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findEligibleAdvisors(AbstractAdvisorAutoProxyCreator.java:87) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.getAdvicesAndAdvisorsForBean(AbstractAdvisorAutoProxyCreator.java:68) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.wrapIfNecessary(AbstractAutoProxyCreator.java:359) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.postProcessAfterInitialization(AbstractAutoProxyCreator.java:322) [spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:407) [spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.postProcessObjectFromFactoryBean(AbstractAutowireCapableBeanFactory.java:1598) [spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:162) [spring-beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
    ... 29 more

    DB:2.64:Aspectj Can't Find Type Sun.Rmi.Registry.Registryimpl c8


    OK, I created a new module that exports the JDK rmi and it seems to work.

    module xmlns="urn:jboss:module:1.1" name="sun.jdk.rmi"

    dependencies

    system export="true"

    paths

    path name="sun/rmi/registry"/

    path name="META-INF/services"/

    /paths

    exports

    include-set

    path name="META-INF/services"/

    /include-set

    /exports

    /system

    /dependencies

    /module

  • RELEVANCY SCORE 2.64

    DB:2.64:Deployment Interceptor For Annotations 8c



    Is the way to call some own code at application deploy for proccede own annotations, like ejb3 deployer ? It find all ejb3 annotations and bind enterprise beans to context.

    DB:2.64:Deployment Interceptor For Annotations 8c


    Is the way to call some own code at application deploy for proccede own annotations, like ejb3 deployer ? It find all ejb3 annotations and bind enterprise beans to context.

  • RELEVANCY SCORE 2.63

    DB:2.63:Ejb3 Without Annotations m9


    Hi,

    Is it possible to create EJB 3 beans without using annotations? I'm using a J2EE profiler that doesn't show any EJB data, most likely because annotations are being used. If I can find a way to specify the EJB3 beans without using Java Annotations, then I might starting seeing EJB data.

    Thank you.

    Regards,
    --Will

    DB:2.63:Ejb3 Without Annotations m9

    Hi,

    Is it possible to create EJB 3 beans without using annotations? I'm using a J2EE profiler that doesn't show any EJB data, most likely because annotations are being used. If I can find a way to specify the EJB3 beans without using Java Annotations, then I might starting seeing EJB data.

    Thank you.

    Regards,
    --Will

  • RELEVANCY SCORE 2.63

    DB:2.63:Single Sign-On Between Spring Rmi And Jboss As 6/7 Stateless Session Beans 9p



    Hi all,

    We have a series of external spring based RMI services which make use of interceptors to authenticate user requests against a centralized authentication server. The authentication server exposes entirely propriatary APIs used by the RMI interceptors and uses a user repository (DB based).

    We are working on a project to move these services to standard stateless session beans hosted in JBoss AS 6 (eventually 7). For these new services, we have been able to configure AS to authenticate the incoming users against the same identity data source used by the older authentication server.

    Having described all this, we will not be able to move all the services at once, so for sometime I need to have a few external processes exposing RMI services with the old interceptors. My question is, without complicating the deployment and requiring any new centralized authentication service that handle requests for both the RMI services outside and stateless session beans in AS, can I get my old interceptors on the external RMI services to invoke authentication API in a standard JBoss AS instance? Are there any articles/examples of this type of use case? Or is the only option to move both JBoss and the RMI serviecs to authenticate against a standard central service?

    Ideally I would like to simplify the deployment to a single JBoss instance hosting the new services (stateless session beans), the older spring based RMI service instance and clients logging into JBoss and able to invoke the old Spring based RMI services without anything in the middle.

    DB:2.63:Single Sign-On Between Spring Rmi And Jboss As 6/7 Stateless Session Beans 9p


    Hi all,

    We have a series of external spring based RMI services which make use of interceptors to authenticate user requests against a centralized authentication server. The authentication server exposes entirely propriatary APIs used by the RMI interceptors and uses a user repository (DB based).

    We are working on a project to move these services to standard stateless session beans hosted in JBoss AS 6 (eventually 7). For these new services, we have been able to configure AS to authenticate the incoming users against the same identity data source used by the older authentication server.

    Having described all this, we will not be able to move all the services at once, so for sometime I need to have a few external processes exposing RMI services with the old interceptors. My question is, without complicating the deployment and requiring any new centralized authentication service that handle requests for both the RMI services outside and stateless session beans in AS, can I get my old interceptors on the external RMI services to invoke authentication API in a standard JBoss AS instance? Are there any articles/examples of this type of use case? Or is the only option to move both JBoss and the RMI serviecs to authenticate against a standard central service?

    Ideally I would like to simplify the deployment to a single JBoss instance hosting the new services (stateless session beans), the older spring based RMI service instance and clients logging into JBoss and able to invoke the old Spring based RMI services without anything in the middle.

  • RELEVANCY SCORE 2.63

    DB:2.63:Two Modules Can Not See Meta-Inf Content Of Each Other c8



    HI All,

    I have a scenario where I want have created a Spring module (Which works properly) the spring module is as following:

    ?xml version="1.0" encoding="UTF-8"?
    module xmlns="urn:jboss:module:1.1" name="org.springframework.spring" slot="main"
    resources
    resource-root path="spring-aop-3.0.6.RELEASE.jar"/
    resource-root path="spring-asm-3.0.6.RELEASE.jar"/
    resource-root path="spring-beans-3.0.6.RELEASE.jar"/
    resource-root path="spring-context-3.0.6.RELEASE.jar"
    filter
    include path="META-INF**" /
    include path="org**" /
    /filter
    /resource-root
    resource-root path="spring-context-support-3.0.6.RELEASE.jar"
    filter
    include path="META-INF**" /
    include path="org**" /
    /filter
    /resource-root
    resource-root path="spring-core-3.0.6.RELEASE.jar"/
    resource-root path="spring-expression-3.0.6.RELEASE.jar"/
    resource-root path="spring-jdbc-3.0.6.RELEASE.jar"/
    resource-root path="spring-jms-3.0.6.RELEASE.jar"/
    resource-root path="spring-oxm-3.0.6.RELEASE.jar"/
    resource-root path="spring-test-3.0.6.RELEASE.jar"/
    resource-root path="spring-tx-3.0.6.RELEASE.jar"/
    resource-root path="spring-web-3.0.6.RELEASE.jar"/
    resource-root path="spring-webmvc-3.0.6.RELEASE.jar"/
    /resources
    dependencies
    module name="org.apache.commons.logging"/
    module name="javax.api" export="true"/
    module name="javax.servlet.api" export="true"/
    module name="com.sun.xml.bind" export="true"/
    module name="org.jboss.vfs"/
    module name="javax.el.api" export="true"/
    /dependencies
    /module

    DB:2.63:Two Modules Can Not See Meta-Inf Content Of Each Other c8


    Sure. There are two parts in this statement. First, by "all paths", I'm referring to the linkage algorithm in JBoss Modules which operates on a granularity of directory paths (or packages, which are functionally equivalent to directory paths). Secondly, in a module dependency relationship there are two participants: the dependency (which exports) and the dependent (which imports). The export side by default includes all paths always unless overridden with a different policy (this is what I mean by "export all paths by default"). The import side by default excludes "META-INF" and its subdirectories unless overridden with a different policy.

    Hope this clarifies things.

  • RELEVANCY SCORE 2.63

    DB:2.63:Jboss 7 "Error Creating Bean" 3f



    I'm having errors upon deployment. It says something about beans not being created. I am running hibernate 3.3 anyway,

    Anyone know of a workaround?

    Error output:

    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.instantiateBean(AbstractAutowireCapableBeanFactory.java:965) [spring-bea

    ns-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:911) [spring-

    beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) [spring-beans-

    3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.

    0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
    ject(AbstractBeanFactory.java:293) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
    y.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.6.RELEAS

    E.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
    an(AbstractBeanFactory.java:290) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
    (AbstractBeanFactory.java:192) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver
    .resolveReference(BeanDefinitionValueResolver.java:322) [spring-beans-3.0.6.RELE

    ASE.jar:]
    ... 49 more
    Caused by: org.springframework.beans.BeanInstantiationException: Could not insta

    ntiate bean class [com.

    project.test.prices

    ]: Constructor threw exception; nested exception is org.springframework.

    beans.factory.BeanCreationException: Error creating bean with name 'pricesCont

    roller': Injection of autowired dependencies failed; nested exception is org.spr

    ingframework.beans.factory.BeanCreationException: Could not autowire field: priv

    ate com.project.test.prices com.project.test.prices

    Controller.pricesDao; nested exception is org.springframework.beans.factory.Be

    anCreationException: Error creating bean with name 'pricesDao': Injection of p

    ersistence dependencies failed; nested exception is org.springframework.beans.fa

    ctory.BeanCreationException: Error creating bean with name 'emf' defined in URL

    [vfs:/C:/jboss-as-7.1.0.CR1b/bin/content/prices.war/WEB-INF/classes/spri

    ng-servlet.xml]: Invocation of init method failed; nested exception is javax.per

    sistence.PersistenceException: [PersistenceUnit: PricestPU] Unable to bui

    ld EntityManagerFactory
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:1
    41) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy
    .instantiate(SimpleInstantiationStrategy.java:74) [spring-beans-3.0.6.RELEASE.ja

    r:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.instantiateBean(AbstractAutowireCapableBeanFactory.java:958) [spring-bea

    ns-3.0.6.RELEASE.jar:]
    ... 57 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creati

    ng bean with name 'pricesController': Injection of autowired dependencies fail

    ed; nested exception is org.springframework.beans.factory.BeanCreationException:

    Could not autowire field: private com.project.test.prices; nested exception is org.s

    pringframework.beans.factory.BeanCreationException: Error creating bean with nam

    e 'pricesDao': Injection of persistence dependencies failed; nested exception

    is org.springframework.beans.factory.BeanCreationException: Error creating bean

    with name 'emf' defined in URL [vfs:/C:/jboss-as-7.1.0.CR1b/bin/content/

    prices.war/WEB-INF/classes/spring-servlet.xml]: Invocation of init method failed

    ; nested exception is javax.persistence.PersistenceException: [PersistenceUnit:

    PricestPU] Unable to build EntityManagerFactory
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
    ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java

    :288) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.populateBean(AbstractAutowireCapableBeanFactory.java:1074) [spring-beans

    -3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-

    3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.

    0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
    ject(AbstractBeanFactory.java:293) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
    y.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.6.RELEAS

    E.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
    an(AbstractBeanFactory.java:290) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
    (AbstractBeanFactory.java:192) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.
    preInstantiateSingletons(DefaultListableBeanFactory.java:585) [spring-beans-3.0.

    6.RELEASE.jar:]
    at org.springframework.context.support.AbstractApplicationContext.finish
    BeanFactoryInitialization(AbstractApplicationContext.java:895) [spring-context-3

    .0.6.RELEASE.jar:]
    at org.springframework.context.support.AbstractApplicationContext.refres
    h(AbstractApplicationContext.java:425) [spring-context-3.0.6.RELEASE.jar:]
    at org.springframework.context.support.FileSystemXmlApplicationContext.
    init(FileSystemXmlApplicationContext.java:140) [spring-context-3.0.6.RELEASE.ja

    r:]
    at org.springframework.context.support.FileSystemXmlApplicationContext.
    init(FileSystemXmlApplicationContext.java:84) [spring-context-3.0.6.RELEASE.jar

    :]
    at com.project.security.AuthenticationSuccessHandlerImpl
    .init(AuthenticationSuccessHandlerImpl.java:30) [classes:]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    [:1.7.0_03]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    [:1.7.0_03]
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou
    rce) [:1.7.0_03]
    at java.lang.reflect.Constructor.newInstance(Unknown Source) [:1.7.0_03]
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:1
    26) [spring-beans-3.0.6.RELEASE.jar:]
    ... 59 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Could not au

    towire field: private com.project.test.prices com.project.test.prices.pricesDao; nested exception is org.springframewor

    k.beans.factory.BeanCreationException: Error creating bean with name 'pricesDa

    o': Injection of persistence dependencies failed; nested exception is org.spring

    framework.beans.factory.BeanCreationException: Error creating bean with name 'em

    f' defined in URL [vfs:/C:/jboss-as-7.1.0.CR1b/bin/content/prices.war/WE

    B-INF/classes/spring-servlet.xml]: Invocation of init method failed; nested exce

    ption is javax.persistence.PersistenceException: [PersistenceUnit:

    PricesPU] Unable to build EntityManagerFactory
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
    ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.j

    ava:508) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.annotation.InjectionMetadata.inject
    (InjectionMetadata.java:84) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
    ostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java

    :285) [spring-beans-3.0.6.RELEASE.jar:]
    ... 77 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creati

    ng bean with name 'pricesDao': Injection of persistence dependencies failed; n

    ested exception is org.springframework.beans.factory.BeanCreationException: Erro

    r creating bean with name 'emf' defined in URL [vfs:/C:/jboss-as-7.1.0.CR1b/bin/

    content/prices.war/WEB-INF/classes/spring-servlet.xml]: Invocation of in

    it method failed; nested exception is javax.persistence.PersistenceException: [P

    ersistenceUnit: PricesPU] Unable to build EntityManagerFactory
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:341)

    [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.populateBean(AbstractAutowireCapableBeanFactory.java:1074) [spring-beans

    -3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-

    3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.

    0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
    ject(AbstractBeanFactory.java:293) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
    y.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.6.RELEAS

    E.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
    an(AbstractBeanFactory.java:290) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
    (AbstractBeanFactory.java:192) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.
    findAutowireCandidates(DefaultListableBeanFactory.java:848) [spring-beans-3.0.6.

    RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.
    doResolveDependency(DefaultListableBeanFactory.java:790) [spring-beans-3.0.6.REL

    EASE.jar:]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.
    resolveDependency(DefaultListableBeanFactory.java:707) [spring-beans-3.0.6.RELEA

    SE.jar:]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanP
    ostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.j

    ava:480) [spring-beans-3.0.6.RELEASE.jar:]
    ... 79 more
    Caused by: org.springframework.beans.factory.BeanCreationException: Error creati

    ng bean with name 'emf' defined in URL [vfs:/C:/jboss-as-7.1.0.CR1b/bin/content/

    Pricest.war/WEB-INF/classes/spring-servlet.xml]: Invocation of init metho

    d failed; nested exception is javax.persistence.PersistenceException: [Persisten

    ceUnit: PricestPU] Unable to build EntityManagerFactory
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420) [spring-bea

    ns-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-

    3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.

    0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
    ject(AbstractBeanFactory.java:293) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
    y.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.6.RELEAS

    E.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
    an(AbstractBeanFactory.java:290) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
    (AbstractBeanFactory.java:192) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.orm.jpa.EntityManagerFactoryUtils.findEntityManag
    erFactory(EntityManagerFactoryUtils.java:98) [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor.findNamedEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java:

    510) [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor.findEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java:492)

    [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor$PersistenceElement.resolveEntityManager(PersistenceAnnotationBeanPostProce

    ssor.java:656) [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor$PersistenceElement.getResourceToInject(PersistenceAnnotationBeanPostProces

    sor.java:629) [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.beans.factory.annotation.InjectionMetadata$Inject
    edElement.inject(InjectionMetadata.java:147) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.annotation.InjectionMetadata.inject
    (InjectionMetadata.java:84) [spring-beans-3.0.6.RELEASE.jar:]
    at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
    essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:338)

    [spring-orm-3.0.5.RELEASE.jar:]
    ... 90 more
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit:

    PricesPU] Unable to build EntityManagerFactory
    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
    figuration.java:914) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
    figuration.java:890) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
    ctory(HibernatePersistence.java:73) [hibernate-entitymanager-4.0.0.Final.jar:4.0

    .0.Final]
    at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.cr
    eateNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225)

    [spring-orm-3.0.5.RELEASE.jar:]
    at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPro
    pertiesSet(AbstractEntityManagerFactoryBean.java:308) [spring-orm-3.0.5.RELEASE.

    jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477) [spring-

    beans-3.0.6.RELEASE.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417) [spring-bea

    ns-3.0.6.RELEASE.jar:]
    ... 104 more
    Caused by: org.hibernate.AnnotationException: @OneToOne or @ManyToOne on com.cat

    alyst.Prices.TeamProjects.projects references an unknown entity: com.cat

    alyst.Prices.Projects
    at org.hibernate.cfg.ToOneFkSecondPass.doSecondPass(ToOneFkSecondPass.ja
    va:109) [hibernate-core-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.cfg.Configuration.processEndOfQueue(Configuration.java:
    1514) [hibernate-core-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.cfg.Configuration.processFkSecondPassInOrder(Configurat
    ion.java:1437) [hibernate-core-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:
    1355) [hibernate-core-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
    a:1724) [hibernate-core-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.ejb.EntityManagerFactoryImpl.init(EntityManagerFactor
    yImpl.java:76) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final]
    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
    figuration.java:905) [hibernate-entitymanager-4.0.0.Final.jar:4.0.0.Final]
    ... 110 more

    09:13:14,602 ERROR [org.apache.catalina.core.StandardContext] (MSC service threa

    d 1-3) Error listenerStart

    09:13:14,603 ERROR [org.apache.catalina.core.StandardContext] (MSC service threa

    d 1-3) Context [/Prices] startup failed due to previous errors

    09:13:14,617 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-

    host].[/Prices]] (MSC service thread 1-3) Closing Spring root WebApplica

    tionContext

    09:13:14,620 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC0000

    1: Failed to start service jboss.web.deployment.default-host./Prices: or

    g.jboss.msc.service.StartException in service jboss.web.deployment.default-host.

    /Prices: failed to start context
    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentS
    ervice.java:82)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Se
    rviceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont
    rollerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [:1
    .7.0_03]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:
    1.7.0_03]
    at java.lang.Thread.run(Unknown Source) [:1.7.0_03]

    09:13:14,845 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015

    856: Undeploy of deployment "prices.war" was rolled back with failure me

    ssage {"JBAS014671: Failed services" = {"jboss.web.deployment.default-host./Tea

    mAssessment" = "org.jboss.msc.service.StartException in service jboss.web.deplo

    yment.default-host./Prices: failed to start context"}}

    09:13:14,872 INFO [org.jboss.jpa] (MSC service thread 1-1) JBAS011403: Stopping

    Persistence Unit Service 'prices.war#PricesPU'

    09:13:15,017 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Sto

    pped deployment Prices.war in 171ms

    09:13:15,019 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBA

    S014774: Service status report
    JBAS014777: Services which failed to start: service jboss.web.deployment.
    default-host./Prices: org.jboss.msc.service.StartException in service jb

    oss.web.deployment.default-host./Prices: failed to start context

    09:13:15,023 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t

    hreads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps

    that failed:" = {"Operation step-2" = {"JBAS014671: Failed services" = {"jbos

    s.web.deployment.default-host./Prices" = "org.jboss.msc.service.StartEx

    ception in service jboss.web.deployment.default-host./Prices: failed to

    start context"}}}}

    DB:2.63:Jboss 7 "Error Creating Bean" 3f


    i got it fixed, just have to add these in persistence.xml

    property name="hibernate.show_sql" value="false" /
    property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" /

  • RELEVANCY SCORE 2.63

    DB:2.63:Using Configuration Descriptor File To Inject Beans For Jbossws-Cxf On Jboss 6.0.0 sa



    Hello I'm trying to figure out how it is possible to use a configuration xml to inject our POJOs similar to the applicationContext.xml of spring for a project using jbossws-cxf. Is there a standard alternative from jboss? there's tons of examples on how to create a project with annotations. Annotations are, sadly, not an option, since we have to include an old project which does not support annotations. Is there some literature / examples / docs which would help to get me started?

    DB:2.63:Using Configuration Descriptor File To Inject Beans For Jbossws-Cxf On Jboss 6.0.0 sa


    Hello I'm trying to figure out how it is possible to use a configuration xml to inject our POJOs similar to the applicationContext.xml of spring for a project using jbossws-cxf. Is there a standard alternative from jboss? there's tons of examples on how to create a project with annotations. Annotations are, sadly, not an option, since we have to include an old project which does not support annotations. Is there some literature / examples / docs which would help to get me started?

  • RELEVANCY SCORE 2.63

    DB:2.63:Weblogic 12c Wlcompile Javadocparsingexception Using Spring 3 Annotations sm


    Hi All

    I have created a split development EAR project with Spring 3 and Mybatis. The application builds perfect and I was able to connect to database and perform CRUD operations. However if I am trying to use Spring 3 tx:annotation-driven/ and use @Transactional on POJO java file my ant build is failing at wlcompile step. I have included every jar file possible in the classpath but no use. Any help is highly appreciated.

    compile:
    *[wlcompile] [JAM] Warning: failed to resolve class ApplicationLifecycleListener*
    *[wlcompile] [JAM] Warning: failed to resolve class Logger*
    *[wlcompile] [JAM] Error: unexpected exception thrown:*
    *[wlcompile] com.bea.util.jam.internal.javadoc.JavadocParsingException: Parsing failure in C:\xxx\yyy\zzz\testEar\appU*
    tils\src\com\qqq\aaa\service\ImageRepositoryService.java at line 28. Most likely, an annotation is declared whose type has not been imported.
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.getAnnotationTypeFor(JavadocTigerDelegateImpl_150.java:410)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.extractAnnotations(JavadocTigerDelegateImpl_150.java:176)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocTigerDelegateImpl_150.extractAnnotations(JavadocTigerDelegateImpl_150.java:152)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.addAnnotations(JavadocClassBuilder.java:404)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.populate(JavadocClassBuilder.java:359)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.populate(JavadocClassBuilder.java:332)
    [wlcompile] at com.bea.util.jam.internal.javadoc.JavadocClassBuilder.populate(JavadocClassBuilder.java:207)
    [wlcompile] at com.bea.util.jam.internal.elements.ClassImpl.ensureLoaded(ClassImpl.java:725)
    [wlcompile] at com.bea.util.jam.internal.elements.ClassImpl.getAnnotation(ClassImpl.java:394)
    [wlcompile] at weblogic.application.utils.AnnotationDetector.hasAnnotation(AnnotationDetector.java:193)
    [wlcompile] at weblogic.application.utils.AnnotationDetector.hasAnnotatedSources(AnnotationDetector.java:184)
    [wlcompile] at weblogic.ejb.spi.EJBJarUtils.hasEJBSources(EJBJarUtils.java:38)
    [wlcompile] at weblogic.ant.taskdefs.build.module.EJBModuleFactory.claim(EJBModuleFactory.java:48)
    [wlcompile] at weblogic.ant.taskdefs.build.module.ModuleFactory.createModules(ModuleFactory.java:76)
    [wlcompile] at weblogic.ant.taskdefs.build.Application.build(Application.java:59)
    [wlcompile] at weblogic.ant.taskdefs.build.WLCompileTask.privateExecute(WLCompileTask.java:194)
    [wlcompile] at weblogic.ant.taskdefs.build.WLCompileTask.execute(WLCompileTask.java:160)
    [wlcompile] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
    [wlcompile] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
    [wlcompile] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wlcompile] at java.lang.reflect.Method.invoke(Method.java:597)
    [wlcompile] at java.lang.reflect.Method.invoke(Method.java:597)
    [wlcompile] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [wlcompile] at org.apache.tools.ant.Task.perform(Task.java:348)
    [wlcompile] at org.apache.tools.ant.Target.execute(Target.java:392)
    [wlcompile] at org.apache.tools.ant.Target.performTasks(Target.java:413)
    [wlcompile] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
    [wlcompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
    [wlcompile] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wlcompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
    [wlcompile] at org.apache.tools.ant.Main.runBuild(Main.java:811)
    [wlcompile] at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [wlcompile] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
    [wlcompile] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
    *[wlcompile] [JAM] Warning: failed to resolve class ApplicationContext*

    spring: applicationContect.xml

    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd"

    DB:2.63:Weblogic 12c Wlcompile Javadocparsingexception Using Spring 3 Annotations sm

    Thought it's throwing these build errors, it looks like these are warnings. I was able to deploy and my application is running. Not sure how to suppress these warnings.

  • RELEVANCY SCORE 2.62

    DB:2.62:Seam With Spring? 11



    Hi,Firstly, I love your demo! I think when promoting a new framework that has some web functionality it is vitally important to have a polished, professional looking demo, so well done.Also, I'm very glad to see you're using Facelets, nice choice.I've been reading a bit about Seam and it seems very good. A couple of questions that I have:1) Is it possible to use Spring with Seam, rather than EJBs? I read in some of the documentation that if you use JavaBeans rather than the other component types (Entity Beans, Session Beans), that there would be no transaction management. The reason I ask is that I am now experienced with Spring and would prefer to keep using it while hopefully also benefitting from what Seam has to offer at the same time.2) This is a general annotation question really... I personally prefer to work in XML I know this is not fashionable :), but I do find mapping files etc. much easier to read than annotations (was never a fan of xdoclet), so is it possible to use xml instead of annotations? I realise that Seam may not support this yet, so this is more of a long-term question.Thanks,Mike.

    DB:2.62:Seam With Spring? 11


    You should use Component.getInstance(pcName)

  • RELEVANCY SCORE 2.62

    DB:2.62:@Ejb Annotation Does Not Inject A Bean (Jboss 4.0.5) mj


    Hi all,

    We have a project that runs fine under jboss 4.0.4 and uses lots of @EJB annotations on fields to inject session beans.
    We're trying to switch to 4.0.5 and suddenly the @EJB annotations no longer work, and the relevant fields are not initialized.

    (@PersistenceContext annotations work fine)

    Has anybody encountered similar problem?

    Thanks in advance,
    d.

    DB:2.62:@Ejb Annotation Does Not Inject A Bean (Jboss 4.0.5) mj

    Hello,

    Did you check at the jboss relase note ?

    Regards,
    Sebastien Degardin

  • RELEVANCY SCORE 2.62

    DB:2.62:Is It Possible To Inject Beanfactory? mf



    Hi! I'm new to the forums, and I would like to know if it's possible to inject the BeanFactory instead of a bean in an EJB (with the '@Spring' annotation and without using InitialContext and JNDI).I thought it could be possible if I use the @Spring annotation without any beanName, but looking in the source code it seems that inject beans by type.I'm using Jboss 4.2.3 with Spring Deployer 2.1Thanks and regards!!

    DB:2.62:Is It Possible To Inject Beanfactory? mf


    Thanks you very much Justin!!! I will try your solution.

  • RELEVANCY SCORE 2.62

    DB:2.62:Proxyasyncconfiguration 38


    Hi,

    I have spent atleast 14+ hrs on trying to migrate my exisiting spring app to jbossAS7 and would really appreciate anyhelp with the following issue, when attempting to start JBoss:

    Exception:
    02:25:44,885 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC service thread 1-4) Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@78090631: defining beans [org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,econDateInitDatabaseImpl,forexPro,importStaticDataImpl,edIndicatorValueFactoryImpl,edCityDAOImpl,edCountryDAOImpl,edHistoryDAOImpl,edHolidayDAOImpl,edIndicatorDAOImpl,edIndicatorValueDAOImpl,edJobDAOImpl,edRegionDAOImpl,edIndicatorSchedulerImpl,proxyAsyncConfiguration,schedulingConfiguration,loadTimeWeavingConfiguration,proxyTransactionManagementConfiguration,delegatingWebMvcConfiguration,org.springframework.aop.config.internalAutoProxyCreator,org.springframework.transaction.annotation.AnnotationTransactionAttributeSource#0,org.springframework.transaction.interceptor.TransactionInterceptor#0,org.springframework.transaction.config.internalTransactionAdvisor,emf,dataSource,transactionManager,exporter,testBean,schedulerFactoryBean,org.springframework.context.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0,org.springframework.context.annotation.internalAsyncAnnotationProcessor,org.springframework.context.annotation.internalScheduledAnnotationProcessor,loadTimeWeaver,transactionAttributeSource,transactionInterceptor,requestMappingHandlerMapping,viewControllerHandlerMapping,beanNameHandlerMapping,resourceHandlerMapping,defaultServletHandlerMapping,requestMappingHandlerAdapter,mvcConversionService,mvcValidator,httpRequestHandlerAdapter,simpleControllerHandlerAdapter,handlerExceptionResolver]; root of factory hierarchy
    02:25:44,888 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-4) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.annotation.internalAsyncAnnotationProcessor' defined in class path resource [org/springframework/scheduling/annotation/ProxyAsyncConfiguration.class]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor()] threw exception; nested exception is java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:581) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1008) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:904) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:488) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:459) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:728) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:449) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:381) [spring-web-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) [spring-web-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [spring-web-3.1.0.RC1.jar:]
    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
    at java.lang.Thread.run(Thread.java:680) [:1.6.0_29]
    Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor()] threw exception; nested exception is java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:169) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:570) [spring-beans-3.1.0.RC1.jar:]
    ... 21 more
    Caused by: java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.util.Assert.notNull(Assert.java:112) [spring-core-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor(ProxyAsyncConfiguration.java:45) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691.CGLIB$asyncAdvisor$0(generated) [cglib-nodep-2.2.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691$$FastClassByCGLIB$$df56e036.invoke(generated) [cglib-nodep-2.2.jar:]
    at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215) [cglib-nodep-2.2.jar:]
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:253) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691.asyncAdvisor(generated) [cglib-nodep-2.2.jar:]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29]
    at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29]
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:149) [spring-beans-3.1.0.RC1.jar:]
    ... 22 more

    02:25:44,890 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/econdates]] (MSC service thread 1-4) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.annotation.internalAsyncAnnotationProcessor' defined in class path resource [org/springframework/scheduling/annotation/ProxyAsyncConfiguration.class]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor()] threw exception; nested exception is java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:581) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1008) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:904) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:488) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:459) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:728) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:449) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:381) [spring-web-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) [spring-web-3.1.0.RC1.jar:]
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [spring-web-3.1.0.RC1.jar:]
    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
    at java.lang.Thread.run(Thread.java:680) [:1.6.0_29]
    Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor()] threw exception; nested exception is java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:169) [spring-beans-3.1.0.RC1.jar:]
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:570) [spring-beans-3.1.0.RC1.jar:]
    ... 21 more
    Caused by: java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
    at org.springframework.util.Assert.notNull(Assert.java:112) [spring-core-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration.asyncAdvisor(ProxyAsyncConfiguration.java:45) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691.CGLIB$asyncAdvisor$0(generated) [cglib-nodep-2.2.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691$$FastClassByCGLIB$$df56e036.invoke(generated) [cglib-nodep-2.2.jar:]
    at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215) [cglib-nodep-2.2.jar:]
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:253) [spring-context-3.1.0.RC1.jar:]
    at org.springframework.scheduling.annotation.ProxyAsyncConfiguration$$EnhancerByCGLIB$$c8304691.asyncAdvisor(generated) [cglib-nodep-2.2.jar:]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29]
    at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29]
    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:149) [spring-beans-3.1.0.RC1.jar:]
    ... 22 more

    02:25:44,915 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Initializing Mojarra 2.1.3 (SNAPSHOT 20110825) for context '/econdates'
    02:25:45,809 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart
    02:25:45,809 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/econdates] startup failed due to previous errors
    02:25:45,810 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/econdates]] (MSC service thread 1-4) Closing Spring root WebApplicationContext
    02:25:45,812 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /econdates
    02:25:45,858 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "econdates.war"

    DB:2.62:Proxyasyncconfiguration 38


    I get the same error:

    @EnableAsync annotation metadata was not injected

    Could anyone give some advise?

    Thanks very much.

  • RELEVANCY SCORE 2.61

    DB:2.61:Dynamic Injection In Web Beans? kp


    I'm assuming that WB provides a dynamic injection facility similar to Seam.
    So I'd like to know how our apps in terms of DI would work if they were not based on dynamic injection.
    e.g.
    The two major flavors of Dependency Injection are Setter Injection (injection via JavaBean setters); and Constructor Injection (injection via constructor arguments). Spring provides sophisticated support for both, and even allows you to mix the two when configuring theone object. http://www.theserverside.com/tt/articles/article.tss?l=SpringFramework
    So how do Spring/Hibernate apps deal with this limitation? Static injection means stale data, no? So is that the difference b/n a stateless (Spring) and stateful (Seam) framework is that one needs static injection and the other needs dynamic injection?
    This was covered a bit in the Seam ref doc but I'm wondering whether Spring 3 will graduate to dynamic injection as well...
    And how DI compares in WB with DI in Spring 3, generally speaking...

    DB:2.61:Dynamic Injection In Web Beans? kp

    Pete Muir wrote on Aug 09, 2009 23:51:I don't get this? The proxy always looks up the most recent version.Arbi, what is dynamic injection?From SiA:
    If youre familiar with Spring, you might be tempted to use static injectionas the primary means of wiring your components together. I dontrecommend that you standardize on this approach. For one, it requires aridiculous amount of XML. In general, XML should be reserved for infrastructureconfiguration. Although not applicable in this example, youalso must ensure that you arent injecting a component from a shortertermscope into a component in a longer-term scope, as it results inscope impedance. Its much cleaner, safer, and Seam-esque to wire componentstogether using dynamic injection, declared using the @In annotationSo dynamic injection is injection that occurs more than once. It occurs every time a business method is called on that component. Static injection occurs only once in the lifetime of the compoment, either via setter method or constructor.
    Reading my initial post, it has more to do with Spring that Seam/WB but I guess I'll re-word it so it's applicable to this forum:
    If WB/Seam3 uses dynamic injection (most likely it does - at least Seam 2.x does), what would happen if it was designed with static injection instead? What limitation(s) would that bring to our apps? I'm just wondering how Spring apps deal with this stale injection problem on a continual basis and if it is a problem in a stateful or stateless architecture or both.
    I mean, if you can deal with static injection, that means less interceptions and injections than dynamic DI and less overhead per life of a component and overall better performance, no?
    Here's my point:
    What if we wanted static DI sometimes and dyamic DI sometimes in the same component or different components? Mix and match as the use case requires to improve performance. Or is the performance hit negligible with dynamic DI? Not all use cases in a Seam app are modeled using stateful components, are they? What about a report, for example, or a web service consumption/client for a credit card validator service, etc?

  • RELEVANCY SCORE 2.61

    DB:2.61:Jboss 5, Spring 3 Autowiring Beans 8f



    Well, I've looked at all the discussions, docs etc. that I can get my hands on and I'm still having problems getting the beans autowired. I can see the beans being instantiated at deployment time, but they're just not making it into my ServiceBean autowired.

    I've tried using both the SpringLifecycleInterceptor.class/@Spring annotations and the SpringBeanAutowiringInterceptor.class/@Autowire methods. No dice.

    Here's my configs and annotations.

    jboss-spring.xml

    ?xml version="1.0" encoding="UTF-8"?

    beans xmlns="http://www.springframework.org/schema/beans"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xmlns:context="http://www.springframework.org/schema/context"

    xsi:schemaLocation="http://www.springframework.org/schema/beans

    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd

    http://www.springframework.org/schema/context

    http://www.springframework.org/schema/context/spring-context-2.5.xsd"

    descriptionBeanFactory=(reportsApp)/description

    context:annotation-config/

    bean id="connectionFactoryList" class="com.likewise.lucy.util.riak.RiakConnectionFactory"

    property name="clients"

    list

    ref bean="riakClient1"/

    ref bean="riakClient2"/

    /list

    /property

    /bean

    bean id="riakClient1" class="com.basho.riak.client.RiakClient"

    constructor-arg ref="riakConfig1"/

    /bean

    bean id="riakClient2" class="com.basho.riak.client.RiakClient"

    constructor-arg ref="riakConfig2"/

    /bean

    bean id="riakConfig1" class="com.basho.riak.client.RiakConfig"

    property name="url" value="http://10.100.1.119:8091/riak"/

    property name="timeout" value="10000"/

    property name="maxConnections" value="10"/

    /bean

    bean id="riakConfig2" class="com.basho.riak.client.RiakConfig"

    property name="url" value="http://10.100.1.117:8091/riak"/

    property name="timeout" value="10000"/

    property name="maxConnections" value="10"/

    /bean

    !-- import resource="applicationContext.xml"/ --

    /beans

    and class snippet.

    @Service

    @Management(RiakEventsForUserMBean.class)

    @Interceptors(SpringBeanAutowiringInterceptor.class)

    public class RiakEventsForUser implements RiakEventsForUserMBean {

    private boolean started = false;

    @Autowired

    //@Spring(jndiName="reportsApp",bean="connectionFactoryList")

    private RiakConnectionFactory factory;

    // private ApplicationContext ctx;

    I'm sure I'm just missing something simple, but can't seem to figure out what.

    DB:2.61:Jboss 5, Spring 3 Autowiring Beans 8f


    Trying the @Autowired approach and having no luck with that either. It's a little unclear from the docs referenced exactly what ejb 3.0 requires. I have a beanRefContext.xml file defined as so:

    beans

    bean id="beanFactory" class="org.springframework.context.support.ClassPathXmlApplicationContext"

    constructor-arg value="applicationContext.xml" /

    /bean

    /beans

    It's being deployed in the META-INF directory (I tried it at root also - unclear where this should really go).

    I have

    @Interceptors(SpringBeanAutowiringInterceptor.class)

    defined in the ServiceBean implementation and @Autowired on the fields to autowire.

    It _appears_ from the docs that this is all that should be necessary, but it's still not working. Anyway, I think I'm doing what I'm supposed to, but still end up with NPEs when referencing objects that should be autowired.

  • RELEVANCY SCORE 2.61

    DB:2.61:Upgraded To As 7.1.1, Null Pointer Exception Inside Infinispan 8d



    Hello, we are in process of upgrading to 7.1.1, which seems to resolve a number of issues for us, but one new issue has cropped up. Even in standalone mode, I can't run our web app inside AS7.1.1 because Infinispan is throwing a NPE:

    16:25:12,399 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'commonShardEntityManagerFactory' defined in "/home/dburgan/bin/jboss-as-7.1.1.Final/standalone/deployments/pa-testing-web.war/WEB-INF/lib/pa-persistence-1.0.0.M3-SNAPSHOT.jar/META-INF/spring/applicationContext-jpa.xml": Invocation of init method failed; nested exception is java.lang.NullPointerException

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:527) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:728) [spring-context-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:449) [spring-context-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:384) [spring-web-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) [spring-web-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [spring-web-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]

    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'commonShardEntityManagerFactory' defined in "/home/dburgan/bin/jboss-as-7.1.1.Final/standalone/deployments/pa-testing-web.war/WEB-INF/lib/pa-persistence-1.0.0.M3-SNAPSHOT.jar/META-INF/spring/applicationContext-jpa.xml": Invocation of init method failed; nested exception is java.lang.NullPointerException

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:400) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.BeanFactoryUtils.beansOfTypeIncludingAncestors(BeanFactoryUtils.java:275) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.detectPersistenceExceptionTranslators(PersistenceExceptionTranslationInterceptor.java:139) [spring-tx-3.0.6.RELEASE.jar:3.0.6.RELEASE]

    at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.init(PersistenceExceptionTranslationInterceptor.java:79) [spring-tx-3.0.6.RELEASE.jar:3.0.6.RELEASE]

    at org.springframework.dao.annotation.PersistenceExceptionTranslationAdvisor.init(PersistenceExceptionTranslationAdvisor.java:70) [spring-tx-3.0.6.RELEASE.jar:3.0.6.RELEASE]

    at org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor.setBeanFactory(PersistenceExceptionTranslationPostProcessor.java:99) [spring-tx-3.0.6.RELEASE.jar:3.0.6.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeAwareMethods(AbstractAutowireCapableBeanFactory.java:1475) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1443) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    ... 18 more

    Caused by: java.lang.NullPointerException

    at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCache(InfinispanRegionFactory.java:445) [hibernate-infinispan-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:198) [hibernate-infinispan-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.internal.SessionFactoryImpl.init(SessionFactoryImpl.java:339) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.ejb.EntityManagerFactoryImpl.init(EntityManagerFactoryImpl.java:84) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]

    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]

    at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:257) [spring-orm-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310) [spring-orm-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) [spring-beans-3.1.0.RELEASE.jar:3.1.0.RELEASE]

    ... 33 more

    I've traced it into the code and it gets as far as org.infinispan.factories.AbstractComponentRegistry line 406:

    @SuppressWarnings("unchecked")

    public T T getComponent(String componentClassName, String name, boolean nameIsFQCN) {

    Component wrapper = lookupComponent(componentClassName, name, nameIsFQCN);

    if (wrapper == null) return null;

    return (T) unwrapComponent(wrapper);

    }

    Basically the wrapper == null, so it returns null, and this sets off the NPE at InfinispanRegionFactory line 445 as shown above.

    We're using the Infinispan provided by AS7.1.1, so it is 5.1.2 final.

    Here is the standalone.xml:

    http://pastebin.com/sznrbNCY

    Kind of at a loss here. This app was working fine under AS7.1. We go live in a few weeks, so I'd really like to set the precedent of using 7.1.1 since it fixes so many issues. Any suggestions?

    Thanks!Darrell

  • RELEVANCY SCORE 2.61

    DB:2.61:Gsoc - Arquillian Spring Integration d7


    Extend Arquillian to support Spring testing (beans and MVC controllers)

    Ref Mail:

    There are a two different parts to this task. I can explain the first part, and Marius is probably a better person to explain the second.

    Currently, we can test Spring in a EE deployed application by doing all the context/bean lookups etc manually or via a Spring to CDI bridge, but Arquillian has a SPI which is called TestEnricher[1]. What this does is to open up for injections into the TestClass instance.

    e.g.

    public class TestClass {

    @Autowired
    private Bean bean;

    @Test
    public void ....
    }

    So our SpringTestEnricher should simply scan the given TestClass for 'supported' annotations and do the ApplicationContext lookups. (unless Spring has some concept of non contextual injection where you can simply say, inject what ever you know into this 'instance').

    Then, there is the DeployableContianer[2] implementation for Spring, another Arquillian SPI that is responsible for starting/stopping/deploying/undeploying Containers and Deployments. We have implementations of this for JBossAS, GLassFish, Tomcat, Jetty, WebLogic, WebSphere, OpenWebBeans, OpenEJB and Weld++. What this should do in the Spring case is basically accept a ShrinkWrap[3] Archive and 'convert' that into a Spring ApplicationContext.

    ShrinkWrap is a library for creating in memory representations of resources, classes etc. It gives you the option to isolate your test environment from the full client classpath your test is running in. Micro deployments as we like to call them. Test isolation level.

    We welcome Jakub Narloch to the Arquillian Familiy!

    The work will be based out of this repository, fork and enjoy: https://github.com/arquillian/arquillian-container-spring

    The two current tasks are :

    https://issues.jboss.org/browse/ARQ-301 - Create a Spring framework integration (for non-embedded containers)

    https://issues.jboss.org/browse/ARQ-219 - Implement an embedded Spring container

    Jakub, I tried to assign the tasks to you, but I couldn't find you in Jira. You might need to login before I can do that..

    For now I think we can keep an open dialog/discussion in this thread. But we start new threads as needed..

    DB:2.61:Gsoc - Arquillian Spring Integration d7


    Ok Marius,

    I will create the repository and move the code there.

  • RELEVANCY SCORE 2.61

    DB:2.61:Core Logic Of Annotation In Ejb3.0 dk


    Hi,
    How does the container implement the core logic of annotation and identify the Stateless or Stateful Beans and dedicate the pool objects to these.

    I have studied on annotations, but my doubt is that how annotations are used at runtime, which are substitute of deployment descriptors.

  • RELEVANCY SCORE 2.61

    DB:2.61:Error Listenerstart - When Deployed War In Jboss As7 98



    Hi

    I am getting below error while deploying war on Jboss 6 EAP (as 7). Please help me =====================================================================================14:14:17,658 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.ppts-lan.war" is using a private module ("org.jboss.as.web:main") which may be changed or removed in futureversions without notice.14:14:24,923 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.ppts-lan.war:main" from Service Module Loader14:14:38,313 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart14:14:38,313 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/ppts-lan] startup failed due to previous errors14:14:38,345 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.deployment.default-host./ppts-lan: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./ppts-lan: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)[jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20]

    14:14:38,704 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ppts-lan.war" was rolled back with failure message {"JBAS014671: Failed services" = {"jboss.web.deployment.default-host./ppts-lan" = "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./ppts-lan: JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" = ["jboss.deployment.unit.\"ppts-lan.war\".jboss.security.jacc Missing[JBAS014861: one or more transitive dependencies]"]}

    ----------------------------------------------------------------------------------------------------------------------------------------------------This error is occuring when I add the below entry in web.xml file is uncommented

    listener listener-classorg.springframework.web.context.ContextLoaderListener/listener-class/listener

    if I comment the above entry in web.xml then it is deploying without issues but giving error while accessing app URL.

    below are jar list in WEB-INF/libfolder

    *ant-antlr-1.6.5

    *antlr-2.7.6rc1

    *aopalliance-1.0

    *aspectjrt

    *aspectjweaver

    bcprov-jdk15-145

    *c3p0-0.9.0

    *cglib-nodep-2.1_3

    cmu-codec-2.0

    *commons-beanutils-1.7.0

    commons-codec-1.4

    commons-collections-3.2.1

    commons-configuration-1.6

    commons-dbcp-1.2.2

    commons-digester-1.8

    commons-el-1.0

    commons-io-1.4

    commons-lang-2.4

    commons-logging

    commons-pool-1.3

    *dom4j-1.6.1

    *ehcache-core-2.2.0

    *el-impl-1.0

    *hibernate3

    *hibernate-annotations

    *hibernate-validator-4.1.0.Final

    iText-5.0.2

    jasper-el

    *jsch-0.1.48

    *jsf-facelets-1.1.15

    *jstl

    *jta

    junit-4.4

    *log4j

    *mail

    poi-3.7-20101029

    poi-ooxml-3.7-20101029

    poi-ooxml-schemas-3.7-20101029

    poi-scratchpad-3.7-20101029

    richfaces-api-3.3.3.Final

    richfaces-impl-3.3.3.Final

    richfaces-ui-3.3.3.Final

    slf4j-api-1.5.11

    slf4j-jdk14-1.5.11

    spring-aop-3.0.2.RELEASE

    spring-asm-3.0.2.RELEASE

    spring-aspect-3.0.2.RELEASE

    spring-beans-3.0.2.RELEASE

    spring-context-3.0.2.RELEASE

    spring-context-support-3.0.2.RELEASE

    spring-core-3.0.2.RELEASE

    spring-expression-3.0.2.RELEASE

    spring-jdbc-3.0.2.RELEASE

    spring-ldap-1.3.1.RELEASE-all

    spring-mock-2.0.1

    spring-orm-3.0.2.RELEASE

    spring-transaction-3.0.2.RELEASE

    spring-web-3.0.2.RELEASE

    standard-1.1.1

    standard-1.1.2

    validation-api-1.0.0.GA

    xalanj1compat

    xmlbeans-2.3.0

    Tried to remove * marked jar's and deploy but getting lot of other errors.

    DB:2.61:Error Listenerstart - When Deployed War In Jboss As7 98


    Hi,

    12:30:21,433 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart

    12:30:21,448 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/ppts-lan] startup failed due to previous errors

    12:30:21,480 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.deployment.default-host./ppts-lan: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./ppts-lan: JBAS018040: Failed to start context

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]

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

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

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

    From your above server.log snippet it seems that the actual cause (root cause) of the Deployment failure is bwing Supressed .... So try to add the following System Property (In $JBOSS_HOME/bin/standalone.conf) while starting your JBoss sothat JBoss will

    ./standalone.sh -Dorg.jboss.as.logging.per-deployment=false

    Above system property will help in revealing the actual cause of the deployment failure.

  • RELEVANCY SCORE 2.61

    DB:2.61:Migration Jboss7 Jndi Error c1



    JNDI "naming.NameNotFoundException error" when I tried to deploy my application Jboss5 on Jboss7.1:

    Whatever the namespace I use, I get always the error(I tried with Jboss7 naming space"java:module/NotificationManager!com.tt.airman.framework.server.manager.INotificationManager" and also Jboss5 "framework/NotificationManager/local" )

    Could sommeone help me pls?

    15:26:25,585 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-7) Context initialization failed: org.springframework.beans.factory.BeanCreationException:

    Error creating bean with name 'notificationManagerEJB': Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: NotificationManager!com.tt.air

    man.framework.server.manager.INotificationManager -- service jboss.naming.context.java.module.framework.2-framework-server-war."NotificationManager!com.tt.airman.framework.serv

    er.manager.INotificationManager"

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412) [spring-beans-3.0.2.RELEASE.jar

    :3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.0.2.RELEASE.jar:3.

    0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.2.RELEASE.jar:3.0.

    2.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) [spring-beans-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:546) [spring-beans-3.0.2.RELEASE.jar:3.0.2.

    RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:872) [spring-context-3.0.2.RELEASE.jar:3.0

    .2.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:423) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

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

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

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]

    Caused by: javax.naming.NameNotFoundException: NotificationManager!com.tt.airman.framework.server.manager.INotificationManager -- service jboss.naming.context.java.module.frame

    work.2-framework-server-war."NotificationManager!com.tt.airman.framework.server.manager.INotificationManager"

    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)

    at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123)

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214)

    at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_30]

    at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:154) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:87) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:95) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:122) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE]

    at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:109) [spring-context-3.0.2.RELEASE.jar:3.0.2.RELEASE

    ]

    at org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean.afterPropertiesSet(LocalStatelessSessionProxyFactoryBean.java:86) [spring-context-3.0.2.RELEASE.jar:

    3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) [spring-beans-3.0.2.RELEASE.

    jar:3.0.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) [spring-beans-3.0.2.RELEASE.jar

    :3.0.2.RELEASE]

    DB:2.61:Migration Jboss7 Jndi Error c1


    Your last log had a deployment timeout in it. I guess you added the "deployment-timeout" attribute to the deployment-scanner?

  • RELEVANCY SCORE 2.61

    DB:2.61:New Spring Integration ca



    I added some simple Spring integration on top of the EmbeddedJMS class I did. It automatically registers configured queues, topics, and connection factories within the Spring bean context so that they can be referenced and injected into other beans.

    I added documentation to the user manual for this as well.

    DB:2.61:New Spring Integration ca


    I added some simple Spring integration on top of the EmbeddedJMS class I did. It automatically registers configured queues, topics, and connection factories within the Spring bean context so that they can be referenced and injected into other beans.

    I added documentation to the user manual for this as well.

  • RELEVANCY SCORE 2.61

    DB:2.61:Eap 6.1.0 Re-Export Not Working With Meta-Inf Resources In The Case Of Multiple Jboss Modules 3f



    Hello,

    We are developing an application which leverages the JBoss module infrastructure to share common libraries (e.g. Groovy, Spring, Hibernate, Vaadin) between multiple web applications. To

    keep things simple we are currently splitting our dependencies between our code and third party dependencies (over time we expect to split them out in multiple modules) , e.g.

    com.acme (our shared application code)

    com.acme-thirdparty (Groovy, Spring, Hibernate, Guava, etc.)

    However I ran into a problem with Spring Security and what I believe is a META-INF visibility issue (/META-INF/spring.handlers to be specific) with re-exporting modules in EAP 6.1.0.

    Unfortunately Spring Security doesn't really have support yet for Java based configuration so I was forced to use their XML support.

    From my understanding of Spring XML configurations it needs to scan the classpath in order to find registered handlers for parsing it's configuration files.

    Aside: I found some hints here about spring configuration handling that others may found helpful:

    http://blog.idm.fr/2009/09/maven-assembly-plugin-and-spring-namespace-handlers.html

    I created a small demo WAR (simple JAX-RS + Spring example) which illustrates the problem.

    From what I gleaned from the JBoss documentation of JBoss AS 7 classloading behavior I knew I needed to make some changes in order for the WAR to see the META-INF directories inside of Spring's JARs.

    Using the "jboss-deployment-structure.xml" descriptor I was able to get it working when everthing was together in a single JBoss module but I ran into problems when I started

    to split off Spring from the rest of the dependencies.

    For example this works fine as a single JBoss module:

    /src/main/webapp/WEB-INF/jboss-deployment-structure.xml (notice that meta-inf="import" is working here)

    ?xml version="1.0" encoding="UTF-8"?

    jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"

    deployment

    dependencies

    module name="org.codehaus.jackson.jackson-jaxrs"/

    module name="org.springframework" services="import" meta-inf="import"/

    /dependencies

    /deployment

    /jboss-deployment-structure

    Here's my custom "org.springframework" JBoss module for reference (C:\tools\jboss-eap-6.1\modules\org\springframework\main):

    ?xml version="1.0" encoding="UTF-8"?

    module xmlns="urn:jboss:module:1.1" name="org.springframework"

    resources

    !-- Core --

    resource-root path="aopalliance-1.0.jar"/

    resource-root path="spring-aop-3.2.3.RELEASE.jar"/

    resource-root path="spring-beans-3.2.3.RELEASE.jar"/

    resource-root path="spring-context-3.2.3.RELEASE.jar"/

    resource-root path="spring-context-support-3.2.3.RELEASE.jar"/

    resource-root path="spring-core-3.2.3.RELEASE.jar"/

    resource-root path="spring-expression-3.2.3.RELEASE.jar"/

    resource-root path="spring-jdbc-3.2.3.RELEASE.jar"/

    resource-root path="spring-orm-3.2.3.RELEASE.jar"/

    resource-root path="spring-oxm-3.2.3.RELEASE.jar"/

    resource-root path="spring-tx-3.2.3.RELEASE.jar"/

    resource-root path="spring-web-3.2.3.RELEASE.jar"/

    resource-root path="spring-webmvc-3.2.3.RELEASE.jar"/

    !-- Spring LDAP --

    resource-root path="spring-ldap-core-1.3.1.RELEASE.jar"/

    resource-root path="spring-ldap-core-tiger-1.3.1.RELEASE.jar"/

    !-- Spring Security --

    resource-root path="spring-security-acl-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-aspects-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-core-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-config-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-crypto-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-openid-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-remoting-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-ldap-3.1.4.RELEASE.jar"/

    resource-root path="spring-security-web-3.1.4.RELEASE.jar"/

    !-- AMQP --

    resource-root path="spring-amqp-1.1.4.RELEASE.jar"/

    resource-root path="spring-rabbit-1.1.4.RELEASE.jar"/

    resource-root path="spring-retry-1.0.0.RELEASE.jar"/

    /resources

    dependencies

    module name="org.apache.commons.lang"/

    module name="javaee.api"/

    module name="org.dom4j"/

    module name="org.jboss.vfs"/

    module name="org.slf4j"/

    module name="org.slf4j.jcl-over-slf4j"/

    module name="sun.jdk"/

    /dependencies

    /module

    As I said this all works just fine. However the following example which attempts to re-export the Spring module does not work:

    /src/main/webapp/WEB-INF/jboss-deployment-structure.xml (notice that meta-inf="import" is NOT working here)

    ?xml version="1.0" encoding="UTF-8"?

    jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"

    deployment

    dependencies

    module name="org.codehaus.jackson.jackson-jaxrs"/

    module name="test" services="import" meta-inf="import"/

    /dependencies

    /deployment

    /jboss-deployment-structure

    C:\tools\jboss-eap-6.1\modules\test\main

    ?xml version="1.0" encoding="UTF-8"?

    module xmlns="urn:jboss:module:1.1" name="test"

    resources

    /resources

    dependencies

    module name="org.springframework" export="true"/

    /dependencies

    /module

    This results in a deployment failure:

    10:59:32,929 ERROR - U: - O: [org.springframework.web.context.ContextLoader] (ServerService Thread Pool -- 54) Context initialization failed: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/security]

    Offending resource: ServletContext resource [/WEB-INF/spring/security.xml]

    So it seems from experimentation that export doesn't include the META-INF information. However I was able to get the "test" JBoss module working by extracting /META-INF/spring.handlers and /META-INF/spring.schemas

    and including them inside the WAR artifact.

    $ unzip -l build/libs/demo.war

    ...

    109 06-10-2013 11:17 WEB-INF/classes/META-INF/spring.handlers

    1068 06-10-2013 11:17 WEB-INF/classes/META-INF/spring.schemas

    While this works it is less than ideal as I have to maintain Spring resources in multiple locations (outside of the Spring standard distribution as well). Is there an option

    to re-export META-INF information like I attempted to do or is there another way of accomplishing this? What is the best practice here?

    I hope all that made sense. Let me know if you have any questions. We are soon to be an EAP customer so any help would be greatly appreaciated.

    p.s.

    The sample project I have is using JBoss's RESTEasy JAW-RS implementation along with the Spring plugin support. It's pretty simple example which uses LDAP authentication and

    authorization via Spring Security.

    @Named

    @Path("/Hello")

    @RolesAllowed("ADMINS")

    public class HelloWorldResource {

    private static final Logger logger = LoggerFactory.getLogger(HelloWorldResource.class);

    @Inject

    private HelloService helloService;

    public HelloWorldResource() {

    logger.info("Creating HelloWorldResource");

    }

    @GET

    @Path("text")

    @Produces(MediaType.APPLICATION_FORM_URLENCODED)

    public Response sayTextHello(@QueryParam("msg") String msg) {

    final String resp = helloService.sayTextHello(msg);

    logger.info("sayTextHello({}): {}", msg, resp);

    return Response.ok(resp).build();

    }

    @POST

    @Path("javabean")

    @Produces({ MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML })

    @Consumes({ MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML })

    public Response sayJavaBeanHello(final HelloMessage msg) {

    final HelloResponse resp = helloService.sayJavaBeanHello(msg);

    logger.info("sayJavaBeanHello({}): {}", msg, resp);

    return Response.ok(resp).build();

    }

    }

    Here's my Spring configration for reference:

    @Configuration

    @ImportResource("/WEB-INF/spring/security.xml")

    public class MyRestConfig {

    // @bean method signature below has to be public for the following code to work

    // org.jboss.resteasy.plugins.spring.SpringBeanProcessor.getBeanClass() (line 399)

    // (Method method : getBeanClass(factoryClassName).getMethods())

    @Bean

    public HelloWorldResource helloWorldResource() {

    logger.info("Creating helloWorldResource bean");

    final HelloWorldResource helloWorldResource = new HelloWorldResource();

    return helloWorldResource;

    }

    }

    /WEB-INF/spring/security.xml

    ?xml version="1.0" encoding="UTF-8"?

    beans:beans xmlns="http://www.springframework.org/schema/security"

    xmlns:beans="http://www.springframework.org/schema/beans"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:schemaLocation="http://www.springframework.org/schema/beans

    http://www.springframework.org/schema/beans/spring-beans-3.1.xsd

    http://www.springframework.org/schema/security

    http://www.springframework.org/schema/security/spring-security-3.1.xsd"

    http auto-config='true' use-expressions='true'

    intercept-url pattern='/**' access='isFullyAuthenticated()' /

    http-basic /

    /http

    ldap-server url="ldap://127.0.0.1:10389/dc=acmecorp,dc=com" manager-dn="uid=admin,ou=system" manager-password="secret" /

    authentication-manager

    ldap-authentication-provider user-dn-pattern="uid={0},cn=users" group-search-base="cn=groups" role-prefix="none"

    /ldap-authentication-provider

    /authentication-manager

    global-method-security jsr250-annotations="enabled" /

    /beans:beans

    public class CpmsRestWebApplicationInitializer implements WebApplicationInitializer{

    static class MyCustomSpringContextLoader extends ContextLoader {

    private SpringContextLoaderSupport springContextLoaderSupport = new SpringContextLoaderSupport();

    public MyCustomSpringContextLoader() {

    super(createContext());

    }

    private static WebApplicationContext createContext() {

    final AnnotationConfigWebApplicationContext rootContext = new AnnotationConfigWebApplicationContext();

    rootContext.setParent(createSharedContext());

    rootContext.register(CpmsRestConfig.class);

    return rootContext;

    }

    private static ApplicationContext createSharedContext() {

    final AnnotationConfigApplicationContext sharedContext = new AnnotationConfigApplicationContext();

    sharedContext.setDisplayName("Shared Spring Application Context");

    sharedContext.register(CpmsSharedConfig.class);

    sharedContext.refresh();

    return sharedContext;

    }

    protected void customizeContext(ServletContext servletContext, ConfigurableWebApplicationContext configurableWebApplicationContext) {

    super.customizeContext(servletContext, configurableWebApplicationContext);

    springContextLoaderSupport.customizeContext(servletContext, configurableWebApplicationContext);

    }

    }

    static class RestSpringContextLoaderListener extends SpringContextLoaderListener {

    @Override

    protected ContextLoader createContextLoader() {

    logger.info("Creating ContextLoader");

    return new MyCustomSpringContextLoader();

    }

    }

    private static final Logger logger = LoggerFactory.getLogger(CpmsRestWebApplicationInitializer.class);

    @Override

    public void onStartup(final ServletContext servletContext) throws ServletException {

    logger.info("onStartup()");

    configure(servletContext);

    }

    private void configure(final ServletContext servletContext) {

    servletContext.setInitParameter("resteasy.servlet.mapping.prefix", "/rest");

    final FilterRegistration.Dynamic springSecurityFilterChain =

    servletContext.addFilter("springSecurityFilterChain", new DelegatingFilterProxy());

    springSecurityFilterChain.addMappingForUrlPatterns(null, false, "/*");

    servletContext.addListener(new ResteasyBootstrap());

    servletContext.addListener(new RestSpringContextLoaderListener());

    final ServletRegistration.Dynamic dispatcher = servletContext.addServlet("resteasy", new HttpServletDispatcher());

    dispatcher.setLoadOnStartup(1);

    dispatcher.addMapping("/rest/*");

    }

    }

  • RELEVANCY SCORE 2.60

    DB:2.60:Loading Spring Annotated Beans From Abstractspringaction In Esb Actionpipeline s3



    Hi,

    I have an issue loading Spring 3 Beans annotated with Stereotypes- @Component,@Repository,@Service.

    My current *applicationContext.xml* defined within the project has ComponentScanning enabled for a package using -

    {code:xml}

    context:annotation-config/

    context:component-scan base-package="classpath*:net.whatever.service"/

    {code}

    I'm using the JBoss ESB 4.11 Server. Here I have a ServicePipeline which takes in an Action with an ActionClass extending the AbstractSpringAction that loads the SpringContext. Here's how I'm doing this -

    {code:xml}

    service category="category" name="servicename"

    listeners

    jms-listener busidref="defined" name="listenername" /

    /listeners

    actions mep="OneWay"

    action name="actionname" class="net.whatever.custom.MySpringEnabledAction" process="processname"

    property name="springContextXml" value="applicationContext.xml"/

    action ... /

    /actions

    /service

    {code}

    Here's a piece of code of how I'm implementing the MySpringEnabledAction.java class -

    {code}

    public class MySpringEnabledAction extends AbstractSpringAction {

    public MySpringEnabledAction(ConfigTree _config){

    configTree = _config;

    }

    public processName ....

    .....

    }

    {code}

    The problem I'm facing is with this now -

    In the package *net.whatever.service* on which Spring does the ComponentScanning there is a class called MyServiceImpl.java which looks like this -

    {code}

    @Service(name="myservice_name")

    public class MyServiceImpl implements MyService{

    ....

    ....

    }

    {code}

    MyService is an interface and there is no ambiguity between beans. This is the only Concrete implementation which implements this interface.

    This annotation is not being seen or not being detected because this Bean is not being Pre-initialized by the Spring Container.. as a result I keep getting an error of org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [net.whatever.service.MyService]...

    This error pops-up because there is another Bean which is trying to use @Autowired annotation and injecting the MyService Bean into its implementation. This other bean looks like this -

    {code}

    public class Receiver {

    protected MyService myservice

    @Autowired

    public class setMyService(MyService myservice){

    this.myservice = myservice;

    }

    .....

    .....

    }

    {code}

    This bean is also loaded by Spring but the difference here is its not part of the ComponentScanning that Spring will use.. it has a bean definition as XML configuration within the applicationContext.xml.

    All the Spring configuration worked fine when I deployed it as a WAR and used the Servlet context to load the Spring Context.. but now with this ESB Action loading the SpringContext.. all the basic annotations are falling apart.

    So could somebody help me figure out what the issue with the SpringContainer not pre-initializing the MyService Bean is?

    Thanks.

    DB:2.60:Loading Spring Annotated Beans From Abstractspringaction In Esb Actionpipeline s3


    Hi,

    I have an issue loading Spring 3 Beans annotated with Stereotypes- @Component,@Repository,@Service.

    My current *applicationContext.xml* defined within the project has ComponentScanning enabled for a package using -

    {code:xml}

    context:annotation-config/

    context:component-scan base-package="classpath*:net.whatever.service"/

    {code}

    I'm using the JBoss ESB 4.11 Server. Here I have a ServicePipeline which takes in an Action with an ActionClass extending the AbstractSpringAction that loads the SpringContext. Here's how I'm doing this -

    {code:xml}

    service category="category" name="servicename"

    listeners

    jms-listener busidref="defined" name="listenername" /

    /listeners

    actions mep="OneWay"

    action name="actionname" class="net.whatever.custom.MySpringEnabledAction" process="processname"

    property name="springContextXml" value="applicationContext.xml"/

    action ... /

    /actions

    /service

    {code}

    Here's a piece of code of how I'm implementing the MySpringEnabledAction.java class -

    {code}

    public class MySpringEnabledAction extends AbstractSpringAction {

    public MySpringEnabledAction(ConfigTree _config){

    configTree = _config;

    }

    public processName ....

    .....

    }

    {code}

    The problem I'm facing is with this now -

    In the package *net.whatever.service* on which Spring does the ComponentScanning there is a class called MyServiceImpl.java which looks like this -

    {code}

    @Service(name="myservice_name")

    public class MyServiceImpl implements MyService{

    ....

    ....

    }

    {code}

    MyService is an interface and there is no ambiguity between beans. This is the only Concrete implementation which implements this interface.

    This annotation is not being seen or not being detected because this Bean is not being Pre-initialized by the Spring Container.. as a result I keep getting an error of org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [net.whatever.service.MyService]...

    This error pops-up because there is another Bean which is trying to use @Autowired annotation and injecting the MyService Bean into its implementation. This other bean looks like this -

    {code}

    public class Receiver {

    protected MyService myservice

    @Autowired

    public class setMyService(MyService myservice){

    this.myservice = myservice;

    }

    .....

    .....

    }

    {code}

    This bean is also loaded by Spring but the difference here is its not part of the ComponentScanning that Spring will use.. it has a bean definition as XML configuration within the applicationContext.xml.

    All the Spring configuration worked fine when I deployed it as a WAR and used the Servlet context to load the Spring Context.. but now with this ESB Action loading the SpringContext.. all the basic annotations are falling apart.

    So could somebody help me figure out what the issue with the SpringContainer not pre-initializing the MyService Bean is?

    Thanks.

  • RELEVANCY SCORE 2.60

    DB:2.60:Accessing Ejb3 With Annotations From Clients Running Jdk1.4 kp


    I'm trying to run a WSL10 server that should deploy SlSBs annotated with EJB3 annotations (@Remote, @Stateless and so on).
    For a client to access the EJB they need to have the client interfaces (which will contain annotations).
    My clients are running WLS8 on JDK1.4 so the client.jar built cannot be used since it cannot have target=1.4 when compiling due to the annotations.
    I use Retroweaver to create a JDK1.4 compliant client.jar and let the client use that.
    The client applications deployed on WLS8 are using Spring to perform lookup on the remote EJB from WLS10 server.
    Looking up the EJB is working, but when I try to call methods on the remote object, I get an exception:
    Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
    at $Proxy0.getResult(Unknown Source)

    When trying to to a lookup without Spring, i.e using the InitialContext and so on, I get a reference to the EJBHome, but since it doesn't contain any create() methods, how should I get a reference to my actual EJB?
    final InitialContext ctx = new InitialContext(p);
    final Object o = ctx.lookup("base-ejbbase-ejb_jarTestImpl_Home");
    final EJBHome narrow = (EJBHome) javax.rmi.PortableRemoteObject
    .narrow(o, EJBHome.class);

    Is it even possible to use EJB3 deployed EJBs from a JDK1.4 container?

    DB:2.60:Accessing Ejb3 With Annotations From Clients Running Jdk1.4 kp

    This NPE looks like a known issue. You can contact WLS support for a patch.

  • RELEVANCY SCORE 2.60

    DB:2.60:Ws-Security Without Spring, Without Ws-Policy And Without The Cxf Annotations? f9



    Is it possible to configure ws-security with JBossWS CXF Stack without using Spring, without using ws-policy, and without using the cxf annotations in the service classes?

    I need to configure ws-security with wsrp, and wsrp is _not_ compatible with ws-policy (its against the spec, it may be supported in the next spec version but its not in the current one). So I can't just use ws-policy with the configuration properties to enable ws-security.

    It looks like you still have the pre and post soap handlers for the CXF stack like you did with the native stack (https://docs.jboss.org/author/display/JBWS/Predefined+client+and+endpoint+configurations). But this is only for adding in soaphandlers, and cxf is configured using interceptors, which means I can't use this to add the security interceptors. Is there anyway to add in intereceptors in a similar manner?

    IIts possible to use the cxf annotations on the java service classes to add in the security interceptors, but this means making our service classes dependent on cxf or having to have separate classes just for cxf. This really isn't an acceptable solution either, we need to support more than one application server.

    Since the recommended way to configure CXF is to use Spring configuration files, I am confused why Spring is not the recommended manner to configure cxf in JBossWS (and Spring isn't include in AS7 either). Or is Spring the recommended manner with the cxf stack in JBossWS and I am reading the docs wrong? I would rather not have to add a spring dependency, but it looks like this might be the only real solution :/

    Am I missing anything obvious on how to do this in a manner that is not dependent on spring, ws-policy or custom cxf only classes with the special cxf annotations?

    DB:2.60:Ws-Security Without Spring, Without Ws-Policy And Without The Cxf Annotations? f9


    Matt Wringe wrote:

    I know (and mentioned) those configuration options in my original post As mentioned:

    1) we can't use ws-policy since its against the wsrp spec

    2) adding annotations to add in interceptors means that our purely jax java service classes now have to become dependent on cxf (which doesn't make a lot of sense since have to support non-cxf based web services, and we also want an admin to be able to enable/disable the interceptors themselves).

    Quite frankly, I see and understand the need for avoiding implementation specific api in endpoints (you might want to deploy the same archive on another vendor container), but as hinted before that's probably simply not doable (especially without WS-Policy support) with WS-Security. The reason basically being that there's no JCP spec covering ws-security configuration, so you'll always need to use an implementation specific configuration approach.

    If the real need is actually with the admin wanting to enable/disable the cxf interceptor without touching the code, you can go the spring descriptor way, after having added spring libraries to the app server.

    3) we don't want to have to bring in spring just to configure the web service. And this doesn't appear to the preferred method of configuring jbossws (but it is the preferred way to configure cxf).

    You don't want to bring in spring because it's just for configuration *or* you're simply somehow confused by the fact jbossas/jbossws does not ship with / install spring by default? If it's a matter of willing to avoid spring for ws configuration only, I see what you mean (as a matter of fact jbossws has moved in this direction, hence is not forcing the spring approach and encouraging the ws-policy based approach), but when you have many other contraints like "wsrp does not support policies", "I don't want to use cxf api", ... you need to come to a compromise and use what is left ;-)

    If it's a matter of you being confused on "what the preferred method is", keep in mind that JBossWS suggest using the policy approach, but allows different methods if you can't go that way. Apache CXF in general simply has multiple configuration mechanisms and I can say that there's not an actual preference for the spring one as of today, they're really all at the same level.

    The problem is how to configure the server. Using JBossWS Native stack I could just use the pre and post handlers to add in proper soap handlers for ws-security, this was simple and straight forward and configurable from an admin perspective. The ws-security setup could be handled outside of the service configuration (add in the options in the web.xml file to specify the endpoint config name and config file). It would be perfect if we could add in interceptors also in this manner, but this option doesn't seem to exist (which is strange since in cxf interceptors are the preferred method).

    The client / endpoint pre-defined configurations can be used to add JAXWS handlers. WS-Security was implemented using handlers in native stack. However it's not implemented using jaxws handlers on cxf and we can't (and do not want to) change that.

    Any mechanism for allowing configuring a generic interceptor through descriptor would basically imply re-inventing the spring configuration approach (a jaxws handler definition is covered by jsr224/jsr109 specs instead).. so again, either the user go the spring way if he really wants to have fine grain control on the interceptor beans or he stay with the suggested configuration mechanism (policy engine + properties through @EndpointConfig) *or* direct cxf api/annotation usage.

    Its strange that CXF is the preferred web service stack in JBossAS, and the preferred way to configure CXF is using Spring configuration files, but JBossAS doesn't ship or include Spring. So we can't properly configure web services the way they were meant to be configured.

    Again, 1) it's not *the* way they're meant to be configured, just *one* of the possible ways 2) you *can* still configure the ws endpoints that way if you want, simply install Spring first (either using the jbossws build or manually copying the spring jars into modules/org/springframework/spring/main and creating a valid module.xml descriptor for the new module).

  • RELEVANCY SCORE 2.60

    DB:2.60:Beehive Controls s9


    I have two questions (this after searching the net and relevant websites extensively)

    1. Can beehive controls be created without annotations?Basically using an externalized configuration file (a la spring configuration)?

    2. Does any one have a view on using beehive controls (for wrapping pojo's , db access etc..) vs Spring in a middle tier?
    any recommendation on when to choose beehive over Spring will be greatly appreciated.

    Thanks
    CS

    DB:2.60:Beehive Controls s9

    No problem.

    Heres what we are planning to use Spring for. Comments on the validity of this approach welcomed.

    We are implementing a set of custom controls in WLI to interact with remote IP based nodes.

    We want to use a JMX management approach for configuration data and runtime instrumentation (counters etc).

    Our thinking is to replace introduce Spring into the control via the factory replacement technique and then to use the Spring JMX capability to JMX enable the control.

    Does this make sense ?

  • RELEVANCY SCORE 2.60

    DB:2.60:Spring p7


    I want to use few features of spring like @Autowire and TransactionManager. My application is a console application. Can I use Spring without using webappwebinf folder?

    DB:2.60:Spring p7

    Thanks problem solved.

    package uk.co.pookey.spring;

    public class SayHello {

    private String name;

    public void setName(String name) {
    this.name = name;
    }

    public String getName() {
    return name;
    }

    public void greet() {
    System.out.println("Hello " + getName());
    }

    }Edited by: csckid on Apr 6, 2011 8:20 PM

    Edited by: csckid on Apr 7, 2011 2:41 AM

  • RELEVANCY SCORE 2.59

    DB:2.59:@Spring Injection In Pojos k8



    I did read the article on sys-conf and it mentioned that I can inject spring beans in POJOs with @Spring annotations and jboss AOP.Is there a concrete example of doing this ? I presume I would have to play with ejb3-interceptors-aop.xml ? but isn't this only for aop interception of ejb3 ?I want to intercept POJOs ?thanks

    DB:2.59:@Spring Injection In Pojos k8


    They are in the SVN jbossas trunk.http://anonsvn.jboss.org/repos/jbossas/trunk/spring-int/

  • RELEVANCY SCORE 2.59

    DB:2.59:@Rolesallowed, @Denyall Usage In Web Tier? p7



    I'm looking at a table in the JEE 6 specification section EE.6.25 that seems to indicate that web containers must support the following annotations: @PermitAll, @DenyAll, @RolesAllowed, @DeclareRoles and @RunAs.

    EE.6.25 Common Annotations for the Java Platform 1.1 Requirements

    The Common Annotations specification defines Java language annotations that are

    used by several other specifications, including this specification. The specifications

    that use these annotations fully define the requirements for these annotations. The

    applet container need not support any of these annotations. All other containers

    must provide definitions for all of these annotations, and must support the semantics

    of these annotations as described in the corresponding specifications and

    summarized in the following table.

    Table EE.6-5 Common Annotations Support by Container

    AnnotationApp ClientWebEJBResourceYYYResourcesYYYPostConstructYYYPreDestroyYYYGeneratedNNNRunAsNYYDeclareRolesNYYRolesAllowedNYYPermitAllNYYDenyAllNYY

    What kinds of objects can these @RolesAllowed and @DenyAll be used on in the web tier? Can these annotations be used with managed beans? If not, why not?

    DB:2.59:@Rolesallowed, @Denyall Usage In Web Tier? p7


    I guess because you can use EJBs as managed beans if you need this functionality. Have a look at EJB 3.1 OR CDI MANAGED BEAN AS JSF BACKING BEAN and the references as well.

  • RELEVANCY SCORE 2.59

    DB:2.59:Cdi Proxy Problem zd



    Recently I migrated some EJB Stateful session beans to CDI beans with dependent scope.

    I was surprised that I get for some beans a proxy and for some not.

    The problem was that I leave the @Prepassivate and @PostActivate annotations. If I comment this out then I get the real instances instead of the proxies.

    Is that a bug or a feature ??

    DB:2.59:Cdi Proxy Problem zd


    Ales Justin schrieb:

    Why do you think it's a bug?

    Beacause, @PrePassivate and @PostActivate are annaotations of the EJB stack. I can't understand why I get a proxy if I use this annotations for @Dependent Scope. ( I know it makes no sense to use this annotations in CDI or I'm worng ?? ).

  • RELEVANCY SCORE 2.59

    DB:2.59:Ejb3 Metadata Combining Annotations &Amp; Xml s1


    Hi ,
    1.
    does the ejb3 spec allow me to combine metadata on a bean ?
    i.e : i have some bussines service that is injected with a dao (which holds an injected entitymanager) and several other injected bussines services ,
    for some interfaces i have more then one impl. and so far i've used @ejb(mappedName="") now i don't want to hold that sort of data in the code , i'd rather map that from outside by a XML file (spring like) so i won't have to recompile on change but i may have other anottations in the core service (the one from the begining) that i'm fine with keeping anottated , is that possible ?

    2.
    will abstract ejb beans be supported in the future ?

    jbos 4.2.latest
    thanks

    Edited by: inquiringMind on May 11, 2008 4:41 AM

    DB:2.59:Ejb3 Metadata Combining Annotations &Amp; Xml s1

    Hi ,
    1.
    does the ejb3 spec allow me to combine metadata on a bean ?
    i.e : i have some bussines service that is injected with a dao (which holds an injected entitymanager) and several other injected bussines services ,
    for some interfaces i have more then one impl. and so far i've used @ejb(mappedName="") now i don't want to hold that sort of data in the code , i'd rather map that from outside by a XML file (spring like) so i won't have to recompile on change but i may have other anottations in the core service (the one from the begining) that i'm fine with keeping anottated , is that possible ?

    2.
    will abstract ejb beans be supported in the future ?

    jbos 4.2.latest
    thanks

    Edited by: inquiringMind on May 11, 2008 4:41 AM

  • RELEVANCY SCORE 2.58

    DB:2.58:Design Framework To Decouple Business Rules From Jsf/Spring Beans x1


    We use JSF beans in the Presentation layer and Spring beans in the Service layer.
    The JSF Backing beans are designated as XXXBean.java whereas Spring beans are designated as XXXManagerImpl.java and are suppose to implement business rules and then call Spring's ORM Hibernate Template to do the persistence to database.

    The problem is JSF/Spring beans are suppose to implement 20-30 business rules. This will eventually in implementing 20-30 methods in JSF/Spring beans

    So we are thinking to decouple the business rules from manager methods into a separate Interface with Concrete class implementing the Rule

    For example each of the XXXManagerImpl.java will have dependency injection of its co-oresponding XXXRuleManager with each of the rules specified as methods

    Here is the code snippet in manager method
    public Class XXXManagerImpl implements XXXManager
    {
    private XXXRuleManager XXXruleManager;
    //getters/setter methods for XXXRuleManager
    XXXruleManager.applyCreateXXXRules();
    XXXruleManager.applyUpdateXXXRules();
    XXXruleManager.applyDeleteXXXRules();
    XXXruleManager.applyValidateXXXRules();

    //Persistence
    hibernateTemplate.save(object);
    }

    We hope applyCreateXXXRules() will have set of rules and Iterator will iterate thru each of these rules by calling applyRule() methods to create an object

    The goal is to make this draft into design which is extensible when we add/delete new rules. Also when we bring new developers to the team, they should be able to implement the rule without stepping on each other code

    Any pointers/suggestions to make this draft into design will be greatly appreciated

    DB:2.58:Design Framework To Decouple Business Rules From Jsf/Spring Beans x1

    This is the nth time that you ask the same Patterns/OO Design question in a JSF forum. Instead of reposting/rephrasing it everytime you could also just kick the originating topic up, if necessary with some additional information. But better post it in the related forum: [Patterns OO Design|http://forums.sun.com/forum.jspa?forumID=425].

  • RELEVANCY SCORE 2.58

    DB:2.58:4.2.3 Migration To Last Good Build ds



    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

    DB:2.58:4.2.3 Migration To Last Good Build ds


    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.

  • RELEVANCY SCORE 2.58

    DB:2.58:Ejb 2.0 And Ejb3.0 In The Same Ear. Is That Possible ? zf


    Hi,

    I am migrating my application to Weblogic 10.
    I have many EJB2.1 beans working, and i don`t like to rewrite them on EJB3.0.
    I just want start my application under weblogic 10.3, and write all new beans using EJB3.0, but keep old EJB2.0 beans without changes.

    And it seems to me it is not possible.

    My configuration is:
    1. EJB2.0 beans with XML deployement descriptor
    2. Severla EJB3.0 described with EJB3.0 annotations

    All these EJB`s are packed in the same EAR and deployed.
    JNDI doesn`t see EJB3.0 beans !
    What is wrong ?

    DB:2.58:Ejb 2.0 And Ejb3.0 In The Same Ear. Is That Possible ? zf

    Hi,
    All EJB 3.0 Beans you can place them as seperate project and EJB 2.0 as different EJB Project.
    Then in EAR build and deployment it will not give any problems...

  • RELEVANCY SCORE 2.58

    DB:2.58:Some Problem With Myit 9f



    Hello

    We have installed 2.0.01: Service Pack 1 has these problems:

    The submitted request doesn't display on the home page

    startup of tomcat we found the following error: (see attached log file) Tomcat's log

    10:56:39.212 [localhost-startStop-1] INFO c.b.b.m.c.ConfigurationManager - Initializing Configurations

    10:56:39.310 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000203 for custom query id 000000000000304

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000206 for custom query id 000000000000305

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000339 for custom query id 000000000000314

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000346 for custom query id 000000000000321

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000368 for custom query id 000000000000325

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000457 for custom query id 000000000000334

    10:56:39.311 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000366 for custom query id 000000000000336

    10:56:39.312 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000411 for custom query id 000000000000342

    10:56:39.312 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000452 for custom query id 000000000000343

    10:56:39.312 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000613 for custom query id 000000000000601

    10:56:39.312 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000910 for custom query id 000000000000602

    10:56:39.312 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000927 for custom query id 000000000000605

    10:56:39.313 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000965 for custom query id 000000000000702

    10:56:39.313 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000945 for custom query id 000000000000809

    10:56:39.313 [localhost-startStop-1] ERROR c.b.b.m.c.ApplicationConfigurator - Invaid default query id 000000000000968 for custom query id 000000000001103

    10:56:39.341 [localhost-startStop-1] INFO c.b.b.m.c.ConfigurationManager - Finish Initializing Configurations

    in the CMDB more pluggable provider does not seem to be working:

    12:14:22.543 [localhost-startStop-1] INFO c.b.b.m.p.PluggableProviderManagerImpl - 'RKM pluggable provider' subscribed services for tenant 000000000000001: {[KnowledgeSearchService]}

    12:14:22.558 [localhost-startStop-1] ERROR c.b.b.m.p.PluggableProviderManagerImpl - Unable to load pluggable provider CMDB pluggable provider

    com.bmc.bsm.mobile.errorhandling.MobilityServerException: There was a problem decrypting the data. (Given final block not properly padded)

    at com.bmc.bsm.mobile.service.EncryptionService.decryptPassword(EncryptionService.java:105) ~[mobility-server-2.0.00.000-BUILD-SNAPSHOT.jar:na]

    at com.bmc.bsm.mobile.service.EncryptionService.decryptARPassword(EncryptionService.java:89) ~[mobility-server-2.0.00.000-BUILD-SNAPSHOT.jar:na]

    at com.bmc.bsm.myit.providers.cmdb.CmdbProviderImpl.init(CmdbProviderImpl.java:39) ~[na:na]

    at com.bmc.bsm.myit.providers.cmdb.CmdbPluggableProviderFactory.create(CmdbPluggableProviderFactory.java:47) ~[na:na]

    at com.bmc.bsm.myit.providers.cmdb.CmdbPluggableProviderFactory.create(CmdbPluggableProviderFactory.java:25) ~[na:na]

    at com.bmc.bsm.myit.providers.PluggableProviderManagerImpl.initialize(PluggableProviderManagerImpl.java:294) ~[myit-server-2.0.00.000-BUILD-SNAPSHOT.jar:na]

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_51]

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.7.0_51]

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.7.0_51]

    at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.7.0_51]

    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:344) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:295) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:130) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:396) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1475) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:323) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:629) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:626) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:389) [spring-web-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:294) [spring-web-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112) [spring-web-3.2.3.RELEASE.jar:3.2.3.RELEASE]

    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) [catalina.jar:7.0.34]

    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) [catalina.jar:7.0.34]

    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:7.0.34]

    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) [catalina.jar:7.0.34]

    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) [catalina.jar:7.0.34]

    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) [catalina.jar:7.0.34]

    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657) [catalina.jar:7.0.34]

    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637) [catalina.jar:7.0.34]

    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.7.0_51]

    at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.7.0_51]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source..

    same solution?

    regards

    DB:2.58:Some Problem With Myit 9f


    Thank you, i'll wait for the doc updates

  • RELEVANCY SCORE 2.58

    DB:2.58:Problem Generating Code From Spring-Beans-2.0.Xsd Schema m7


    Hi guys,
    sorry for cross-posting, but I didn't receive any answer on http://forums.java.net/jive/thread.jspa?threadID=31568. Maybe you could help. Here is the original post:

    I'd like to generate sources with the xjc compiler for the above mentioned schema. I used the following call:

    xjc.sh -verbose -d src/java/ -nv src/spring-beans-2.0.xsd

    And the following exceptions arose:
    ERROR] Property "Ref" is already defined. Use jaxb:property to resolve this conflict.
    line 552 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 581 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Value" is already defined. Use jaxb:property to resolve this conflict.
    line 554 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 588 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Ref" is already defined. Use jaxb:property to resolve this conflict.
    line 921 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 939 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Value" is already defined. Use jaxb:property to resolve this conflict.
    line 923 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 946 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Key" is already defined. Use jaxb:property to resolve this conflict.
    line 1009 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 1012 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd It seems that the compiler doesn't like the following construct:

    xsd:element name="constructor-arg"
    [...]
    xsd:complexType
    xsd:sequence
    xsd:element ref="description" minOccurs="0"/
    xsd:choice minOccurs="0" maxOccurs="1"
    [...]
    xsd:element ref="ref"/
    [...]
    /xsd:choice
    /xsd:sequence
    [...]
    xsd:attribute name="ref" type="xsd:string"[...]
    /xsd:attributeI'm used xjc version 2.1.5-b01-fcs. Any ideas, workarounds, bugfixes?

    Bye,
    Jan

    PS: The schema may be found here: http://www.springframework.org/schema/beans/spring-beans-2.0.xsd

    DB:2.58:Problem Generating Code From Spring-Beans-2.0.Xsd Schema m7

    Hi guys,
    sorry for cross-posting, but I didn't receive any answer on http://forums.java.net/jive/thread.jspa?threadID=31568. Maybe you could help. Here is the original post:

    I'd like to generate sources with the xjc compiler for the above mentioned schema. I used the following call:

    xjc.sh -verbose -d src/java/ -nv src/spring-beans-2.0.xsd

    And the following exceptions arose:
    ERROR] Property "Ref" is already defined. Use jaxb:property to resolve this conflict.
    line 552 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 581 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Value" is already defined. Use jaxb:property to resolve this conflict.
    line 554 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 588 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Ref" is already defined. Use jaxb:property to resolve this conflict.
    line 921 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 939 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Value" is already defined. Use jaxb:property to resolve this conflict.
    line 923 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 946 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] Property "Key" is already defined. Use jaxb:property to resolve this conflict.
    line 1009 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd

    [ERROR] The following location is relevant to the above error
    line 1012 of file:/home/jtietjen/temp/beandoc-jaxb/src/spring-beans-2.0.xsd It seems that the compiler doesn't like the following construct:

    xsd:element name="constructor-arg"
    [...]
    xsd:complexType
    xsd:sequence
    xsd:element ref="description" minOccurs="0"/
    xsd:choice minOccurs="0" maxOccurs="1"
    [...]
    xsd:element ref="ref"/
    [...]
    /xsd:choice
    /xsd:sequence
    [...]
    xsd:attribute name="ref" type="xsd:string"[...]
    /xsd:attributeI'm used xjc version 2.1.5-b01-fcs. Any ideas, workarounds, bugfixes?

    Bye,
    Jan

    PS: The schema may be found here: http://www.springframework.org/schema/beans/spring-beans-2.0.xsd

  • RELEVANCY SCORE 2.58

    DB:2.58:Unable To Locate Namespacehandler For Namespace [Http://Jbos fz



    Geeks, Save the foot soldier. Trying to make Seam+Spring+Hibernate app, getting the below error, name space lookup problem. Pls. help.12:01:15,765 INFO [STDOUT] 12:01:15,750 ERROR [[/prevea]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListenerorg.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate NamespaceHandler for namespace [http://jboss.com/products/seam/spring-seam]Offending resource: ServletContext resource [/WEB-INF/applicationContext.xml] at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:59) at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:64) at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:55) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1144) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1137) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:143) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions blah blah blah.....My applicationContext.xml is?xml version="1.0" encoding="UTF-8"?beans xmlns="http://www.springframework.org/schema/beans" xmlns:aop="http://www.springframework.org/schema/aop" xmlns:util="http://www.springframework.org/schema/util" xmlns:seam="http://jboss.com/products/seam/spring-seam" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tx="http://www.springframework.org/schema/tx" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-2.0.xsd http://jboss.com/products/seam/spring-seam http://jboss.com/products/seam/spring-seam-1.2.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd" default-lazy-init="true" !-- Spring Data Access Exception Translator Defintion -- seam:configure-scopes / seam:instance id="hbmSessionFactory" name="hibernateSessionFactory" proxy="true"/ seam:instance id="pDS" name="preveaDatasource" proxy="true"/

    DB:2.58:Unable To Locate Namespacehandler For Namespace [Http://Jbos fz


    Well, they're located in CVS at "/src/ioc/META-INF" I don't know if they are getting packaged into a source package.

  • RELEVANCY SCORE 2.58

    DB:2.58:Classnotfoundexception: Org.Jboss.Virtual.Virtualfilevisitor While Deploying In Jboss 8f



    I had developed an application using Spring 3/Hibernate 4 in JBoss Developer Studio 6.

    While deploying the application, getting the below exception. As a resolution i had added jboss-vfs-3.1.0.Final.jar file to the build path, but still its throwing the same exception.

    Error:

    00:51:54,738 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-100:52:01,456 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-200:52:03,160 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting00:52:19,894 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found conciergeFlows.war in deployment directory. To trigger deployment create a file called conciergeFlows.war.dodeploy00:52:20,191 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)00:52:20,379 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-100:52:20,816 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-100:52:21,176 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-100:52:21,613 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers00:52:21,707 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.00:52:21,769 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension00:52:22,832 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)00:52:23,098 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.14.Final-redhat-200:52:23,410 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.13.Final-redhat-1)00:52:23,754 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service00:52:24,332 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]00:52:27,832 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.6.GA-redhat-200:52:28,191 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:808000:52:29,676 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:999900:52:29,676 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\Program Files\JBossStudio\runtimes\jboss-eap\standalone\deployments00:52:30,192 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "conciergeFlows.war"00:52:30,629 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:444700:52:32,926 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]00:52:44,567 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class at /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/icu4j-2.6.1.jar: java.lang.IllegalStateException: Unknown tag! pos=40 poolCount = 47 at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:78) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21] at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]

    00:52:45,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb-api.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/jaxb-impl-2.1.3.jar does not point to a valid jar for a Class-Path reference.00:52:45,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry activation.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/jaxb-impl-2.1.3.jar does not point to a valid jar for a Class-Path reference.00:52:45,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/jaxb-impl-2.1.3.jar does not point to a valid jar for a Class-Path reference.00:52:45,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/jaxb-impl-2.1.3.jar does not point to a valid jar for a Class-Path reference.00:52:45,879 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry activation.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/mail-1.4.jar does not point to a valid jar for a Class-Path reference.00:52:45,879 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry xercesImpl.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/xalan-2.6.0.jar does not point to a valid jar for a Class-Path reference.00:52:45,879 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry xml-apis.jar in /C:/Program Files/JBossStudio/runtimes/jboss-eap/standalone/deployments/conciergeFlows.war/WEB-INF/lib/xalan-2.6.0.jar does not point to a valid jar for a Class-Path reference.00:52:51,348 ERROR [org.jboss.remoting.remote.connection] (Remoting "wvdi1itcs11:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine00:52:51,411 ERROR [org.jboss.remoting.remote.connection] (Remoting "wvdi1itcs11:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine00:52:51,411 ERROR [org.jboss.remoting.remote.connection] (Remoting "wvdi1itcs11:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine00:52:52,301 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component org.springframework.web.context.ContextLoaderServlet due to exception: java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderServlet from [Module "deployment.conciergeFlows.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21] at java.lang.Class.forName(Unknown Source) [rt.jar:1.7.0_21] at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21] at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]

    00:52:53,458 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.conciergeFlows.war:main" from Service Module Loader00:52:54,380 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/conciergeFlows]] (MSC service thread 1-1) Initializing Spring root WebApplicationContext00:52:54,380 INFO [org.springframework.web.context.ContextLoader] (MSC service thread 1-1) Root WebApplicationContext: initialization started00:52:54,427 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (MSC service thread 1-1) Refreshing Root WebApplicationContext: startup date [Thu May 23 00:52:54 EST 2013]; root of context hierarchy00:52:54,552 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (MSC service thread 1-1) Loading XML bean definitions from ServletContext resource [/WEB-INF/dispatcher-servlet.xml]00:52:55,505 INFO [org.springframework.context.annotation.ClassPathBeanDefinitionScanner] (MSC service thread 1-1) JSR-250 'javax.annotation.ManagedBean' found and supported for component scanning00:52:55,520 INFO [org.springframework.context.annotation.ClassPathBeanDefinitionScanner] (MSC service thread 1-1) JSR-330 'javax.inject.Named' annotation found and supported for component scanning00:52:55,536 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-1) Context initialization failed: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/dispatcher-servlet.xml]; nested exception is java.lang.NoClassDefFoundError: org/jboss/virtual/VirtualFileVisitor at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:465) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:395) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:272) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:196) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.17.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.17.Final-redhat-1.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:89) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21] at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]Caused by: java.lang.NoClassDefFoundError: org/jboss/virtual/VirtualFileVisitor at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:348) [spring-core-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:269) [spring-core-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.getResources(AbstractApplicationContext.java:1196) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:204) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:204) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1335) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1325) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:136) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] ... 21 moreCaused by: java.lang.ClassNotFoundException: org.jboss.virtual.VirtualFileVisitor from [Module "deployment.conciergeFlows.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 34 more

    00:52:55,536 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/conciergeFlows]] (MSC service thread 1-1) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/dispatcher-servlet.xml]; nested exception is java.lang.NoClassDefFoundError: org/jboss/virtual/VirtualFileVisitor at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:465) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:395) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:272) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:196) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.17.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.17.Final-redhat-1.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:89) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21] at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]Caused by: java.lang.NoClassDefFoundError: org/jboss/virtual/VirtualFileVisitor at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:348) [spring-core-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:269) [spring-core-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.support.AbstractApplicationContext.getResources(AbstractApplicationContext.java:1196) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:204) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:204) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84) [spring-context-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1335) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1325) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:136) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) [spring-beans-3.0.1.RELEASE.jar:3.0.1.RELEASE] ... 21 moreCaused by: java.lang.ClassNotFoundException: org.jboss.virtual.VirtualFileVisitor from [Module "deployment.conciergeFlows.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 34 more

    00:52:56,692 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Error listenerStart00:52:56,692 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/conciergeFlows] startup failed due to previous errors00:52:57,458 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/conciergeFlows]] (MSC service thread 1-1) Closing Spring root WebApplicationContext00:52:57,473 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.deployment.default-host./conciergeFlows: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./conciergeFlows: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:94) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_21] at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_21]

    00:52:57,692 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "conciergeFlows.war"00:52:57,692 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status reportJBAS014777: Services which failed to start: service jboss.web.deployment.default-host./conciergeFlows: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./conciergeFlows: JBAS018040: Failed to start context

    00:52:57,864 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management00:52:57,864 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:999000:52:57,864 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started (with errors) in 71002ms - Started 380 of 465 services (2 services failed or missing dependencies, 82 services are passive or on-demand)

    Library files in my build path:

    WebContent/WEB-INF/lib/activation-1.0.2.jarWebContent/WEB-INF/lib/antlr-2.7.6.jarWebContent/WEB-INF/lib/aopalliance-1.0.jarWebContent/WEB-INF/lib/asm-1.5.3.jarWebContent/WEB-INF/lib/asm-attrs-1.5.3.jarWebContent/WEB-INF/lib/cglib-2.1_3.jarWebContent/WEB-INF/lib/commons-beanutils-1.7.0.jarWebContent/WEB-INF/lib/commons-collections-2.1.1.jarWebContent/WEB-INF/lib/commons-digester-1.8.jarWebContent/WEB-INF/lib/commons-email-1.0.jarWebContent/WEB-INF/lib/commons-fileupload-1.1.1.jarWebContent/WEB-INF/lib/commons-io-1.1.jarWebContent/WEB-INF/lib/commons-lang-2.5.jarWebContent/WEB-INF/lib/commons-logging-1.1.1.jarWebContent/WEB-INF/lib/dom4j-1.6.1.jarWebContent/WEB-INF/lib/dumbster-1.6.jarWebContent/WEB-INF/lib/ehcache-1.2.3.jarWebContent/WEB-INF/lib/hibernate-3.2.6.ga.jarWebContent/WEB-INF/lib/hibernate-annotations-3.3.1.GA.jarWebContent/WEB-INF/lib/hibernate-commons-annotations-3.0.0.ga.jarWebContent/WEB-INF/lib/hibernate-entitymanager-3.3.2.GA.jarWebContent/WEB-INF/lib/hibernate-search-3.0.0.GA.jarWebContent/WEB-INF/lib/hibernate-validator-4.0.2.GA.jarWebContent/WEB-INF/lib/icu4j-2.6.1.jarWebContent/WEB-INF/lib/javassist-3.4.GA.jarWebContent/WEB-INF/lib/jaxb-api-2.1.jarWebContent/WEB-INF/lib/jaxb-impl-2.1.3.jarWebContent/WEB-INF/lib/jaxen-1.1.1.jarWebContent/WEB-INF/lib/jboss-common-4.0.2.jarWebContent/WEB-INF/lib/jboss-spring-deployer-as6-spring3-2.0.5.Final.0.5.Final.zipWebContent/WEB-INF/lib/jboss-vfs-3.1.0.Final.jarWebContent/WEB-INF/lib/jdom-1.0.jarWebContent/WEB-INF/lib/jstl-1.2.jarWebContent/WEB-INF/lib/jta-1.1.jarWebContent/WEB-INF/lib/log4j-1.2.14.jarWebContent/WEB-INF/lib/lucene-core-2.3.2.jarWebContent/WEB-INF/lib/lucene-highlighter-2.0.0.jarWebContent/WEB-INF/lib/mail-1.4.jarWebContent/WEB-INF/lib/mysql-connector-java-5.0.5.jarWebContent/WEB-INF/lib/persistence-api-1.0.jarWebContent/WEB-INF/lib/quartz-1.5.2.jarWebContent/WEB-INF/lib/slf4j-api-1.5.6.jarWebContent/WEB-INF/lib/slf4j-log4j12-1.5.6.jarWebContent/WEB-INF/lib/spring-aop-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-asm-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-beans-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-context-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-core-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-expression-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-jdbc-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-orm-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-tx-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-web-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/spring-webmvc-3.0.1.RELEASE.jarWebContent/WEB-INF/lib/stax-api-1.0-2.jarWebContent/WEB-INF/lib/validation-api-1.0.0.GA.jarWebContent/WEB-INF/lib/xalan-2.6.0.jarWebContent/WEB-INF/lib/xercesImpl-2.6.2.jarWebContent/WEB-INF/lib/xml-apis-1.3.02.jarWebContent/WEB-INF/lib/xmlParserAPIs-2.6.2.jarWebContent/WEB-INF/lib/xom-1.0.jar

    Could anyone please help me to reslove me this issue?

  • RELEVANCY SCORE 2.58

    DB:2.58:Jboss As 7 Not Deploying -- Caused By: Java.Io.Ioexception: No Context Factory For Vfs: a9



    11:50:52,097 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA

    11:50:55,429 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA

    11:50:55,750 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

    11:51:04,654 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

    11:51:04,691 INFO [org.xnio] XNIO Version 3.0.3.GA

    11:51:04,940 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

    11:51:05,056 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

    11:51:05,285 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem

    11:51:05,290 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem

    11:51:05,291 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.

    11:51:05,304 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem

    11:51:05,306 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

    11:51:06,131 INFO [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

    11:51:06,561 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

    11:51:06,579 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final

    11:51:07,178 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

    11:51:08,351 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

    11:51:10,966 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

    11:51:12,217 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/MySqlDS]

    11:51:12,692 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA

    11:51:13,433 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Backup\Eclipse\Share\Jboss\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments

    11:51:13,564 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999

    11:51:13,565 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:4447

    11:51:14,072 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "Virtuoso.war"

    11:52:00,761 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/lib/mail-1.4.jar" does not point to a valid jar for a Class-Path reference.

    11:52:01,673 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'

    11:52:01,770 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011401: Read persistence.xml for Virtuoso

    11:52:03,801 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011402: Starting Persistence Unit Service 'Virtuoso.war#Virtuoso'

    11:52:04,774 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-2) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

    11:52:04,852 INFO [org.hibernate.Version] (MSC service thread 1-2) HHH000412: Hibernate Core {4.0.1.Final}

    11:52:04,855 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000206: hibernate.properties not found

    11:52:04,862 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-2) HHH000021: Bytecode provider name : javassist

    11:52:05,020 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [

    name: Virtuoso

    ...]

    11:52:08,664 ERROR [org.hibernate.internal.util.xml.ErrorLogger] (MSC service thread 1-2) HHH000196: Error parsing XML (2) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '2.0'.

    11:52:11,061 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-2) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

    11:52:11,786 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect

    11:52:11,824 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-2) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory

    11:52:11,834 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-2) HHH000397: Using ASTQueryTranslatorFactory

    11:52:12,002 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final

    11:52:15,143 WARN [org.hibernate.internal.SessionFactoryImpl] (MSC service thread 1-2) HHH000008: JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession()

    11:52:19,979 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/Virtuoso]] (MSC service thread 1-1) Initializing Spring root WebApplicationContext

    11:52:19,982 INFO [org.springframework.web.context.ContextLoader] (MSC service thread 1-1) Root WebApplicationContext: initialization started

    11:52:20,021 INFO [org.springframework.web.context.support.XmlWebApplicationContext] (MSC service thread 1-1) Refreshing Root WebApplicationContext: startup date [Thu Dec 06 11:52:20 IST 2012]; root of context hierarchy

    11:52:20,104 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (MSC service thread 1-1) Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]

    11:52:20,346 INFO [org.springframework.context.annotation.ClassPathBeanDefinitionScanner] (MSC service thread 1-1) JSR-250 'javax.annotation.ManagedBean' found and supported for component scanning

    11:52:20,351 INFO [org.springframework.context.annotation.ClassPathBeanDefinitionScanner] (MSC service thread 1-1) JSR-330 'javax.inject.Named' annotation found and supported for component scanning

    11:52:20,375 INFO [org.jboss.virtual.spi.cache.VFSCacheFactory] (MSC service thread 1-1) Using VFSCache [NoopVFSCache]

    11:52:20,384 ERROR [org.springframework.web.context.ContextLoader] (MSC service thread 1-1) Context initialization failed: org.springframework.beans.factory.BeanDefinitionStoreException: I/O failure during classpath scanning; nested exception is java.io.IOException: No context factory for vfs:/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/classes/com/lntinfotech/virtuoso/db/

    at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:249) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:204) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1335) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1325) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:136) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:458) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:388) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:192) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

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

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

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

    Caused by: java.io.IOException: No context factory for vfs:/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/classes/com/lntinfotech/virtuoso/db/

    at org.jboss.virtual.VFS.getVFS(VFS.java:244) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.jboss.virtual.VFS.createNewRoot(VFS.java:261) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.jboss.virtual.VFS.getRoot(VFS.java:277) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver$VfsResourceMatchingDelegate.findMatchingResources(PathMatchingResourcePatternResolver.java:651) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:347) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:269) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.getResources(AbstractApplicationContext.java:1156) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:204) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    ... 30 more

    11:52:20,509 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/Virtuoso]] (MSC service thread 1-1) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanDefinitionStoreException: I/O failure during classpath scanning; nested exception is java.io.IOException: No context factory for vfs:/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/classes/com/lntinfotech/virtuoso/db/

    at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:249) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:204) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:84) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1335) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1325) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:136) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:93) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) [spring-beans-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:93) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:458) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:388) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:192) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47) [spring-web-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

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

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

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

    Caused by: java.io.IOException: No context factory for vfs:/C:/Backup/Eclipse/Share/Jboss/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/bin/content/Virtuoso.war/WEB-INF/classes/com/lntinfotech/virtuoso/db/

    at org.jboss.virtual.VFS.getVFS(VFS.java:244) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.jboss.virtual.VFS.createNewRoot(VFS.java:261) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.jboss.virtual.VFS.getRoot(VFS.java:277) [jboss-vfs-2.2.0.M2.jar:2.2.0.M2]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver$VfsResourceMatchingDelegate.findMatchingResources(PathMatchingResourcePatternResolver.java:651) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:347) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:269) [spring-core-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.getResources(AbstractApplicationContext.java:1156) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:204) [spring-context-3.0.0.RELEASE.jar:3.0.0.RELEASE]

    ... 30 more

    11:52:20,739 INFO [org.quartz.simpl.SimpleThreadPool] (MSC service thread 1-1) Job execution threads will use class loader of thread: MSC service thread 1-1

    11:52:20,777 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Quartz Scheduler v.null.null.null created.

    11:52:20,782 INFO [org.quartz.simpl.RAMJobStore] (MSC service thread 1-1) RAMJobStore initialized.

    11:52:20,784 INFO [org.quartz.impl.StdSchedulerFactory] (MSC service thread 1-1) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

    11:52:20,787 INFO [org.quartz.impl.StdSchedulerFactory] (MSC service thread 1-1) Quartz scheduler version: null.null.null

    11:52:20,789 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

    11:52:20,899 INFO [stdout] (MSC service thread 1-1) Attribute set

    11:52:20,982 INFO [stdout] (MSC service thread 1-1) msgLocale attribute set!!!

    11:52:21,138 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Error listenerStart

    11:52:21,140 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/Virtuoso] startup failed due to previous errors

    11:52:21,175 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/Virtuoso]] (MSC service thread 1-1) Closing Spring root WebApplicationContext

    11:52:21,187 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.web.deployment.default-host./Virtuoso: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Virtuoso: JBAS018040: Failed to start context

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

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

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

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

    11:52:21,203 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990

    11:52:21,205 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 100096ms - Started 399 of 478 services (2 services failed or missing dependencies, 76 services are passive or on-demand)

    11:52:21,411 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Virtuoso.war" was rolled back with failure message {"JBAS014671: Failed services" = {"jboss.web.deployment.default-host./Virtuoso" = "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Virtuoso: JBAS018040: Failed to start context"}}

    11:52:21,464 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011403: Stopping Persistence Unit Service 'Virtuoso.war#Virtuoso'

    Virtuoso.war/WEB-INF/classes/com/lntinfotech/virtuoso/db/ -- contains the HQL queries

  • RELEVANCY SCORE 2.58

    DB:2.58:Please Help Me - Spring - Scope? cc


    Hi,
    How to use transaction-manager + non-singleton in spring
    How to import singleton option without use DTD?
    I want to define singleton = "false" (the default is true) in me xsm file but I can do that only if I using:
    Am I need to use scope for this problem? to definr non singleton? If yes, How?

    !DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd"But I'm using tran for the transaction with the folowing:

    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd" aop:config
    aop:advisor pointcut="execution(* tx*(..))"
    advice-ref="txAdvice"/
    /aop:config

    tx:advice id="txAdvice" transaction-manager="transactionManager"
    tx:attributes
    tx:method name="tx*" propagation="REQUIRED"/
    /tx:attributes
    /tx:adviceHow to use transaction + singleton = "false" ?

    Edited by: yael800 on Jun 23, 2008 11:18 AM

    DB:2.58:Please Help Me - Spring - Scope? cc

    Hi,
    How to use transaction-manager + non-singleton in spring
    How to import singleton option without use DTD?
    I want to define singleton = "false" (the default is true) in me xsm file but I can do that only if I using:
    Am I need to use scope for this problem? to definr non singleton? If yes, How?

    !DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd"But I'm using tran for the transaction with the folowing:

    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd" aop:config
    aop:advisor pointcut="execution(* tx*(..))"
    advice-ref="txAdvice"/
    /aop:config

    tx:advice id="txAdvice" transaction-manager="transactionManager"
    tx:attributes
    tx:method name="tx*" propagation="REQUIRED"/
    /tx:attributes
    /tx:adviceHow to use transaction + singleton = "false" ?

    Edited by: yael800 on Jun 23, 2008 11:18 AM

  • RELEVANCY SCORE 2.58

    DB:2.58:Registering Application Context Of An Existing Spring Application In Spring 9m


    Hi,

    I am using spring container for my web application and integrated coherence data grid to cache some data.

    I want to use the refresh ahead mechanism of coherence to refresh my cache every x minutes. To refresh the cache the business rule is already written in a service class which is registered in the spring container as a bean.

    Now I want to reuse this business logic by using the bean of the service class in my query cache loader by see a server start up failure after doing the following configurations:

    beans default-autowire="byName"
    xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:jms="http://www.springframework.org/schema/jms" xmlns:amq="http://activemq.apache.org/schema/core"
    xmlns:context="http://www.springframework.org/schema/context"
    xsi:schemaLocation="http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
    http://activemq.apache.org/schema/core
    http://activemq.apache.org/config/1.0/core/activemq-core-5.3.0.xsd
    http://www.springframework.org/schema/jms
    http://www.springframework.org/schema/jms/spring-jms-3.0.xsd
    http://www.springframework.org/schema/context
    http://www.springframework.org/schema/context/spring-context-3.0.xsd"

    bean id="cacheFactory" class="com.ladbrokes.core.services.cache.impl.SpringAwareCacheFactory"
    /bean

    bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean"
    property name="targetClass" value="com.tangosol.net.CacheFactory"/
    property name="targetMethod" value="setConfigurableCacheFactory"/
    property name="arguments" ref="cacheFactory"/
    /bean

    bean id="cacheLoader" class="com.ladbrokes.core.services.cache.impl.QueryCacheLoader"
    property name="eventListAccessor" ref="eventListAccessor" /
    /bean

    /beans

    Please guide me when am I making a mistake?

    Regards,
    Amit

  • RELEVANCY SCORE 2.57

    DB:2.57:Beaninfo Annotations dx


    How can I specify BeanInfo metadata using Java 5 annotations instead of separate BeanInfo classes? If someone has written a set of annotations to accomplish this, please share.

    I ran into this problem when I was using XMLEncoder/XMLDecoder to persist some beans. I wound up writing parallel BeanInfo classes to specify persistence delegates and tag certain attributes as transient. It works, but it would be a lot cleaner if I could keep the metadata in the same file using annotations.

    DB:2.57:Beaninfo Annotations dx

    How can I specify BeanInfo metadata using Java 5 annotations instead of separate BeanInfo classes? If someone has written a set of annotations to accomplish this, please share.

    I ran into this problem when I was using XMLEncoder/XMLDecoder to persist some beans. I wound up writing parallel BeanInfo classes to specify persistence delegates and tag certain attributes as transient. It works, but it would be a lot cleaner if I could keep the metadata in the same file using annotations.

  • RELEVANCY SCORE 2.57

    DB:2.57:Singleton And Spring sk


    Would it be just my impression?

    I have an impression of proliferation of singleton pattern in the usage of Spring framework, mainly because the default mode in Spring beans is singleton, and not prototype. I think people are taking the exceptional case as the general rule, making all the Spring beans as singletons. I think prototype should be more used. Not to mention the problems related to the singleton (anti-)pattern, as for example threads concurrency problem if those singleton beans are not correctly applied.

    DB:2.57:Singleton And Spring sk

    why don't you discuss that in the Spring support forums?

    But yes, you do have a point and I mark most of my Spring beans to not be singletons :)

  • RELEVANCY SCORE 2.57

    DB:2.57:New Feature Proposal: Bytype Injection Of Spring Beans mp



    Hi guys,The current JBoss Spring integration seems to support only byName injection, it would be great if it could support also byType injection.ByType injection of dependencies is a very powerfull feature of Spring, and it would be great if it could be leveraged in the JBoss Spring integration. ByType injection could be attempted by the SpringInjectionSupport whenever the bean attribute of the Spring annotation is missing.
    @Spring(jndiName = "spring-pojo")
    private IntCreator intCreator;

    DB:2.57:New Feature Proposal: Bytype Injection Of Spring Beans mp


    SpringDeployer compatible with Spring2.0 final.http://www.jboss.org/index.html?module=bbop=viewtopicp=3979096

  • RELEVANCY SCORE 2.56

    DB:2.56:Developing Ejb 3.0 With Eclipse sj


    Hello,

    I've recently started to involve myself with EJB 3.0 development but I'm having trouble getting a practical development situation going on with Eclipse (3.2.1).

    Would any of you be so kind to explain how your Eclipse is set up to comfortably develop beans and such without excessive configuration, XML-editing and whatnot. Even getting the annotations to be recognized is a bit of a challenge. Am I missing something?

    Regards,

    Remon

  • RELEVANCY SCORE 2.56

    DB:2.56:Re: Spring Vs Ejb 87


    what debate?
    Use both together, as Spring was intended to be
    used...Have you stumbled across Rod Johnson's book "J2EE
    without EJB"Yeh. Still discusses appropriate use of EJB, though, doesn't it? Even Teh Sequel - a 700+page advert for Spring - advocates the use of EJB where appropriate. Spring can sit quite nicely within an EJB container, if need be

    Secondly how are you going to use DI and inversion of
    control from both spring and EJB 3 at the same time?Who said you had to? Take a leaf out of Spring's book - use whatever is most appropriate for you.

    DB:2.56:Re: Spring Vs Ejb 87


    you don't have to choose one OR the other.
    It's very well possible to successfully combine both
    to get something that's stronger than either one
    taken on its own.

    Especially you're likely going to want to create a
    client library to your EJB system, and that one could
    very well benefit from Spring.

    Or do as we did, create an EJB application which the
    client library accesses through a serverside Spring
    layer, completely shielding the client application
    from both EJB AND Spring.I do like you ridea of creating a client library. Thanks

  • RELEVANCY SCORE 2.55

    DB:2.55:Manning Di Book 8d


    So I was briefly reading the new DI book from Manning. It briefly mentioned Seam in the intro to dependency injection frameworks but I did not see any reference to 299 or Web Beans. I also did not see the author mention the fact that Seam uses dynamic DI whereas Spring uses static DI. Or any general coverage on the differences b/n the two approaches/techniques. But I didn't read too much of it honestly. Now I'm wondering if Guice (which 299 is partially based on) uses static or dynamic DI.

    DB:2.55:Manning Di Book 8d

    Gavin King wrote on Oct 06, 2009 02:07:This is the first time the name of the RI has changed. What happened previously was that the name of the specification changed. Of course neither name change was our preference, so it's a bit unfair to be bitching at us about it.Well, I guess I can't argue. But you'd imagine that if you were a spec lead and the other members of the EG (or the community?) forced or mandated a name change against the direction of the spec lead, something may be amiss.
    So, sorry, but the EGs should try to at least nail down the names in the beginning of the JSR formations, etc.
    So Weld it is (for now).

  • RELEVANCY SCORE 2.55

    DB:2.55:Tranaction Issue Using Seam Spring Integration 98


    Currently we are doing POC using SEAM, SPRING, JPA webapplication on Tomcat server(Without JBOSS)

    While integrating SPRING with SEAM, event is not getting raised using raiseTransactionSuccessEvent(), but we could acheive it by using raiseEvent(). Any idea what could be the issue.

    Following code snippets

    1) applicationContext.xml

    ------------------------------

    beans xmlns="http://www.springframework.org/schema/beans" xmlns:aop="http://www.springframework.org/schema/aop"

    xmlns:util="http://www.springframework.org/schema/util" xmlns:seam="http://jboss.com/products/seam/spring-seam"

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tx="http://www.springframework.org/schema/tx"

    xmlns:jee="http://www.springframework.org/schema/jee"

    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd

    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd

    http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.0.xsd

    http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-2.0.xsd

    http://jboss.com/products/seam/spring-seam http://jboss.com/products/seam/spring-seam-2.0.xsd

    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd"

    default-lazy-init="false"

    !-- This uses resource local JpaTransactionManager. You could just as easily use a JtaTransactionManager --

    bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager"

    !-- Be sure to specify the SeamManagedEntityManagerFactory since that will manage the EM that will be

    beginning and ending transactions.--

    property name="entityManagerFactory" ref="seamEntityManagerFactory"/

    /bean

    tx:annotation-driven proxy-target-class="true" /

    !-- using PersistenceAnnotationBeanPostProcessor for persistence --

    bean id="orderService" class="com.service.impl.OrderServiceImpl" scope="prototype"

    seam:component/

    /bean

    bean id="userService" class="com.service.impl.UserServiceImpl" scope="prototype"

    seam:component/

    /bean

    seam:configure-scopes /

    bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"

    !-- Because we have multiple EntityManagerFactories in this applicaitonContext identify the

    SeamManagedEntityManagerFactory as the default --

    property name="defaultPersistenceUnitName" value="conversationScoped"/

    /bean

    !-- EMF that wraps a Seam Managed EM instance for use in Spring --

    bean id="seamEntityManagerFactory" class="org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean"

    !-- The Seam managed-persistence-context component name. --

    property name="persistenceContextName" value="em" /

    !-- Optionally provide a unit name. If not specified the default would be the persistenceContextName --

    property name="persistenceUnitName" value="conversationScoped"/

    /bean

    /beans

    DB:2.55:Tranaction Issue Using Seam Spring Integration 98

    This is a bug. Thanks for finding it. :)
    http://jira.jboss.com/jira/browse/JBSEAM-2662

  • RELEVANCY SCORE 2.55

    DB:2.55:As 7.1.1 To Eap 6.1 Migration Of Owf fs



    I'm in the process of migrating a customized OWF application from JBoss AS 7.1.1 to JBoss EAP 6.1. I've copied over the war the modules, and I've updated the configuration start scripts as far as I can tell is needed. The issue seems to be that the resources imported by the Spring resources.xml, which exist under a particular JBoss module's path, are not loaded.

    Here's the /WEB-INF/spring/resources.xml, which tries to import the OWF config files:

    ?xml version="1.0" encoding="UTF-8"?
    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans-3.0.xsd"
    import resource="classpath*:*OWFsecurityContext*.xml" /
    import resource="classpath*:OwfConfig.xml" /
    /beans

    DB:2.55:As 7.1.1 To Eap 6.1 Migration Of Owf fs


    The AS 7.1.1 instance did have snowdrop installed as a module, though the configuration didn't look like it was using it. The config file entries seemed to be making reference to Grails components instead. I haven't looked into it too much, since removing the wildcards caused the application to load successfully.

    However, now, when I try to hit an OWF page, I get this in the logs:

    17:20:52,548 ERROR [com.mycompany.sso.SSOTokenValidatorLoginModule] (ajp-/0.0.0.0:8009-1) problem during validation of sso token: org.apache.commons.lang.SerializationException: java.lang.ClassNotFoundException: com.mycompany.sso.SubjectWrapper from [Module "org.apache.commons.lang:main" from local module loader @68a0864f (finder: local module finder @2d1e233 (roots: /opt/jboss/default/modules,/opt/jboss/default/modules/system/layers/base))]

    at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:166) [commons-lang-2.6-redhat-2.jar:2.6-redhat-2]

    at org.apache.commons.lang.SerializationUtils.deserialize(SerializationUtils.java:193) [commons-lang-2.6-redhat-2.jar:2.6-redhat-2]

    at com.mycompany.sso.cache.access.impl.SubjectSerializer.deserializeSubject(SubjectSerializer.java:27) [web-sso.jar:]

    at com.mycompany.sso.cache.access.impl.HTTPCacheAccess.getCachedSubject(HTTPCacheAccess.java:89) [web-sso.jar:]

    at com.mycompany.sso.SSOTokenValidatorLoginModule.login(SSOTokenValidatorLoginModule.java:80) [web-sso.jar:]

    ...

    Caused by: java.lang.ClassNotFoundException: com.mycompany.sso.SubjectWrapper from [Module "org.apache.commons.lang:main" from local module loader @68a0864f (finder: local module finder @2d1e233 (roots: /opt/jboss/default/modules,/opt/jboss/default/modules/system/layers/base))]

    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final-redhat-1]

    ...

    The weird part is that the class that it can't find, com.mycompany.sso.SubjectWrapper, is in the same web-sso.jar as the com.mycompany.sso.SSOTokenValidatorLoginModule referenced in the stack trace above. Here's a cut from the class listing of the jar in question:

    # jar tvf /opt/jboss/default/modules/com/mycompany/login/main/web-sso.jar

    ...

    4341 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/SSOTokenValidatorLoginModule.class

    1804 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/valve/ResponseForwarderValve.class

    703 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/valve/CatalinaRequestWrapper.class

    2496 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/CacheUtils.class

    2170 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/misc/PropertiesUtility.class

    2344 Thu Aug 15 18:17:50 GMT 2013 com/mycompany/sso/SubjectWrapper.class

    638 Thu Aug 15 18:17:50 GMT 2013 web-sso.properties

    ...

    Any idea how one class file from a jar could be successfully loaded, while the other is unable to be found at runtime? Would some kind of class load failure of one of the classes in between the two cause the class loader to stop processing the jar and not load SubjectWrapper...or maybe a failure in SubjectWrapper itself? There are no other logged errors in boot-up or otherwise, just this one when a login is attempted.

    Thanks,

    Kyle

  • RELEVANCY SCORE 2.55

    DB:2.55:Using Spring Jms Defaultmessagelistenercontainer Within Oracle Cep kj


    Hi everyone,
    I need to use a DefaultMessageListenerContainer Spring bean (from spring-jms.jar), have the wlevs bean factory to assemble it (it depends from a POJO) and set it as a property of an Adapter bean.
    How do I do it?
    I tried to put the spring-jms.jar into the xbootclasspath but it depends from spring-core.jar. If i put spring-core.jar into the xbootclasspath, the server dies screaming.
    Documentation says i can use legacy Spring beans within an OCEP application, well how do i do it? Can anyone tell me the right steps to do?

    DB:2.55:Using Spring Jms Defaultmessagelistenercontainer Within Oracle Cep kj

    Yes, the jmsAdapter shipped with OCEP does something similar but unfortunately in this case we cannot use it, cause it requires that the connection factory object must be reachable through a JNDI lookup with provider url, credentials etc.
    The recomended method (and the only working one, so far) to obtain an Oracle AQ connection factory is through a call to AQjmsFactory.getQueueConnectionFactory(oracleHost, oracleSID, oraclePort, "thin")) or similar. We also tried this trick here:

    http://biemond.blogspot.com/2009/07/using-aq-jms-text-message-in-wls-1031.html

    (basically, import Oracle AQ as a foreign JMS server within a WLS instance and then connect CEP to the mirrored JMS objects on WLS using the standard jmsAdapter, but... didn't work).

    So I thought about using a Spring DefaultMessageListenerContainer, whose injected ConnectionFactory is actually a proxy encapsulating a ConnectionFactory created via the AQjmsFactory.getQueueConnectionFactory method. And it worked, apart from hanging on the shutdown() call :(

    Edited by: javawarrior2003 on 13-gen-2011 17.59

  • RELEVANCY SCORE 2.55

    DB:2.55:Jboss 5.1 - Java.Lang.Reflect.Invocationtargetexception cx



    I am getting the following errors while deploying the mands-jmx-packet-sender-2.0.0-.ear in Jboss 5.1.

    Note: This was working in Jboss 4.2.3 without any exceptions.

    Please find the attached file for stack trace.

    Contents of PacketSender.appctx.xml

    ?xml version="1.0" encoding="UTF-8"?

    !DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd"

    beans

    bean id="sessions" class="org.springframework.jndi.JndiObjectFactoryBean"

    property name="jndiName" value="java:/mands/packetSender/hibernate/sessionFactory" /

    /bean

    bean id="dao" class="uk.co.choice.mands.server.jmx.packetsender.dao.hibernate.HibernateInventoryPacketTreeItemDao"

    property name="sessionFactory" ref="sessions" /

    /bean

    /beans

    It would be great, if any one provides some inputs to resolve this issue.

    Thanks,

    Prakash

    DB:2.55:Jboss 5.1 - Java.Lang.Reflect.Invocationtargetexception cx


    Hi Jaikiran,

    The logs which I have attached are not the same log files, each log file contains only the relavent logs for the particular issue, which I have mentioned in the subject line.

    All are distinct issues.

    Thanks,

    Prakash

  • RELEVANCY SCORE 2.55

    DB:2.55:Deployer Problem: Duplicate Applicationcontext Beans Created 1c



    I am having a a problem with the spring deployer creating duplicate instances of a spring program from *-spring.xml files in the deploy directory. It appears as though the xml file gets read and parsed once, and the the ApplicationContext and all beans in the xml file get created TWICE.

    I have no idea where to start with this problem. I have verified that there aren't any redundant spring jars in the classpath. Any pointers would be greatly appreciated.

    I am using:

    jboss 5.1.0

    spring 3.0.3

    spring deployer 3.3 from snowdrop (same problem with spring-int from jboss svn)

  • RELEVANCY SCORE 2.55

    DB:2.55:Module Classloading Problems With Jboss-Deployment-Structure.Xml In .Ear File md


    Hi,

    I am trying to deploy ear which contains single war which depends on resteasy, cxf, spring and IBatis I am trying to use resteasy and cxf dependencies provided by jboss eap module. For spring integration I create another module 'org.springframework.spring' to fix XML schema validation, as suggested in other forum threads. I was able to deploy it succesfully on JBoss EAP 6.0.1 but when I try to call any service I am getting ava.lang.ClassNotFoundException

    Any suggestions?

    The ear structure looks like:
    ------------------------------------------
    META-INF/application.xml
    META-INF/MANIFEST.MF
    META-INF/jboss-deployment-structure.xml
    demo-1.1.21-SNAPSHOT.war

    the war structure looks like:
    ------------------------------------------
    WEB-INF/web.xml
    WEB_INF/lib/ all third party jars and application jars
    WEB_INF/classes/logback.xml
    WEB_INF/classes/cxf-servlet.xml

    --------------------------------------------

    jboss-deployment-strcture.xml
    -----------------------------------------

    jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"

    sub-deployment name="demo-1.1.21-SNAPSHOT.war"

    exclusions

    module name="org.slf4j" /

    module name="org.slf4j.impl" /

    /exclusions

    dependencies

    module name="org.apache.cxf" /

    module name="org.apache.cxf.impl" /

    module name="org.springframework.spring"

    imports

    include path="META-INF**" /

    include path="org**" /

    /imports

    /module

    /dependencies

    local-last value="true" /

    /sub-deployment

    /jboss-deployment-structure

    ExceptionStackTrace:

    ------------------------------------------------------

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionLogDataService' defined in class path resource [DATA_ACCESS_LAYER-data-dao.xml]: Cannot resolve reference to bean 'transactionLogDAOFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionLogDAOFactory' defined in class path resource [DATA_ACCESS_LAYER-data-dao.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.demo.transaction.logging.dao.impl.oracle.TransactionLogDAOFactory]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/iba

    tis/common/xml/NodeletException

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1003) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895) [spring-context-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425) [spring-context-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:139) [spring-context-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:93) [spring-context-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at com.demo.transaction.logging.DemoTransactionLogging.init(DemoTransactionLogging.java:64) [demo-service-transaction-logging-1.1.21-SNAPSHOT.jar:]

    at com.demo.transaction.logging.DemoTransactionLogging.clinit(DemoTransactionLogging.java:33) [demo-service-transaction-logging-1.1.21-SNAPSHOT.jar:]

    ... 45 more

    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionLogDAOFactory' defined in class path resource [DATA_ACCESS_LAYER-data-dao.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.demo.transaction.logging.dao.impl.oracle.TransactionLogDAOFactory]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/ibatis/common/xml/NodeletException

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:288) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1003) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    ... 63 more

    Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.demo.transaction.logging.dao.impl.oracle.TransactionLogDAOFactory]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/ibatis/common/xml/NodeletException

    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:141) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:108) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    ... 72 more

    Caused by: java.lang.NoClassDefFoundError: com/ibatis/common/xml/NodeletException

    at com.demo.transaction.logging.dao.impl.oracle.TransactionLogDAOFactory.init(TransactionLogDAOFactory.java:34) [demo-service-transaction-logging-1.1.21-SNAPSHOT.jar:]

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_45]

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_45]

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_45]

    at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_45]

    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126) [spring-beans-3.0.5.RELEASE.jar:3.0.5.RELEASE]

    ... 74 more

    Caused by: java.lang.ClassNotFoundException: com.ibatis.common.xml.NodeletException from [Module "org.springframework.spring:main" from local module loader @b0a3f5 (roots: C:\tools\ais-jbosseap6\modules)]

    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)

    ... 80 more

    PS: when I exclude all JBoss provided dependencies and use jars from EAR/WAR/WEB-INF/lib every thing works fine. But when I try to use JBoss provided dependencies I am facing the issue.

    DB:2.55:Module Classloading Problems With Jboss-Deployment-Structure.Xml In .Ear File md


    I believe you have missing ibatis module configurations

    I dont know the answer but I can say that new class loader is no better than last one. at least last one had a clear cut strategy put every thing in lib folder and at least one application can work by default with out any conflicts at least in one instance of jboss , not it is kind of nightmare or it may just me not able to understand the class loading model here in the new wild fly .

  • RELEVANCY SCORE 2.55

    DB:2.55:Mediator To Spring Error-Could Not Convert From Java Interface To Interface 8m


    Hi,

    I have a requirement to using a Spring component and my composite application would be File Read - Mediator - Spring Component - File Write.

    I have to read a file and using mediator map the same to the Spring input and write the Spring component output to a file.

    I have created a Java interface ( Package Name - transformtospring , Interface Name - TransformInterface) and also created a Java Class ( TransformImpl ) which implements the Interface in this package. Saved all these artifacts in SCA-INF/src folder of the application.

    My Spring Bean configuration file is as follows ( saved the file in the same folder as composite.xml )

    ______________________

    ?xml version="1.0" encoding="windows-1252" ?
    beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:util="http://www.springframework.org/schema/util"
    xmlns:jee="http://www.springframework.org/schema/jee"
    xmlns:lang="http://www.springframework.org/schema/lang"
    xmlns:aop="http://www.springframework.org/schema/aop"
    xmlns:tx="http://www.springframework.org/schema/tx"
    xmlns:sca="http://xmlns.oracle.com/weblogic/weblogic-sca"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-2.5.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/lang http://www.springframework.org/schema/lang/spring-lang-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/tool http://www.springframework.org/schema/tool/spring-tool-2.5.xsd http://xmlns.oracle.com/weblogic/weblogic-sca META-INF/weblogic-sca.xsd"
    !--Spring Bean definitions go here--
    bean class="transformtospring.TransformImpl" name="TransformBean"/
    sca:service name="TransformService" target="TransformBean"
    type="transformtospring.TransformImpl"/
    /beans

    ________________________

    I have created a Spring Context which uses the above Spring Configuration. When i tried to map the mediator output to Spring , i'm getting an error shown below.

    " Could not convert from java interface to interface type wsdl . Exception=java.lang.ClassNotFoundException transformtospring.TransformImpl "

    Please do let me know where exactly i'm doing wrong.

    Regards,
    Sri.

    DB:2.55:Mediator To Spring Error-Could Not Convert From Java Interface To Interface 8m

    I am confused. The above error you mentioned was obvious (first no interface declared, and then a missing build path). Ok you are through this now.

    Which service, the composite service (or the intra composite spring service) is not returning anything? a flow of the composite would help to understand your problem much better.

    Cheers

  • RELEVANCY SCORE 2.55

    DB:2.55:Concurrency Support Of Spring Bean In Web Logic Container fk


    We are building multiple spring beans using spring framework. We would deploy spring container inside web logic. What should we do so that we would have concurrency support for individual spring beans inside web logic container.

    DB:2.55:Concurrency Support Of Spring Bean In Web Logic Container fk

    We are building multiple spring beans using spring framework. We would deploy spring container inside web logic. What should we do so that we would have concurrency support for individual spring beans inside web logic container.

  • RELEVANCY SCORE 2.54

    DB:2.54:Jboss 7 Modules And Lib Inside War Conflict pa



    I'm migrating my application to Jboss 7.1 and I'm having same problem using jboss modules for a war file that use spring 3.1 and hibernate 4.

    If I include all of the hibernate/spring files inside the lib directory, the application works. But if I tried to configure jboss-deployment-structure.xml to use the org.hibernate module and not include hibernate jars inside lib folder, this error appear.

    17:38:47,154 ERROR [org.hibernate.internal.SessionFactoryImpl] (MSC service thread 1-1) HHH000302: Unable to construct current session context [org.springframework.orm.hibernate4.SpringSessionContext]: org.hibernate.service.classloading.spi.ClassLoadingException: Unable to load class [org.springframework.orm.hibernate4.SpringSessionContext]

    at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:141) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at org.hibernate.internal.SessionFactoryImpl.buildCurrentSessionContext(SessionFactoryImpl.java:1491) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at org.hibernate.internal.SessionFactoryImpl.init(SessionFactoryImpl.java:502) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1746) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1784) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at org.springframework.orm.hibernate4.LocalSessionFactoryBuilder.buildSessionFactory(LocalSessionFactoryBuilder.java:242) [spring-orm-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.orm.hibernate4.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:372) [spring-orm-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.orm.hibernate4.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.java:357) [spring-orm-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1452) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1360) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1118) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1360) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1118) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

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

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) [spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469) [spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383) [spring-web-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283) [spring-web-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) [spring-web-3.1.2.RELEASE.jar:3.1.2.RELEASE]

    at org.appfuse.webapp.listener.StartupListener.contextInitialized(StartupListener.java:51) [classes:]

    at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3394) [jbossweb-7.0.17.Final.jar:]

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

    at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:89) [jboss-as-web-7.1.3.Final.jar:7.1.3.Final]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)

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

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

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

    Caused by: java.lang.ClassNotFoundException: Could not load requested class : org.springframework.orm.hibernate4.SpringSessionContext

    at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl$1.findClass(ClassLoaderServiceImpl.java:99) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [rt.jar:1.6.0_18]

    at java.lang.ClassLoader.loadClass(ClassLoader.java:248) [rt.jar:1.6.0_18]

    at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_18]

    at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_18]

    at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:138) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]

    ... 50 more

    It seems that the hibernate module jars does not see the spring jars located inside the war lib folder. Is there any correct way to configure this to work, or do I need to include all of the jars file inside lib folder?

    Thanks in advance!

    DB:2.54:Jboss 7 Modules And Lib Inside War Conflict pa


    Well, maybe that's the problem. I should stop looking for a workaround then

    Thanks for the link!

  • RELEVANCY SCORE 2.54

    DB:2.54:Is It Possible To Create Beans/Services Without Xml (By Annotations)? 9j



    Is it possible to create beans without using XML deployment descriptor ? is it possible by annotions?

    sample link will be great.

    DB:2.54:Is It Possible To Create Beans/Services Without Xml (By Annotations)? 9j


    Is it possible to create beans without using XML deployment descriptor ? is it possible by annotions?

    sample link will be great.

    http://java.dzone.com/articles/a-look-inside-jboss-microconta-0

  • RELEVANCY SCORE 2.54

    DB:2.54:Monitoring Spring Application Components sk


    Is it possible to monitor all the activities of Spring container components from WL Console (Extension) including,
    a.Data Sources, Connection Pools
    b.Stateless Session Beans (Springs)
    c.JMS, WS, etc?

    DB:2.54:Monitoring Spring Application Components sk

    Are you talking about monitoring Weblogic components or Spring components? You subject says monitoring Spring application components, but you list below are all Weblogic components.

    You can monitoring the Weblogic components on the console, everything you listed below, even they are be used from the Spring application.

    You can't monitoring the Spring Beans since Spring has not add standard monitoring capabilities to their container. You could write your own RuntimeMBean to monitoring the Spring Beans, but that takes work.