[Design of JBoss ESB] - Barriers inhibiting tight JBPM integration
by bill.burke@jboss.com
Here's what I can think of that are barriers to tight JBPM integration.
* JBPM Designer doesn't support pluggable action/node types (JBPM core does through node.types.xml). I know nothing about eclipse or how hard this would be.
* JBPM nodes/actions don't support lifecycle. We need start/stop for both nodes and actions. This may be solvable by MCizing/beanitizing the JBPM object model and rewriting the JBPM XML parser so that it creates MC bean metadata.
* Different Message interfaces. ESB has org.jboss.soa.esb.Message. JBPM has Token. Both have different ways at getting at metadata and conversational data. I think we can solve this problem with pluggable node/action types that JBPM core provides (so long as the designer supports it) as well as using Seam bijection. If all our ESB actions are written in terms of Seam bijection, then maybe we can plug/play with JBPM.
The end goal of all of this is to be able to blur ESB, JBPM, and Web flow so that ESB actions and glue can be used anywhere within a business process or webflow. Vice versa too. ESB can embed workflow within its definitions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038686#4038686
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038686
18 years, 11 months
[Design of JBoss Build System] - Maven project naming conventions
by pgier
Looking at the snapshots repository, I can imagine the root jboss folder
http://snapshots.jboss.org/maven2/jboss getting large very quickly. Possibly to the point where it is difficult to navigate.
Would it be beneficial to change the naming conventions to group smaller projects together similar to their structure in svn?
For example, instead of the current flat structure common could be grouped like this within the jboss directory:
| /common
| /common/jboss-common-core
| /common/jboss-common-logging-jdk
| /common/jboss-common-logging-log4j
| /common/jboss-common-logging-spi
| /common/jboss-common-xb
|
This way the actual artifact names would still be unique as long as we keep the path in the artifact name.
The javaee project could have a structure like this:
| /javaee/jboss-javaee-ejb-api
| /javaee/jboss-javaee-jacc-api
| /javaee/jboss-javaee-jad-api
| etc...
|
This structure would map a little better to our svn structure, and I think it would be a little easier to navigate.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038634#4038634
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038634
18 years, 11 months