THIS ISSUE HAS ALREADY 10 DUPLICATES

code analysis shows that it may happen when model contains 
circular specializations, ie. A->B->A. This can be created 
 as a result of the following scenario:

0.lets have A->B
1.RE both interfaces
2.source code edit to make B->A
3.partial RE, ie. only B.java

The partial RE, while being usefull and effective, have a set 
of potential drawbacks when only one side of an updated relation 
is REed. The above mentioned case is just one example.

To avoid the infinite recursion problem the defensive code 
will be added to block creation of such circular situation. 

Fixed. Added defensive check to RE to block circular generalization 
relationship creation.


author	lvv@netbeans.org
	Thu Jan 31 17:34:59 2008 -0800 (12 minutes ago)
changeset 65441	ea358d996d1f
parent 65440	b5a249ba0ebe
child 65443	e72d3aee0433
child 65444	8791fd6a63ab
Fix for 115479 java.lang.StackOverflowError typemanagement.TypeManager. 

and 

Checking in uml/core/src/org/netbeans/modules/uml/core/reverseengineering/reinte
gration/UMLParsingIntegrator.java;
/cvs/uml/core/src/org/netbeans/modules/uml/core/reverseengineering/reintegration
/Attic/UMLParsingIntegrator.java,v  <--  UMLParsingIntegrator.java
new revision: 1.7.2.4; previous revision: 1.7.2.3
done
Checking in uml/core/src/org/netbeans/modules/uml/core/metamodel/core/foundation
/RelationValidator.java;
/cvs/uml/core/src/org/netbeans/modules/uml/core/metamodel/core/foundation/Attic/
RelationValidator.java,v  <--  RelationValidator.java
new revision: 1.2.6.3; previous revision: 1.2.6.2
done

verified in NB 6.1 build 200803251204.
The resulting model no longer has the circular result.

Reopening - reproduced in NetBeans IDE 6.1 (Build 200804211638)
http://statistics.netbeans.org/exceptions/detail.do?id=124906

it seems not all cases was fixed in 6.1

able to reproduce with re of properties from hg (Resource Bundle)

it's enough to re org.netbeans.modules.properties.PropertiesEditorSupport class ino new project to get the issue.

root cause is incorrect elements resolving causing circular generalization creation. see simle attached project below
with reproducible case.

Created attachment 75302 [details]
simle java project with reproducible case

stackoverflow is replaced with warning in log, for me it's better. initial reasons for the issue are not resolved yet.

Integrated into 'main-golden', will be available in build *200901121401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/54332ee77058
User: sergeyp@netbeans.org
Log: fix #115479 made verification to avoid stackoverflow - infinite recursion. still need to resolve corrupted model which cause this problem.

Integrated into 'main-golden', will be available in build *200902010201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/7ae17487a878
User: sergeyp@netbeans.org
Log: fix #115479 - part fix, check in proper places

Build: NetBeans IDE 6.5 (Build 200811100001)
VM: Java HotSpot(TM) Client VM, 11.0-b15, Java(TM) SE Runtime Environment, 1.6.0_10-b33
OS: Linux, 2.6.27-11-generic, i386

User Comments: 
creating an UML project from an existing Java project

Stacktrace: 
java.lang.StackOverflowError
        at org.jaxen.BaseXPath.<init>(BaseXPath.java:157)
        at org.jaxen.dom4j.Dom4jXPath.<init>(Dom4jXPath.java:103)
        at org.dom4j.xpath.DefaultXPath.parse(DefaultXPath.java:302)
        at org.dom4j.xpath.DefaultXPath.<init>(DefaultXPath.java:52)
        at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:182)
        at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)

Created attachment 76823 [details]
stacktrace

in 6.7 only a better log can be added, so there will be no exceptions and also user will know smth isn't good.
"    There was some problems with source parsing, see report: 
Possible generalization-implementation resolve problem."
text is added to report for this case, in general it's related to some resolve problem if there are classes with the
same name (may be for nested classes only).

keep the issue opened to find root cause later.

Integrated into 'main-golden', will be available in build *200903181604* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/cfd9f0791b2a
User: sergeyp@netbeans.org
Log: fix #115479 - now user will see smth is wrong

Build: NetBeans IDE Dev (Build 200909220201)
VM: Java HotSpot(TM) Client VM, 11.0-b16, Java(TM) SE Runtime Environment, 1.6.0_11-b03
OS: Windows XP, 5.1, x86

User Comments: 
Deploying a JEE project and reverse engineering (UML) another one. The switching to another application.

Stacktrace: 
java.lang.StackOverflowError
        at java.lang.Character.digit(Character.java:4494)
        at java.lang.Integer.parseInt(Integer.java:445)
        at java.lang.Integer.parseInt(Integer.java:497)
        at com.werken.saxpath.XPathReader.numberInteger(XPathReader.java:140)
        at com.werken.saxpath.XPathReader.filterExpr(XPathReader.java:205)
        at com.werken.saxpath.XPathReader.pathExpr(XPathReader.java:75)

Created attachment 88188 [details]
stacktrace

Created attachment 101133 [details]
stacktrace

Running reverse engineering.