June 2008 - jbpm-dev - Jboss List Archives

by Thomas Diesler

Folks, here is the entry point for API discussion on the forum http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160822#4160822 cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Defining a public API for jBPM (Repost)

by thomas.diesler＠jboss.com

The situation with jbpm-3.2.3.GA and below is that there is no stable public API defined for it. As a result, application code depends on implementation detail that might change without prior notice between the versions. To fix this we are going to define a BPM API which is going to bee the standard of how you work with BPM in JBoss. http://jbws.dyndns.org/jbpmwiki/index.php?title=JBPM3-Public-API #1 What does the API cover? The API is going to cover all valid use cases we know of. To monitor progress and to add your requirements you can go to http://jira.jboss.org/jira/browse/JBPM-1250 #2 What is expected to be stable, what is not? Application code that uses the API will not be effected by jBPM updates. Minor versions of the API are backward compatible. The API has support for a number of process descriptor formats, which are also backward compatible between minor versions. Code that has dependencies on jBPM implementation classes might break. We do however not intend to change the jBPM3 code base (unless necessary) until we reach API completeness. Database layout is considered implementation detail that might change between minor versions. #3 How is the correctness of the API verified? We ship a set of samples that are based on the API. Functionality that is available through the API is covered by a sample, documented in the wiki and integrated in automated testing. We verify that all samples run as expected in all supported target containers with all supported JDKs. In parallel we work on jBPM4 (a.k.a. the Process Virtual Machine). For every API construct there must be a mapping against the jBPM3 and the jBPM4 code base. Hence, the jBPM4 code base goes lock-step with jBPM3 in terms what is provided through the API. As a result, users can switch to jBPM4 when we reach API completeness with their application code unaffected. #4 What are the supported target containers? We support the lasts three releases of the JBossAS and Apache Tomcat in a given version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160822#4160822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160822

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Defining a public API for jBPM

by thomas.diesler＠jboss.com

The situation with jbpm-3.2.3.GA and below is that there is no stable public API defined for it. As a result, application code depends on implementation detail that might change without prior notice between the versions. To fix this we are going to define a BPM API which is going to bee the standard of how you work with BPM in JBoss. http://jbws.dyndns.org/jbpmwiki/index.php?title=JBPM3-Public-API #1 What does the API cover? The API is going to cover all valid use cases we know of. To monitor progress and to add your requirements you can go to http://jira.jboss.org/jira/browse/JBPM-1250 #2 What is expected to be stable, what is not? Application code that uses the API will not be effected by jBPM updates. Minor versions of the API are backward compatible. The API has support for a number of process descriptor formats, which are also backward compatible between minor versions. Code that has dependencies on jBPM implementation classes might break. We do however not to intend to change the jBPM3 code base (unless necessary) until we reach API completeness. Database layout is considered implementation detail that might change between minor versions. #3 How is the correctness of the API verified? We ship a set of samples that are based on the API. Functionality that is available through the API is covered by a sample, documented in the wiki and integrated in automated testing. We verify that all samples run as expected in all supported target containers with all supported JDKs. In parallel we work on jBPM4 (a.k.a. the Process Virtual Machine). For every API construct there must be a mapping against the jBPM3 and the jBPM4 code base. Hence, the jBPM4 code base goes lock-step with jBPM3 in terms what is provided through the API. As a result, users can switch to jBPM4 when we reach API completeness with their application code unaffected. #4 What are the supported target containers? We support the lasts three releases of the JBossAS and Apache Tomcat in a given version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160822#4160822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160822

15 years, 10 months

1
0
0 / 0

community instruments

by Tom Baeyens

i have created http://jira.jboss.com/jira/browse/JBPM-1284 we need to sort out what mailing lists, forum, wiki to use for what purpose and communicate that clearly to our community. -- regards, tom.

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jPDL 4 early feedback

by tom.baeyens＠jboss.com

Thanks for pointing that out, Alejandro. Not all of it was clear to me so that proves my point that people should be able to use it without messing with namespaces :-) feature http://apache.org/xml/features/validation/dynamic is not supported in suns JDK 5 Dom parser http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6399139 anonymous wrote : javax.xml.parsers.DocumentBuilderFactory.setFeature( | "http:// customer .org/xml/features/validation/dynamic", true); | | causes the following exception at runtime: | | javax.xml.parsers.ParserConfigurationException: | jaxp_feature_not_supported: Feature | "http:// customer .org/xml/features/validation/dynamic" is not supported. | | ... | | This is fixed in JAXP1.4/JDK6 | Posted Date : 2007-04-03 20:23:47.0 | The only way I got around it was the following: Use a SAX parser. The JDK 5 sax parser supports that feature. Then I 'borrowed' a DOMBuilder from ODE that implements ContentHandler and builds up a DOM (in the meantime it adds the line number information as attributes) Not sure if this is a practical solution going forward. I also wondered if it was necessary. Cause I found out that I was in fact NOT using a validating parser all the time. Our parser that walks the DOM generates most problems anyway. And people will author the process in an XML editor that still *does* support the validation. So the way forward, I think is this: 1) We just use the plain DOM parser when walking the DOM and building the process object model. This does not do any validation 2) We have a list of deployers that is processing a deployment. So we can offer a separate validation deployer step that is configurable. If people use this, they will parse the process 2 times. I don't think that is a big deal. 3) We make the parser that builds up the object model from the DOM configurable. So that users that are using JDK 6 can activate schema validation in the DOM parse if they want to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160757#4160757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160757

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM3 status after switch to maven

by thomas.diesler＠jboss.com

Yes you can. Snapshots can already be consumed from http://snapshots.jboss.org/maven2/org/jboss/jbpm/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160745#4160745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160745

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Expression Evaluation in ActionHandler Properties

by thomas.diesler＠jboss.com

All BPM functionality will eventually have to go through the public API. If this is needed please add it to http://jira.jboss.com/jira/browse/JBPM-1250 with a reference to this forum thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160742#4160742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160742

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Expression Evaluation in ActionHandler Properties

by alex.guizar＠jboss.com

I find this feature quite useful. It makes data extraction and manipulation very transparent. Perhaps we could add it as early as jPDL 3.3? The challenge would be to pass the ExecutionContext all the way down to Instantiator.instantiate(). This requires changing the signature of a number of methods, but other than that, the coding seems straightforward. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160711#4160711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160711

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Please subscribe to jbpm-dev@lists.jboss.org

by alex.guizar＠jboss.com

I'd say forum mostly. From time to time one wants to communicate things that may not quite belong in the forum, like: * check out this jbpm-related article (url of the article here) * last month we broke the download record, way to go! * some note related to partners/competitors although some or all of the above could probably go to the forum as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160705#4160705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160705

15 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jPDL 4 early feedback

by alex.guizar＠jboss.com

The standard JAXP attribute http://java.sun.com/xml/jaxp/properties/schemaSource lets you specify schemata to be considered while parsing XML, without entering in the whole catalog stuff. Likewise, the Xerces attribute http://apache.org/xml/features/validation/dynamic tells the parser to validate the document only if a schema is specified. Together, these two attributes allow the parser to work offline and validate only those elements whose schema is available. Working without namespaces is a matter of setting either the default namespace or the xsi:noNamespaceSchemaLocation attribute right. Should not be an obstacle to a solution based on namespaces. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160701#4160701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160701

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev June 2008