Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Server component

Hi Ed,

The wst.server component is currently focussed on "servers that you can develop and publish content to", since those are the types of servers that we're mainly interested in. That said, AFAIK it doesn't (and shouldn't) force the server to accept content and should be a usable base for any kind of server. All publishing and module related parts of the API should be optional or easy to provide null implementations for.

Anywhere this isn't the case, you're welcome to open defects and/or provide patches. If you have any other suggestions or input on how to support both types of servers effectively, please feel free to contact me offline and we can email or arrange a meeting.

Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)

"Ed Burnette" <Ed.Burnette@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

04/12/2005 10:39 AM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
[wtp-dev] Server component

Is the wst.server component intended for use for things other than web and application servers? For example, database servers, business intelligence servers, and so on. I took a look at it but the concept of publishing and models seems pretty well entrenched in the API and user interface. What I needed was something that could monitor server health, remember connection passwords, start and stop servers, and provide a naming service for other tools that need to connect to a server (so every tool doesn't have to have its own define server command and server list).
wtp-dev mailing list

Back to the top