Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 bim2007@basistech.com does not designate 199.88.205.99 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7FEDC.34A50153"
Subject: Thoughts on generated Javascript
Date: Mon, 24 Sep 2007 14:53:31 -0400
Message-ID: <E95FD77F0171D14DA1EEE0A785E92B430228657C@mail3.basistech.net>
Thread-Topic: Thoughts on generated Javascript
Thread-Index: Acf+3DORDADQw/mSQ0ir26O/3SnhfQ==
From: "Benson Margulies" <bim2007@basistech.com>
To: <cxf-dev@incubator.apache.org>

------_=_NextPart_001_01C7FEDC.34A50153
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The Javascript project consists of deploying, really, three artifacts:

=20

1)     Some common code to manage communications with a server in
Firefox/Mozilla or IE. (Don't ask me about https, I have no idea if it
can be done). This code should only be loaded into the browser once per
page, or perhaps once, altogether (*).

2)     Classes generated from the XSD that model the objects used in a
service. We at Basis never considered the equivalent of the 'Soap 1.1'
support in CXF, we only worked with per-service schemata. There are some
issues with what consists of a clean way of managing the namespace in
Javascript.

3)     Classes generated from the WSDL that model the operations.

=20

(*) I'm wondering if we should even think about the mozilla Javascript
code-signing mechanism here.

=20

A page might talk to more than one service. So, to avoid redundancy, I
think that we need a somewhat more complex URL structure than simple ?js
delivering the entire pile.=20

=20

I have no idea how to avoid chaos if two services have classes in
common, other than that the last one loaded wins.

=20

I'm not especially attached to how the existing code wraps things for
name isolation. If anyone else has a proposed best practice for mapping
from a URI to some javascript scoping construct, please speak up.

=20


------_=_NextPart_001_01C7FEDC.34A50153--