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.
Steps to reproduce: 1. create .wsdl from scratch. 2. Add new message 3. Select part1, and select refactor > rename 4. In the window, enter a new name and click "Next" You will get the attached stackflowerror after some time.
Created attachment 32520 [details] StackFlowError
The majority of the stack is in BPEL refactoring. Assigning to BPEL team for evaluation.
I tried the following: 1. Create Bpel module 2. Create wsdl file 3. Create new message 4. Invoke Refactor > Rename for part1 5. Press Next, weait, press Do Refactoring Everything is ok, exception is not reproduced. I tried with coke soa 060803_19 and coke beta 060803_7 builds. Please verify on the latest build (soa and beta) and in case of exception, please attached original project and describe detailed steps for reproducing.
Created attachment 32552 [details] BPEL project with multiple bpels and wsdls
Attached is a BPEL module with many wsdls and bpels. If you open this and add a new wsdl and follow the steps above to "refactor", you will get this stackFlowError. I have lowered the priority to P3, since the workaround is: 1. create bpel and wsdl in another BPEL Module, and copy/paste it over.
The problem is that QueryWithNamespace1.wsdl contains recursive definition of addressType <xsd:complexType name="addressType"> <xsd:sequence> <xsd:element name="street" type="tns:addressType"/> <xsd:element name="city" type="xsd:string"/> <xsd:element name="state" type="xsd:string"/> <xsd:element name="zip" type="xsd:string"/> </xsd:sequence> </xsd:complexType> Additional check should be done in bpel refactoring provider.
Vladimir. Do you agree that workaround listed here is a valid workaround? I was surprised to read this workaround. It does not seem like it would help. If this is not valid workaround, maybe we need to raise bug priority again.
Mike, what workaround do you mean? I suggested additional check - passed type should be skipped, it keeps from infinity loop.
fixed.
I meant the workaround listed by lchang: "I have lowered the priority to P3, since the workaround is: 1. create bpel and wsdl in another BPEL Module, and copy/paste it over." She had originally created this bug as a P1 or P2 and lowered it to P3 because of "workaround". But I am not sure workaround is workaround. The "workaround" is only significant for Beta since you have now fixed this in release55.
The workaround is not valid. Reopening the bug and setting priority back to P2 The problem is already fixed in trunk we suggest it to be fixed in beta branch.
will be fixed in cokebeta branch on 9 Aug 2006
fixed in coke beta.
verified