Hi Tammo, Thank you very much for the detailed explanation. Now I have the idea of what really the project requirement is all about. I have some experience in working with JAXWS ,REST,JSON but I haven't work with CXF. Now I'm following tutorials and articles about CXF and the Apache ODE .Its very interesting that I have learnt and work with these technologies in my internship as well. I think it will be an advantage for me. I'll contact you all via mailing list when I raise any question and discuss .
Thank you On 11 March 2014 23:13, Tammo van Lessen <tvanles...@gmail.com> wrote: > Hi Ujitha, > > thanks for posting here. Apache ODE is a Web service orchestration engine > that executes orchestration scripts expressed in WS-BPEL. ODE's > architecture is pretty modular, i.e. most top-level components are defined > in terms of an API and are provided by one or more implementations. One of > the key components is of course the integration layer, which is in charge > of exposing BPEL processes as Web services and calling other Web services > in the course of the execution. Up to now ODE has two integration layer > implementations, one is for JBI/ServiceMix, the other is based on Axis2 and > the most used implementation. It also features some support for REST-based > services and employs rampart/rahas for WS-Security. > > Meanwhile, the WS-* framework landscape has been stabilized and > API-standards like JAX-WS have emerged since the beginning of ODE. That's > why it would make sense to think of additional integration layer > implementations. 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. > > 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. > > How does that sound? Please feel free to ask any questions, we're here to > help. > > Best, > Tammo > > > On Mon, Mar 10, 2014 at 6:48 PM, Ujitha Iroshan <dguji...@gmail.com> > wrote: > > > Hi Tammo and All, > > > > I'm Ujitha Iroshan, third year undergraduate from Department of Computer > > Science and Engineering University of Moratuva Sri Lanka. Currently I'm > > working as an intern in WSO2 inc an Open source middleware company.I'm > > planing to participate in the Google Summer of code 2014.And I'm very > much > > interest in the project idea of CXF Implementation of the IAPI [1].I > have > > a good knowledge about Java and WS. Currently I'm studying about CXF as > > well. So to start with the project and to create project proposal I need > to > > have a more details about the project.Can you please explain the project > > requirements in details? > > > > > > [1] https://issues.apache.org/jira/browse/ODE-41 > > -- > > Ujitha Iroshan Wickramarathna > > Undergraduate > > Department of Computer Science and Engineering > > University of Moratuwa. > > > > > > -- > Tammo van Lessen - http://www.taval.de > -- Ujitha Iroshan Wickramarathna Undergraduate Department of Computer Science and Engineering University of Moratuwa.
