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.
Created attachment 46500 [details]
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.
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.
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.
-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
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.
Product Version: NetBeans IDE Dev (Build 200708310258)