[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9334) Cannot publish to remote EAP 5.1

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-9334:
--------------------------------------

Rob, how recent a patch are we talking?
I can confirm what you say - if you create a local server and then change it to RSE, it automatically changes to Server deployment. However, there is one problem: If you change it back to local, it will change to metadata deployment even if it was set to Server deployment before.
Steps:
1) Create a new EAP 5.1 server, as local
2) Double-click server
3) Go to page 2, verify server deploys to "server"
5) Go to page 1, switch from local to RSE
6) Go to page 2, verify server now deploys to 'server' rather than the metadata.
7) Go to page 1, change back to local
8) Go to page 2, the server deploys to "metadata" - fail

Also, my original issue still holds true - try creating a RSE server rightaway (not creating local and changing it to RSE) and you will see deployment is set to metadata even though it is greyed out - a screenshot will follow.

> Cannot publish to remote EAP 5.1
> --------------------------------
>
>                 Key: JBIDE-9334
>                 URL: https://issues.jboss.org/browse/JBIDE-9334
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.3.0.M2
>         Environment: Mac OS X 10.6 Snow Leopard
>            Reporter: Martin Malina
>            Assignee: Martin Malina
>             Fix For: 3.3.0.M3
>
>         Attachments: errorMsg.jpg
>
>
> Scenario:
> 1. Start JBT with a fresh workspace
> 2. Create a simple dynamic web project
> 3. Add a local EAP 5.1 server runtime + server adapter
> 4. Add a remote EAP 5.1 server adapter
> 5. Start the remote server
> 6. An error message will pop up

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira