[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- This is what is written in the workspace log: {noformat} !STACK 0 org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.core.runtime.Path.initialize(Path.java:577) at org.eclipse.core.runtime.Path.<init>(Path.java:163) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.loadRemoteDeploymentDetails(RSEPublishMethod.java:160) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishStart(RSEPublishMethod.java:58) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:56) at org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.publishStart(JBossServerBehavior.java:111) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:927) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3029) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:341) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9334: ------------------------------------ I am not able to replicate this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- Rob, I just tried the scenario from this JIRA's description on a fresh workspace on a Mac and then again on Linux 64bit and I could reproduce it both times. I was using JBT 3.3.0.M2 build H7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Rob Stryker edited comment on JBIDE-9334 at 7/18/11 9:22 AM: ------------------------------------------------------------- " 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." I am 100% unable to replicate this and I've just tested again. When switching the combo in the Server creation wizard from "local" to "rse", I get the following stack trace: ServerWorkingCopy.setAttribute(String, String) line: 188 ServerModeSectionComposite$ChangeServerPropertyCommand.execute() line: 221 ServerModeSectionComposite$ChangeServerPropertyCommand(ServerCommand).execute(IProgressMonitor, IAdaptable) line: 39 JBossServerWizardFragment$NewServerWizardBehaviourCallback.execute(IUndoableOperation) line: 185 ServerModeSectionComposite.deployTypeChanged(boolean) line: 178 ServerModeSectionComposite.access$1(ServerModeSectionComposite, boolean) line: 168 ServerModeSectionComposite$2.modifyText(ModifyEvent) line: 117 TypedListener.handleEvent(Event) line: 179 EventTable.sendEvent(Event) line: 84 Combo(Widget).sendEvent(Event) line: 1258 The value of the first setAttribute(a,b) is "org.jboss.ide.eclipse.as.core.server.serverMode" and "rse". The value of the second setAttribute(a,b) is "org.jboss.ide.eclipse.as.core.server.deployDirectoryType", "server" The second attribute, deployDirectoryType, is NOT set again for the remainder of the wizard. Upon pressing finish, the server is created, Opening the server and switching to the second page to check the deployment shows the following: 1) The metadata option is grey 2) The "JBoss Deploy folder" radio button is selected. I am, again, 100% incapable of replicating this. Seriously. was (Author: rob.stryker): : 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 I am 100% unable to replicate this and I've just tested again. When switching the combo in the Server creation wizard from "local" to "rse", I get the following stack trace: ServerWorkingCopy.setAttribute(String, String) line: 188 ServerModeSectionComposite$ChangeServerPropertyCommand.execute() line: 221 ServerModeSectionComposite$ChangeServerPropertyCommand(ServerCommand).execute(IProgressMonitor, IAdaptable) line: 39 JBossServerWizardFragment$NewServerWizardBehaviourCallback.execute(IUndoableOperation) line: 185 ServerModeSectionComposite.deployTypeChanged(boolean) line: 178 ServerModeSectionComposite.access$1(ServerModeSectionComposite, boolean) line: 168 ServerModeSectionComposite$2.modifyText(ModifyEvent) line: 117 TypedListener.handleEvent(Event) line: 179 EventTable.sendEvent(Event) line: 84 Combo(Widget).sendEvent(Event) line: 1258 The value of the first setAttribute(a,b) is "org.jboss.ide.eclipse.as.core.server.serverMode" and "rse". The value of the second setAttribute(a,b) is "org.jboss.ide.eclipse.as.core.server.deployDirectoryType", "server" The second attribute, deployDirectoryType, is NOT set again for the remainder of the wizard. Upon pressing finish, the server is created, Opening the server and switching to the second page to check the deployment shows the following: 1) The metadata option is grey 2) The "JBoss Deploy folder" radio button is selected. I am, again, 100% incapable of replicating this. Seriously. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9334: ------------------------------------ Attachment: deploy-folder.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9334 at 7/18/11 11:20 AM: ------------------------------------------------------------------- I tried to replicate this, too but could not either !deploy-folder.png! I created a server in remote mode directly, then switched it back to local mode and went to the 2nd page to check the deploy folder option. it was in the 2nd position. Then I went back to the 1st page, switched it back to remote mode, saved and checked the deploy folder option again. It is still in the 2nd position for me. !overview.png! What am I missing? was (Author: adietish): I tried to replicate this, too but could not either !deploy-folder.png! I created a server in remote mode directly, then switched it back to local mode and went to the 2nd page to check the deploy folder option. it was in the 2nd position. Then I went back to the 1st page, switched it back to remote mode, saved and checked the deploy folder option again. It is still in the 2nd position for me. What am I missing? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- I recorded my steps here: http://screencast.com/t/e7pR0LVjUe now I'm really curious if I'm doing something completely wrong or what :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina edited comment on JBIDE-9334 at 7/18/11 12:09 PM: ---------------------------------------------------------------- I recorded my steps here: http://screencast.com/t/VpnvSRsovK now I'm really curious if I'm doing something completely wrong or what :) was (Author: mmalina): I recorded my steps here: http://screencast.com/t/e7pR0LVjUe now I'm really curious if I'm doing something completely wrong or what :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- This is the other issue that I previously described: http://screencast.com/t/SedkOCsa0ZN What it demonstrates is that if you have a local server deploying to server, than switch to remote and back to local, it is switched to metadata deployment (even if it was set to server deployment at the very beginning). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- OK, so I tried again today. Brand new installation of JBT 3.3.0.M2 [1] on top of Eclipse Indigo [2]. Still the same problem. Recorded here: http://screencast.com/t/d0u73RaI I seriously don't understand how come you can't see what I see. What could be broken on my side? [1] http://download.jboss.org/jbosstools/updates/development/indigo/ [2] http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9334: -------------------------------------- And I just verified again that immediately when I try to start the remote server (with the wrong deployment settings) I get an error message immediately, telling me that it cannot publish to the server. (see my earlier screenshot - errorMsg.jpg). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9334: ------------------------------------ Attachment: create-eap5.ogv -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9334: ------------------------------------ Thank christ. I thought I was going crazy being unable to replicate it ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9334?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9334. -------------------------------- Verified in jbosstools-3.3.0.M3-M3-H14 . -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira