Hi all,
i have to partially reset what i said in my previous post.
Probably i made some mistake pasting the properties file path and perhaps that's the reason why the --properties option was ignored.
Anyhow creating again the runtime and server i'm now able to use the --properties option.
Nonetheless when i edit the launch config to add the --properties option it is decorated with a red error marker and this msg "Configuration can only be changed by modifying the server's runtime."

Then i wish to signal some more glitches that perhaps are due to the alpha status, but may be are slipped through the tests.

1- the server launch config is not shown in the "Run configurations" panel

(all the following are related to the Properties view of XML Configuration/Ports)
2- when the xpath matches only a single location, the name is shown but the location is not
3- the Properties view is not refeshed. Subsequent stop/start of the server still continues to show the location of /tmp/deploy/tmpxxxxxjboss-service.xml of the first launch that is no longer in the tmp directory. The "Edit file" then silently fails. The "Refresh item" of the ports category has no effect.
4- the "JNDI" and "JNDI RMI" xpaths never show the locations even if they have more than one match (two when the server is stopped, three when started)

(these are really whishes and not bugs)
the server has no support for ${jboss.server.base.dir} and ${jboss.server.base.url} configuration properties, this means that:

5- the xpath processor always tries to match into the tmp relative to ${jboss.home.dir} also when the runtime tmp is the one relative to ${jboss.server.base.dir}

6- the xpath processor always matches into the conf relative to ${jboss.home.dir} also while the runtime conf is the one relative to ${jboss.server.base.dir}

would it be possible to integrate support for those JBoss advanced configuration properties?

Hi Rob,
first of all, WOW!! In the mean time i peeked around a bit in the doc and if your beast maintains just half of the promises i see there, it looks really great!

I cannot repeat hte launch configuration issue in the current TRUNK stream. I must have made the launch configuration more liberal some time ago.

1) You must create a server via servers and runtimes. The API provided by webtools does not allow willy nilly launch configuration creation.

2) This is a feature. If you'd like an option / property to customize, file a JIRA for it

3) The XPath portion is unique becuase I clearly can't have it refreshing and scanning files for differences left and right. The original scan takes quite a while and so it is cached. I'll have to think about a solution. For now, does right-clicking on the element in the JBoss Server's view and clicking "refresh" fix it?

4) Will have to look into it

5) I believe I used to have support for this. I'll have to double check if there was a regression somewhere.

6) Dependent on 5 obviously.

Hi Rob,
I do not agree with myself!

Sure, you are right, even the WTP defaut JBoss server is not there.