Package org.alfresco.util
Class WebApplicationContextLoader
- java.lang.Object
-
- org.alfresco.util.WebApplicationContextLoader
-
public class WebApplicationContextLoader extends Object
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description protected static class
WebApplicationContextLoader.WebApplicationContext
-
Constructor Summary
Constructors Constructor Description WebApplicationContextLoader()
-
Method Summary
All Methods Static Methods Concrete Methods Modifier and Type Method Description static org.springframework.context.ConfigurableApplicationContext
getApplicationContext(javax.servlet.ServletContext servletContext, String[] configLocations)
Provides a static, single instance of the application context.static org.springframework.context.ConfigurableApplicationContext
getApplicationContext(javax.servlet.ServletContext servletContext, String[] configLocations, String[] classLocations)
static boolean
isContextLoaded()
Is there currently a context loaded and cached?static boolean
isNoAutoStart()
Will Subsystems with the autoStart=true property set on them be allowed to auto start? The default is to honour the spring configuration and allow them to, but they can be prevented if required.static boolean
isUsingLazyLoading()
Will the Spring beans be initilised in a lazy manner, or all in one go? The default it to load everything in one go, as spring normally does.static void
setNoAutoStart(boolean noAutoStart)
Should the autoStart=true property on subsystems be honoured, or should this property be ignored and the auto start prevented? Normally we will use the spring configuration to decide what to start, but when running tests, you can use this to prevent the auto start.static void
setUseLazyLoading(boolean lazyLoading)
Should the Spring beans be initilised in a lazy manner, or all in one go? Normally lazy loading/intialising shouldn't be used when running with the full context, but it may be appropriate to reduce startup times when using a small, cut down context.
-
-
-
Method Detail
-
getApplicationContext
public static org.springframework.context.ConfigurableApplicationContext getApplicationContext(javax.servlet.ServletContext servletContext, String[] configLocations)
Provides a static, single instance of the application context. This method can be called repeatedly. If the configuration requested differs from one used previously, then the previously-created context is shut down.- Returns:
- Returns an application context for the given configuration
-
getApplicationContext
public static org.springframework.context.ConfigurableApplicationContext getApplicationContext(javax.servlet.ServletContext servletContext, String[] configLocations, String[] classLocations) throws IOException
- Throws:
IOException
-
setUseLazyLoading
public static void setUseLazyLoading(boolean lazyLoading)
Should the Spring beans be initilised in a lazy manner, or all in one go? Normally lazy loading/intialising shouldn't be used when running with the full context, but it may be appropriate to reduce startup times when using a small, cut down context.
-
isUsingLazyLoading
public static boolean isUsingLazyLoading()
Will the Spring beans be initilised in a lazy manner, or all in one go? The default it to load everything in one go, as spring normally does.
-
setNoAutoStart
public static void setNoAutoStart(boolean noAutoStart)
Should the autoStart=true property on subsystems be honoured, or should this property be ignored and the auto start prevented? Normally we will use the spring configuration to decide what to start, but when running tests, you can use this to prevent the auto start.
-
isNoAutoStart
public static boolean isNoAutoStart()
Will Subsystems with the autoStart=true property set on them be allowed to auto start? The default is to honour the spring configuration and allow them to, but they can be prevented if required.
-
isContextLoaded
public static boolean isContextLoaded()
Is there currently a context loaded and cached?
-
-