wow, we have a noob here in the forum... ;-)
Yes, sounds logical. But this means that signalling via the api should set this variable? or can we have an additional solution that if there is a textual (non formal) condition that when signalling flow name/id is used.
I can implement anything like this, but it has to be very specific. Including things like what if there is no flow that has a condition that evaluates to true. etc...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246843#4246843
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246843
"camunda" wrote : P.S: I commit a failing test case with a uncontrolled sequence flow as Fork and two tasks, if somebody cannot stop himself from coding ;-)
|
If this test was the only thing failing ;-)
- dueDate -> duedate, but named queries not updatred jbpm.execution.hbm.xml : Koen
- AbstractTaskBinding in jbpm.bpmn.flownodes.xml which does not exist (yet?) : Bernd
And the strange thing is, I do not see hudson failing yet...Or is there a delay?
Oh... I take up the challenge... coding continues
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246827#4246827
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246827
I didn't hear any feedback, so I went ahead and made this change.
The default for SOAPClient, SOAPProducer, SOAPProxy and HttpRouter is now such that their response status will get returned by either the JBossRemotingGatewayListener and/or the HttpGatewayListener.
If you want the legacy behavior, you can override this at an action level (META-INF/jboss-esb.xml):
<action name="..." class="...">
| <property name="http.responseStatusEnabled" value="false"/>
| </action>
or at a global level (jbossesb-properties.xml):
<esb>
| <properties name="transports">
| <property name="org.jboss.soa.esb.http.responseStatusEnabled" value="false"/>
| </properties>
| </esb>
Again, the default is now true. I still have to update the docs about this.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246794#4246794
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246794
Maybe it is a good idea for the time-being to just make it work and file a jira issue for a real solution. That way it can work for everybody by using the source, but the issue is not forgotten.
And now we are into languages anyway:
"als het niet kan zoals het moet, dan moet het maar zoals het kan" is what we say in Dutch. (finding a proper translation I came across: if it ain't dutch it ain't much. Something completely different, but just as true) 1 Heineken for each proper translation as google fails miserably
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246786#4246786
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4246786