Yes, as Jim said, we're working on the databinding framework to support
pluggable databindings and transformation on the wire. I'm not sure if you
notice that there's a databinding-xmlbeans project and it would be nice that
you can contribute the databinding-e4x.
Thanks,
Raymond
----- Original Message -----
From: "Jim Marino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, August 20, 2006 8:41 AM
Subject: Re: Using Interceptors to convert objects to XmlObjects for
JavaScript/E4X support
Raymond and I are having a discussion about this he is working on the
data binding framework which will enable doing this. You should sync with
him as I believe this will entail adding an E4X extension.
Jim
On Aug 20, 2006, at 5:51 AM, Venkata Krishnan wrote:
Hi Ant,
Is this something that works in M2 now? I remember doing a util for
creating xml instances for this.
When I see the current trunk's javascript container I don't see the e4x
samples. Shall I try moving them over and intergrating with the xml
instance creation utility. Please let me know.
Thanks.
- Venkat
On 6/7/06, ant elder <[EMAIL PROTECTED]> wrote:
No reply to this yet...after a little playing around it seems to work
so
I'm
going to go ahead unless anyone raises any objections now. Sebastien,
you
did the async work using PolicyBuilders and Interceptors so have you
any
comments to what I suggested in the email below?
...ant
On 6/6/06, ant elder <[EMAIL PROTECTED]> wrote:
>
> I wondered about using Tuscany PolicyBuilders and Interceptors
to help
> with E4X support for the work required in TUSCANY-418,
TUSCANY-419, and
> TUSCANY-420. Right now the E4X code isn't so elegant with the
way it
works
> out when and how to convert the Java objects in a message into
E4X XML,
and
> with the current code i can't get E4X XML as parameters on
reference
> invocations working.
>
> Looking at how the code for async works, it seems like for E4X
support
> there could be source and target policy builders that look at
the wires
and
> when required (*) insert an interceptor that converts the message
objects
> from/to XmlObjects, and then the JavaScript container would simply
always
> convert XmlObjects from/to E4X XML objects.
>
> (*) the when required would be something like when the wire
target is a
> JavaScript component with interface described by a WSDL
portType, or a
wire
> source is a JavaScript component and the wire target has an
interface
> described with WSDL.
>
> Does this sound like a reasonable use of PolicyBuilders and
Interceptors?
> It seems like something like this may also be a step on the way
to the
> efficient streaming of messages in TUSCANY-104?
>
> ...ant
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
