I have my doubts... task also has an attribute called description. Why should that be there and a translated description not? (regardless of easier redeploying or not)
With regard to this, I Would have liked a separate name and id on the nodes where you transition to the id but can display the name. Both can be the same (and will be if not edited manually) but don't have to be. Often I run into translating spaces in names to _ since I cannot use the name as an 'id' the way it is. This is not a jBPM4 issue btw, was/is also a 'problem' in 3. (sorry for partially threadjacking)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245227#4245227
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245227
Joram,
So, then your opinion is that the translations are not part of the definition?
The result of this approach is that you can change a translation without a new deploy. The drawback of this is that in this case there is not a track of this change.
So for the system you propose (normal 'Java' way) I assume that I just have to base my placeholder on the tasks name since that's the Taks 'Key' field?
Regards,
Gert
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245223#4245223
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245223
