[jbosstools-issues] [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying

[Stefan Bunciak (JIRA)]

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

Stefan Bunciak edited comment on JBIDE-11850 at 5/22/12 10:08 AM:
------------------------------------------------------------------

@Max:
I've figured out a solution (probably little complicated), please comment:
* while creating/importing OpenShift application we do *know* its type, so
* we can save the type as properties to : 
** <project>/.settings/org.jboss.tools.openshift.express.ui.prefs (application)
** <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml (server)
* then we can compare their types and decide (but handle the case when there is not such information)

WDYT of it?
                
      was (Author: sbunciak):
    @Max:
I've figured out a solution, please comment:
* while creating/importing OpenShift application we do *know* its type, so
* we can save the type as properties to : 
** <project>/.settings/org.jboss.tools.openshift.express.ui.prefs (application)
** <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml (server)
* then we can compare their types and decide (but handle the case when there is not such information)

WDYT of it?
                  
> error when changing to ruby project and deploying
> -------------------------------------------------
>
>                 Key: JBIDE-11850
>                 URL: https://issues.jboss.org/browse/JBIDE-11850
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: JBossAS/Servers, openshift
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Stefan Bunciak
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.3.0.CR1
>
>
> From my point of view does not make sense to allow users to switch deploy project from JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app instead of JBoss a NPE was thrown:
> {code}
> java.lang.NullPointerException
> 	at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
> 	at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> 	at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
> 	at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
> 	at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira