Hi Oliver, If you are interested on this implementation, and you need some help. I'd love to help.
Regards, Fernando Avalos. > From: [email protected] > To: [email protected] > Subject: Re: WS-MEX support > Date: Tue, 7 Jun 2011 15:38:26 -0400 > CC: [email protected] > > > > I hoping to get a GSoC student to do the WS-MEX stuff, but didn't. :-( > > I'd definitely like to see WS-MEX support. With 2.4, some of it is > definitely easier. The WSDL retrieval is already done as an interceptor on > the endpoint chain. Thus, we already have some stuff setup to handle these > types of interactions as part of the chain. It's just something we'd need > to > prioritize and likely try and find resources to implement. > > Dan > > > On Tuesday, June 07, 2011 1:50:32 AM Oliver Wulff wrote: > > Hi there > > > > I thought that WS-MEX is one of the standards which is implemented by a few > > stacks only but not widely used because it's not really a standard from > > Oasis or W3C and it's a perfect candiate for REST. Microsft WCF is heavily > > based on WS-MEX for policy retrieval and automatic configuration > > generation. > > > > I just noticed today that there is a Candiate Recommendation published from > > april this year: http://www.w3.org/TR/ws-metadata-exchange/ > > > > I think it would make a lot of sense to have this functionality in CXF > > also. I'm aware of Metro and WCF which support it. > > > > Maybe we could provide a property/attribute in the JAX-WS endpoint bean > > whether metadata (wsdl, policy) can be retrieved of WS-MEX. > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com
