Also wanted to make sure that you felt welcome to participate in refining and improving WTP’s server integration api.
Typically we communicate suggestions via bugzilla reports, but I think it may be a good time to schedule a design phone call to discuss any 1.5 and beyond changes in the server area.
One particular topic that I would throw out there is reconciliation of the facet runtime and server tools runtime api. We postponed doing this for 1.0, hopefully this is something we can take up again, because I think there’s good opportunity for extensibility of server representations that is hard to implement with the current bridging mechanism.
-Ted
Vincent,
Yes, we're always open to collaboration. I can imagine several ways to proceed. Do any of the following make sense?
1. You could create a WTP server adapter for any cargo container. Presumably that would enable existing cargo containers to integrate with WTP.
2. You could create a cargo adapter for existing WTP adapters. That would let them run in different environments.
3. You could propose a new API for WTP.
You could do 1 or 2 at either cargo or WTP depending on the licences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
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
Hi everyone,
Thanks to Sachin Patel I've had a look today at the WST/JST API for wrapping
servers and I've noticed that there's a clear overlap with Cargo
(http://cargo.codehaus.org). Actually I've known about WTP for some time (I
even sent an email in may 2005 to propose some collaboration but
unfortunately I never got an answer) but it's only this morning that I
started looking into it in more details.
Cargo is a framework I've started about a year and half ago with the goal of
offering a Java API for manipulating servers (we call them containers).
Cargo offers a API for starting, stopping, configuring containers and
deploying modules to them. It has a core API and quite a lot of container
implementations. Cargo's main goal is to make it easy for anyone who needs
to manipulate containers, like IDEs, automated builds, etc.
Cargo is meant to be agnostic to its execution environment so that users can
use it all different kinds of situations. However we've implemented some
extensions that use the Cargo Java API. For example we have Ant tasks,
maven1 plugin, maven2 plugin, netbeans and intellij IDEA plugins, etc. All
those extensions are generic and using the core Cargo Java API.
While reading
http://www.eclipse.org/webtools/wst/components/server/api_concepts.html this
morning I realized how similar the Cargo and the WST API are.
I thought I should discuss this with you and see what are the options and
how we could possibly collaborate instead of redoing the same things...
WDYT? Do you think there's some possibility of collaboration? I'm very open
to any idea.
Thanks a lot
-Vincent
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
