Thank you for your reply!
Unfortunately, this is not the solution. I tried a dozen+ different address
formats :-)
In the meantime I managed to find the solution. The solution is to go back
from 2.2.1 to version 2.1.X of cxf. That
eliminates the problem. Actually I don't think that this is a bug in CXF 2.2
1. I suspect that the developers changed the configuration method. The
change has not been documented, which means that the only documentation we
can find is misleading because it refers to the 2.1.X procedure. I also
suspect that the change has to do with the import of the xml files that
exists in some examples:
<import resource="classpath:META-INF/cxf/cxf.xml"/>
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
<import resource="classpath:META-INF/cxf/cxf-servlet.xml"/>
It appears that these imports are different in different examples found on
the net.
Well, never mind, we will all be OK untill we are forced to drop v. 2.1.X,
and hopefully, by then we will be able to find some other solution.
Kind regards
Henrik
Eoghan Glynn-4 wrote:
>
> Try address="/MonitorImpl" instead of address="MonitorImpl"
>
> Cheers,
> Eoghan
>
>
>
--
View this message in context:
http://old.nabble.com/address-in-spring-bean-definition-tp27977016p27989415.html
Sent from the cxf-user mailing list archive at Nabble.com.
