Mauricio, great job with all the wiki's
about it! it really helps to follow the design.
As it comes for comments, most of them have already sent to you
like a month ago. In addition to those I have few more:
- is task definition service mandatory - I mean we already have
definition of a task as userTask in bpmn2 so don't see a reason
why we need to have definition once again stored on task server?
- seam transactions - does that mean we have tight dependency on
seam framework? do we want that? I recall that some time ago we
tried to remove such dependency... and wondering how that would
look like in other application servers, etc....
- backward compatibility - will we have any layer that will
provide old way to the new task server or we consider this as one
time switch?
Maciej
On 19.07.2012 11:25, Mauricio Salatino wrote:
Hi Guys,
I've made a brief about the refactorings that I'm planning to
do based on the experiments that I was doing based on the
concepts and requirements for a Human Task module that we all
know.
I've published this wiki page summarizing the main points
that I'm targeting to cover on this refactor, so I appreciate
any feedback remarks, questions.
Let me know if you don't understand something or if you have
doubts about this approach. In my perspective this looks clear,
simple, flexible as it should be :)
But I'm open to any constructive criticism.
The next step after the feedback is making it real :)
Cheers
_______________________________________________
jbpm-dev mailing list
jbpm-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev