Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of nvijayak@cisco.com designates
 171.68.10.87 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C97841.4AD04F1D"
Subject: Post to Etch developer community
Date: Fri, 16 Jan 2009 17:17:04 -0800
Message-ID: 
 <4465623F8C892B4C829F7B4D09A4C2B906B0924A@xmb-sjc-234.amer.cisco.com>
Thread-Topic: Post to Etch developer community
Thread-Index: Acl4QU5jwHYkGq8hRH6opbLI0MFjhw==
From: "Nithya Vijayakumar (nvijayak)" <nvijayak@cisco.com>
To: <etch-dev@incubator.apache.org>
Cc: "Srikanth Bhamidipati (bsri)" <bsri@cisco.com>

------_=_NextPart_001_01C97841.4AD04F1D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Etch Developers,
=20
Our current posting is to request no-arg default constructor in all
generated Etch java sources.=20
=20
We are using Apache Etch for our services. We have a requirement to
expose Etch as a SOAP web service. We are using the open source Apache
software Tuscany 1.3 and Axis 2 for this purpose.  While integrating we
found that the java source code created by the Etch Compiler cannot be
exposed as a SOAP service as it currently does not have a no-arg default
constructor.  The requirement stems from Apache Axis 2 and its use of
JAXB for data binding.=20
=20
Apache Axis 2 is our underlying SOAP provider. This dictates for a
no-arg default constructor for even things like WSDL generation. Further
when we would like to serialize objects to XML using libraries like
Xstream/JAXB, which in turn try to construct objects before serializing
them to XML using the default constructor. Even when services are
exposed as SOAP via just Apache AXIS (stand alone), there is a need for
a default constructor. We ran some examples that ship with Axis 2 and
removed the no-arg constructors for complex objects and the service
didn't deploy.

We are adding some references to this topic. We hope the Etch developer
community would be quick to respond to this issue.

http://www.mail-archive.com/user@tuscany.apache.org/msg00951.html

http://ws.apache.org/axis2/1_4_1/jaxws-guide.html

Thanks,
Nithya

Nithya Vijayakumar, Ph.D.
Software Engineer, Cisco

=20

=20

------_=_NextPart_001_01C97841.4AD04F1D--