"brittm" wrote : 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.
Why the need for it to be in tables? Nodenames are unique, If you have the
processdefinition in a dom, you van easily use an xpath statement to get to specific
attributes of a specific node... no need to store it in a db. Just make sure in the
processdefinition object that is in the hibernate cache, there also is a cached dom
version of it... This could be implemented now without any changes to databases or
whatever.
anonymous wrote : Of course, we could do the same thing with a generic "meta"
tag on the key jpdl elements.
I hate 'generic' tags. They quickly become meaningless.
"brittm" wrote :
| 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.
Would we see people using it? Would they give feedback on how they use it? I doubt it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054154#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...