No.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:07 PM
To: cxf-user@incubator.apache.org
Subject: RE: WSDL Generation problem using Aegis binding
Is there a .aegis.xml file in the neighborhood of your problem?
> -Origi
---Original Message-
> From: omatzura [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 18, 2007 2:57 PM
> To: cxf-user@incubator.apache.org
> Subject: Re: WSDL Generation problem using Aegis binding
>
>
> Hi Samuel,
>
> Just to clarify the error: an element definition l
PROTECTED]
Sent: Wednesday, July 18, 2007 2:57 PM
To: cxf-user@incubator.apache.org
Subject: Re: WSDL Generation problem using Aegis binding
Hi Samuel,
Just to clarify the error: an element definition like this is fine, the
problem in this particular case is that the type for the element is not
ted, timely or free of
> viruses, and Princeton Retirement Group, Inc. cannot accept any liability
> for E-mails that have been altered in the course of delivery. Princeton
> Retirement Group, Inc. reserves the right to monitor, review and retain
> all electronic communications, including E-mail, traveling through its
> networks and systems (subject to and in accordance with local laws). If
> any of your details are incorrect or if you no longer wish to receive
> mailings such as this by E-mail please contact the sender by reply E-mail.
>
>
>
>
--
View this message in context:
http://www.nabble.com/WSDL-Generation-problem-using-Aegis-binding-tf4105058.html#a11674917
Sent from the cxf-user mailing list archive at Nabble.com.
Below is a snippet of the WSDL that's getting generated using Aegis
binding with the embedded server and causing errors. We're doing Java
first development, no annotations or anything as these are all internal
appsl. When the .NET client tried to connect we were getting a bizarre
error which I be
