June 2011 - jboss-dev-forums - Jboss List Archives

[JBoss AS7 Development] - Deploying an application from an external deployment location

by jaikiran pai

jaikiran pai [http://community.jboss.org/people/jaikiran] created the document: "Deploying an application from an external deployment location" To view the document, visit: http://community.jboss.org/docs/DOC-16939 -------------------------------------------------------------- Just like previous versions ( http://community.jboss.org/docs/DOC-13241 AS5 and http://community.jboss.org/docs/DOC-16444 AS6), JBoss AS7 allows you to deploy applications from an external deployment folder. i.e. you +don't+ have to place the deployment within the JBoss AS installation directory hierarchy for it to be picked up and deployed by the server. The following sections will explain how you can configure AS7 to look for deployments in an external deployment directory. h5. Standalone server: By default, the standalone server looks for deployments in JBOSS_HOME/standalone/deployments folder. In this example, we will configure the AS7 standalone server to additionally pick up deployments from a folder named /home/me/as7/mydeployments. * Stop the standalone server, if it is already running. * Open the JBOSS_HOME/standalone/configuration/standalone.xml file in a text editor of your choice * Look for <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0"> subsystem in that file. You'll notice that it already contains a <deployment-scanner> child element which configures the server to look for deployments in a folder named "deployments" relative-to the jboss.server.base.dir. * Now let's add a new deployment-scanner which will look for deployments under the folder named /home/me/as7/mydeployments: <deployment-scanner name="my-external-deployment-scanner" path="/home/jpai/as7/deployments" scan-interval="5000" /> Notice that we have named this deployment-scanner "my-external-deployment-scanner". You can give it a (unique) name of your choice. The "path" points to /home/jpai/as7/deployments folder, which is where we will be placing our deployments. The "scan-interval" is the interval in milliseconds for the scanner thread to run, to check for hot deployment. * With this addition, the susbsystem section will now look like: <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0"> <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" /> <deployment-scanner name="my-external-deployment-scanner" path="/home/jpai/as7/deployments" scan-interval="5000" /> </subsystem> * Let's now save the changes in the standalone.xml file and start the standalone server: jpai@jpai-laptop:bin$./standalone.sh If you had any deployments in /home/jpai/as7/deployments folder, then you'll notice that the server has picked up those deployments for deploying. Also, if you add any new deployments, to this folder while the server is running, they will be picked up too (unless you configure the deployment scanner to disable hot deployment). For complete reference on what the deployment-scanner element configuration allows, take a look at the jboss-deployment-scanner.xsd here https://github.com/jbossas/jboss-as/blob/master/deployment-scanner/src/ma... https://github.com/jbossas/jboss-as/blob/master/deployment-scanner/src/ma... -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16939] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

13 years, 6 months

1
0
0 / 0

[JBoss AS7 Development] - Logging Id's

by James Perkins

James Perkins [http://community.jboss.org/people/jamezp] modified the document: "Logging Id's" To view the document, visit: http://community.jboss.org/docs/DOC-16810 -------------------------------------------------------------- || *Range* || *Subsystem * || | *10100 - 10199* | *Transaction* | | *10200 - 10299 * | *Clustering** * | | *10300 - 10399 * | *CLI**U**U* | | *10400 - 10499* | *Connector** * | | *10500 - 10599* | *Controller** * | | *10600 - 10699* | *Controller Client* | | *10700 - 10799* | *Deployment Repository* | | *10800 - 10899* | *JPA* | | *10900 - 10999* | *Deployment Scanner* | | *11000 - 11099* | *EE* | | *11100 - 11199* | *Embedded* | | *11200 - 11299* | *JAXRS* | | *11300 - 11399* | *JMX* | | *11400 - 11499* | *JPA* | | *11500 - 11599* | *Logging* | | *11600 - 11699* | *Messaging* | | *11700 - 11799* | *mod_cluster* | | *11800 - 11899* | *Naming* | -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16810] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

13 years, 6 months

1
0
0 / 0

[JBoss Web Services Development] - JBossWS - Running the test suites

by Alessio Soldano

Alessio Soldano [http://community.jboss.org/people/asoldano] modified the document: "JBossWS - Running the test suites" To view the document, visit: http://community.jboss.org/docs/DOC-13523 -------------------------------------------------------------- *** #Working_with_the_integration_layers Working with the integration layers **** #Ant_build Ant build **** #Maven__Ant_build Maven + Ant build *** #Working_with_JBossWSNative Working with JBossWS-Native **** #Ant_build_65545 Ant build **** #Maven__Ant_build_28091 Maven + Ant build *** #Working_with_JBossWSCXF Working with JBossWS-CXF **** #Ant_build_853149 Ant build **** #Maven__Ant_build_430673 Maven + Ant build *** #Working_with_the_Hudson_QA_environment Working with the Hudson QA environment **** #Maven__Ant_build_59362 Maven + Ant build Typically you would build, deploy, test one of the web service stacks against one of the supported target containers. Here we explain first the manual procedure. Further down you find instruction on how to do this using our automated Hudson QA environment. Please not two different builds are available, Ant and Maven+Ant, as the binary distribution does not use Maven. h3. Working with the integration layers To run the general JAX-WS samples against our native WS stack on JBoss-6.0 you would run the sequence below. This is also the required sequence before any SVN commit. If one of the tests fails, please complain loudly. h4. Ant build +*Note*+ +Make sure to *modify ant.properties* accordingly before running the tasks below. Running the tests against another target container simply means changing the ant.properties calling "ant deploy-jboss510" for instance. Also please note that the provided Ant targets may change from release to release because of different supported AS containers; calling "ant -projecthelp" is often a good idea to understand which targets are available.+ cd stack/native/trunk ant deploy-jboss600 ant tests-main ant tests-samples To run the collection of provider sample tests, you would run ant -Dtest=jaxws/samples/provider test To run a single specific test, you would run ant -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test This can be done in debug mode as well ant -Ddebug=true -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test h4. Maven + Ant build +*Note*+ +Make sure to *copy/modify profiles.xml.example/profiles.xml* accordingly before running the tasks below. Running the tests against another target container both means changing the deploy ant command ("ant deploy-jboss510" for instance) and the specified maven profile when running the tests. This simply means changing the specified profile to "jboss510" for instance. Also please note that the provided target profiles may change from release to release because of different supported AS containers.+ cd stack/native/trunk ant deploy-jboss600 mvn -Ptestsuite,jboss600 test To run the collection of provider sample tests, you would run mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider test To run a single specific test, you would run mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase test This can be done in debug mode as well mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase -Dmaven.surefire.debug=true test Finally, depending on the Maven version you're using, you might need to set the jbossXYZ.home property: mvn -Ptestsuite,jboss600 -Djboss600.home=/home/user/jboss/build/output/jboss-6.0.0.Final test h3. Working with JBossWS-Native The jbossws native test-suite is a super set of the general JAX-WS test-suite. It tests our native stack, JAX-RPC, the tools layer, etc. This shows how to run the full core test-suite against JBoss-6.0 h4. Ant build cd stack/native/trunk ./build.sh deploy-jboss600 ./build.sh tests-main ./build.sh tests h4. Maven + Ant build When running the testsuite, the Maven build always performs both common and stack specific tests, so nothing different from what's explained above in "Working with the integration layers" is required. h3. Working with JBossWS-CXF The jbossws cxf test-suite is a super set of the general JAX-WS test-suite. It tests the jbossws-cxf integration, JAX-RPC, the tools layer, etc. This shows how to run the full core test-suite against JBoss-6.0 h4. Ant build cd stack/cxf/trunk ./build.sh deploy-jboss600 ./build.sh tests-main ./build.sh tests h4. Maven + Ant build When running the testsuite, the Maven build always performs both common and stack specific tests, so nothing different from what's explained above in "Working with the integration layers" is required. Starting from 3.4.0 just keep in mind that SpringFramework dependencies are not triggered by default anymore. You can add Spring to the testsuite client classpath as well as enable additional tests relying on Spring using the custom "spring" maven profile: mvn -Ptestsuite,jboss600,spring test h3. h3. Working with the Hudson QA environment The Hudson QA environment helps you to test any supported stack against any supported target container. h4. Maven + Ant build The Hudson setup is still based on Ant. You just need to checkout the jbossws-framework and move to the "hudson" directory. cd jbossws/framework/trunk/hudson ant hudson-setup ant hudson-start When you hit http://localhost:8180/hudson http://localhost:8180/hudson you should be able to * log-in * build a target container * run a test-suite against the target container Publicly, Hudson is available at http://jbossws.jboss.org:8180/hudson/ http://jbossws.jboss.org:8180/hudson/ (or http://jbossws.jboss.org:8280/hudson/ http://jbossws.jboss.org:8280/hudson/ during QA release phase) -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-13523] Create a new document in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

13 years, 6 months

1
0
0 / 0

[jBPM Development] - Why is there no implementation for ProcessEnginePlugin from bpm integration?

by Mare Geldenhuys

Mare Geldenhuys [http://community.jboss.org/people/mgeldenhuys] created the discussion "Why is there no implementation for ProcessEnginePlugin from bpm integration?" To view the discussion, visit: http://community.jboss.org/message/610150#610150 -------------------------------------------------------------- Hi, when starting up JBPM, the console on jboss displays the following when starting up the gwt-console-server : org.jboss.bpm.console.server.plugin.PluginMgr] (http-127.0.0.1-8080-2) Unable to load plugin: 'org.jboss.bpm.console.server.plugin.ProcessEnginePlugin' After some investigation, I couldn't find an implementation for the interface in the source code (looked in both 5.0 and 5.1) Am I missing somethng or was this intentional? If so, why is the gwt-console server trying to load the plugin? Thanks, Mare -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610150#610150] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
1
0 / 0

[jBPM Development] - org.jbpm.api.JbpmException: couldn't execute remote command: null org.jbpm.enterprise.internal.ejb.EjbRemoteCommandService.execute

by sunil M

sunil M [http://community.jboss.org/people/suniltatatel] created the discussion "org.jbpm.api.JbpmException: couldn't execute remote command: null org.jbpm.enterprise.internal.ejb.EjbRemoteCommandService.execute" To view the discussion, visit: http://community.jboss.org/message/610990#610990 -------------------------------------------------------------- hi.. I am new to JBPM...using JBPM4.4 and trying to connect to the JBPM4.4 process engine from client app..getting the below error org.jbpm.api.JbpmException: couldn't execute remote command: null org.jbpm.enterprise.internal.ejb.EjbRemoteCommandService.execute(EjbRemoteCommandService.java:71) org.jbpm.pvm.internal.processengine.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:152) org.jbpm.pvm.internal.processengine.ProcessEngineImpl.<init>(ProcessEngineImpl.java:105) org.jbpm.pvm.internal.cfg.ConfigurationImpl.instantiateProcessEngine(ConfigurationImpl.java:100) org.jbpm.pvm.internal.cfg.ConfigurationImpl.buildProcessEngine(ConfigurationImpl.java:92) com.process.actions.IntiateAction.execute(IntiateAction.java:24) org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194) org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) note The full stack trace of the root cause is available in the Apache Tomcat/5.5 logs. attached the jbpm.cfg .xml for client app and default jbpm.cfg .xml process engine app -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610990#610990] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
0
0 / 0

[JBoss AS7 Development] - Re: Non-Java EE (Spring) JPA/Hibernate and native Hibernate applications in AS7

by Scott Marlow

Scott Marlow [http://community.jboss.org/people/smarlow] created the discussion "Re: Non-Java EE (Spring) JPA/Hibernate and native Hibernate applications in AS7" To view the discussion, visit: http://community.jboss.org/message/610542#610542 -------------------------------------------------------------- I would like to keep shipping Hibernate 4 but also want to see the ability to integrate different persistence providers that are tagged with a version identifier. The AS7 javax.persistence.spi.PersistenceProviderResolver should be able to contain multiple instances of the same provider with different version tags. The packaging of the persistence provider should allow for additional integration classes to be specified (e.g. custom classes for scanning a VFS file url for entities or using jandex for faster annotation scanning). A custom persistence.xml "version" property can be introduced to match the persistence providers version tag. If we were to do this via "module" packaging, Hibernate 3 could be resolve via a dropped in Hibernate 3 module. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610542#610542] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

2
2
0 / 0

[JBoss AS7 Development] - Profiles in jboss as7

by Oved O

Oved O [http://community.jboss.org/people/ovedwish] created the discussion "Profiles in jboss as7" To view the discussion, visit: http://community.jboss.org/message/610907#610907 -------------------------------------------------------------- Hey, I worked mostly with jboss eap 5.1, and there I had profiles (default, minimal,all). Is there such a term in jboss as7? Is there a minimal profile as in 5.1? Thank you, Oved -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610907#610907] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
0
0 / 0

[JBoss Portal Development] - Different headers for different pages in portal

by Abhidipta Som

Abhidipta Som [http://community.jboss.org/people/abhidipta_som] created the discussion "Different headers for different pages in portal" To view the discussion, visit: http://community.jboss.org/message/610793#610793 -------------------------------------------------------------- Hi All, I am new to JBOSS portal server. I have got a requirement where different pages of the same portal has different headers(i.e. header.jsp) I have gone through a lot of articles but I didn't get any feasible solution. I have some queries: 1) *Is it possible* for different pages in the same portal to have different headers? 2) If I want to display the logged-in user name in the template jsp, how to I access the api from the jsp? If I create a new jsp, all request attributes are null including +*request.getAttribute("org.jboss.portal.header.USER")*+ Thanks in advance. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610793#610793] Start a new discussion in JBoss Portal Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
0
0 / 0

[jBPM Development] - Not showing processes in jbpm console

by Hanumantharao satuluri

Hanumantharao satuluri [http://community.jboss.org/people/hanu.satuluri] created the discussion "Not showing processes in jbpm console" To view the discussion, visit: http://community.jboss.org/message/610761#610761 -------------------------------------------------------------- Hi Everyone, I am very new to JBPM . I have installed jbpm5.0 full version in my machine. My requirement is to run the jbpm console in Tomcat environment. I have done all the configuration in Tomcat and when I open jbpm console in Tomcat, there is no process is showing in the process overview submenu. The following error is show when I refresh the process overiew org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: Could not initialize stateful knowledge session: Could not initialize class org.hibernate.ejb.Ejb3Configuration org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59 Could anyone please help on this -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610761#610761] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
0
0 / 0

[jBPM Development] - Not showing processes in jbpm cosole

by Hanumantharao satuluri

Hanumantharao satuluri [http://community.jboss.org/people/hanu.satuluri] created the discussion "Not showing processes in jbpm cosole" To view the discussion, visit: http://community.jboss.org/message/610758#610758 -------------------------------------------------------------- Hi Everyone, I am very new to jbpm. I have installed JBPM5.0 full installer in my machine. My requirement is to run jbpm cosole in Tomcat server and deploy the processes in the console. I have confiured the jbpm into Tomcat. When I open the jbpm-console and click on process overview the following error is coming: org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: Could not initialize stateful knowledge session: null org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319) org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230) org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *root cause* java.lang.RuntimeException: Could not initialize stateful knowledge session: null org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:149) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:157) org.jbpm.integration.console.CommandDelegate.<init>(CommandDelegate.java:67) org.jbpm.integration.console.ProcessManagement.<init>(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *root cause* java.lang.ExceptionInInitializerError org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:97) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:157) org.jbpm.integration.console.CommandDelegate.<init>(CommandDelegate.java:67) org.jbpm.integration.console.ProcessManagement.<init>(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *root cause* org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:105) org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:97) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:157) org.jbpm.integration.console.CommandDelegate.<init>(CommandDelegate.java:67) org.jbpm.integration.console.ProcessManagement.<init>(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *root cause* org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416) org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:105) org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:97) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:157) org.jbpm.integration.console.CommandDelegate.<init>(CommandDelegate.java:67) org.jbpm.integration.console.ProcessManagement.<init>(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) *root cause* org.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412) org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272) org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246) org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395) org.hibernate.ejb.Ejb3Configuration.<clinit>(Ejb3Configuration.java:105) org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:124) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) org.jbpm.integration.console.CommandDelegate.newStatefulKnowledgeSession(CommandDelegate.java:97) org.jbpm.integration.console.CommandDelegate.getSession(CommandDelegate.java:157) org.jbpm.integration.console.CommandDelegate.<init>(CommandDelegate.java:67) org.jbpm.integration.console.ProcessManagement.<init>(ProcessManagement.java:35) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:22) org.jbpm.integration.console.ManagementFactory.createProcessManagement(ManagementFactory.java:19) org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessManagement(ProcessMgmtFacade.java:98) org.jboss.bpm.console.server.ProcessMgmtFacade.getDefinitionsJSON(ProcessMgmtFacade.java:122) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117) org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232) org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166) org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59) Could anyone please help on this. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/610758#610758] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2011