[Design of JBoss jBPM] - Re: Register EventListener on JbppmContext
by camunda
Okay, to give you the latest update:
For creating the events I need, I implemented an own LoggingService, which keeps a list of ProcessLog objects internally in memory. When closing the LoggingService, I look through these evens and create the necessary BAM events and send them to my BAM service.
One important issue was, to place the LoggingService BEFORE the PersistenceService, by doing so, the LoggingService can still access the HibernateSession (otherwise it would be closed earlier). This works if the loadForUpate methods where called everywhere correctly :-)
But I discussed that implementation with another guy, and we concluded, that the EventListener still is a valuable Feature. Because if you really want to listen for events, it is the right place. Logs are created much later (e.g. during jbpmContext.close) and have different granularity.
What does others think about that?
For my problem I am happy with the LoggingService, for the other project, they patched jbpm already to include the EventListener. But I think it would make sense, at least for jbpm 4.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191842#4191842
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191842
16 years
[Design of JBoss jBPM] - xsddoc
by tom.baeyens@jboss.com
can someone on linux fiddle around with the xsddoc task ?
in jbpm 4, in api, there is this snippet commented:
<!--
| <plugin>
| <artifactId>maven-antrun-plugin</artifactId>
| <executions>
| <execution>
| <id>generate-jpdlxsd-doc</id>
| <phase>package</phase>
| <goals>
| <goal>run</goal>
| </goals>
| <configuration>
| <tasks>
| <echo message="basedir: ${basedir}" />
| <taskdef name="xsddoc" classname="net.sf.xframe.xsddoc.Task" classpathref="maven.plugin.classpath" />
| <mkdir dir="target/doc/schemadoc" />
| <xsddoc out="${basedir}/target/doc/schemadoc" title="jBPM 4 Schema's" verbose="false">
| <fileset dir="src/main/resources" />
| </xsddoc>
| </tasks>
| </configuration>
| </execution>
| </executions>
| <dependencies>
| <dependency>
| <groupId>xsddoc</groupId>
| <artifactId>xsddoc</artifactId>
| <version>1.0</version>
| </dependency>
| <dependency>
| <groupId>xalan</groupId>
| <artifactId>xalan</artifactId>
| <version>2.7.0</version>
| </dependency>
| </dependencies>
| </plugin>
| -->
If you uncomment it, it works on my windows, but not on linux with java5 for some reason.
It has to do with how maven passes the basedir property to the ant task, i believe.
It's in this hudson run that i got a problem:
http://jbpm.dyndns.org:8180/hudson/job/jBPM4-JDK1.5/9/console
for some reason or another, the basedir seems to be duplicated:
and without the basedir, it doesn't work when this build is being called from the parent project.
it seems a pitty that we can't use this as it works well on windows and i couldn't get this xsddoc to work in any other way. also not the maven integration...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191772#4191772
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191772
16 years