[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-6972: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Robert (Bob) Brodt Fix Version/s: 3.2.0.Beta -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Marek Baluch commented on JBIDE-6972: ------------------------------------- Hi. I know I can set it using the editor. Nevertheless I think the editor should do it automatically when pick is added. Of course the value should be set according to the position of the activity. It's quite easy to omit the attribute afterwards. Btw. I was not able to find the createInstance option in the details window for invoke. Am I looking in a bad place? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6972: ------------------------------------------- Actually, I think the editor's current behavior is OK - see JBIDE-6971. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6972: ------------------------------------------- Well...almost OK :) I DID find that the editor does not check for this condition (from the WS-BPEL 2.0 spec): The following example IS NOT allowed, since the <assign> activity is not a start activity: <flow> <receive ... createInstance="yes" /> <assign ... /> </flow> The following example IS allowed, since the <assign> activity will not be performed prior to or simultaneously with the <receive> activity: <flow> <links> <link name="RecvToAssign" /> </links> <receive ... createInstance="yes"> <sources> <source linkName="RecvToAssign" /> </sources> </receive> <assign> <targets> <target linkName="RecvToAssign" /> </targets> ... </assign> </flow> We should probably check for these types of conditions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Marek Baluch commented on JBIDE-6972: ------------------------------------- yep. keep it open then. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Marek Baluch commented on JBIDE-6972: ------------------------------------- Yes close JBIDE-6971 please. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6972: ------------------------------------------- We'll keep this JIRA open to fix the validation problem described above (see my comment from 03/Sep/10 09:48 AM). This is fairly complicated and will not be fixed by 3.2.0.Beta so I'm moving it to 3.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBIDE-6972: ------------------------------------------ Bob, bumped to 3.2.1 for now. If not 3.2.1, should probably go in a 3.3 release or LATER. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt updated JBIDE-6972: -------------------------------------- Fix Version/s: 3.3.0.M1 (was: 3.2.1.M1) This is a complex problem that is going to take some time to fix, with minimal benefit...in other words, I don't have time to work on this before the June release because there are more important things to do before then, so I'm pushing this to 3.3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-6972?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt updated JBIDE-6972: -------------------------------------- Fix Version/s: 3.3.x (was: 3.3.0.M2) Not a critical issue - pushed to 3.3.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira