access messages.properties

[tma0si3]

Hello Friends,
For internationalization sake, I have defined messages in message.properties file. I have maintained different copies for different languages. It’s all fine now. Now, for generic error handling, I need access messages.properties values in DAO layer. How can access messages.properties in Spring Java Code?

~San

[Rossen Stoyanchev]

You can implement the MessageSourceAware interface.

[tma0si3]

Thanks ... But I am a newbee to spring !!!
Could you elobrate more on this Please

Thanks ~san

[Lyserg]

Hi,

if you implement MessageSourceAware, then the Spring Applicationcontext will inject the MessageSource into your Spring configured bean.

Here is an example

class Sample implements MessageSourceAware {

 private MessageSource messageSource;

 public void setMessageSource(MessageSource messageSourcePar) {

        messageSource = messageSourcePar;
 }

public void foo(){
      messageSource.getMessage(.. ,  .. ,  ...);
}
}

Note. The bean must be instanciated through teh Spring IOC Container, otherwise your MessageSource is null

regards
agim

[tma0si3]

Ok.I did as you suggested. Now I get some other error.

Piece of code “messageSource.getMessage("header.searchHotels", null,
Locale.ENGLISH)” gives me this following error is

"org.springframework.context.NoSuchMessageExceptio n: No message found under code 'header.searchHotels' for locale 'en'."




My Message Soorce entried in IBE-Servlet-config.xml are as follow

<bean id="messageSource" class="org.springframework.context.support.Resourc eBundleMessageSource">
<property name="basename" value="messages"/>
</bean>

<bean id="localeChangeInterceptor" class="org.springframework.web.servlet.i18n.Locale ChangeInterceptor">
<property name="paramName" value="siteLanguage"/>
</bean>

[Rossen Stoyanchev]

Check the content of your properties file. Is there a "header.searchHotels" property in the messages_en.properties on your classpath?

[tma0si3]

Got it , I moved the messageSoorce bean definition to Application Context XML.

<bean id="messageSource" class="org.springframework.context.support.Resourc eBundleMessageSource">
<property name="basename" value="messages"/>
</bean>


Its working now .Thanks

[Hardie82]

Hi at all,

I also want to use the message resource in my controller and implemented the interface. Now my question: how do I instanciate the resource to my controller? Is the following the right way?

<bean id="messageSource" class="org.springframework.context.support.Resourc eBundleMessageSource">
<property name="basenames">
<list>
<value>systemmsg</value>
<value>international</value>
<value>documentcreator</value>
</list>
</property>
</bean>

<bean id="fileUploadController" class="de.saxsys.hshec.controller.FileUploadContro ller">
<property name="commandClass" value="de.saxsys.hshec.domain.FileUploadBean" />
<property name="formView" value="ecupload" />
<property name="successView" value="ecupload" />
<property name="msgSource" ref="messageSource" />
</bean>

Regards
Hardie

[m4rkuz]

If Your using Web FLow:

Declaration of the message sopurce:

	<bean id="messageSource"
          class="org.springframework.context.support.ResourceBundleMessageSource">
        <property name="basenames">
            <value>messages</value>
        </property>
    </bean>

From within a flow just send the EL variable messageContext to your method ...

and the one I like:

	protected MessageContext getMessageContext() {
		MessageContext messageContext = (MessageContext) RequestContextHolder
		.getRequestContext().getMessageContext();
		return messageContext;
	}

with the last one you can get you're message properties anywhere on you're code, but seems to me that is not a god idea to attach messages from within a Dao, you better throw spring exceptions, like DataAccessException, ObjectRetrievalNotFound... etc.

[Tomasz Minkowski]

Just implement MessageSourceAware... I mean, come on, how cool is that??

Spring is just super-awesome.
And all these tireless answers on the forum... you're great.
Many thanks.