Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 112626 - Exception after Delete/Undo element of XML schema.
Exception after Delete/Undo element of XML schema.
Status: VERIFIED FIXED
Product: xml
Classification: Unclassified
Component: Schema Tools
6.x
All All
: P1 (vote)
: TBD
Assigned To: Sonali Kochar
issues@xml
:
Depends on: 112574
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-13 12:18 UTC by Michael Nazarov
Modified: 2007-09-03 15:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments
exception (4.63 KB, text/plain)
2007-08-13 12:19 UTC, Michael Nazarov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Nazarov 2007-08-13 12:18:43 UTC
Product Version: NetBeans IDE Dev (Build 200708130000)

Steps to reproduce:

1. Create BluePrint1 Sample and BPEL module.
2. Add to Module Sample Loan Application XML schema.
3. Add to Sample reference to Module.
4. Import to purchaseOrder reference to newLoanApplication.
5. Add Complex Type to purchaseOrder. Use type referenced from newLoanApplication.
6. Go to Design view and Delete created type. Right CLick / Delete / Refactor.
7. Go to Source view and Undo last action. Refactor / Undo.

Exception will come. See attach.
Comment 1 Michael Nazarov 2007-08-13 12:19:25 UTC
Created attachment 46500 [details]
exception
Comment 2 Samaresh Panda 2007-08-13 17:57:50 UTC
The traces are exactly same as the one I reported earlier. See IZ: 112574. I feel that all these issues (112233, 112342,
112574 and this one) are related.

Please see my comments in 112342. I'm sure these are problems related to changes either in Lookup or in core refactoring.
Comment 3 Samaresh Panda 2007-08-14 18:35:06 UTC
The step #5 is not clear. Do you mean to create a new complex type in PO.xsd or you want me to change the type of
purchaseOrder element to point to some complex type from loanApp.xsd? Please be clear!

In fact, first I would like you to verify if this bug exists anymore? I suspect the fix in 112342 fixes this issue as well.
Comment 4 tonybeckham 2007-08-14 18:40:01 UTC
Product Version: NetBeans IDE Dev (Build 200708140000) 
Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-87 
System: Mac OS X version 10.4.10 running on i386; MacRoman; en_US (nb)

With the above system I did not get any exception.

Steps:
-I created BluePrint1 sample
-created new BPEL module
-added sample loan schema to new BPEL module
-added new BPEL module to blueprint1 as a project reference
-imported newLoan schema to purchaseOrder schema
-then followed steps 5-7 from original description 
Comment 5 Samaresh Panda 2007-08-15 18:09:49 UTC
I do not see this assertion I reported earlier (issue: 112574) anymore. Like I said earlier, these are all related and
sure enough, this is no longer an issue.
Comment 6 Michael Nazarov 2007-09-03 15:51:32 UTC
Product Version: NetBeans IDE Dev (Build 200708310258)


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo