Yes, no xml. And yes, you can always use an additional table in the same
database, retrieve data and set variables via the api.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110885#4110885
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
"kukeltje" wrote :
| npe: in that case the other solution will indeed not work. Generating xml
from the PD object is not supported anymore (jpdlxmlwriter is deprecated)
I'm not sure I get that well :
That means I have to forget about XML (no problem though) and persist it in
another way ?
Simon,
The PD is xml, it is fairly easy to retrieve, make a Document out of it and
retrieve e.g. via xpath the required fields. The change you want will most
likely not be done before jBPM 4.
npe: in that case the other solution will indeed not work. Generating xml from
the PD object is not s
Actually i'm facing a problem with that and I quite agree with simon.
I created my process definition programmatically with an action that creates
the variables of the process at the start of a new instance, based on a map
that is a field of my action handler (maybe not the best solution but it'
"kukeltje" wrote : Simon,
|
| You can already add any tag you want to the processdefinition and when
retrieving a processdefinition , also retrieve the xml file with it. You can
translate that to a dom and read any element you put in there.
Ok, that's good to know we can add extra tags.
Simon,
You can already add any tag you want to the processdefinition and when
retrieving a processdefinition , also retrieve the xml file with it. You can
translate that to a dom and read any element you put in there.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
"kukeltje" wrote : I forgot to add: "because often it hides other missing
features"
|
I agree with that. Hopefully people will still request features they are
interested in and the designers can see which ones truly represent a common and
core need.
View the original post :
http://www.jbo
"kukeltje" wrote : userobject: care to elaboreate? I have no clue why this
could be useful? Things that are to generic tend to blur usability and promote
abuse.
There is a lot of practical real-world stuff that goes into delivering and
maintaining a system for real customers. Typically monito
anonymous wrote : Can someone confirm this please ?
Confirmed
anonymous wrote : Is that correct ?
Yes
anonymous wrote : The thing is that in the functional problem i'm dealing with
i want to set at design time the variables that will be used by every instance,
so I do not want to create vari
Hi all,
As far as I understood all the doc I could found and the subject of this topic,
it's impossible to store variables at the process definition level.
It means that you have to instantiate and eventually initialize the variables
each time you instantiate a process instance.
Can someone co
I forgot to add: "because often it hides other missing features"
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109581#4109581
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109581
_
userobject: care to elaboreate? I have no clue why this could be useful? Things
that are to generic tend to blur usability and promote abuse.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109579#4109579
Reply to the post :
http://www.jboss.com/index.html?m
Michele!
Those are good ideas. I'll have to check more into the "script" tag, there are
many features in jBPM which I'm not very familiar with yet that could provide
solutions.
I'd also like the designers to consider adding a "user object" property
(setUserObject(Object userObject), getUserOb
A formal tag would certantly be nice. Our use case is
similar (but not the same) as http://jira.jboss.com/jira/browse/JBPM-679. Maybe
we could open a jira and link there... it's scheduled for jBPM 3.3.
As for now, I think the value bearer action has to do the hard work. I think
you should use
Mauro: I'm interested in what you end up doing. I'm also considering using a
custom action to set some "process variables" from the processdefinition.xml
file as the process starts. I'm not sure what is the best choice of place to
"attach" the action handler (start node, start node transition,
I'm planning to solve the same problem using some custom action that copies in
the deploy envirorment its configuration, thus transferring static process
parameters.
Mauro Michele
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107963#4107963
Reply to the po
I guess to answer my own question, I could store the name/paths of the files as
data in a FileDefinition, and retrieve them from the FileDefinition
inputstream. Seems overkill, but I guess that would work.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=410762
17 matches
Mail list logo
