<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Apache CXF and validation</title>
	<atom:link href="http://www.carbonrider.com/2010/02/28/apache-cxf-and-validation/feed/" rel="self" type="application/rss+xml" />
	<link>http://articles.carbonrider.com/2010/02/28/apache-cxf-and-validation/</link>
	<description>You make a matrix, you define the limits.</description>
	<lastBuildDate>Wed, 25 Jan 2012 04:45:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Carbon Rider</title>
		<link>http://articles.carbonrider.com/2010/02/28/apache-cxf-and-validation/comment-page-1/#comment-414</link>
		<dc:creator>Carbon Rider</dc:creator>
		<pubDate>Thu, 05 Aug 2010 17:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://articles.carbonrider.com/?p=226#comment-414</guid>
		<description>Hi Glen,

With Code-First approach, developers usually dont write WSDL and let the framework take overhead of generating it.
As per your suggestion, specifying wsdlLocation in endpoint would require generating WSDL and I personally feel that it would defeat
the purpose of code-first approach.
If WSDL is created for code-first approach, it would also require developers to keep it upto date with java code, which might be error prone.
Hence the simplest approach would be to use the schemaLocation and specify the XSDs used for JAXB value object generation.
This also saves from efforts spent in maintaining upto date version of WSDL with java code.

Anyways thanks for pointing to the link.</description>
		<content:encoded><![CDATA[<p>Hi Glen,</p>
<p>With Code-First approach, developers usually dont write WSDL and let the framework take overhead of generating it.<br />
As per your suggestion, specifying wsdlLocation in endpoint would require generating WSDL and I personally feel that it would defeat<br />
the purpose of code-first approach.<br />
If WSDL is created for code-first approach, it would also require developers to keep it upto date with java code, which might be error prone.<br />
Hence the simplest approach would be to use the schemaLocation and specify the XSDs used for JAXB value object generation.<br />
This also saves from efforts spent in maintaining upto date version of WSDL with java code.</p>
<p>Anyways thanks for pointing to the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen Mazza</title>
		<link>http://articles.carbonrider.com/2010/02/28/apache-cxf-and-validation/comment-page-1/#comment-411</link>
		<dc:creator>Glen Mazza</dc:creator>
		<pubDate>Tue, 03 Aug 2010 23:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://articles.carbonrider.com/?p=226#comment-411</guid>
		<description>I don&#039;t work much with Java-first web services, but populating the endpoint wsdlLocation field might also help:

http://stackoverflow.com/questions/2231779/cxf-and-validation-schema-restrictions-ignored</description>
		<content:encoded><![CDATA[<p>I don&#8217;t work much with Java-first web services, but populating the endpoint wsdlLocation field might also help:</p>
<p><a href="http://stackoverflow.com/questions/2231779/cxf-and-validation-schema-restrictions-ignored" rel="nofollow">http://stackoverflow.com/questions/2231779/cxf-and-validation-schema-restrictions-ignored</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

