Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of jim.ma@iona.com designates
 12.170.54.180 as permitted sender)
Message-ID: <46A6CD3E.3020903@iona.com>
Date: Wed, 25 Jul 2007 12:10:38 +0800
From: Jim Ma <ema@iona.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: cxf-dev@incubator.apache.org
Subject: Re: Code first tool proposal
References: <46A6BB63.2040909@iona.com> <46A6C2DF.1040709@iona.com>
In-Reply-To: <46A6C2DF.1040709@iona.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

James,

Thank you for your thoughts and insights .
> IMHO, the java2wsdl does support the jaxws, and simple frontend, but 
> it's only generate the wsdl, is it the duplicate function in the java2cs,
> Or is it possible to extend the java2wsdl (we need to find a better 
> name for it)
> Or java2cs will call into the java2wsdl to generate the wsdl files, 
> and associate the artifacts (like the beans/binding files in case of 
> jaxws)
Agreed . I do not plan to rewrite these function that java2wsdl and 
wsdl2java can provided .  Java2cs tool can internally invoke java2wsdl 
and wsdl2java
to generate client ,server wsdl for jaxws frontend .

> And the java2cs should also generate the configuration files, right? 
> (spring, servlet etc.), and also we need have the ant tasks, so 
> generating artifacts, and then compile, deploy, all in one command.
Great idea!   I will add three options for java2cs :
       -servlet-config
       -ant
       -all

Regards

Jim