Sergey Beryozkin wrote: > > >> I had some problems with Sun's Metro in conjunction with Spring and >> Hibernate so I switched back to CXF. > > Interesting :-). I think you can definitely use Spring and Hibernate in > CXF. >
I already have a working webservice which I created with CXF. However, I had a few problems when I tried to use it from my .NET client. Then I read about Metro and WSIT which is heavily tested with Microsoft's WCF. I hoped I could get rid of my problems (*) by switching to Metro. Well, that didn't work as well as I hoped it would. At first I couldn't inject my Spring beans into the endpoint until I figured out that NetBeans is deploying the same webservice two times. The Spring support works only in one of them. :-/ After that I started porting all of my code which includes some Hibernate DAOs. Well, I just couldn't find a way to deploy my webservice when I used Spring and Hibernate. It looks like there were some problems with the JARs. Of course, the same JARs plus the ones from CXF work without a problem when I deploy them to my Jetty server ... To make a long story short, those are the reasons why I switched back to CXF. So I just hope that I can get this to work as soon as possible since I have to show this to the tutor of my bachelor thesis at the end of next week. (*) Those problems existed in Metro as well, so I guess I'll have to ask here some more questions about interoperability problems during the next few days. ;-) -- View this message in context: http://www.nabble.com/CXF%2C-WS-Policy-and-Spring-tp16718063p16733412.html Sent from the cxf-user mailing list archive at Nabble.com.
