Guillaume Nodet wrote:
* Which website is supposed to be the right one?
http://servicemix.org/ or http://incubator.apache.org/servicemix/ ?
I guess http://incubator.apache.org/servicemix/, we need to fix some links.
Can we get servicemix.org to redirect to the incubator site then? One is
codehaus, one is apache...
Well, the XFire example sources are still available at
http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-assembly/src/sandbox/xfire-binding/
I removed it from the distribution because this is a pure XFire sample
and is in no way related to ServiceMix (it may be better to put it in
XFire distribution ;) )
Yeah, IIRC, Hiram just copied this from XFire CVS at one point, so I
think we have it. I wanted to put together a true example that shows how
to do some more stuff with xfire.
I guess we could write a pure xfire binding component: there are a
couple of enhancements that xfire would need to keep up with
servicemix-http ;) like jett6 continuations, accessing directly a stax
based jaxp source, use of commons-httpclient pooling on the client
side. This would enable to use xfire handlers like the WS-Security
one directly. But this deserves another thread ...
OK, yeah this does deserve another thread. I'll take a look into some of
these issues soon and see what I can do.
None of these are necessariliy blockers as its a M1 release, so I am +0.
I would like to see SM-393 addressed and the soap binding link fixed,
but don't have time to do it myself at the moment.
I will fix the link (which is not a bad link actually, the doc has not
been written).
Ok, cool. Cheers,
- Dan
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
