I must had missed your note, my apologies.
I think that was the day that the coffee machine was broken.. :)
I am one of the developers for servertools
but unfortunately I haven't played too much with the InstallableRuntime
extension point. Tim (the other developers) is out of the office right
now, so I am left with the task of adventuring into exploring his code.
1) This extension points represents
a downloadable adapter. Which means a set of plugins and features that
are not included in wtp but that can be downloaded to add a new Server
Adapter to the environment. This functionality is exposed via the "Download
additional server adapters" link on the top right of the "New
Server Runtime Environment".
2) Correct many of the plugins use it,
but it is exposed as an early adopter. We are still finalizing the API
and its extension point, if you have any input we will be glad to hear
3) Without knowing what version of WTP
you are using I can only say that HEAD is probably not what you want to
checkout. HEAD corresponds to our current in development build, which changes
very frequently :). We have created branches for our releases, so if you
are using something other than the 3.0 nightly builds, you might need to
use one of our branches.
4) We introduce this "installable"
button recently, and haven't completed the changes. It sounds like you
have some UI suggestions and improvements :) so I will encourage you to
open a bug so that we can work together on how to improve the UI, we are
always glad to hear from our community.
Let me know if you have more question..
Mr. Angel Vera
Server Tools Developer for WTP and Rational
Lotus Notes: Angel Vera/Toronto/IBM@IBMCA
Tel: 905-413-5919 - E-Mail: arvera@xxxxxxxxxx
Those who think that something is impossible,
should not interfere with those who are willing to do it. - Angel Vera
raccah@xxxxxxxxxxxx Sent by: wtp-dev-bounces@xxxxxxxxxxx
04/03/2008 07:46 PM
Please respond to
"General discussion of project-wide or architectural issues."
[wtp-dev] Re: Direction on using installable
I have not received a response, but have made some
progress, so I'll
update the note below with my findings and would appreciate if someone
can help with the remaining issues. #4 is the most important.
> I found this:
> which warns that it's an interim API and subject to change....
> My questions:
> 1) Am I correct in interpreting the purpose of this extension to allow
> plugin developer a way to install a runtime (like an application server)
> and not just a feature or plugin? The structure of the attributes
> an example site.xml I found leave me unsure.
Yes, that is what it does.
> 2) If yes, what is the stability of this API now? Does the interim
> warning mean that it's best I don't use it or just that there may
> some minor changes before the final release?
I still don't know about the stability, but many of the plugins use it.
> 3) The examples in the page don't use URLs, but when I tried with
> path, I just got an error like invalid URL. So, since I'm trying
> test one of these locally, I tried using a file:/// url. Apparently,
> still don't have all the path components right and debugging gets
> the source of InstallableRuntimeDecorator (in jst), but not
> InstallableRuntime (in wst). Being an eclipse newbie, I'm not
> to rectify that. I believe I need to download the source from
> and configure it to be used in my debugging session, but could not
> the right jar on the download site or the right option to configure.
> someone point me in the right direction?
I was able to check the source out of cvs, but it does not match the
version of eclipse I have, so I still could not debug. I have found
some of the downloads on the site offer source (preconfigured for
debugging as a plugin), but not for this code. What I was really
looking for is that kind of plugin for this set of source.
> 4) Finally, the default wizard page contains "Application Server
> Directory" with Browse and the Install Server button which also
> a Choose Directory dialog. Why is this information gathered
Okay, so I have some of this working sort of, but the default wizard
layout and behavior offers no feedback to a user! It has the JRE
configuration, the App server directory with Browse, and the Install
Server button. I see these use cases:
a) User puts in a non-existent dir - works correctly: status message at
top that it doesn't exist
b) User puts in a real dir but there is no appserver installed there -
this is where the install server button is helpful, but the first thing
it does is popup a directory chooser and ask the user where to put it
again! Worse, after the user chooses it, it is silently installed
<dir>/<server> but the app server directory field is not updated
the new directory, so it is still not recognized as a valid server. I
didn't even know an install happened at all until I looked on disk
several hours later.
What I think should happen: Status message at top should say no server
there but can install one, dir chooser should only come up if field is
blank and should be updated after the installation.
c) User puts in a directory that contains an appserver installation -
this works correctly, except I think the install button should be disabled.
Based on my (newbie) investigation of the code, I cannot fix this
without rewriting the wizard fragment, all decorators, etc. It seems
me that I am actually not requesting anything custom here - just
requesting that the built in support work in a way that would make sense
to a user. If not, I'd be happy to supply an alternate wizard fragment,
but would prefer to use as much as possible without replacing everything.