Mailing-List: contact cxf-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-user@incubator.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Importance: normal
Priority: normal
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: wsdl generation ala Xfire
Date: Mon, 23 Jul 2007 13:59:34 -0400
Message-ID: 
 <A99DF4A557C3934B81B4A5D6FC6BF4C601F0BD10@MLNYC728MB.amrs.win.ml.com>
Thread-Topic: wsdl generation ala Xfire
Thread-Index: AcfNUxPOkeh9zn0HQLmgWrUV1fCnNAAABi0Q
From: "Clough, Samuel \(USPC.PRG.Atlanta\)" <Samuel_Clough@princetonrg.com>
To: <cxf-user@incubator.apache.org>

Yes, you can do that with Aegis or Jaxb binding. (Xfire defaults to
Aegis).=20

-----Original Message-----
From: Dave Kallstrom [mailto:dave.kallstrom@gmail.com]=20
Sent: Monday, July 23, 2007 1:58 PM
To: cxf-user@incubator.apache.org
Subject: wsdl generation ala Xfire

We are thinking about migrating from Xfire to CXF.  There is one thing
that
I cannot find in the documentation for CXF. Is there a way to get the
wsdl
from cxf like we do with xfire by appending ?wsdl to the endpoint url
without ever having to actually write a wsdl?

--=20
Dave Kallstrom=20
--------------------------------------------------------

Princeton Retirement Group, Inc - Important Terms=20
This E-mail is not intended for distribution to, or use by, any person =
or entity in any location where such distribution or use would be =
contrary to law or regulation, or which would subject Princeton =
Retirement Group, Inc. or any affiliate to any registration requirement =
within such location.=20
This E-mail may contain privileged or confidential information or may =
otherwise be protected by work product immunity or other legal rules. No =
confidentiality or privilege is waived or lost by any mistransmission. =
Access, copying or re-use of information by non-intended or =
non-authorized recipients is prohibited. If you are not an intended =
recipient of this E-mail, please notify the sender, delete it and do not =
read, act upon, print, disclose, copy, retain or redistribute any =
portion of this E-mail.=20
The transmission and content of this E-mail cannot be guaranteed to be =
secure or error-free. Therefore, we cannot represent that the =
information in this E-mail is complete, accurate, uncorrupted, 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.=20

--------------------------------------------------------