[ http://jira.jboss.com/jira/browse/JBPM-1352?page=all ] Thomas Diesler updated JBPM-1352: --------------------------------- Component/s: jPDL 4 (was: API) Fix Version/s: jPDL 4.0 alpha1 (was: API 1.0.0.Beta) Assignee: Heiko Braun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1352?page=all ] Thomas Diesler updated JBPM-1352: --------------------------------- Please add a mapping for this API functionality in jBPM4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1352?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1352: ------------------------------ Fix Version/s: (was: jBPM 4.0.x) jBPM 4.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1352?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1352: ----------------------------------- i've plugged in jsr 223 with scripting.dev.java.net. in the configuration, you can configure a named list of expression languages and also indicate which is the default expression language. in the jpdl language, for each expr attribute, there is an optional lang attribute. ok. my expectation is that you drive the seam integration. i'll be ready to supply any jbpm update that you'll need and re-upload a snapshot. does that work for you ? regards, tom. Pete Muir wrote: > > On 14 Apr 2009, at 14:50, Tom Baeyens wrote: > >> the initial work needs to be done by us, i think. >> >> implementation wise there are a couple of directions, but there is still a bit of thinking involved. >> >> mostly, the current integration is based on integrating the naming resolutions while resolving UEL expressions. apart from that there is only the special SEAM annotations, which will boil down to jbpm service invocations. >> >> * setup of the seam contexts. find the proper places where we need to intercept to set up the seam contexts. this could potentially be very easy. we have a set of services now (==session facades). we also have a mechanism to add interceptors to those. a seam interceptor could ensure that seam is properly initialized around jBPM operations. > > Great, sounds easy enough :-) > >> * expanding the jbpm variable resolver so that it also delegates to the seam contexts. > > >> * tx around the jbpm timers and messages. we should be able to leverage our container integration. since we'll be deployable as a service, we'll build our own tx interceptor for managing the JTA tx. this is leveraged when using seam. > > Kev has been doing some work on this - but I agree, we should just use JTA here - Seam will join or start a TX as required. > >> >> >> * pageflow. build the page activity. create a pageflow parser. >> >> this is all not cristal clear though. requires getting our hands dirty to see if this plans are complete. i think we should plan a week where we together set out the initial structure. then we can involve productization people to finish the integration. > > Ok. > >> ... >> >> regards, tom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira