[jbosstools-issues] [JBoss JIRA] Assigned: (JBIDE-5036) JDT Internal Error connected with JBossAS while java method renaming

Rob Stryker (JIRA) jira-events at lists.jboss.org
Tue Oct 27 18:47:05 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker reassigned JBIDE-5036:
----------------------------------

    Assignee: Snjezana Peco  (was: Rob Stryker)


This bug has to do with jaxb-xjc.jar being a weird jar.  

Basically, our AS has the jaxb-xjc.jar in the client folder. This jar seems to have a non-standard format which confuses eclipse and makes the refactor blow up because jdt (java development toolkit) gets very confused. The problem with jaxb-xjc.jar is that it has a folder named 1.0.

Basically, JDT is looking on the classpath and going through all the jars on the classpath to see what is affected by this refactor. While scanning the jaxb-xjc.jar file, it finds a folder named 1.0.  Under that folder it finds other folders with class files inside them. It assumes "1.0" is a package fragment, then, but it's name violates package fragment rules, and so it blows up. 

I'm going to assign this to Snjezana. If she thinks this should be reported to eclipse she can go ahead and do that. 



> JDT Internal Error connected with JBossAS while java method renaming 
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-5036
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5036
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.M3
>            Reporter: Daniel Azarov
>            Assignee: Snjezana Peco
>
> Testcase:
> 1. Create jsf KickStart project with JBossAS
> 2. Open \JavaSource\demo\User.java in java editor
> 3. Select getName() method name
> 4. Mouse right click
> 5. Select Refactor->Rename
> 6. Type new name, "getName2" for instance
> 7. Press Enter
> FAIL:
> java.lang.reflect.InvocationTargetException
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:91)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
> at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
> at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113)
> at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143)
> at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224)
> at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> ... 1 more
> Root exception:
> Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
> at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
> at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113)
> at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360)
> at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143)
> at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224)
> at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list