Hi all, > > ODE-41 is pretty early ticket and is about implementing > > CXF support for ODE. While this is still an interesting topic and a good > > contribution as CXF is a mature WS stack meanwhile with support for > > WS-Policy, Security, various transports, REST, JSON..., another idea > would > > be to generalize this ticket and come up with a JAX-WS<-->ODE Integration > > Layer bridge, so that ODE can deal with any JAX-WS implementation, if > > possible. > I'd like to say that I like the idea of JAX-WS -- ODE bridge. Since CXF support JAX-WS front-end, the bridge will work with CXF naturally or any other JAX-WS implementation as Tammo mentioned. But I'm not sure if we can take advantage of the features like WS-* support provided by CXF easily. As far as I konw, JAX-WS spec (JSR224) did not cover these WS-* standards (except WS-Addressing). So a workaround would be a generalized JAX-WS -- ODE bridge and CXF-specific implementation on other functions needed by ODE that beyond JAX-WS?
> > So the goal of the GSoC propsal would be a) to decide whether it is > better > > to add a CXF integration layer to ODE or a JAXWS integration layer. We > can > > discuss that here in the list. And then come up with proposal with a > > detailed schedule. The perfect outcome for us would be a modern > integration > > layer that has (almost) the same functionality that the current > Axis2-based > > implementation has. Of course we will help you with scoping that. > I'm interested in the GSoc project too. I'm a postgraduate student in Beijing Normal University, China. My research mainly oriented in web service transaction and composition. Hope that we can work it out together. Best, Zhen
