Brian De Pradine wrote: >> >> Brian, >> >> This is one of the problems I've been looking at for some time. IMO, >> EndpointReference class better be independent of WS-A. We got the >> attributed of the EPR class by looking at 2005/08 spec, but after >> that it had nothing to do with that. > > Why does the EndpointReference class need to be independent of the > WS-Addressing > namespace? This is the aspect of this discussion that I haven't > understood yet. > Considering that in axis2 ALL EPRs are represented using instances of > this class > it seems to me that the addressing namespace is an important attribute > to capture.
My only concern is EPR is used everywhere and it doesn't need to contain WS-Addressing namespace in it. Its required only when you serialize/de-serialize it. For example, when you formulate a request to be sent and when you are doing request-response invocation over the same HTTP channle, you don't need to know anything about WS-Addressing. And no WS-Addressing modules are required. Thats why I like to keep EPR class independent from any namespace. For me its just a bean which encapsulates information about an endpoint. Serializing it using WS-A rules or any other rules is not its problem. Yes, I agree its a problem if where to keep the code, both of us agree on other stuff :) -- Chinthaka
signature.asc
Description: OpenPGP digital signature
