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 46850 - javax.jmi.reflect.CompositionViolationException
Summary: javax.jmi.reflect.CompositionViolationException
Status: RESOLVED DUPLICATE of bug 46291
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-03 07:56 UTC by Peter Nabbefeld
Modified: 2004-08-13 12:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
My startup log (I've not yet shut down NB) (28.38 KB, text/plain)
2004-08-03 07:58 UTC, Peter Nabbefeld
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2004-08-03 07:56:42 UTC
I wanted to experiment with the metrics module and
how to upgrade it to 4.0. First I wanted to make
some changes in the package structure: move all
XXXMetrics classes into a spi subpackage.
Refactoring complains, and some other component
also (I don't remember at the moment, but this has
also been a problem with 3.5 versions, so You
probably will remember). That's more or less as
expected, as NB is still not even beta, so didn't
matter. After moving the classes I restarted the
NB4.0dev. First time: hanging up, had to kill it
from the task manager. Second time: Started, but
with an error message. For more information I
attach the startup log.
Comment 1 Peter Nabbefeld 2004-08-03 07:58:06 UTC
Created attachment 16620 [details]
My startup log (I've not yet shut down NB)
Comment 2 Peter Nabbefeld 2004-08-03 08:13:16 UTC
Just found out, that CompositionViolationException is thrown because
of the invalid package (moving between packages does not update the
pacake-declaration!!!). However, an invalid package may not result in
an exception. The unfamous "Exception in RequestProcessor" is thrown
several times while manually correcting the package-declaration.

BTW: I'm using a Maven project running the mevenide bridge. However,
this should be independent of my problems, because SourceGroup objects
are used to detect packages etc., IMO only an improper constant
expression (such as sometimes used in hotfixes) might cause problems here.
Comment 3 Martin Matula 2004-08-03 09:11:34 UTC

*** This issue has been marked as a duplicate of 46291 ***