[jBPM Development] - apache commons.io dependency problem in jbpm-console-server
by Peter Courcoux
Peter Courcoux [https://community.jboss.org/people/peter_courcoux] created the discussion
"apache commons.io dependency problem in jbpm-console-server"
To view the discussion, visit: https://community.jboss.org/message/756971#756971
--------------------------------------------------------------
The org.apache.batik.pdf_1.6.0.v201105071520.jar included with the birt report-engine integration appears to include an old version of the classes from commons.io.
As I understand it,to install the report engine, the libraries from reportEngine/lib, including the batik.pdf jar should be copied to WEB-INF/lib, which I have done.
In the jbpm-gwt-shared project the GuvnorConnectionUtils.getProcessSourceContent() method is throwing a NoSuchMethodError at line 212, which is not being caught or logged.
The cause is that method org.apache.commons.io.IOUtils.copy(InputStream, Writer) does not exist. This method was introduced in version 1.1 of commons.io.
Removing the org.apache.batik.pdf_1.6.0.v201105071520.jar, allows the classes in commons.io.1.4.jar to become visible and solves the problem.
I am not familiar with the jboss Modules system. Is there some configuration which can hide these offending classes from other libraries within the same deployment?
I can submit a patch which replaces the catch block at line 214 of GuvnorConnectionUtils to catch a Throwable, so at least the problem is logged if it affects anyone else.
Am I doing somethng daft or missing another obvious solution?
Any pointers to solutions will be much appreciated.
I have asked a question about the inclusion of the commons.io classes in the batik.pdf jar on the eclipse Birt forum.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756971#756971]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month
[JBoss AS 7 Development] - Bom's dependencies not picked up when running test phase in maven
by Dimitris Papangelis
Dimitris Papangelis [https://community.jboss.org/people/papangdim] created the discussion
"Bom's dependencies not picked up when running test phase in maven"
To view the discussion, visit: https://community.jboss.org/message/756792#756792
--------------------------------------------------------------
Hi there,
I have been trying for quite some time now to get jms to work after migrating from as5 to as7. After looking up at the as7 quickstarts (helloworld-jms) i managed to make it work. The fact that i was based on the quickstarts means that i added the bom in my project's pom as well.
The bom looks llike that:
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-jms-client-bom</artifactId>
<version>7.1.1.Final</version>
<type>pom</type>
</dependency>
Everything works fine and my project can build and run with no problem at, but I recently started running the fest GUI tests that I have written and i get a ClassNotFoundException in org.jnp.interfaces.NamingContextFactory. I know that this comes from the quickstart's bom which means that during maven's test phase it doesnt get picked up in order to provide me with the classes that are needed. I (think) i confirmed this by adding jbossall-client as a dependency and that works fine with the tests. I also tried adding <scope>test</scope> in the bom and it doesnt seem to work either.
Any ideas?
thanks D.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756792#756792]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month
[JBoss AS 7 Development] - Error while deploying MDB(EJB2.1) in jboss as 7
by Amol Dongare
Amol Dongare [https://community.jboss.org/people/amol.p.dongare] created the discussion
"Error while deploying MDB(EJB2.1) in jboss as 7"
To view the discussion, visit: https://community.jboss.org/message/747697#747697
--------------------------------------------------------------
I am getting following error while deploying MDB in JBOSS7
my ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
" http://java.sun.com/dtd/ejb-jar_2_0.dtd http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>MDB</ejb-name>
<ejb-class>com.example.GreetingMessageDriverBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
And getting following Exception
4:44:59,884 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled ba
k. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"mdb.jar\".component.TextMDB.START" => "o
g.jboss.msc.service.StartException in service jboss.deployment.unit.\"mdb.jar\".component.TextMDB.START: Failed to start service"}}}}
4:50:30,020 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "mdb1.jar"
4:50:30,054 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."mdb1.jar".PARSE: org
jboss.msc.service.StartException in service jboss.deployment.unit."mdb1.jar".PARSE: Failed to process phase PARSE of deployment "mdb1.jar"
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]
aused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Exception while parsing ejb-jar.xml: /D:/JBoss/jboss-as-7.1.1.Final/bin/c
ntent/mdb1.jar/META-INF/ejb-jar.xml
at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:248)
at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:118)
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
aused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,7]
*essage: Unexpected element 'message-driven-destination' encountered*
at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:108)
at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElement(AbstractMetaDataParser.java:53)
at org.jboss.metadata.ejb.parser.spec.AbstractNamedMetaDataWithDescriptionGroupParser.processElement(AbstractNamedMetaDataWithDescriptionGroup
arser.java:66)
at org.jboss.metadata.ejb.parser.spec.AbstractEnterpriseBeanMetaDataParser.processElement(AbstractEnterpriseBeanMetaDataParser.java:84)
at org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(AbstractMessageDrivenBeanParser.java:93)
at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:76)
at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:36)
at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65)
at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.parse(MessageDrivenBean31Parser.java:43)
at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:98)
at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:38)
at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65)
at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:74)
at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:66)
at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:111)
at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:38)
at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65)
at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:109)
at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:53)
at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:245)
... 7 more
4:50:30,115 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "mdb1.jar" was rolled back with failure mess
ge {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"mdb1.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment
unit.\"mdb1.jar\".PARSE: Failed to process phase PARSE of deployment \"mdb1.jar\""}}
4:50:30,119 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment mdb1.jar in 4ms
4:50:30,122 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
BAS014777: Services which failed to start: service jboss.deployment.unit."mdb1.jar".PARSE: org.jboss.msc.service.StartException in service jbo
s.deployment.unit."mdb1.jar".PARSE: Failed to process phase PARSE of deployment "mdb1.jar"
4:50:30,128 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled ba
k. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"mdb1.jar\".PARSE" => "org.jboss.msc.serv
ce.StartException in service jboss.deployment.unit.\"mdb1.jar\".PARSE: Failed to process phase PARSE of deployment \"mdb1.jar\""}}}}
Your help is highly anticipated.
-AMol
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747697#747697]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month
[JBoss AS 7 Development] - calling ejb bean in a jar from another ejb bean in another jar in Jboss 7.1.1
by Bijoy James
Bijoy James [https://community.jboss.org/people/bijoyjp] created the discussion
"calling ejb bean in a jar from another ejb bean in another jar in Jboss 7.1.1"
To view the discussion, visit: https://community.jboss.org/message/756053#756053
--------------------------------------------------------------
Am using JBoss 7.1.1 Final. i have a Client application and 2 ejb bean jar files names as Jar A and Jar B.
I want to call bean method in the Jar B from Jar A. I am getting the object of the looking bean but not able to access the create () method.
Below code am using to get the second bean object
Properties env = *new* Properties ();
env.put("java.naming.factory.initial", "org.jboss.as.naming.InitialContextFactory");
// other than this is not working for me in inside jar
// In the Client main application am using below property
// objProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.+PROVIDER_URL+, "remote://localhost:4447");
env.put("jboss.naming.client.ejb.context", *true*);
env.put(Context.+URL_PKG_PREFIXES+, "org.jboss.ejb.client.naming");
initContext = *new* InitialContext(env);
Object obj_Visualization = initContext.lookup("java:jboss/exported/FMS_Entity/VisualHome!HomeInterfaces.VisualHome");
// If am using lookup("FMS_Entity/VisualHome!HomeInterfaces.VisualHome"); am getting exception
System.out.println("obj_Visualization: "+obj_Visualization);
obj_Visualization_Home = (VisualHome) PortableRemoteObject.narrow(obj_Visualization, VisualHome.class);
obj_Visualization_Home.create();
The Sysop is printing as
obj_Visualization: Proxy for remote EJB EJBHomeLocator{appName='', moduleName='FMS_Entity', distinctName='', beanName='VisualHome', view='interface HomeInterfaces.VisualHome'}
Exception in thread "Thread-79" java.lang.NoClassDefFoundError: HomeInterfaces/VisualHome
Caused by: java.lang.ClassNotFoundException: HomeInterfaces.VisualHome from [Module "deployment.JarA.jar:main" from Service Module Loader]
Am getting the object but not able to convert object to home interface object.
Please help me to solve this issue.
Advance thanks for your valuable help.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/756053#756053]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month