Announcement

**Isomorphic** · 15 Sep 2010, 12:08

Yes, the "fmt" tag is from that taglib - you'll need to install it.

When you switch over to JSP-based formatting, you need to replace the DataSourceLoader servlet as well - note the section that talks about this and shows "<isomorphic:XML>" tags.

Basically, create .jsp with one <jsp:include> per i18n'd DataSource, and use a <script src=> tag to point to that .jsp instead of the DataSourceLoader servlet. If you watch in Firebug, you'll see the .jsp returning a series of JavaScript DataSource definitions (just like the DataSourceLoader servlet).

**dczech** · 16 Sep 2010, 09:53

Thanks for the advice. I have it working, but I'd like to check to see if I did it correctly since I wasn't able to get the <script src=> the .jsp part working in my Ping.html within GWT development mode in Eclipse. (I've not checked that approach in a deployment environment yet.)

These are the changes I did in regards to my above code. First, I fixed the web.xml to point to the correct ds directory:

Code:

        <!-- For I18N of ds.xml fields, etc. -->
        <jsp-property-group>
            <url-pattern>/ds/*</url-pattern>
        </jsp-property-group>

Next I changed Ping.html into Ping.jsp, with the following difference:

Code:

    <!--load the datasources-->
    <jsp:include page="loadpingds.jsp"></jsp:include>

This is the new loadpingds.jsp:

Code:

<%@ taglib uri="/WEB-INF/iscTaglib.xml" prefix="isomorphic" %>

<SCRIPT>
    <isomorphic:XML>
    <jsp:include page="/ds/PING.ds.xml"></jsp:include>            
    </isomorphic:XML>
</SCRIPT>

I was unsure where to put the "<jsp:include> per the i18n'd DataSource", but I did modify the ds.xml like this to get the localizations to get appropriately swapped.

Code:

<!--
<%@ taglib prefix="fmt" uri="/WEB-INF/fmt.tld" %>

<fmt:setBundle basename="com.smartgwt.sample.client.ClientConstants" />

-->

<DataSource xmlns:fmt="urn:jsptld:/WEB-INF/fmt.tld"  
	schema="PING"
	dbName="Oracle"
	tableName="PING"
	ID="PING"
	serverType="sql"
>
	<fields>
		<field sequenceName="PING_SEQ" primaryKey="true" name="id" type="sequence" hidden="true"></field>
		<field name="name" length="51" type="text">
			<title><fmt:message key="ping_ds_field_name" /></title>
			<validators>
				<validator type="isUnique" requiresServer="true" />
			</validators>
		</field>
		<field name="other" length="21" type="text">
			<title><fmt:message key="ping_ds_field_other" /></title>
		</field>
	</fields>
	
	<operationBindings>
		<operationBinding operationType="fetch" >
			<orderClause>UPPER(ping.PING.name)</orderClause>
		</operationBinding>
	</operationBindings>
</DataSource>

Lastly, I added a new properties file, ClientConstants_en.properties, for English:

Code:

clear=Clear 
_new=New
save=Save

ping_ds_field_name=Name
ping_ds_field_other=Other

If I didn't have the English version of properties, the translations did not use the defaults in the ClientConstants.class file.

Now it works, but, is this the acceptable, correct approach?

I note that the localization seems to be driven by the browser's Language preference setting, rather than the meta tag set for GWT that is in the .jsp �

Code:

    <meta name="gwt:property" content="locale=es">

This seems to mean as a side effect of not being a pure-Javascript SmartClient app, a SmartGWT app will have two mechanisms for localization if I want ds.xml files are to be localized.

So, in the Ping.java instead of writing code like this:

Code:

    private ClientConstants constants = GWT.create(ClientConstants.class);

// ... and so on
        newBtn = new IButton(constants._new());

Have code like this:

Code:

	newBtn = new IButton("<fmt:message key=\"ping_ds_field_other\" />");

Is there a best practices approach to use the same approach in the .java code?

**Isomorphic** · 16 Sep 2010, 10:28

By "<jsp:include> per the i18n'd DataSource" we meant that to i18n further DataSources, you can just add more jsp:include lines to your loadpingds.jsp (so it should probably be named loadDataSources.jsp or similar instead).

You didn't mention what we wrong when you tried to just point a <script src=> tag at this .jsp - is that not working?

We're not sure what Ping.java is but you don't need any Java code for this localization - this is server-side localization and doesn't involve the GWT compiler. However you may want to use a shared .properties file for the messages you are using server-side and the ones you are using client-side, since they probably overlap - there are multiple GWT localization strategies some of which support using .properties files.

Finally, yes, since this is .jsp-based localization, the default locale is the one sent from the browser, but could pass it in as an ordinary HTTP parameter to the JSP if you want to provide explicit switching.

**dczech** · 16 Sep 2010, 10:54

You didn't mention what we wrong when you tried to just point a <script src=> tag at this .jsp - is that not working?

What I've determined is that DataSource isn't being processed and the page does not load. Here's the error GWT Eclipse plug-in Development Mode:

Code:

11:33:43.392 [ERROR] [Ping] Unable to load module entry point class com.smartgwt.sample.client.Ping (see associated exception for details)
java.lang.NullPointerException: null
    at com.smartgwt.client.widgets.grid.ListGrid.setDataSource(ListGrid.java:11727)
    at com.smartgwt.sample.client.Ping.onModuleLoad(Ping.java:50)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:369)
    at com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:185)
    at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:380)
    at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:222)
    at java.lang.Thread.run(Unknown Source)

Ping.java, line 50 is:

Code:

        grid.setDataSource(ds);

I've not been able to get any additional information about this from the Developer Console.

We're not sure what Ping.java is but you don't need any Java code for this localization - this is server-side localization and doesn't involve the GWT compiler.

Ping.java is my 'small reproducer' test program for trying out new-to-me SmartGWT concepts or exploring issues I'm facing in developing a larger application. It is a learning tool for me. I thought I needed Java code for this localization to get the three buttons to localize in the Java code. This is not correct?

However you may want to use a shared .properties file for the messages you are using server-side and the ones you are using client-side...

I am sharing or at least believe I am, although my name choice should be better. The ClientConstants_en.properties and ClientConstants_es.properties are shared between the GWT compiled ping app (for the three buttons) and the server-side localization that the jsp is doing for the DataSource.

**Isomorphic** · 16 Sep 2010, 11:12

That error indicates the DataSource didn't load - almost all of the steps in the FAQ for troubleshooting DataSource loading from the DataSourceLoader apply (eg, look at what the response was in Firebug).

You want to continue to internationalize your client-side GWT code in the same way - nothing changes there.

**dczech** · 16 Sep 2010, 12:30

The response Firebug shows for loadpingds.jsp seems okay. Here it is for English:

Code:

<SCRIPT>
    
    

isc.DataSource.create({
    ID:"PING",
    dbName:"Oracle",
    schema:"PING",
    serverType:"sql",
    tableName:"PING",
    fmt:"urn:jsptld:/WEB-INF/fmt.tld",
    fields:{
        id:{
            hidden:true,
            name:"id",
            primaryKey:true,
            sequenceName:"PING_SEQ",
            type:"sequence"
        },
        name:{
            length:"51",
            name:"name",
            type:"text",
            title:"Name",
            validators:[
                {
                    requiresServer:"true",
                    type:"isUnique"
                }
            ]
        },
        other:{
            length:"21",
            name:"other",
            type:"text",
            title:"Other"
        }
    },
    operationBindings:[
        {
            operationType:"fetch",
            orderClause:"UPPER(ping.PING.name)"
        }
    ]
})
         
</SCRIPT>

I went back and restepped through the DataSource troubleshooting section of the FAQ and each checkpoint seems okay, but I have a question.

Even though the DataSourceLoader is in the web.xml, which isn't being used by Ping.html, do I need to also place the loadpingds.jsp in the web.xml as well? I've not done this.

Other than that, the DataSource ID and file name matches.

The server.properties' project.datasource is set correctly.

There are no malformed XML messages associated with loadpingds.jsp (or anything else) in the server log (in this case the Eclipse console output).

And the <script src="loadpingds.jsp"></script> line comes after the <script type="text/javascript" language="javascript" src="Ping/Ping.nocache.js"></script> in index.html.

The datasource and Ping app loads fine (minus localization) if I use the DataSourceLoader method, so unless the loadpingds.jsp needs to be somehow in the web.xml I'm not sure what else to try.

**Isomorphic** · 16 Sep 2010, 13:20

Those are all the right things to check - if you open your Developer Console and type isc.DS.get("PING") into the Evaluate JS Expression area and hit Evaluate, what do you get?

**dczech** · 16 Sep 2010, 14:11

Evaluator: result of 'isc.DS.get("PING")' (0ms):
null

**Isomorphic** · 16 Sep 2010, 14:16

Sorry for the wild goose chase, the problem is that you should not have <script> tags inside loadpingds.jsp because it's supposed to return just pure JavaScript.

**dczech** · 16 Sep 2010, 14:22

Excellent! That was it. Thank you.

**nikolayo** · 15 Nov 2010, 05:57

This thread seems as a good starting point for exploration of i18n. There are however 2 issues which perplex me :

1/ What exactly do tags of the kind "<fmt:message key="some_key"/>"? Do they retrieve translated message from a bundle on the server or do they generate JavaScript code which retrieves translated message from a bundle on the client? Or something else?
2/ In either case : how do these tags know which bundle to use?

**Isomorphic** · 15 Nov 2010, 11:27

The "fmt" tag is a standard JSTL tag - try Googling "fmt jsp tag" for usage and samples.

**nikolayo** · 15 Nov 2010, 12:32

Thank you! Sorry about being so uneducated on standard JSPs:(

**mathias** · 23 Nov 2010, 02:38

Hi,

i have asked a little bit about this kind of thing in another thread. Just as a gentle question - to me, it would be really neat to be able to somehow use GWT standard i18n for fields in the ds.xml's. This approach (which i just now saw) should work i guess, but it's a bit awkward having to split up my i18n resources in different places.

Is this somehow a known issue and/or are there any plans for adding "smoother" i18n features for the datasources?

Love the product, cheers.

Announcement

Not understanding i18n of DataSource ds.xml title fields

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment