Hello, Thank you for your reply. I thought that there is already some API in cxf for ws-discovery support like other WS-* standards. That is mean, I have to implement from scratch all the details of the ws-discovery specification. As my goal for the moment is to have a running example for this standard, finally I used Java-ws-discovery (http://code.google.com/p/java-ws-discovery/). But in our future work, we will use cxf for the implementation of our model based on a discovery mechanism. Thus, we need to go deeply in all these details.
Thank you again, Best regards, Diana On 21 nov. 2011, at 19:58, Daniel Kulp wrote: > On Saturday, November 19, 2011 2:15:12 PM Diana ALLAM wrote: >> Hello, >> >> I'm a new cxf user. >> I'm working on an example for using ws-discovery standard to publish and >> require services. I have a difficulty to start with my example. I search a >> long time for it but I didn't find any helpful indications on the cxf web >> site. >> Maybe it could be possible by using interceptors but I am not sur. >> >> Any ideas? Could I have some help please? >> It is very urgent for me. >> >> Thank you in advance, > > WS-Discovery is a big enough thing that you should likely start by trying to > chop that into smaller parts and tackling it in chunks. Each chunk would > have different requirements and such and discussing each one on the list > (likely the dev list, not users list) separately would probably be the best > option. > > For example, right off the top of my head I can break this into several > parts/discussions: > > 1) Ad-Hoc vs Managed - Managed will be a lot easier as CXF really doesn't > have > any support for multicast related transports right now. Thus, ad-hoc will > be > a bit more involved to do "internal CXF changes". HOWEVER, Managed mode > would require writing a Discovery Proxy. That may be pretty easy though as > there aren't a lot of operations to implement (hello/bye/probe/resolve). > > 2) Service side - you would just need to write a ServerLifecycleListener that > would send the "hello" and "bye" messages out. This is likely pretty easy > and would be a greate starting point if you have a DiscoveryProxy avail to > test with. > > 3) There are many ways to wire in the client side stuff. We could just > provide an API which would allow the developer to get an EPR that they then > pass directly into the JAX-WS createXYZService(....) calls. That would a > simple step one. Another option is to add a callback into the createXXX > calls that would allow a listener to be registered that would lookup that > stuff so the developer doesn't have to do anything. > > Anyway, WS-Discovery does have a bunch of moving parts in it with different > modes of operation. If you can break it down into smaller chunks that you > are interested in tackling, we can definitely help provide pointers as to > where to start looking. > > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com
