[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-3896) Add possibility to create a new JBoss AS profile when create a new server

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-3896.
--------------------------------

    Resolution: Done


This is on the server page and *not* the runtime page. The reason it is on the server page is because it is primarily a feature of dealing with the server and not of the runtime.

A runtime is primarily used for setting up project classpaths. The runtime object stores only the home location and the configuration name. Since the wizard only allows you to make direct copies and not pick and choose which jars you want to copy, the configuration the server uses is an exact clone of the one the runtime uses. 

To enable a runtime to have a cloned configuration somewhere in project metadata would have required changing several of the classpath providers to be on the lookout for this. It would have been a lot more work with zero gain since the cloned runtime in workspace metadata would have been the exact same as the one in the actual installation folder.

Additionally, if the runtime were the object cloning the server, then the following scenerio would not work in terms of isolation:
 1) create a runtime (clone from default)
 2) create a server (serverA) from the runtime
 3) create a server (serverB) from the runtime

In this case, serverA and serverB would actually be referencing the exact same location on disk, and thus not isolating themselves from each other. If the user wanted to properly separate the two he'd need a new runtime for each server he makes. Because the new server wizard pre-populates the runtime list with the last-used runtime and does not easily allow for a new runtime without a good 6 or 7 more clicks, this would have been a big big pain for the user. 

So instead, you can create one runtime for the default configuration (for example) and then create 3 servers referencing that runtime but cloning it at the moment the server is created. This makes the wizard flow a lot better and still allows each server to have their own configuration in metadata. 
---
The talk about changes not persisting referred specifically to the launch configuration. It is designating this field (jboss.server.base.url) to be one of the untouchable fields that the launch configuration will always overwrite. See the comments in JBIDE-3073 



> Add possibility to create a new JBoss AS profile when create a new server
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-3896
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3896
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 3.0.0.CR2
>         Environment: JBDS 2.0.0.CR2
>            Reporter: Joao Paulo Viragine
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.1.0.M1
>
>         Attachments: JBIDE-3896.jpg
>
>
> When we are developing, sometimes we need various JBoss AS profiles.
> It would be nice if we could create a new JBoss AS profile (to preserve default or production original) when create a new server
> .
> JBDS/JBoss Tools may ask for base profile (for be based on) and then make a "copy" (only conf, deploy and lib folders) to the new specified profile name.

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