THe first two are live insofar as they deliver a real feature: validation of the XSD that we produce in Aegis.
The primary reason to have this feature is to catch our own mistakes: if Aegis is coded right, it should never produce an invalid XSD. On Fri, Sep 17, 2010 at 11:10 AM, Daniel Kulp <[email protected]> wrote: > > There are some jars and such on trunk that we are building and using during > testing and such that are not part of the cxf-bundle or even packaged in the > distribution at all: > > cxf-wstx-msv-validation > xerces-xsd-validation > cxf-rt-databinding-sdo > cxf-rt-management-web > > and all the transient deps of the above..... > > So, which of the above should be added to the bundle? We could add all of > them to the bundle and just mark all their deps optional/provided. > > > Also, are there things in the bundle that could/should be pulled out? I'm > actually thinking of creating a separate "cxf-tools" and moving the command > line tooling things into there. Thus, the bundle would be more just the > runtime parts. Thoughts? > > > Another quick question: are there docs for the validation things above or the > management-web? There isn't for SDO so I'll add that to my todo as well. > > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog >
