This content has been marked as final.
Show 4 replies
-
1. Re: Job.configuration property
aguizar Feb 27, 2009 12:46 PM (in response to camunda)No, must be a legacy artifact. It is not persisted, so its value is kinda limited from my point of view.
-
2. Re: Job.configuration property
camunda Feb 27, 2009 4:14 PM (in response to camunda)I think too. But I would keep it and just add a javadoc. It is quite handy if you need to store something together with the Job.
And in this case you can just exchange the hibernate mapping in your project... -
3. Re: Job.configuration property
tom.baeyens Mar 2, 2009 4:08 AM (in response to camunda)i don't recall this. but i assume it is probably for some kind of extensibility like bernd needs it for :-)
-
4. Re: Job.configuration property
camunda Mar 2, 2009 4:09 AM (in response to camunda)Perfect. jBPM is always one step ahead :-))