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.

Bug 130023 - There should be a way to tell the mapper to use entities other than elements names as their display names
Summary: There should be a way to tell the mapper to use entities other than elements ...
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: Tools (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Svata Dedic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-13 13:00 UTC by Kirill Sorokin
Modified: 2011-11-30 16:18 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
In predicate ERR.4 corresponds to Severity in the tree (9.17 KB, image/png)
2009-10-09 18:57 UTC, Nikita Krjukov 		Details
Look to the highlighted type name. (21.96 KB, image/png)
2009-10-09 18:59 UTC, Nikita Krjukov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kirill Sorokin 2008-03-13 13:00:34 UTC 
[filing on behalf of Michael Czapski]

In the HL7 XML structure one does not get to know what the field names are so unless one is _very_ familiar with hl7 one
has to continually refer to HL7 spec, or something, to work out to which fields to assign data. CM_PAT_ID.1 is "Set ID -
Patient ID", as the LongName in the XSD says but there is no way to see that in the BPEL mapper.

KS: The proper display name is declared in an xsd annotation. This is not a declared functionality, thus I'm filing as
an enhancement request.
Comment 1 Sergey Lunegov 2008-03-13 13:44:52 UTC 
This is really enhancement.
Comment 2 Kirill Sorokin 2008-05-05 13:25:31 UTC 
Let's consider an approach with an alternative tree model for this issue.
Comment 3 Nikita Krjukov 2008-07-16 20:04:18 UTC 
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.
Comment 4 Vladimir Yaroslavskiy 2009-09-24 08:48:01 UTC 
fixed in gfesbv22: 672498f67b9f
Comment 5 Nikita Krjukov 2009-10-09 18:55:28 UTC 
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.
Comment 6 Nikita Krjukov 2009-10-09 18:57:41 UTC 
Created attachment 89220 [details]
In predicate ERR.4 corresponds to Severity in the tree
Comment 7 Nikita Krjukov 2009-10-09 18:59:35 UTC 
Created attachment 89222 [details]
Look to the highlighted type name.
Comment 8 Vladimir Yaroslavskiy 2009-10-13 15:04:45 UTC 
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.