Re: Purpose of Destination/AbstractEndpoint, RMEndpoint on WS-RM
Hi Aki, I haven't checked the jaxws/jaxrs endpoint implementations but I will. My module is also implemented as a CXF feature with interceptors and Spring integration the same way as ws-rm implementation and I'm quite happy with that. The only thing I don't like is the way the RMEndpoint is managed and associated with the CXF endpoint. Rgds, Jesus. -- View this message in context: http://cxf.547215.n5.nabble.com/Purpose-of-Destination-AbstractEndpoint-RMEndpoint-on-WS-RM-tp5718243p5719528.html Sent from the cxf-dev mailing list archive at Nabble.com.
Re: Purpose of Destination/AbstractEndpoint, RMEndpoint on WS-RM
hi Jesus, If you are thinking of a specific endpoint type like jaxws or jaxrs etc, you will have a specific endpoint factory to instantiate its client or server side endpoint. In contrast, the RM is configured as a feature that is enabled in the bus. So, depending on what you are intending to do, you may look at the other endpoints which might fit to your intention. regards, aki 2012/11/27 Jesus Castillo : > Thanks for your reply Aki, it's clear now. > > It seems that CXF doesn't have an easy way to extend the functionality of > the Endpoint class. > So, even if I create MyCustomEndPoint to extend EndPoint, Cxf would not be > aware of this as > there is no register mechanism. > > I guess, this is why there is a Map to create an > association between the > Cxf endpoint and the corresponding RMEndPoint. > > I think a feature like this would make Cxf more pluggable and extensible. > > Jesus. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Purpose-of-Destination-AbstractEndpoint-RMEndpoint-on-WS-RM-tp5718243p5719162.html > Sent from the cxf-dev mailing list archive at Nabble.com.
Re: Purpose of Destination/AbstractEndpoint, RMEndpoint on WS-RM
WS-RM uses terms Source and Destination to describe the components that are used to interface the application to the protocol implementing part. Since both RM's Source and Destination share some common functionality, they are derived from RM's AbstractEndpoint. RMEndpoint is the RM-version of the endpoint which encapsulates the normal endpoint and the RM specific properties/functionalities in CXF. If you have more questions, you can use the users@cxf mailing list which is more appropriate for general questions. Thanks. aki 2012/11/11 Jesus Castillo : > Hi, > > I was trying to understand the WS-RM implementation but I got lost with the > multiple > abstractions of Destination and Endpoint. > > On CXF core, there are Destination, Endpoint. > On WS-RM. Destination/AbstractEndpoint, RMEndpoint. > > Can somebody clarify the use/purpose of them in WS-RM as opposed to the ones > in CXF? > I couldn't find any document explaining this. > > Thanks. > > Jesus. > > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Purpose-of-Destination-AbstractEndpoint-RMEndpoint-on-WS-RM-tp5718243.html > Sent from the cxf-dev mailing list archive at Nabble.com.
