[jBPM Development] - How to change the param value dynamically?
by mariaprabudass Edwin
mariaprabudass Edwin [https://community.jboss.org/people/mariaprabudass] created the discussion
"How to change the param value dynamically?"
To view the discussion, visit: https://community.jboss.org/message/649669#649669
--------------------------------------------------------------
Hi all,
I am new for jbpm. I have passed *boolean value* to the variable name "*qcapproval*". I used *constraints* in bpmn diagram, in that if the variable *qcapproval == true* the process end. otherwise (that is *qcapproval == false*) process continue. But I need to change the variable value as *true dynamically*. Because if i set the variable false loop continues. I need to stop the process in the particular stage. So i need to change the variable value as *true dynamically*. Kindly advise me. I have attached my code below.
*Code:-- *
StatefulKnowledgeSession ksession = createKnowledgeSession("Print.bpmn");
Map<String, Object> params = new HashMap<String, Object>();
params.put("qcapproval", false);
TaskService taskService = getTaskService(ksession);
ProcessInstance processInstance = ksession.startProcess("com.tnq.workflow.jobflow.Print.bpmn", params);
assertProcessInstanceActive(processInstance.getId(), ksession);
Thanks for looking into this....
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/649669#649669]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[JBoss Web Development] - Migrating from Weblogic to JBoss
by Sean Smith
Sean Smith [https://community.jboss.org/people/pyroplasm] created the discussion
"Migrating from Weblogic to JBoss"
To view the discussion, visit: https://community.jboss.org/message/715012#715012
--------------------------------------------------------------
Hello,
I am part of a team that is migrating an application from Weblogic 11g to JBoss Enterprise Platform 5.0.1.CR2. I know that part of this is to change the existing weblogic.xml file over to a jboss.xml file. I have seen some things online about using XLST stylesheets to do this, I believe, at runtime but this really isn't an option for me. I'm looking to see if there is either a methodoligy that I need to use when converting it over from JBoss to Weblogic or if there is some kind of tool that I can use that I give some information and it does the conversion or if I need to use something like the XLST but I only need to use it once and it converts my code. Below is my weblogic.xml file. Any help would be appreciated.
[code]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC
"-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
" http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<description>
sensitive
</description>
<!-- Disables session cookies and encoding the session ID in the URL because we're not using sessions -->
<session-descriptor>
<session-param>
<param-name>TimeoutSecs</param-name>
<param-value>120</param-value> <!-- 30 minute timeout -->
</session-param>
<session-param>
<param-name>URLRewritingEnabled</param-name>
<param-value>false</param-value>
</session-param>
<session-param>
<param-name>CookiesEnabled</param-name>
<param-value>false</param-value>
</session-param>
</session-descriptor>
<jsp-descriptor>
<jsp-param>
<param-name>compileFlags</param-name>
<param-value>-g</param-value>
</jsp-param>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<context-root>sensitive</context-root>
</weblogic-web-app>
[/code]
I also have a web.xml file that was told needed to be changed.
[code]
<?xml version="1.0" encoding="UTF-8"?>
<!-- Filename: web.xml -->
<!-- $Header: //VM_Data/IRS_GOV/Source_Code/a/Source_Code/IRS_App/JAVA/sensitive/WebContent/WEB-INF/web.xml-arc 1.15 Aug 18 2010 12:34:24 me $ -->
<!-- $Revision: 1.15 $ -->
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" " http://java.sun.com/dtd/web-app_2_3.dtd http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>Application</display-name>
<context-param>
<param-name>log4jConfigLocation</param-name>
<param-value>classpath:log4j.properties</param-value>
</context-param>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>
classpath:/foundation-core-context.xml,
classpath:/integration-context.xml,
classpath:/integration-core-context.xml,
classpath:/service-context.xml,
classpath:/controller-servlet.xml,
classpath:/controller-support.xml,
classpath:/override-context.xml
</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>log4j</servlet-name>
<servlet-class>sensitive.servlet.Log4jServlet</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/classes/log4j.properties</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<init-param>
<param-name>namespace</param-name>
<param-value>classes/controller-servlet</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet>
<servlet-name>errorHandlerServlet</servlet-name>
<servlet-class>sensitive.servlet.ErrorServlet</servlet-class>
<init-param>
<param-name>errorPage</param-name>
<param-value>/WEB-INF/error.jsp</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>log4j</servlet-name>
<url-pattern>/log4j</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>/list/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>errorHandlerServlet</servlet-name>
<url-pattern>/errorHandlerServlet</url-pattern>
</servlet-mapping>
<!-- The Welcome File List -->
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<error-page>
<error-code>400</error-code>
<location>/WEB-INF/errorPages/400errorPage.jsp</location>
</error-page>
<error-page>
<error-code>403</error-code>
<location>/WEB-INF/errorPages/403errorPage.jsp</location>
</error-page>
<error-page>
<error-code>404</error-code>
<location>/WEB-INF/errorPages/404errorPage.jsp</location>
</error-page>
<error-page>
<error-code>408</error-code>
<location>/WEB-INF/errorPages/408errorPage.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/WEB-INF/errorPages/500errorPage.jsp</location>
</error-page>
<error-page>
<error-code>503</error-code>
<location>/WEB-INF/errorPages/503errorPage.jsp</location>
</error-page>
<error-page>
<error-code>504</error-code>
<location>/WEB-INF/errorPages/504errorPage.jsp</location>
</error-page>
<error-page>
<error-code>505</error-code>
<location>/WEB-INF/errorPages/505errorPage.jsp</location>
</error-page>
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/errorHandlerServlet</location>
</error-page>
<taglib>
<taglib-uri> http://java.sun.com/jstl/core http://java.sun.com/jstl/core</taglib-uri>
<taglib-location>/WEB-INF/tld/c.tld</taglib-location>
</taglib>
</web-app>
[/code]
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/715012#715012]
Start a new discussion in JBoss Web Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[JBoss AS 7 Development] - ClassNotFoundException (org.xml.sax.helpers.DefaultHandler) in a module
by Markus Straub
Markus Straub [https://community.jboss.org/people/markus_s] created the discussion
"ClassNotFoundException (org.xml.sax.helpers.DefaultHandler) in a module"
To view the discussion, visit: https://community.jboss.org/message/714930#714930
--------------------------------------------------------------
Hi,
I am trying to deploy a web application within JBoss AS, where a class in a custom-built library (let's call it mylib.jar) extends org.xml.sax.helpers.DefaultHandler.
As long as mylib.jar is situated in /opt/jboss/standalone/deployments/mywebapp.war/WEB-INF/lib everything works fine.
The problem starts when I want to use mylib.jar as a module, since several of my web applications should use it.
I created a module by putting mylib.jar into /opt/jboss/modules/at/mylib/main. The module.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="at.mylib">
<resources>
<resource-root path="mylib.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
</dependencies>
</module>
Then I use the module by removing mylib.jar from WEB-INF and putting the line "Dependencies: at.mylib" into META-INF/MANIFEST.MF
The module is found and loaded, but classloading of the class which extends DefaultHandler fails because DefaultHandler could not be loaded in the first place.
I wonder how this can happen since it is part of Java6. My guess is that rt.jar (which contains DefaultHandler.class) is not loaded.
However I have no good idea how I should fix this. It would be great if somebody could help me to find a solution. Stacktrace and System Specs are below.
Thanks,
Markus
*Stacktrace:*
11:37:14,628 WARN [org.jboss.modules] (http--127.0.0.1-8080-1) Failed to define class at.trafficstate.provider.its.YTimeseriesReader in Module "at.mylib:main" from local module loader @340d1fa5 (roots: /opt/jboss-as-7.1.0.CR1b/modules): java.lang.LinkageError: Failed to link at/trafficstate/provider/its/YTimeseriesReader (Module "at.mylib:main" from local module loader @340d1fa5 (roots: /opt/jboss-as-7.1.0.CR1b/modules))
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73)
at org.jboss.modules.Module.loadModuleClass(Module.java:505)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
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)
at at.trafficstate.provider.its.XYZRegionRealTimeProvider.updateData(XYZRegionRealTimeProvider.java:147) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.trafficstate.provider.its.XYZRegionRealTimeProvider.<init>(XYZRegionRealTimeProvider.java:50) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.trafficstate.provider.factory.XYZRegionRealTimeProviderFactory.createProvider(XYZRegionRealTimeProviderFactory.java:9) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.trafficstate.provider.factory.AbstractProviderFactory.createProvider(AbstractProviderFactory.java:22) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.trafficstate.TrafficState.addProvider(TrafficState.java:142) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.mylib.util.io.mylibContext.getTrafficStateManager(mylibContext.java:474) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.mylib.weighter.edge.TravelTimeEdgeWeighter.<init>(TravelTimeEdgeWeighter.java:73) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.mylib.weighter.edge.TravelTimeEdgeWeighter.createInstance(TravelTimeEdgeWeighter.java:219) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.mylib.weighter.WeighterFactory.getEdgeWeighter(WeighterFactory.java:66) [mylib.jar:1.0-b314 2012-Feb-07 11:35:49]
at at.mylib.routingservice.empora.RoutingManager.getRoute(RoutingManager.java:91) [classes:]
at at.mylib.routingservice.empora.ws.EmporaRoutingService.getRoute(EmporaRoutingService.java:19) [classes:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:37) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:57) [jboss-as-ejb3-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.jboss.as.webservices.invocation.AbstractInvocationHandlerEJB.invoke(AbstractInvocationHandlerEJB.java:112)
at org.jboss.wsf.stack.cxf.JBossWSInvoker._invokeInternal(JBossWSInvoker.java:169)
at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:117)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_26]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_26]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_26]
at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:206)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91)
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:184)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.0.GA.jar:2.0.0.GA]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.7.Final.jar:]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:151) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.7.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.7.Final.jar:]
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:897) [jbossweb-7.0.7.Final.jar:]
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626) [jbossweb-7.0.7.Final.jar:]
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2033) [jbossweb-7.0.7.Final.jar:]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: java.lang.NoClassDefFoundError: org/xml/sax/helpers/DefaultHandler
at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_26]
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [:1.6.0_26]
at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [:1.6.0_26]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [:1.6.0_26]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391)
... 86 more
Caused by: java.lang.ClassNotFoundException: org.xml.sax.helpers.DefaultHandler from [Module "at.mylib:main" from local module loader @340d1fa5 (roots: /opt/jboss-as-7.1.0.CR1b/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.performLoadClassChecked(ConcurrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 92 more
*OS:* Ubuntu 11.04 (Natty) 64bit
Linux msb 2.6.38-13-generic #53-Ubuntu SMP Mon Nov 28 19:33:45 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
*Java:* java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
*JBoss:* jboss-as-7.1.0.CR1b
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714930#714930]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[JBoss AS 7 Development] - AS7 - RAR deployment issue in build # 548
by Mehboob Alam
Mehboob Alam [https://community.jboss.org/people/bob_alam] created the discussion
"AS7 - RAR deployment issue in build # 548"
To view the discussion, visit: https://community.jboss.org/message/714694#714694
--------------------------------------------------------------
Standalone rar (not inside of an ear) won't deploy. This is happening on build # 548. It used to work. However, the good news is that if the rar was inside an ear, it now deploys successfully and registers the connection factory.
09:51:48,344 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."helloworld.rar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld.rar".PARSE: Failed to process phase PARSE of deployment "helloworld.rar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
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]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: IJ010061: Unexpected element: connection-factories
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:85)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
... 5 more
Caused by: org.jboss.jca.common.metadata.ParserException: IJ010061: Unexpected element: connection-factories
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:123)
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:82)
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:80)
... 6 more
09:51:48,360 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "myapp.ear" was rolled back with no failure message
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714694#714694]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[JBoss AS 7 Development] - AS7 JCA Resource Adapter JNDI Not Binding
by Mehboob Alam
Mehboob Alam [https://community.jboss.org/people/bob_alam] created the discussion
"AS7 JCA Resource Adapter JNDI Not Binding"
To view the discussion, visit: https://community.jboss.org/message/714399#714399
--------------------------------------------------------------
Hi,
I have noticed that if my resource adapter is within a ear, the ear is deployed, but the rar is not deploying correctly. The same rar deploys correctly if it is outside the ear. This is a legacy application that works correctly in AS6/AS61
I added proper declaration for the resource-adapter in standalone-full.xml, e.g.:
<resource-adapter>
<archive>
**myapp*.ear#myrar.rar*
</archive>
<transaction-support>
NoTransaction
</transaction-support>
<connection-definitions>
<connection-definition class-name="com.test.connector.HelloWorldManagedConnectionFactory" jndi-name="java:/HelloWorldConnectionFactory" enabled="true" use-java-context="true" pool-name="HelloWorldConnectionFactory" use-ccm="true">
<pool>
<prefill>
false
</prefill>
<use-strict-min>
false
</use-strict-min>
<flush-strategy>
FailingConnectionOnly
</flush-strategy>
</pool>
<security>
<application/>
</security>
<validation>
<background-validation>
false
</background-validation>
<use-fast-fail>
false
</use-fast-fail>
</validation>
</connection-definition>
</connection-definitions>
</resource-adapter>
However, after the server starts, the archive entry is changes to something like this:
<resource-adapter>
<archive>
*myapp.ear*
</archive>
.....
.....
</resource-adapter>
Obviously this is incorrect.
I experimented and found that if I pulled the rar out of the ear, (using appropriate archive value change for the resource-adapter), then I am able to successfully deploy both the rar and the ear. In that case, I see a message logged like the one below and my application works correctly.
*16:46:02,315 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/HelloWorldConnectionFactory]*
Tried build #524 from Feb3. The error is there as well.
Is this a known issue?
Thanks in advance!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/714399#714399]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 11 months
[JBoss Web Services Development] - JBossWS - Running the test suites
by Alessio Soldano
Alessio Soldano [https://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Running the test suites"
To view the document, visit: https://community.jboss.org/docs/DOC-13523
--------------------------------------------------------------
***
#Working_with_the_integration_layers Working with the integration layers
****
#Ant_build Ant build
****
#Maven__Ant_build_JBossWS_3x Maven + Ant build (JBossWS 3.x)
****
#Maven__Ant_build_JBossWS_4x Maven + Ant build (JBossWS 4.x)
****
#JBossWSCXF_Spring_testsuite JBossWS-CXF Spring testsuite
***
#Working_with_the_Hudson_QA_environment Working with the Hudson QA environment
****
#Maven__Ant_build 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/target/jbossws-bin-dist
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 (JBossWS 3.x)
+*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
Please note that starting from JBossWS 4, the integration testsuites have been moved to the 'integration-test' maven phase. So you need to replace 'test' with 'integration-test' in the mvn commands above.
h4. Maven + Ant build (JBossWS 4.x)
cd stack/cxf/trunk
ant deploy-jboss710
mvn -Pjboss710 -Djboss710.home=<path-to-jboss-710> integration-test
To run the collection of provider sample tests, you would run
mvn -Pjboss710 -Djboss710.home=<path-to-jboss-710> -Dtest=jaxws/samples/provider test integration-test
To run a single specific test, you would run
mvn -Pjboss710 -Djboss710.home=<path-to-jboss-710> -Dtest=jaxws/samples/provider/ProviderPayloadTestCase integration-test
This can be done in debug mode as well
mvn -Pjboss710 -Djboss710.home=<path-to-jboss-710> -Dtest=jaxws/samples/provider/ProviderPayloadTestCase -Dmaven.surefire.debug=true integration-test
h4. JBossWS-CXF Spring testsuite
Starting from jbossws-cxf 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
[https://community.jboss.org/docs/DOC-13523]
Create a new document in JBoss Web Services Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
