|
From: Kristof J. <dy...@on...> - 2005-02-23 14:12:25
|
Scott, We're having the very same scenario here. Could you please post privately the according part of your spring applicationcontext configuration where lazy-init really happens lazily? Did you also wrap the bean with LazyInitTargetSource? I'd love to see a working solution for that.. thanks, Kristof Scott Battaglia wrote: > Juergen Hoeller wrote: > >> BTW, why do you prefer your JaxRpcPortProxyFactoryBean to be lazily >> initialized? To avoid checking the WSDL at startup? It would maybe make >> sense to add a lazy initialization option to Spring's >> JaxRpcPortProxyFactoryBean itself in this case (I'll consider this). >> >> > We've had to use the lazy-init on the JaxRpcPortProxyFactoryBean in > order avoid checking the WSDL at start up in the case where the client > of the web service is deployed in the same Tomcat instance as the web > service itself (maybe there's a better way to handle this situation > though...). > > -Scott > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |