On Tuesday 12 February 2008, rsheldon wrote:
Thanks to everyone for their help on this. It turns out that despite
some logging that made me think it was connecting to the web service,
CXF actually doesn't talk to the remote server until it's first used.
I double checked this with
Can you just use the lazy-init=true stuff built into spring?
bean id=accountService
lazy-init=true
class=my.web.service.AccountService
factory-bean=accountProxyFactory factory-method=create/
Dan
On Tuesday 12 February 2008, rsheldon wrote:
I've just started using CXF with
this message in context:
http://www.nabble.com/Lazy-instantiation-of-Web-Service-Client-tp15427056p15446405.html
Sent from the cxf-user mailing list archive at Nabble.com.
Ian Roberts wrote:
http://johnheintz.blogspot.com/2007/11/using-lazy-proxy-to-avoid-spring.html
The LazyProxyFactoryBean shown in this post basically allows you to wrap
up another Spring bean with a proxy that shows the same interface, but
delays asking for the real bean until the first
Hi Richard
Hi
For the client instantiation, it just need to create the service
model[1] first.
If you add the wsdlLocation attribute in your SEI's WebService
annotation or specify the wsdlLocation property for the
JaxWsProxyFactoryBean with your service endpoint's address, the client
will
can put into this map.
Can anyone help?? Is there an attribute or property I can set to prevent
immediate creation of the service?
Many thanks,
Richard
Thanks
Richard
--
View this message in context:
http://www.nabble.com/Lazy-instantiation-of-Web-Service-Client-tp15427056p15427056.html
Sent
