On Monday 05 January 2009 2:48:51 pm Benson Margulies wrote: > As I recall, there are compliance requirements for the tasks.
Not really. The TCK setup has the original copies of the tasks. Thus, if they are removed from CXF, it's not really an issue as the TCK runs use a different copy. I never changed the TCK to use the CXF provided tasks. Dan > On Mon, Jan 5, 2009 at 2:40 PM, Glen Mazza <[email protected]> wrote: > > While we're at it, I think we should nuke the Ant task for 2.2--using > > Ant's own <java/> task to run wsdl2java/java2whatever/whatever2whatever > > is easier and nicely self-documenting anyway, and the <java/> task, by > > definition, maps 100% to our command-line documentation so it requires > > zero maintenance. > > > > Glen > > > > dkulp wrote: > >> On Sunday 04 January 2009 7:34:42 am Benson Margulies wrote: > >>> I know that some of you out there wish that CXF were slimmer. I've > >>> have an opportunity to do some trimming come up. > >>> > >>> Aegis has code to allow mapping of JDOM Elements to XML and vica versa. > >>> > >>> Does anyone want this or care? At one level, I think it should be a > >>> separate (if tiny) sample of using the API to add mappings rather than > >>> a core feature? > >> > >> I think this is a good idea. Would need to be mentioned in the > >> migration > >> guide for 2.2 though, but that's not a huge deal. > >> > >> > >> -- > >> Daniel Kulp > >> [email protected] > >> http://dankulp.com/blog > > > > -- > > View this message in context: > > http://www.nabble.com/POLL%3A-JDDOM-Usage-and-Aegis-tp21275741p21297768.h > >tml Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog
