Hi Ujitha, hi Zhen, The Axis2 layer currently uses a similar approach, the IL is not aware of WSS, WSRM, not even WS-A (which is suboptimal). The configuration then happens via custom properties files or service.xmls that cause the configuration of the axis services. Perhaps the same approach would be possible for a JAX-WS IL that allows for custom configurations for certain implementations. I'm unfortunately not very familiar with the low-level JAX-WS api, so I don't know if there are suitable hooks for that. But that would be also part of the architecture and then engineering part of the project. Perhaps Jeff has some insights, IIRC he worked on something similar a while ago.
@Zhen, great that you're interested in the GSoC project as well. Let me say that we have some more GSoC project ideas. A nice one would add support for clustering to ODE, then we have some OModel serialization issues which must be addressed in the near term, so there is actually no need to apply for the same project. Of course, if this is your favorite project idea, you can of course submit competing proposals... Thanks, Tammo On Wed, Mar 12, 2014 at 7:49 PM, Ujitha Iroshan <dguji...@gmail.com> wrote: > Hi All > > Yeah idea of JAXWS-ODE bridge is a good idea. But the thing is as Tammo > mentioned that we need a modern integration layer, but it should have > almost same functionalities that current Axis2 implementation has. CXF has > support for many WS-* like WS-addressing,WS-policy,WS-RM and etc which also > supported by Axis2. As far as I know JAX-WS doesn't support these > standards. It is a good idea that if we can implement a generalize > JAX-WS-ODE bridge with the support of CXF for other WS-* implementations. > On the other hand if we mainly focus on the functionalities that should > implement in the integration layer which should be as good as current Axis2 > implemetation just CXF implementation also a good choice I suppose. > > Best Regards > Ujitha > > > On 12 March 2014 09:37, Fang Zhen <fangzhenz...@gmail.com> wrote: > > > 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 > > > > > > -- > Ujitha Iroshan Wickramarathna > Undergraduate > Department of Computer Science and Engineering > University of Moratuwa. > -- Tammo van Lessen - http://www.taval.de
