The question is this done intentionally or is it bug.
Well, I'm trying to debug this through and find a reason why it is working differently.
So here a little progress:
With Liferay 6.0.6 and 6.1.0 both reason ends up at
com.liferay.portal.bean.BeanLocatorImpl method
doLocate(..) and at line "
return _applicationContext.getBean(name);"
When I inspect that "
_applicationContext"
at 6.0.6 I get with debug
1_applicationContext.getClassLoader()
2 (org.apache.catalina.loader.WebappClassLoader) WebappClassLoader
3 context:
4 delegate: false
5 repositories:
6 /WEB-INF/classes/
7----------> Parent Classloader:
8org.apache.catalina.loader.StandardClassLoader@6d3f7281
9
10_applicationContext.getDisplayName()
11 (java.lang.String) Root WebApplicationContext
12
13_applicationContext.getBeanDefinitionCount()
14 (int) 1
and 6.1.0 I get with debug
1_applicationContext.getClassLoader()
2 (org.apache.catalina.loader.WebappClassLoader) WebappClassLoader
3 context:
4 delegate: false
5 repositories:
6 /WEB-INF/classes/
7----------> Parent Classloader:
8org.apache.catalina.loader.StandardClassLoader@11a06e38
9
10_applicationContext.getDisplayName()
11 (java.lang.String) Root WebApplicationContext
12
13_applicationContext.getBeanDefinitionCount()
14 (int) 0
So it seems that bean is not getting registered to _applicationContext at 6.1.0, why is that? Where the bean registration to
_applicationContext happen?
Be kell jelentkezni ahhoz, hogy ez helytelenként legyen megjelölve.