|
From: Cameron B. <ca...@da...> - 2003-11-05 03:52:18
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> I have a FactoryBean that is a singleton. It is a prototype factory (is that correct terminoligy?)<br> <br> When the application context initialized, the FactoryBean.getObject() is being called before I call getBean() from my application.<br> <br> The problem is that the contract for BeanFactory.getObject() states that it shoud never be null.<br> <br> /**<br> * Return an instance (possibly shared or independent) of the object<br> * managed by this factory. As with a BeanFactory, this allows<br> * support for both the Singleton and Prototype design pattern.<br> * @return an instance of the bean <b>(should never be null)</b><br> * @throws Exception in case of creation errors<br> */<br> Object getObject() throws Exception;<br> <br> Though in my application, I can't gaurantee this. I am relying on source of information that doesn't exist until a servlet call is made.<br> <br> How come this happens, and is it necessary to create an instance that gets thrown away ?<br> <br> Cheers<br> <br> Cameron<br> <br> <br> <pre cols="72" class="moz-signature">-- Any damn fool can write code that a computer can understand... The trick is to write code that humans can understand. [Martin Fowler <a class="moz-txt-link-freetext" href="http://www.martinfowler.com/distributedComputing/refactoring.pdf">http://www.martinfowler.com/distributedComputing/refactoring.pdf</a>]</pre> </body> </html> |