Can you kindly point me to a wiki or example that shows an actual implementation for registering one's own LanguageImpl bean into the portal's Spring context to replace the default bean?I can't provide you with an actual implementation, but I can describe what that implementation needs to look like.
To do exactly what you've decribed, you would need to create an
EXT plugin, which would theoretically allow you to replace the bean for LanguageUtil (see
util-spring.xml to see how it was originally defined) with a different bean that sets the language property to your own custom implementation, which would probably look something like this:
<beans default-destroy-method="destroy" default-init-method="afterPropertiesSet" xmlns="http://www.springframework.org/schema/beans" xmlns:aop="http://www.springframework.org/schema/aop" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">
<bean id="com.liferay.portal.kernel.language.LanguageUtil" class="com.liferay.portal.kernel.language.LanguageUtil">
<property name="language">
<bean class="com.example.MyCustomLanguageImpl" />
</property>
</bean>
</beans>
If you're trying to avoid using EXT plugins, you can achieve something similar by calling
LanguageUtil.setLanguage to replace the underlying implementation of Language (since the LanguageUtil you're looking at comes from the global classloader, so setting static fields works), and then all calls to LanguageUtil will use your implementation instead.
You can do this inside of a servlet context listener which you specify in your plugin's web.xml or instead of a global.startup.events portal properties hook. The code sample below is what the injection would look like for a servlet context listener:
package com.example;
import com.liferay.portal.kernel.util.BasePortalLifecycle;
import javax.servlet.ServletContextListener;
public class MyContextListener
extends BasePortalLifecycle
implements ServletContextListener {
@Override
protected void doPortalInit() throws Exception {
_oldLanguage = LanguageUtil.getLanguage();
new LanguageUtil().setLanguage(new MyCustomLanguageImpl());
}
@Override
public void contextDestroyed(ServletContextEvent servletContextEvent) {
new LanguageUtil().setLanguage(_oldLanguage);
}
@Override
public void contextInitialized(ServletContextEvent servletContextEvent) {
registerPortalLifecycle();
}
private Language _oldLanguage;
}
The EXT plugin approach allows you to reuse a lot of the original LanguageImpl implementation (because you are in the portal class loader, you can just extend LanguageImpl directly), but the regular plugin approach allows you to redeploy your changes and test your modifications incrementally.
