Actually, it is solved. But why did the applicationContext.xml have lazy init turned on? When I commented this out, it worked. Wast there a good reason to have lazy init turned on? Everything else still seems to work with this turned off. Seems like a bad default. I spent many hours trying to figure this out.
applicationContext.xml has this next the top of the file. default-lazy-init="true" Sincerely, Wayne hatrang wrote: > > I also tried implementing the ApplicationContactAware interface > but that the setApplicationContect() function never gets called. > > A: maybe because your backing bean is not a Spring bean (i.e. you didn't > define a bean for this class in the Spring configuration file). > > > How can I make it access my Manager classes? > > A: in the Spring configuration file, you should define a bean for your > manager class, e.g > > <bean id="myManager" class="your.path.MyManager" /> > > If your backing bean is a Spring bean, then implementing the > ApplicationContextAware will give your backing bean a reference to the > ApplicationContext which is used to access other Spring beans (including > the `myManager' bean above). > > If your backing bean is not a Spring bean, then can it access a > reference to the HttpServletRequest or anything which can get a > reference to the ServletContext? If it can, then use > org.springframework.web.context.support.WebApplicationContextUtils. > getWebApplicationContext(ServletContext sc) to get an > ApplicationContext. > > -----Original Message----- > From: WayneFH [mailto:[EMAIL PROTECTED] > Sent: Friday, October 12, 2007 3:03 PM > To: [email protected] > Subject: [appfuse-user] Dependency Injecting into a POJO bean fails? > > > I'm new to Spring and searched everywhere. > > My department refuses to use JSF, Spring MVC, etc. > Just regular JSP pages. > > So, I have a JSP and backing bean (POJO) that will have an instance per > session. > > How can I make it access my Manager classes? I already have working > JUnit > tests that call the Manager classes and create, read, update, and delete > succesfully. > > I tried this and the pointer is always null. > > private CaseItemManager caseItemManager = null; > > public void setCaseItemManager( CaseItemManager caseItemManager) { > this.caseItemManager = caseItemManager; > } > > I also tried implementing the ApplicationContactAware interface > but that the setApplicationContect() function never gets called. > > How to make this object Spring aware? > > Sincerely, > Wayne > > -- > View this message in context: > http://www.nabble.com/Dependency-Injecting-into-a-POJO-bean-fails--tf461 > 4413s2369.html#a13177765 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > NOTICE: This message (including any attachments) from Momentum Systems, > Inc. contains information that is PRIVILEGED and CONFIDENTIAL. If you are > not an intended recipient, you are hereby notified that any dissemination > of this message is strictly prohibited. If you have received this message > in error, please do not read, copy or forward this message. Please > permanently delete all copies and any attachments and notify the sender > immediately by reply email or by calling our Office at 703.740.9300. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Dependency-Injecting-into-a-POJO-bean-fails--tf4614413s2369.html#a13182904 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
