why not simply use an event on the transition and set a processvariable. Even more backwards compatible and not that different.
The reason I mention this is that there are so many usecases wich can be solved by extending jPDL but also by using the actions on events. extending jPDL is not that trivial and Tom is (for good reason) hasitant to do this in minor releases. There are some changes on the roadmap for 4.0 but not sure if this will be one of them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991474#3991474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991474
something whacked out my last posts on this... I'm resubmitted as a new thread.
---
I did a search on this and couldn't find anything on it.
In jboss-service.xml, you can define values via properties like this:
${my.prop:123}
where the value will be 123 iff my.prop property is not explictly set.
However, this syntax does not seem to work on JBossAS 4.0.5 within the jbossweb-tomcat55.sar's server.xml.
If I use ${my.prop} in server.xml, it works fine. But if I define a default value like ${my.prop:123}, it doesn't work - the value becomes literally ${my.prop}.
Wondering if its just me or if its a known issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991470#3991470
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991470