Re: [jboss-user] [jBPM] - jPDL vs. another process definition language
by Sameeh Harfoush
Sameeh Harfoush [http://community.jboss.org/people/sameeh.harfoush] replied to the discussion
"jPDL vs. another process definition language"
To view the discussion, visit: http://community.jboss.org/message/533483#533483
--------------------------------------------------------------
Hello,
I have been reading JPDL documentation and realized that we can add our custom implantation java classes to handle workflows according to some business requirements
We achieve such customization by implementing
* Custom actions by implanting *ActionHandler* interface
* Decision handlers by implementing *DecisionHandler* interface
* Task assignment handlers by extending *AssignmentHandler* interface
* Event listeners by extending *EventListener* interface
* Custom external activity behavior by extending *ExternalActivityBehaviour* interface
* User defined java classes and scripts by using java and script JPDL tags
This can save lots of time and effort to develop a definition language and parser
I attached a file, that I got from JBPM documentationm, that contains examples on how to use the above listed handlers
1. So can we use the above interfaces and implement them to have classes that behave according to our business needs?
2. Is there a limitation to what extent we can control JPDL actions, decision, tasks, events, and activities behavior ?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533483#533483]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months
[jBPM] - JBPM with Tomcat
by Karthikeyan Mohan
Karthikeyan Mohan [http://community.jboss.org/people/kmsk_1318] created the discussion
"JBPM with Tomcat"
To view the discussion, visit: http://community.jboss.org/message/533478#533478
--------------------------------------------------------------
Hai,
I am creating a workflow sample application using JBPM4.3,Spring 2.5,Hibernate 3 and Tomcat 5.5. When i deployed my application, i am getting a startup error saying,
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/WorkflowExample-data.xml]: Invocation of init method failed; nested exception is org.hibernate.InvalidMappingException: Could not parse mapping document from resource jbpm.identity.hbm.xml
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
... 22 more
Caused by: org.hibernate.InvalidMappingException: Could not parse mapping document from resource jbpm.identity.hbm.xml
at org.hibernate.cfg.Configuration.addResource(Configuration.java:602)
at org.hibernate.cfg.Configuration.parseMappingElement(Configuration.java:1621)
at org.hibernate.cfg.Configuration.parseSessionFactory(Configuration.java:1589)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1568)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1542)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1477)
at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:603)
at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:211)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257)
... 29 more
Caused by: org.hibernate.InvalidMappingException: Could not parse mapping document from input stream
at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:541)
at org.hibernate.cfg.Configuration.addResource(Configuration.java:599)
... 38 more
Caused by: org.dom4j.DocumentException: null Nested exception: null
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:532)
... 39 more
When i tried all the test case given, it works fine in standalone. I really don't know why this exception rise.
Some of the details for your reference.
in WEB-INF/lib
|
|---jbpm.jar
|---hibernate3.jar
|---spring.jar
|---..
and my WorkflowSample-data.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="sessionFactory" singleton="false">
<property name="configLocation" value="classpath:jbpm.hibernate.cfg.xml" />
<property name="dataSource" ref="dataSource" />
</bean>
<bean id="transactionManager" singleton="false">
<property name="sessionFactory" ref="sessionFactory" />
<property name="dataSource" ref="dataSource" />
</bean>
<bean id="dataSource">
<property name="driverClassName" value="com.mysql.jdbc.Driver" />
<property name="url" value="jdbc:mysql://localhost:3306/jbpmdb" />
<property name="username" value="root" />
<property name="password" value="java" />
</bean>
</beans>
WorkflowSample-service.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="springHelper" class="org.jbpm.pvm.internal.processengine.SpringHelper"/>
<bean id="processEngine" factory-bean="springHelper" factory-method="createProcessEngine" />
</beans>
I have also attached configuration files for your reference
Please guide me if anything is wrong here.
Thanks in advance,
Karthikeyan.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533478#533478]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months
Re: [jboss-user] [jBPM] - jPDL vs. another process definition language
by Rudolf Michael
Rudolf Michael [http://community.jboss.org/people/ruds] replied to the discussion
"jPDL vs. another process definition language"
To view the discussion, visit: http://community.jboss.org/message/533475#533475
--------------------------------------------------------------
well i have been reading the docs since 2 days now and i can say that i have an 80% clear view on how jBPM works.
The engine is designed to support multiple DSL, so this is good. and i have also played around with the tutorial in Chapter 3.
I am new to this kind of development and i can see that sooner or later people will have the option to write a program/application using Workflows as the logic says everything can be turned into a workflow.
I am working with a team where one of the guys suggested to have the following architecture:
http://community.jboss.org/servlet/JiveServlet/showImage/2390/strcuture.png http://community.jboss.org/servlet/JiveServlet/downloadImage/2390/272-600...
as you can see in the above picture, we are building a layer on top of PVM called SMD; all of our classes will extends the jPDL ones and add the extra methods/tags/whatever needed in order to have our own Process Definition Language.
the bcdl, brdl, bwdl are workflows definition that will extend the SMD structure but everyone has its own xsd schema.
For me i do see it as re-inventing the wheel; i just can't convince that guy that there's no need for that, he keeps on saying the following:
As we discuss before, we need to change the XML format from standard SMDL format
To the SMDL format (the SMDL format consist to define the activity under the step tag different from JPDL format).
In JPDL, we have just the custom tag that we can customize our step/activities.
So he wants a new language bc the custom tags will make the graph messy? or will be too much complicated/complex..therefore he decided to write his own tag definition but with extending 90% of it from jPDL
The other concern that i have is that we will be building our own graph designer using flex. so this might lead us to have our own DSL.
so i am still kinda lost in here and i thought of sharing this with you guys in case someone is interested to give feedback/comments
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533475#533475]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months
Re: [jboss-user] [EJB 3.0 Development] - Fixing the EJB3 testsuite...
by Carlo de Wolf
Carlo de Wolf [http://community.jboss.org/people/wolfc] replied to the discussion
"Fixing the EJB3 testsuite..."
To view the discussion, visit: http://community.jboss.org/message/533441#533441
--------------------------------------------------------------
I've applied the patch with a minor modification. http://fisheye.jboss.org/changelog/JBossAS/?cs=102770 Rev 102770 can serve as a template to fix the other tests.
Commits should go under: http://https://jira.jboss.org/jira/browse/EJBTHREE-2057 EJBTHREE-2057
Note that I get:
javax.jms.JMSException: Failed to initialise session factory
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:1043)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:790)
at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:572)
at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:602)
at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:116)
at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:111)
at org.jboss.ejb3.mdb.ProducerManagerImpl.connect(ProducerManagerImpl.java:221)
at org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase.testMixedConsumer(InterceptorsTestCase.java:610)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
Caused by: HornetQException[errorCode=0 message=Failed to initialise session factory]
Caused by: java.lang.IllegalArgumentException: Error instantiating connector factory "org.hornetq.integration.transports.netty.NettyConnectorFactory"
at org.hornetq.core.client.impl.FailoverManagerImpl.instantiateConnectorFactory(FailoverManagerImpl.java:1016)
at org.hornetq.core.client.impl.FailoverManagerImpl.<init>(FailoverManagerImpl.java:228)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.initialise(ClientSessionFactoryImpl.java:237)
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:1039)
Caused by: java.lang.ClassNotFoundException: org.hornetq.integration.transports.netty.NettyConnectorFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at org.hornetq.core.client.impl.FailoverManagerImpl.instantiateConnectorFactory(FailoverManagerImpl.java:1011)
I guess the client side classes of HornetQ are not yet available in $JBOSS_HOME/client (and jbossall-client.jar Class-Path).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/533441#533441]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 3 months
