[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5468) Server instance not allways created when creating new runtime

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5468:
------------------------------------

It's fixable, but some fo the WTP stuff there took a while to debug. So annoying.  Basically, I've had to change my defaults method to set the server id as something like the server's first name followed by a timestamp. 

During my testing i observed the following also:
  create server EAP
  rename server to EPP
  create new server EXP
  try to rename EXP to EAP (fail)
  try to rename EXP to EPP (fail)

Basically, the new server cannot share a name *or* an id with the old server. So from now on new servers will have an id with a timestamp somewhere in it to reduce collisions. 

> Server instance not allways created when creating new runtime
> -------------------------------------------------------------
>
>                 Key: JBIDE-5468
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5468
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.CR1
>            Reporter: Dominik Pospisil
>            Assignee: Rob Stryker
>             Fix For: 3.1.1
>
>
> When creating new server runtime, associated server instance is not allways created as expected (even if create local server checkbox is selected).
> Steps to reproduce:
> 1. Create new runtime (e.g. JBoss EAP 4.3 Runtime) with non-default name (e.g. JBoss EPP 4.3 Runtime)
> 2. Rename created server to non-default name (JBoss EPP 4.3 Runtime Server)
> 3. Now we have EPP runtime and EPP server
> 4. Create new runtime of the same type (JBoss EAP 4.3 Runtime)
> 5. Corresponding server is not created (JBoss EAP 4.3 Runtime Server)

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