[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4912) NPE during publish in PublishCopyUtil.copyFile()

[Darryl Miles (JIRA)]

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

Darryl Miles commented on JBIDE-4912:
-------------------------------------

>> What do you mean 'restoring components.xml on bootup'?

When you start up eclipse, you get a splash screen with initialization of plugins text that changed.  Then the splash screen disappears.  Then the workbench appears setup in the perspective you were using at the time you last shutdown, inside that perspective you have "editors" to edit files, this maybe text editor, this maybe XML editor, etc....

Well I guess there is a special editor for Seam's "WEB-INF/components.xml".  So the stack trace I posted in the 2nd and 3rd comment that related to XModel are from bootup, a bootup that was probably "restoring the components.xml editor" at the time.  Restoring as in from the workbench.xml settings file (that maintains visual state of your workbench/perspectives over eclipse restarts).  So this is why I was seeing the Error Log info during bootup, if I close all my editors and restart eclispe I don't get to see the error.


I twigged (understood) this once I witnessed the stack trace from my last comment, the one with the contents of my components.xml.  The special situation that existed at that time was that I has just restarted eclipse but the perspective I was in, did not have any editors on display.  I switched to my Java perspective which does have editors open (and WEB-INF/components.xml was one of them), when I first clicked on it's tab (to active that editor, bring it into focus) I then got this stack trace.  This is how I understand the cause of the stack trace to be related to the editor not the bootup process.

PS The exact details of when the stack trace occurred might be incorrect, it might not be when I first brought the editor into focus, it might be at the time I first switched to Java perspective.


> NPE during publish in PublishCopyUtil.copyFile()
> ------------------------------------------------
>
>                 Key: JBIDE-4912
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4912
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: XML Structured Editor
>    Affects Versions: 3.1.0.M2
>            Reporter: Darryl Miles
>            Assignee: Viacheslav Kabanovich
>
> If it is not a JBoss AS Driver bug, i.e. it maybe an Eclipse WTP bug passing null's into lists etc..., then the driver needs to be hardened to it.
> java.lang.NullPointerException
> 	at java.io.FileInputStream.<init>(FileInputStream.java:103)
> 	at org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.copyFile(PublishCopyUtil.java:456)
> 	at org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.copy(PublishCopyUtil.java:506)
> 	at org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.publishFull(PublishCopyUtil.java:482)
> 	at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:121)
> 	at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:101)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:82)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1038)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
> 	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
> 	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
> 	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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira