April 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - conditional transitions in 3.2GA - not working when using ex

by cristim1979

Hi, I have this problem: some process definition using decisions worked well on JBPM 3.1.4, but when i tried upgrading to 3.2GA, it always chose the default transition (no decision was correctly evaluated). After some tries, I've seen that the conditions simply do not work in that syntax - using the 'expression' as ATTRIBUTE of the condition tag - but works in the alternate one: using expression as child element. Is this normal in 3.2 ? from the userguide (18.4.29. condition): "{content} For backwards compatibility, the condition can also be entered with the 'expression' attribute, but that attribute is deprecated since 3.2" if it's still allowed (even deprecated), i was expecting it to still work, somehow... this junit test shows this: | import junit.framework.TestCase; | import org.jbpm.graph.def.ProcessDefinition; | import org.jbpm.graph.exe.ProcessInstance; | | /** | * JUnit test of JBPM to check issues regarding the sintax of conditional transitions.<br> | * In 3.2 it seems that using the 'expression' ATTRIBUTE of the <condition> tag does not | * work! (but only the alternative, where the expression is passed as a child element of the tag!) | */ | public class TestDecisionAndConditionalTransitions extends TestCase | { | | public void testDecision( ) | { | String def1 = "<process-definition>" + " <start-state>" + " <transition to='d' />" | + " </start-state>" + " <decision name='d'>" | + " <transition name='t1' to='a'>" | + " <condition>#{a == '1'}</condition>" + " </transition>" | + " <transition name='t2' to='b'>" | + " <condition>#{a == '2'}</condition>" + " </transition>" | + " <transition name='t3' to='c'>" | + " <condition>#{a == '3'}</condition>" + " </transition>" | + " </decision>" + " <state name='a' />" + " <state name='b' />" | + " <state name='c' />" + "</process-definition>"; | | String def2 = "<process-definition>" + " <start-state>" + " <transition to='d' />" | + " </start-state>" + " <decision name='d'>" | + " <transition name='t1' to='a'>" | + " <condition expression=\"#{a == '1'\"/>" + " </transition>" | + " <transition name='t2' to='b'>" | + " <condition expression=\"#{a == '2'\"/>" + " </transition>" | + " <transition name='t3' to='c'>" | + " <condition expression=\"#{a == '3'\"/>" + " </transition>" | + " </decision>" + " <state name='a' />" + " <state name='b' />" | + " <state name='c' />" + "</process-definition>"; | | ProcessDefinition processDefinition1 = ProcessDefinition.parseXmlString( def1 ); | ProcessDefinition processDefinition2 = ProcessDefinition.parseXmlString( def2 ); | | //test def 1 - should work | ProcessInstance processInstance = new ProcessInstance( processDefinition1 ); | processInstance.getContextInstance( ).setVariable( "a", "2" ); | processInstance.signal( ); | assertEquals( processDefinition1.getNode( "b" ), | processInstance.getRootToken( ).getNode( ) ); | | //test def 2 - doesn't work on JBPM 3.2 ? (but used to work on 3.1.4 ?) | ProcessInstance processInstance2 = new ProcessInstance( processDefinition2 ); | processInstance2.getContextInstance( ).setVariable( "a", "2" ); | processInstance2.signal( ); | assertEquals( processDefinition2.getNode( "b" ), | processInstance2.getRootToken( ).getNode( ) ); | } | } | anonymous wrote : View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039931#4039931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039931

18 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: how to create variables with Expression in processdefini

by kukeltje

did you try? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039930#4039930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039930

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB

by timfox

It's my understanding that the JMSActivation will be used for an MDB but if you create a connection directly (from inside your Ejb for instance) using the managed connection factory then (if it can't find an appropriate cached one) then a new JMSManagedConnection will be created and JMSManagedConnection::setup() wil be called. AFAICT This will always end up creating an XAConnection (even for JBoss MQ) if the default JMSProviderAdapter is used, since the default JMSProviderAdapter shipped with AS4.x always looks up using /XAConnectionFactory. So I don't see how separating out Connection and XAConnection is going to help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039925#4039925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039925

18 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: how to create variables with Expression in processdefini

by cristim1979

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: aop-mc-int tests with maven

by pgier

I added the dtd and license to be included in the snapshot jar. It is in the resources section of the pom. To upload a new snapshot: mvn deploy But you will need to configure your settings.xml file with your svn account. You can see this for more information: http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSnapshotRepository View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039910#4039910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039910

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBoss common vs common core, common logging etc

by timfox

Yikes. So we can't guarantee that an application that uses common in JBoss AS 4.x will run in JBAS 5.0 without scoping. Sounds nasty. I should revert our dependency to be jboss commons (same as AS 4.2) so *at least* we can guarantee it will run unscoped in AS 4.2. But this means we will have to release a different release of JBM that is guaranteed to run in JBAS 5.0 which has dependencies aligned with AS 5.0 dependencies. Either that, or an explicit compatibility is defined and tested somehow between the old commons and the new common core etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039908#4039908 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039908

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBoss common vs common core, common logging etc

by dimitris＠jboss.org

JBoss common 1.0.x, 1.2.x is the one that comes from the JBoss AS 4.x series. For jboss HEAD/5 it was broken into common-core, common-logging-spi, etc. In general they "should" be compatible, but currently it's not guaranteed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039906#4039906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039906

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB

by clebert.suconic＠jboss.com

Just to add some information on this: At JmsActivation the transactional attribute is taken in consideration. So.. even CF is a XAConnectionFActory it wouldn't use the XA method if the transactional parameter is false on a createSession request. Relevant code: | package org.jboss.resource.adapter.jms.inflow; | | public class JmsActivation implements ExceptionListener | { | | .... | | protected TopicConnection setupTopicConnection(Context ctx, String | user, String pass, String clientID) throws Exception | { | String topicFactoryRef = adapter.getTopicFactoryRef(); | log.debug("Attempting to lookup topic connection factory " + | topicFactoryRef); | TopicConnectionFactory tcf = (TopicConnectionFactory) | Util.lookup(ctx, topicFactoryRef, TopicConnectionFactory.class); | log.debug("Got topic connection factory " + tcf + " from " + | topicFactoryRef); | log.debug("Attempting to create topic connection with user " + | user); | TopicConnection result; | if (tcf instanceof XATopicConnectionFactory && | isDeliveryTransacted) | { | XATopicConnectionFactory xatcf = (XATopicConnectionFactory) | tcf; | if (user != null) | result = xatcf.createXATopicConnection(user, pass); | else | result = xatcf.createXATopicConnection(); | } | else | { | if (user != null) | result = tcf.createTopicConnection(user, pass); | else | result = tcf.createTopicConnection(); | } | if (clientID != null) | result.setClientID(clientID); | result.setExceptionListener(this); | log.debug("Using topic connection " + result); | return result; | } | | .... | } | This way a non transacted Session would be aways a plain Connection... but not for us! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039902#4039902 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039902

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Idiot's guide to setting up mc build in Eclipse?

by bytor99999

Don't you see a group of tests that failed in the console like below? | 08:15:18,683 INFO [ASeamAction] sorting - null, true | Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.093 sec | Running org.jboss.test.TemplatePopulatorTest | Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec | Running org.jboss.test.TextareaMapConverterTest | Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec | | Results : | | Failed tests: | testGetServices(org.jboss.test.NameOfSomeTest) | | Tests run: 15, Failures: 1, Errors: 0, Skipped: 1 | It will give you a list of failed tests. Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039894#4039894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039894

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - BeanMetaDataBuilderImpl introduction

by alesj

Previously BeanMetaDataBuilder (part of spi) had all sort of plugin dependencies - this shouldn't even compile in the first place, if we want to have clean separation between spi and plugins. So I introduced it as interface in the spi, and as an impl in the plugins. And a new factory that 'connects' the two of them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4039893#4039893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4039893

18 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2007