Re: [jbosstools-dev] Export/Import Runtime/Servers?
It seems this has been fixed in HEAD and will be out in M7.
Specifically, server id's are now equal to the server name! (AWESOME!!)
In this way, importing a launch configuration *should* work... or at
least is no longer as unfeasible. Obviously I'd have to do more tests to
know for sure just how easy it is, and if an import / export server
action might be appropriate, but, at the very least, the big hurdle I
imagined is no longer there.
Both examples below were made with the generic jboss adapter:
Previous server example:
<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
<server hostname="localhost" *id="4_29_08_7_12_PM5"
name="JBOSS 4.2"
runtime-id="
JBoss v4.2"* server-type="org.eclipse.jst.server.generic.jboss42"
server-type-id=
"org.eclipse.jst.server.generic.jboss42" timestamp="1">
<map jndiPort="1099" key="generic_server_instance_properties"
port="8080" serv
erAddress="127.0.0.1" serverConfig="default"/>
</server>
M7 example:
<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
<server hostname="localhost" *id="JBoss v4.2 at localhost"
name="JBoss
v4.2 at localhost" runtime-id="JBoss v4.2"*
server-type="org.eclipse.jst.server.generic.jboss42" server-type-
id="org.eclipse.jst.server.generic.jboss42" start-timeout="50000"
stop-timeout="15000" timestamp="3">
<map jndiPort="1099" key="generic_server_instance_properties"
port="8080" serverAddress="127.0.0.1"
serverConfig="default"/>
</server>
Max Rydahl Andersen wrote:
On Wed, 30 Apr 2008 00:02:50 +0200, Rob Stryker
<rob.stryker(a)redhat.com> wrote:
> No that is not a way.
>
> Unfortunately, webtools links the launch configuration with a specific
> server, and it does so by server *id*, NOT name. This causes breakages
> because even if you create a new server there is practically zero chance
> it has the same id as the launch configuration you're importing.
>
So what is the purpose of being able to save the launch config outside of the workspace
metadata?
-max
> I'm thinking of making an import action from launch configuration files,
> but from what I've been able to tell so far it'd require much more than
> just the launch configuration and I'm not even entirely sure it's possible.
>
> I'll look into it. I might need to make an export and import in order
> to do both.
>
> - RS
>
> Max Rydahl Andersen wrote:
>
>> what about the option of storing the launch config in a seperate project ? is
that not also a doable way ?
>>
>> We actually shuold get these things into the userdocs for the AS doc - hint
hint.
>>
>> /max
>>
>>
>>
>>> (QFT) quoted for truth
>>>
>>>
>>>> Use the same workspace should work ;)
>>>>
>>>> /max
>>>>
>>>>
>>>>
>>
>>
>>
>