Hiya,
So you're proposing we ship a drop in plugin for the STP project in the
distribution kit? Could we make it a separate download? It could even be
a sub project of sorts. Or, might create a bundled version of STP+CXF
ourselves? Or might we have it as an eclipse plugin that can be
downloaded for our update site?
- Dan
Oisin Hurley wrote:
Daniel Kulp wrote:
If the STP project had something we can ship so the kits would have a
completely usable set of eclipse tooling, then I'd be quite OK with
including this and the STP stuff together in the kits.
You need to explain what you mean by 'completely usable set'
- we're always looking for suggestions and feedback for scenarios
on stp-dev.
I doubt you want to include the entire STP and dependencies in
your kits, unless you would enjoy making the cxf kits about
oooh 250MB :) However, the JAX-WS supporting stuff from
the development side, i.e. the annotations framework, automatic
code generation and incremental build, is relatively small -
once you get into WSDL editing and deployment to Tomcat, etc
you need to start picking up more material.
Thus, give us something useful to ship that provides value to the
users. :-)
You have to remember that the JAX-WS dev support and deployment
is only a small piece of the STP goals - there are 4 other
subprojects in there that are the same size or larger. We're
working with cxf as the exemplar runtime for JAX-WS development
and deployment, but the thing is designed to run with any other
JAX-WS runtime, and will be developed to include other runtimes.
There is actually a case that you could make that the
cxf exemplar extensions should actually be shipped by cxf and
not by STP at all, since it isn't scalable for the project to
supply extension instances for all the runtimes it will need
to support.
--oh
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
