1. If we have to keep old tasks used without migration
(Which is just the first proposal from Ark's email)
2. If we just have to keep old tasks used by migrating them
No matter how we name the red parts, no matter we keep old class and copy them then write new, or we just update old code, the tasks will include
- B4P wsdl includes
- TMSB4P.wsdl to create webservice interface ( totally different with current )
- serviceB4P.xml to create webservice in Axis ( totally different with current )
- TMSB4P mainly includes
- new TMSRequestProcessor for web service implementation ( can partialy use current code, see Compare Tempo with B4P compliant Task Engine to know detail )
- new ITMSServer for task management real process ( totally different with current, althrough some method's name looks similar, but parameter is different )
- new TMSServer for task management process interface( can partialy use current code, see Compare Tempo with B4P compliant Task Engine to know detail)
- new Marsheller/UnMarsheller ( totally different with current )
- TMP basically has no change before open issue 6 and 7 comfirmed.
- TMSClientB4P mainly includes
- JPAB4P mainly includes
- new db schema for B4P task properties, states, priorities, attachments info.( mostly different with current, althrough some method's name looks similar )
- new Entity classes,such as TaskB4P...( mostly different with current)
- xform manager b4p mainly includes
- Since UI calls most TMS operation by xpl/xform, so xpl parts will change a lot to allow user do B4P HT operation on taskss.
- SecurityB4P
- Authentication is reused.
- People assignment on generic human role is defined in User Process when design time.
- According to b4p spec, the underlying people assignment will be retrieved from HT request or coordinate protocal. But since the coordinating protocal won't be implemented in this phase, so people assignment will deployed into Tempo.
- The logic group will be directly map to actual group in LDAP or DB.
- TASB4P mainly includes
TAS will basically has no change. Some properties for Attachment will be changed.
- UI mainly includes
UI will basically has no change., because thanks Tempo, UI just implements representation layer, most logical stuff is responsible by xform/xpl.
- Tempo Designer b4p mainly includes ( not included in this project )
- More operation provided for user
- xform model/schema should be changed to alighn with B4PHT operation
- other tbd
- WDS
- change to store people assignment
- FDS
- FDS translates msg between TMP, TMS, and user process, it basically has no big change.
TMS ( TMSRequestProcessor / TMSServer / marshaller/unmarshaller )
UI/portlet/alfresco/formMananger/CAS
