if we call it servicemix-cxf or servicemix-xfire - that still isn't
very descriptive of what it does :)
On 8 Oct 2006, at 16:44, James Strachan wrote:
On 10/8/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I assume we would need to migrate to CXF instead of XFire.
Yeah - I guess we could leave things as they are until we make a call
on upgrading to CXF/whatever its called later.
Btw, CXF will certainly provide JBI components on top of
CXF, so there is certainly something to do there. And it
brings one question about the location of JBI components
tightly tied to other projects (tuscany, CXF, Axis, etc ...).
Should ServiceMix host all these components or should
they be developed in their respective projects ?
Yeah, good point. (Ode too). I guess we should generally try and push
the JBI components into the respective projects since the JBI plumbing
should be fairly constant but the project in question wil be changing
at a higher frequency.
Maybe in ServiceMix-land we can focus on an integration test suite to
test the various JBI components from other projects inside ServiceMix
- while leaving the actual source code of the JBI components within
their project?
--
James
-------
http://radio.weblogs.com/0112098/
