[JBoss jBPM] - jbpm.3 ide most recent Decision xml config
by myarrow
Hello jBPM community
Looking around at the posts about the Decision tag content,
it seems to have changed more than once in the last couple
of years.
Could someone please show me a correctly formatted
current jbpm.3 decision tag with content, say for two
transitions out (e.g., true-false).
Note: what I have seen are the following:
|
| <decision name="evaluateGuess" expression="#numberGuess.correctGuess}">
| <transition name="true" to="win"/>
| <transition name="false" to="evaluateRemainingGuesses"/>
| </decision>
|
and I have also seen:
|
| <decision name="decision-x">
| <transition name="t1" to="node-a" />
| <transition name="t2" to="node-b">
| <condition expression="#{...}" />
| </transition>
| </decision>
|
|
Please comment: which is correct ? Are both correct ?
In addition, does anyone have a trivial processdefinition.xml
which adds two numbers and then tests for even-odd in a
decision, or maybe any other trivial decision-string test
processdefinition.xml which works in jbpm.3 ?
Maurice Yarrow
SplashNote Systems
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006896#4006896
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006896
19 years, 2 months
[JBoss Seam] - Re: pagination problem, advice needed
by liudan2005
Sorry I was trying to explain my situation better but made it worse. Here is my scenario. The person.xhtml page shows all the properties of Person entity. In this page, I need to show top 5 records of person's calls and reviews. Here is the code:
| <h:outputText value="#{person.name}" />
| <h:outputText value="#{person.age}" />
| <h:dataTable value="#{person.reviews}" var="review" >
| <h:outputText value="#{review.title}" />
| </h:dataTable>
|
| <h:dataTable value="#{person.calls}" var="call" >
| <h:outputText value="#{call.duration}" />
| </h:dataTable>
|
Paginating for {person} is easy when using Query. but to paginating for {person.reviews} and {person.calls} is not easy. By now, I have to create a pagination object for each collection based property. If Person has 4 collection type properties (e.g. calls,reviews...), I basically have to create 4 extra pagination objects with customised Hsqls for pagination. It's so time consuming to do it this way. If I use t:dataScroller, I wouldn't have to create those 4 extra objects. But as you said, there's performance problem with t:dataScroller. It would be nice if Seam can provide a s:dataScroller, which support real database based pagination.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006893#4006893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006893
19 years, 2 months