March 2009 - jbpm-dev - Jboss List Archives

[Design of JBoss jBPM] - Re: jBPM 4 Email Question

by tom.baeyens＠jboss.com

maybe alejandro is going to look at it next iteration. the only update we plan is to replace our own templating with templating based on jsr223 scripting. would it be something you're interested in contributing that migration ? that would be really helpfull to the project. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222450#4222450 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222450

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - jBPM 4 Email Question

by bradsdavis

Who is implementing the email functionality for jBPM 4? Has it been started? Thanks, Brad View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222419#4222419 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222419

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Deprecated JbpmContext.getCurrentJbpmContext

by heiko.braun＠jboss.com

You seem to be be looking at the jbpm3 codebase quiet thoroughly. Since that's mostly legacy and most efforts go into jbpm4, why don't you move to 4 right away. Feedback like this on new codebase would be highly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222228#4222228 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222228

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - running the test suite on spring

by tom.baeyens＠jboss.com

2 parts of the puzzle are already figured out: 1) Configuration delegates to a subclass internally. So new Configuration("spring") creates and delegates to a SpringConfiguration, which can build a specialized SpringProcessEngine 2) Maven properties are passed as system properties. So public class PropertyTest extends TestCase { | | public void testProperty() { | System.out.println(System.getProperty("jbpm.cfg.type")); | } | | } | can be run like this C:\wsjbpm4\jbpm4\modules\test-pojo>mvn -Dtest=PropertyTest -Djbpm.cfg.type=spring clean test | | ... | | Running org.jbpm.test.activities.PropertyTest | spring | Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec | | Results : | | Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 | | [INFO] ------------------------------------------------------------------------ | [INFO] BUILD SUCCESSFUL | [INFO] ------------------------------------------------------------------------ | ... | what else do we need ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222216#4222216 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222216

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Deprecated JbpmContext.getCurrentJbpmContext

by tom.baeyens＠jboss.com

we don't have plans to remove things from jbpm 3 at this point. we only do stabilization meaning bug fixing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222210#4222210 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222210

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Deprecated JbpmContext.getCurrentJbpmContext

by bradsdavis

I noticed that JbpmContext.getCurrentJbpmContext is deprecated. However, it is used throughout the jBPM codebase. Does this need to be cleaned up? There is more functionality around the JbpmContext.getCurrentJbpmContext than within the JbpmConfiguration.getCurrentJbpmContext. Because of this, it is not equivalent to use one versus the other. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222121#4222121 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222121

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Debug Logging

by bradsdavis

David, I am not trying to argue about it. I think this is a genuine place we could improve efficiency. anonymous wrote : | Not Apache clogging, JBoss common logging. http://anonsvn.jboss.org/repos/common/common-logging-spi/trunk/src/main/j... | Correct me if I am wrong, but I think that most of the logging performed in jBPM is with Common's logging. Also, we want this to be portable to all containers, which means we should be programming for commons logging, and should also use the suggestions of Apache for how to use their logger. I am sure there should be plenty of places where trace should be used rather than debug. However, I am trying to contribute something that is an easy and a proper fix for the issue at hand. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222058#4222058 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222058

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Debug Logging

by david.lloyd＠jboss.com

"bradsdavis" wrote : Within that document, they also suggest that the debug level is for: | | anonymous wrote : | | Developer or in depth information required for support is the basis for this priority. | | | | That doesn't suggest that most will have debugging enabled in a production environment. We should be targeting production for efficient business processing. | The suggestion occurs later in the document. This has been discussed to death over several years, so I'm not going to argue about it. It's the policy. "bradsdavis" wrote : I haven't seen that isDebugEnabled is deprecated. Can you shoot me a link to that? Not Apache clogging, JBoss common logging. http://anonsvn.jboss.org/repos/common/common-logging-spi/trunk/src/main/j... "bradsdavis" wrote : Also, putting general debug messages that log full objects can lead to Hibernate lazy loading of objects when there is not necessarily a reason to load the object. This is definitely a place for efficiency bugs to creep up. Sounds like it ought to be a trace message. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222052#4222052 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222052

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Debug Logging

by bradsdavis

Within Commons Logging's documentation: http://commons.apache.org/logging/apidocs/index.html[/url] anonymous wrote : | Performance is often a logging concern. By examining the appropriate property, a component can avoid expensive operations (producing information to be logged). | | For example, | | if (log.isDebugEnabled()) { | ... do something expensive ... | log.debug(theResult); | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222049#4222049 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222049

15 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Debug Logging

by bradsdavis

Within that document, they also suggest that the debug level is for: anonymous wrote : | Developer or in depth information required for support is the basis for this priority. | That doesn't suggest that most will have debugging enabled in a production environment. We should be targeting production for efficient business processing. I haven't seen that isDebugEnabled is deprecated. Can you shoot me a link to that? Also, putting general debug messages that log full objects can lead to Hibernate lazy loading of objects when there is not necessarily a reason to load the object. This is definitely a place for efficiency bugs to creep up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222047#4222047 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222047

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jbpm-dev March 2009