cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Diephouse <>
Subject Re: Is the idea of wsdl2java (aegis) really useful?
Date Sat, 22 Sep 2007 20:13:55 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Yeah, I think its definitely a waste of time to do an Aegis
schema-&gt;java. We would gain absolutely no benefit from it as far as
I can tell :-) <br>
- Dan<br>
Daniel Kulp wrote:
<blockquote cite="" type="cite">
  <pre wrap="">I had this conversation with Dan D. before and the thoughts were pretty

much exactly the same.   If you are generating java code from schema, 
you should use the "standard" JAXB stuff since that supports more of the 
schema types than Aegis does.    Aegis is primarily targeted for the 
Java first case.   Having java -&gt; wsdl tools for it makes sense.   
However, the wsdl -&gt; java stuff makes less sense.


On Friday 21 September 2007, Benson Margulies wrote:
  <blockquote type="cite">
    <pre wrap="">I'm wondering why anyone would want this. If the user is going to run
a code generator, what's wrong with JAXB? The virtue of Aegis is to
avoid an infestation of snails (@) in existing code. Once you are
firing up a generator, it's new code.

I note that Aegis has some not-very-documented capabilities, and I
wonder if some of them are superior to JAXB in some way.

Do we ever post some sort of [POLL] to the user list asking 'who would
use this feature' questions?
  <pre wrap=""><!---->

<pre class="moz-signature" cols="72">-- 
Dan Diephouse
<a class="moz-txt-link-freetext" href=""></a>
| <a class="moz-txt-link-freetext" href=""></a></pre>

View raw message