Announcement

**Isomorphic** · 30 Dec 2011, 13:07

Your <fmt> tag is probably not executing at all because you've done something wrong in implementing DataSource i18n as explained in the docs.

**claudiobosticco** · 31 Dec 2011, 03:19

I think that the <fmt:message> tag is executing correctly, because I'm already using the datasource internationalization with success, so my ds starts with:

Code:

<!--
 <%@page pageEncoding="UTF-8" contentType="text/xml; charset=UTF-8"%>
 <%@ taglib prefix="fmt" uri="/WEB-INF/fmt.tld" %>
 <fmt:setBundle basename="i18nMessages_${locale}" var="i18n"/>
 -->
<DataSource xmlns:fmt="urn:jsptld:/WEB-INF/fmt.tld"
...

and like I said in the "view source" of the page I see the js translated datasource code correct:

Code:

operationBindings:[
        {
            operationType:"fetch",
            criteria:{
                fieldName:"NOME_GRUPPO",
                value:"ROLE_ADMIN"
            }
        }
    ]

**Isomorphic** · 31 Dec 2011, 12:43

Ah, sorry. Yes it's being processed for delivery to the client, but the server-side definition of the DataSource does not use your i18n strings and in fact gets the raw XML of the <fmt> tag which causes the error you're seeing.

If you actually have a reason to use i18n strings in server-side logic like you show, you can add a DMI that retrieves the String and adds it to the criteria in the dsRequest.

**claudiobosticco** · 2 Jan 2012, 01:35

thanks, now I see that what I was doing is absurd..clearly the i18n approach works only for client-only datasource attributes.

Announcement

[bug ?] operationBinding criteria and fmt:message tag

Comment

Comment

Comment

Comment