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 84978 - Mapping elements disappear
Summary: Mapping elements disappear
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: XAM (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Girish Balachandran
URL:
Keywords:
: 85402 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-15 09:52 UTC by mfoster
Modified: 2007-03-29 18:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
BPEL project (90.71 KB, application/octet-stream)
2006-09-15 09:53 UTC, mfoster
Details
CA Project (311.28 KB, application/octet-stream)
2006-09-15 09:53 UTC, mfoster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mfoster 2006-09-15 09:52:50 UTC
See the attached bpelArdatis project and the bpArdatis inside.
Double-click on "Assign2" to get the mapper window open.
Expand "GetAanvraagAansluitingOut1" and notice everything in the mapper goes 
blank.
This may have something to do with the errors generated when I try to build the 
project in "caArdatis" - it complains about elements not being defined, I will 
raise a separate issue for this.
Comment 1 mfoster 2006-09-15 09:53:25 UTC
Created attachment 33992 [details]
BPEL project
Comment 2 mfoster 2006-09-15 09:53:53 UTC
Created attachment 33993 [details]
CA Project
Comment 3 Joshua Sandusky 2006-09-18 22:38:33 UTC
I believe this is an issue with the XML Retriever.

The XML retriever is being used to obtain an XSD that is being shown inside the
bpel mapper. The problem is that when the XML retriever attempts to load the
XSD, it forces the Output window to be active, which hides the mapper. This I
think is fine, except that this is happening even when there is no output
actually being displayed, which looks like a bug instead of how things are
supposed to work.

I think the XML Retriever shouldn't make the Output window active unless output
is actually shown to the user. Perhaps this can simply be done by initializing
the Output window with something like "retrieving xml" instead of being left blank.
Comment 4 Girish Balachandran 2006-09-20 04:20:01 UTC
Fixed on 9/19. Retriever will not automatically open the o/p window. User will
have to right click on the progressbar to invoke it explicitly.
Comment 5 Joshua Sandusky 2006-09-22 03:30:25 UTC
*** Issue 85402 has been marked as a duplicate of this issue. ***
Comment 6 tonybeckham 2007-03-29 18:46:07 UTC
Issue 85402 is a duplicate and has been verified in build 060925.  Changing this
issue to verified.