[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6975) Could not publish to the server.

[Rob Stryker (JIRA)]

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

Rob Stryker updated JBIDE-6975:
-------------------------------

    Fix Version/s: 3.2.0.Beta1
                       (was: 3.2.0.Beta2)


I've just discovered that hte single deployable factory *often* can't find its modules. It loads them fine from the project, but the module id is stored in relative form in the data file, but absolute form in the module id. 

Since all paths should be project relative, and since some modules already deployed use the absolute form, the module factory must now respond to both absolute and relative paths to avoid breakage. This has a big effect on remote publishing as if the module is not found, the framework creates a DeletedModule in its place which is not marked as binary and breaks deployment. 

Feh. 

> Could not publish to the server.
> --------------------------------
>
>                 Key: JBIDE-6975
>                 URL: https://jira.jboss.org/browse/JBIDE-6975
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.M2
>            Reporter: Alexey Kazakov
>            Assignee: Rob Stryker
>             Fix For: 3.2.0.Beta1
>
>
> 1. Create a seam web project. Use JBoss AS 5.0 or 6.0 (didn't try others) as target servers.
> 2. Run the application on the server.
> 3. Error window appears with message that there is a problem with publishing.
> 4. See the log:
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:231)
> at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:154)
> at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:93)
> at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1016)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1106)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:939)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2888)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> It seems that the project has been published correctly in spite of the error message.
> Rob, let me know if you can't reproduce it. I will try to get more details.

-- 
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