This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello All, I am working on an application that was developed using spring framework.The application server used was Weblogic 7.0. When an application is deployed, I could see few beans loaded and executed. But I couldnot figure out where these beans are cofigured. I was trying to identify the entry point to the application when it is deployed. I have checked weblogic application server startup classes and I see that no classes are configured as startupclasses. Hence my thinking is that these classes might be configured somewhere in the application. I am not sure where. I have gone through web.xml file and could find nothing. I am not quite sure of spring framework configuration hence I was thinking of getting help from some one in finding the configuration for these files.
Your suggestion would be a great help to me.
Thank you in advance [ March 29, 2005: Message edited by: s penumudi ]
Spring applications are most often configured using xml files. For web apps, these will typically be found in WEB-INF with names like applicationContext.xml and xxxxx-servlet.xml (if SpringMVC was caused).
kktec<br />SCJP, SCWCD, SCJD<br />"What we observe is not nature itself, but nature exposed to our method of questioning." - Werner Heisenberg
Joined: Nov 17, 2004
Yes, I looked at XXX-servlet.xml file for the startup files.
I haven't seen any configuration that says these classes have to be loaded on deployment of the application.
Do you know how the startup classes are configured?
Joined: Nov 27, 2002
I'm not sure what you're getting at.
In the Petclinic web.xml is a declaration of a servlet, org.springframework.web.context.ContextLoaderServlet, that takes care of loading the Spring application context files. Alternatively, a listener of type org.springframework.web.context.ContextLoaderListener could have been declared that does the same thing. Either method has the same result; the beans declared in the xml files (which are the application configuration files) are instantiated and wired up. This works the same way in any servlet container.