David,

That sounds like a good plan to me. Better to have something running
then nothing at all.

Jarek

On 2/6/07, David Blevins <[EMAIL PROTECTED]> wrote:

On Jan 10, 2007, at 11:21 AM, David Blevins wrote:
>
> On Jan 9, 2007, at 8:44 PM, Jarek Gawor wrote:
>
>> On 1/9/07, David Blevins <[EMAIL PROTECTED]> wrote:
>>>
>>> On Jan 9, 2007, at 7:28 AM, David Jencks wrote:
>>>
>>> >
>>> > On Jan 9, 2007, at 10:19 AM, Jarek Gawor wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> I'm looking into integrating CXF with OpenEJB (OpenEJB3
>>> specifically
>>> >> as that's the version that supposed to be integrated in M2). I
>>> see
>>> >> that OpenEJB2 has a bunch of code for web services support that's
>>> >> based on Axis1. However, I do not see such code for OpenEJB3.
>>> So I'm
>>> >> wondering what that means exactly as we still need support for
>>> >> JAX-RPC-based web services in 2.0. Perhaps the code hasn't been
>>> >> ported
>>> >> over yet or I'm just not finding the right code?
>>> >>
>>> >> Can someone please clarify?
>>> >
>>> > I think no one has looked at porting the code yet, but I could be
>>> > wrong.  I hope that whatever we come up with for openejb3 can work
>>> > with axis1, cxf, and axis2, but I don't yet have an idea if
>>> this is
>>> > practical.
>>>
>>> Right, it's not ported yet.
>>>
>>
>> Do you think this will be ported over before M2?
>
> We're most likely looking at M3 for that.

Ok, I'm looking at this a bit now and have some initial thoughts.

I think the easiest way to get started is to just forget about the
handler chain for the moment and write something that can wrap and
delegate to an org.apache.openejb.RpcContainer.  Unmarshal the args
from xml and pass them in as the arg list, then take the return value
and create the SOAP response.  Or if the invocation resulted in an
exception thrown from the invoke method, take the exception and
create a soap fault.

The more I think about the j2ee 1.4 web service handler chain the
more I know we want to do have that done via the new EJB 3
interceptors, which is what the new javaee 5 web services use.  We
can get started with what we have now and get basic invocations to
work.  Once the EJB 3 interceptor code is in place we can flip the
unmarshalling/marshalling inside out and find a way to do it after
the interceptor stack rather than before, very likely using an
interceptor.

-David

>
> -David
>


Reply via email to