[ https://jira.jboss.org/browse/JBIDE-6765?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6765: --------------------------------------- Assignee: Robert (Bob) Brodt Fix Version/s: 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://jira.jboss.org/browse/JBIDE-6765?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6765: ------------------------------------------- Changing namespace prefixes is probably not a good idea because all references to the ns prefix would have to be found and changed within the BPEL process. This is a problem because these references can (and usually do) appear in XPath expressions. We have two options: 1. If we want to do this right, then a prefix name change would fall into the "refactoring" category. 2. Build a new Property Sheet Tab called, let's say "Namespaces", which would simply consist of a table of the namespace prefixes, namespace URIs, contexts (because each Activity can have its own list of namespaces) and locations (resources like WSDLs or XSDs). This would allow the user to quickly identify namespaces that don't have prefixes defined by the Process (required if you want to use any of the complex types defined within that namespace scope). It would also allow the user assign a prefix to ONLY those that are missing. Question: should we take the quick & easy way out for now (option 2) and have something usable relatively quickly, or should I take a week or two to sort out the BPEL code refactoring option (1)? -- 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-6765?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6765: ------------------------------------------- Mmk, so given a choice of either 1 or 2, you would like to have both :^) Yes I agree refactoring is an issue and needs to be addressed, and soon! It's scary to discover all of the places in the code where stuff is just added or removed, willy-nilly, to the model without going through "proper channels" (i.e. the EMF editing domain which manages all of the undo/redo and proper notifications of model listeners). ...OMG, what have I gotten myself into? ;) -- 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-6765?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-6765: ------------------------------------ Bob, That's great. I will test it out as soon as it is available from the Nightly Build. I would say close this one and open a new one or extend the descriptions on the other ones. I do want to keep the comment about the Editor complaining one already exists when you try to use it again. Perhaps I should document that better with steps to re-produce/ Thanks, Jeff -- 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-6765?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-6765: ------------------------------------------- Merged into eclipse.org/bpel see bug 324162 -- 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-6765?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-6765: ------------------------------------ I checked out the latest build, and the new Namespaces table is able to Assign Prefix to Namespaces without prefixes already assigned. Thanks. -- 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-6765?page=com.atlassian.jira.plugin.s... ] Jeff DeLong commented on JBIDE-6765: ------------------------------------ While Bob did add a Namespaces Table that is helpful, I don't think it completely solves the problem. For example, you can't edit the table to change a namespace prefix. And I still see times where I go to use a prefix and it claims it is already assigned, but it is not in the table. If we are going to close this JIRA we should open another one related to namespace re-factoring / namespace management. -- 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