On Monday 01 December 2008 12:39:31 pm Daniel Kulp wrote: > > What, for Pete's sake, is Neethi, and why was it necessary > > to add it? > > Neethi is the WS-Policy implementation. That said, if you aren't using > any policy assertions we probably could somehow make this optional. > That's definitely something we could look into. For basic soap/http, this > could be removable. However, once we start getting the WS-SecurityPolicy > stuff flushed, it would DEFINITELY be required for that.
Actually, the JAX-WS 2.1 spec requires processing of the ws-addressing policy assertions in the wsdl. Thus, neethi wouldn't be optional for JAX-WS frontend. -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
