September 2008 - jboss-dev-forums

[Design of JBoss jBPM] - Re: jBPM project structure and direction

by thomas.diesler＠jboss.com

Thanks Ronald for your feedback. Could you please work with somebody who has access to these resources to get the individual issues resolved. Unfortunately, not for every item above I know what you talking about. Maybe Tom is you best contact - he should have all the access required. I'll assign this issues https://jira.jboss.org/jira/browse/JBPM-1760 to him and sak him to work with you to get it resolved. cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179001#4179001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179001

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - community branch

by tom.baeyens＠jboss.com

when jbpm 4 goes GA, i think we should do similar as the SEAM guys: create a community branch. that allows for an easy of contributing and we can then look if features get completed (with test cases and docs). we can decide to lend a hand if we want but that should not be treated as a given. as long as the feature is not accepted by the team, it only stays in the community branch and doesn't make it into the next GA release. It's probably too early to think about this but i wanted to share this thought as i just saw the seam community branch and i think it is a good idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179000#4179000 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179000

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by jbarrez

Tom, that is a very good idea! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178999#4178999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178999

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Pass process instance key to sub process

by tom.baeyens＠jboss.com

this is a good addition. but keep in mind that just posting the code is not enough. also the XSD need to be updated, test cases need to be created for each feature and the documentation needs to be updated. keep that in mind as we will not be able to do that work for this contribution. without those additional elements we cannot add it to the codebase. i just saw that SEAM has a community branch. maybe we should do something similar. a branch where community people can commit all kinds of stuff. then if it is considered ready, it can be merged into trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178996#4178996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178996

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM project structure and direction

by kukeltje

Thomas, Kudos for al the great work. We've certainly come a long way which is largly because of your behind the scenes work. Although behind the scenes... I remeber you migrating cvs to svn while attending presentations in Dublin. The 'notebook' was for a brief period of time a 'laptop' again :-) I still think that we ar not completely there yet. There are multiple broken links in the jBPM site, among which are: - the wiki link on the jpdl subproject site is incorrect - the svn link on the pvm sources page is invalid - the jira link on the pvm page is invalid - the about jBPM link in the new wiki is invalid - in two places there are links/references to http://www.jboss.org/jbossjbpm/jbpm_demo/ which does not exist - the reference to the jBPM BPEL wiki from the jBPM BPEL pages leads to a non-existent page (http://wiki.jboss.org/wiki/JbpmBpel) - the jBPM BPEL sources page does not contain the correct information I a generic 'update' the site issue in jira and assigned it to 3.3.0 GA (might not be according the freeze 'rules', but I think it is needed and does not conflict with anything) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178993#4178993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178993

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by alessio.soldano＠jboss.com

"heiko.braun(a)jboss.com" wrote : I could as well imagine that the runtime dependencies (tomcat) cause problems when moving that stuff. I.e. when the WS deployer and runtime live under a different scope then the tomcat runtime you just move the problem around. You know what I mean? | I think so; I guess you mean what I wrote at the beginning of the thread, i.e. we rely upon the generated webapp being deployed and started in tomcat, but that can only happen once the tomcat runtime is started too. Otherwise we don't have the right runtime classloader for JSE endpoints. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178991#4178991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178991

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM project structure and direction

by thomas.diesler＠jboss.com

Hi Joram, part of how we make sure to achieve our goals is good usage of JIRA. For every given 8 week release cycle, we have JIRa freeze after 2 weeks and code freeze after 6 weeks. The remaining 2 weeks is for QA and documentation. In JIRA you should see reliable release dates associated with a given version and details of what remains to do be done is in the JIRA road map. i.e. for jbpm-3.3.0.GA there are now 58 issues that remain to get resolved https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hi... So in a way, the above post is rather conservative and uses a lot of words to say: "Let's get these 58 issues resolved in time" ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178989#4178989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178989

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by heiko.braun＠jboss.com

I could as well imagine that the runtime dependencies (tomcat) cause problems when moving that stuff. I.e. when the WS deployer and runtime live under a different scope then the tomcat runtime you just move the problem around. You know what I mean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178987#4178987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178987

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by alessio.soldano＠jboss.com

"heiko.braun(a)jboss.com" wrote : anonymous wrote : | | having everything we need for deployment in server//deployers. | | | | Hm, I don't know. Guess this is something you need to try. If I remember correctly the main reason for having it in 'deploy' is that you can remove/change it, whereas 'deployers' is more bare bone AS stuff that people shouldn't mess with. | OK, actually I suspected that was somehow related to the stacks switch (having everything stack specific in 'deploy') View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178986#4178986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178986

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM project structure and direction

by jbarrez

Ambitious writing! I'm looking forward to 1 november! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178985#4178985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178985

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2008