I see, you're right that if it's inherited it should be like that but the documentation would certainly help with it :). I personally wouldn't rely on the fact that endpoint/service values or set properly because the accidental mismatch can lead to losing a lot of time if someone doesn't know the actual mechanism behind that. I would force someone to check annotations. Of course this is personal preference
regards Lukasz Freeman Fang wrote: > > Hi Lukasz, > > Actually we use xbean to generate xsd and service endpoint are fields > which is inherited from super class. > Besides that, IMHO I think the attribute servicename and endpoint are > still useful, think about this scenario, > developer A write the cxf se SU, if there is no service and endpoint in > the xbean.xml, it's hard for other developer like B who write cxf bc SU > figure out what's the targetService/targetEndpoint should be if he want > to route message to cxf se SU. > Of course developver A should guarantee the service/endpoint he specify > in xbean.xml should be identical with that from annotation or from > auto-generated one, we may need put it into our documentation. > > Regards > Freeman > > -- View this message in context: http://www.nabble.com/CXF-SE-endpoint-service-name-tp18711641p18729234.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
