On Wednesday 02 March 2011 1:28:45 PM jaybytez wrote: > When creating a jaxws:endpoint, are proxies used under the covers to create > this running service endpoint implementation?
Normally, no. You can have the jaxws:endpoint use a ref to another spring bean that is proxied though. > Also if the interface/implementation that I am configuring to handle the > web service requests also uses Spring AOP for transaction management, > could that cause Proxy overhead as far as registering the class for CXF as > well as Spring AOP Transactions? > > I have a bug I am tracking down on how I define AOP Pointcuts, but out of > 25 services, 2 of them a fairly complicated and when the war gets deployed > and all the bootstrapping occurs of CXF and Spring beans, a log file will > grow into 5+ megs in about 15 seconds with what appears to be an infinite > loop or recursive initialization of the AOP/Proxied bean. Can you try with CXF 2.3.3? First off, 2.3.3 is tested much better with Spring 3. 2.2.x really wasn't. Second, a lot more things are "lazy" init in 2.3.3 so less stuff needs to be created up front which can cause more issues with circular deps and such. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
