[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6314) NPE on every start of eclipse

[Viacheslav Kabanovich (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534189#action_12534189 ] 

Viacheslav Kabanovich commented on JBIDE-6314:
----------------------------------------------

The troublemaker entry is /hibernate-distribution-3.5.2-Final.pom which starts with '/' while usually all file entries in the root of jar do not have it as leading symbol. I can easily modify my code to check for it, but it seems that Eclipse itself is not happy about it. Find hibernate3.jar Package Explorer under libraries of a project, navigate to hibernate-distribution-3.5.2-Final.pom and try to open it. Editor fails. So, what should we do. May we ask provider of hibernate3.jar to modify the entry path as erroneous, or should we report to Bugzilla on Eclipse failure to process such entries?

> NPE on every start of eclipse
> -----------------------------
>
>                 Key: JBIDE-6314
>                 URL: https://jira.jboss.org/browse/JBIDE-6314
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 3.2.next
>         Environment: nightly build 201005181730
> java.version=1.6.0_16
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG
> Framework arguments:  -product org.eclipse.epp.package.jee.product
> Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product -clean
>            Reporter: Krasimir Goutcev
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.2.next
>
>         Attachments: hibernate3.jar
>
>
> An internal error occurred during: "JBoss Tools Model Update".
> log:
> java.lang.NullPointerException
> at java.util.zip.ZipFile.getInputStream(ZipFile.java:180)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:200)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:235)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:90)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:74)
> at org.jboss.tools.common.model.filesystems.impl.JarSystemImpl.loadChildren(JarSystemImpl.java:46)
> at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:140)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:131)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:335)
> at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJar(TaglibMapping.java:224)
> at org.jboss.tools.jst.web.tld.TaglibMapping.findTldsInJars(TaglibMapping.java:208)
> at org.jboss.tools.jst.web.tld.TaglibMapping.revalidate(TaglibMapping.java:84)
> at org.jboss.tools.jsf.web.JSFWatcherContributor.updateProject(JSFWatcherContributor.java:49)
> at org.jboss.tools.common.model.project.Watcher.updateAll(Watcher.java:106)
> at org.jboss.tools.common.model.project.Watcher.access$0(Watcher.java:89)
> at org.jboss.tools.common.model.project.Watcher$WatcherRunnable.run(Watcher.java:47)
> at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:158)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

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