This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | There should be a way to tell the mapper to use entities other than elements names as their display names | ||
---|---|---|---|
Product: | xml | Reporter: | Kirill Sorokin <ksorokin> |
Component: | Tools | Assignee: | Svata Dedic <sdedic> |
Status: | NEW --- | ||
Severity: | blocker | CC: | supernikita |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
In predicate ERR.4 corresponds to Severity in the tree
Look to the highlighted type name. |
Description
Kirill Sorokin
2008-03-13 13:00:34 UTC
This is really enhancement. Let's consider an approach with an alternative tree model for this issue. Actually the precise schema component is known for a tree item in the BPEL mapper. Obviously I mean the items which relates to a schema components like elements or attributes. So the annotation can be taken easily. I don't think such annotations should be used instead of tree nodes' names, but they can be shown in tool-tips at least. The only problem is if the annotation are used in the HL7 are standard. Also an additional button can be put to mapper's toolbar to instruct the mapper to show annotations instead of real names if possible. I remember a tool with similar design. It was for DB design. The tables and the rows had physical and human names. The physical is concise and the human is descriptive. It was allowed easy switching between them. It was quite helpful feature. fixed in gfesbv22: 672498f67b9f The HL7 names are shown well now in different trees. But there are some exceptions: -- In BPEL mapper the predicates are shown with real names. Try create a predicate anywhere. The new predicated item appears in the tree. The item has user-friendly name, but the predicate expression is the same as in sources, with real elements' names. -- In BPEL mapper try to create a pseudo element from xsd:any. Choose "Any Element" and call "Cast To..." pop-up command. A new dialog appears. It contains a tree where global schema types can be chosen. The types has real names. I suppose, they also can be replaced with HL7 user-friendly names. Created attachment 89220 [details]
In predicate ERR.4 corresponds to Severity in the tree
Created attachment 89222 [details]
Look to the highlighted type name.
display name of predicate is shown in org.netbeans.modules.soa.xpath.mapper.lsm.MapperPredicate and taken from XPathSchemaContext via method toStringWithoutParent which returns String. For HL7 check real type (object from schema model) should be returned, interface XPathSchemaContext (XPathExt Model) doesn't have required method. Request: provide API to obtain element/type of predicate. |