Namespaces seems like a good idea *if* jBPM could throw that part of the configuration into 'external config' tables with a foreign key to the jpdl parent element. I wouldn't care if the configuration were simply stored as a string--at least it would be trivial to retrieve in relation to the appropriate jpdl element. We're already doing this kind of thing with ActionHandler configuration. Of course, we could do the same thing with a generic "meta" tag on the key jpdl elements. One advantage to this approach could be that if we see people using this functionality to carry the same types of configuration over and over, then that usage could be a candidate for standardizing in the jpdl. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054049#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...