[
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)?
Manage namespaces better
------------------------
Key: JBIDE-6765
URL:
https://jira.jboss.org/browse/JBIDE-6765
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: bpel
Affects Versions: 3.2.0.M1
Environment: Eclipse 3.6 on Mac with JB Tools 3.2
Reporter: Jeff DeLong
Assignee: Robert (Bob) Brodt
Fix For: 3.2.x
The BPEL Editor should improve its managment of namespaces. Sometimes when configuring a
Copy operations as part of an Assign activity, a dialog will pop up asking the user to
create a Namespace Prifix for a particular Target Namespace. But when you enter the
defined Prefix Name for this Target Namespace, it says "This prefix is already
used".
Also, there does not appear to be a place to change these mapping (other than in the
source file).
--
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