June 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: Hudson now integral part of jBPM3 codebase

by jbarrez

This is great news Thomas! I've been a big Hudson fan for quite some time now and I can only applaud this effort! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160873#4160873 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160873

15 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Hudson now integral part of jBPM3 codebase

by thomas.diesler＠jboss.com

In order to reproduce the QA environment that was used for a given release, it must be an integral part of the release. This has now been done and is documented here http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingFromSource#S... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160863#4160863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160863

15 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM3 switched to maven

by kukeltje

cool... kudos... if someone could place 3.2.3 in http://repository.jboss.com/maven2/org/jbpm/jbpm-jpdl/ that would be even better ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160845#4160845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160845

15 years, 11 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, 11 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, 11 months

1
0
0 / 0

[Design of Security on JBoss] - Re: GSSAPI/Negotiate

by darran.lofthouse＠jboss.com

For SPNEGO for web application please see the following post for information on the JBoss Negotiation project: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137786 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160805#4160805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160805

15 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS HDScanner test

by dimitris＠jboss.org

I've expressed my opinion before: just copy the library that's about to be locked in server/xxx/tmp/deploy and access it from there. We have been doing this all along, it may not be optimal, but it works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160800#4160800 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160800

15 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS HDScanner test

by alesj

I don't see that (reaper) as a trick. It can be called pre-mature optimization, and in our case a good one, in more ways: 1) exposed new issues 2) removed locking 3) does fair optimization How safe the solution is, only good tests can show. ;-) And we're making sure every issue we encounter is put in VFS's tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160797#4160797 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160797

15 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS HDScanner test

by sacha.labourey＠jboss.com

so you are saying that we currently have a safe solution (not relying on tricks) for all OSes? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160795#4160795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160795

15 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS HDScanner test

by alesj

"sacha.labourey(a)jboss.com" wrote : | For me, using things like "5 seconds timers" are not synonym with "make it work" Probably because you didn't follow all previous discussions on Winz locking issues. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160792#4160792 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160792

15 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008