From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Arthur Ryman
Sent: Thursday, June 16, 2005 7:14
PM
To: General
discussion of project-wide or architectural issues.
Cc: General
discussion of project-wide or architectural issues.;
wtp-dev-bounces@xxxxxxxxxxx
Subject: RE: [wtp-dev] Remote
Server Support
Thomas,
Yes,
I believe we cited both JSR 77 and JSR 88 in our plans. We need to start making
progress on those.
Arthur Ryman,
Rational Desktop Tools Development
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/
"Thomas Yip"
<tyip@xxxxxxx>
Sent
by: wtp-dev-bounces@xxxxxxxxxxx
06/16/2005 08:06 PM
Please
respond to
"General discussion of project-wide or
architectural issues."
|
|
To
|
"General
discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [wtp-dev] Remote Server Support
|
|
For deployment, I think “JSR 88: J2EE Application
Deployment” is the way to go.
It defines a standard way of deploy/undeploy/start/stop an
application. Looking at the expert groups, the momentum is there.
However, I haven’t heard many vendors have implemented
them in their release version. When it is ready, we certainly want to help on
getting the control and ui in WTP.
I believe debugging and profiling support doesn’t
require much modification.
I am not sure there is a defacto way of using JMX for remote
starting and stopping of server. Maybe the assumption is that the server is
always up and running during the development.
Thomas
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Arthur Ryman
Sent: Thursday, June 16, 2005 2:34 PM
To: gerry.kessler@xxxxxxxxxx; General
discussion of project-wide or architectural issues.
Cc: wtp-dev@xxxxxxxxxxx; wtp-dev-bounces@xxxxxxxxxxx
Subject: RE: [wtp-dev] Remote Server Support
Gerry,
Tim Deboer is the authoritative source on this topic. However, the current
support does not require JMX. You can use any proprietary means of controlling
the server. Our intension is to move towards the JCP standards in this area
such as JSR 77. Are you interesting in working on that?
Aside from publishing, you should support debugging and profiling. You should
also be able to restart the server or a specific application, and do the usual
config such as adding or deleting applications.
Arthur Ryman,
Rational Desktop Tools Development
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/
"Gerry Kessler"
<gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
06/16/2005 04:49 PM
Please
respond to
"gerry.kessler@xxxxxxxxxx" and "General
discussion of project-wide or architectural issues."
|
|
To
|
Arthur Ryman/Toronto/IBM@IBMCA,
"wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [wtp-dev] Remote Server Support
|
|
Arthur,
Thanks for the response - I do understand that a remote server would require a
controller of some kind like JMX to manage it. More specifically, I am
looking to find out what services, if any, the WTP framework supplies for
remote servers. If there are services, how do I plugin to them?
What are the implied requirements for "supporting" a remote host?
Clearly publishing to it is a must-have as there would be little point
without it. What else?
Thanks,
Gerry Kessler
Oracle
-----Original Message-----
From: Arthur Ryman [mailto:ryman@xxxxxxxxxx]
Sent: Thursday, June 16, 2005 12:47 PM
To: gerry.kessler@xxxxxxxxxx; General
discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Remote Server Support
Gerry,
A remote server is a server that is located on another machine. You need some
type of controller on that machine, or use JMX.
Arthur Ryman,
Rational Desktop Tools Development
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/
"Gerry Kessler"
<gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
06/16/2005 03:01 PM
Please
respond to
"gerry.kessler@xxxxxxxxxx" and "General
discussion of project-wide or architectural issues."
|
|
To
|
"wtp-dev@xxxxxxxxxxx"
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
[wtp-dev] Remote Server Support
|
|
Tim deBoer posted the following in the newsgroup recently:
"The WTP
server framework fully supports remote servers, however none of the
current server types that have been contributed to WTP do. There are no
immediate plans for remote server support, but contributions may appear in
later versions."
Could someone please clarify what is meant by "supports remote
servers"? What does the framework provide? What would the
server provider be expected to provide? Documentation?
Thanks,
Gerry Kessler
Oracle_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev