June 2009 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: Why is the console a different repos

by heiko.braun＠jboss.com

anonymous wrote : | generic will always limit our ability to make progress. | haha, hence the PVM in the first place, right? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239289#4239289 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239289

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Why is the console a different repos

by heiko.braun＠jboss.com

anonymous wrote : | i don't think we should be sharing our console. | tom, that's childish. it's both open source projects, run by the same company. and most importantly: both projects expose the same management requirements. we didn't put any effort in making it available to drools flow. although it was designed to allow for different engines in the first place, kris did the adoption on his own. IMO it's a good thing for the console, because we share QA and verification of requirements. For users that are unaffected by the "drools vs. jbpm" discussion, it's definitely a benefit to have a similar management console. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239288#4239288 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239288

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Why is the console a different repos

by tom.baeyens＠jboss.com

generic will always limit our ability to make progress. and of course it always costs more effort to have make things pluggable and generic. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239285#4239285 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239285

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Why is the console a different repos

by camunda

For me the important issue is, that being generic doesn't slow down the development of the console and features required for jbpm. Or make it harder to use or understand (like levels of indirection tend to introduce). I think, the most important goal is a really useful, cool jbpm console, like from professionell (means expensive) bpm engines. Since the web console is one of the first things you see of the product... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239284#4239284 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239284

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by heiko.braun＠jboss.com

A while ago I've commited a change to the samples that created .bar archives and deployed them through the deployer. something like this would have caught the problems in hudson already. Unfortunately you reverted that change. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239283#4239283 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239283

15 years, 8 months

1
0
0 / 0

Reporting in console

by Bernd Rücker

Hi Heiko. Just a quick question, maybe I am too blind again. But my console doesnt show the reports. What do I have to do to see them? Or is that not included in CR1? If not, is there a release that I can use? Task-Forms worked for me today :-) Cheers Bernd

15 years, 8 months

2
2
0 / 0

[Design of JBoss jBPM] - Re: Why is the console a different repos

by tom.baeyens＠jboss.com

given that they want to compete, i don't think we should be sharing our console. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239275#4239275 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239275

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Transaction interceptor changes

by tom.baeyens＠jboss.com

"heiko.braun(a)jboss.com" wrote : @Tom: Btw, if you would have kept the integration tests I did provide a while ago, this would have occurred in the nightly QA. So I'd say the current integration tests are insufficient. which ones are you referring to ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239274#4239274 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239274

15 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: EJB 2.1 Beans in jbpm 4?

by tom.baeyens＠jboss.com

lazy fetched relations are indeed not exposed in the objects that are returned from the service methods. this is to prevent lazy initialization exceptions. but commands are not the solution. adding a findProcessInstanceByTask(long taskDbid) on the TaskService is the way to go. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239273#4239273 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4239273

15 years, 8 months

1
0
0 / 0

Build failed in Hudson: jbpm4-base » java15_default,linux #323

by jboss-qa-internal＠redhat.com

See http://hudson.qa.jboss.com/hudson/job/jbpm4-base/./jdk=java15_default,lab... ------------------------------------------ started Building remotely on dsp-sllxmm2-rhel4-vm Updating https://svn.jboss.org/repos/jbpm/jbpm4/trunk ERROR: Failed to update https://svn.jboss.org/repos/jbpm/jbpm4/trunk org.tmatesoft.svn.core.SVNException: svn: Cannot write entries file 'http://hudson.qa.jboss.com/hudson/job/jbpm4-base/./jdk=java15_default,lab...' : No space left on device at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:595) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:257) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:245) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:258) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1212) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:1078) at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:449) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:394) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:210) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:464) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:435) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1252) at hudson.remoting.UserRequest.perform(UserRequest.java:92) at hudson.remoting.UserRequest.perform(UserRequest.java:46) at hudson.remoting.Request$2.run(Request.java:236) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Recording test results

15 years, 8 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev June 2009