Announcement

**Isomorphic** · 3 Jan 2012, 12:07

Note how the date value has been submitted to the server as a String (as shown in the server logs). This suggests that the field type is not being detected as "date" based on your SQL schema (which doesn't seem to be in the test case). Setting an explicit type="date" on the field would probably correct this, however, if you think we should have guess "date" was the right type based on the SQL schema, please let us know what the schema was.

**bbruyn** · 3 Jan 2012, 12:34

Right. Also from the server logs:

=== 2012-01-03 08:58:08,195 [l0-3] WARN SQLDataSource - ds:isc.DataSource.create({
serverType:"sql",
generatedBy:"SC_SNAPSHOT-2012-01-03_v8.3d/PowerEdition Deployment 2012-01-03",
schema:"PUBLIC",
dbName:null,
ID:"Order_inheritsFrom",
dataSourceVersion:"1",
fields:[
{
primaryKey:true,
name:"ORDERID",
type:"integer"
},
{
name:"CUSTOMERNAME",
length:255,
type:"text"
},
{
name:"ORDERDATE",
type:"date"
},
{
name:"TRACKINGNUMBER",
type:"integer"
}
]
})

The schema is the hsqldb schema from the samples dist - but it is in the testcase at WEB-INF/db/hsqldb.

In any case, I've also set the field type explicitly with the same result.

**Isomorphic** · 3 Jan 2012, 16:50

Something is definitely not right here. General ListGrid editing of "date" fields is obviously not out-and-out broken in the 3.0 release, so we think that test was not actually performed against 3.0. Similarly we're not seeing an issue with a JavaScript error on every save of a "date" field in the latest.

Both problems, if real, would have triggered failures on dozens of automated tests and we would also have dozens of users reporting the issue..

So you should sanity check your environment, specifically, use the instructions in the FAQ to verify that you're actually delivering updated .js files to the browser, and look for mixed versions being delivered.

**bbruyn** · 4 Jan 2012, 09:58

Were you able to run the test case successfully on your end then?

I've done all the usual clear cache, GWT compile, etc. with no change. FWIW, the version/dates (Version SC_SNAPSHOT-2012-01-03_v8.3d/PowerEdition Deployment (2012-01-03)) all check out for the following files:

ISC_Calendars.js
ISC_Containers
ISC_Core.js
ISC_Databinding.js
ISC_Forms.js
ISC_Foundation.js
ISC_Grids.js
ISC_RichTextEditor.js

Reaching, I thought there might be a problem with my gwt inherits, so pared it down to the following with the same result:

<inherits name='com.google.gwt.user.User'/>
<inherits name="com.smartgwtpower.SmartGwtPower"/>

Note that I don't have any problem if I build with the 2.5-RELEASE version.

**bbruyn** · 4 Jan 2012, 10:28

It's probably worth repeating that the net result, after clearing the 'uncaught exception' dialog by clicking 'ok', looks correct: The validation was applied and I find the error marker in the right place with the 'must be a date' prompt.

**bbruyn** · 5 Jan 2012, 08:54

Looks like this is only happening in development mode. IE 9 and Firefox 7.0.1.

Eclipse 3.7.1
Google Plugin for Eclipse 2.5.0v201112160242-rel-r37

**Isomorphic** · 6 Jan 2012, 05:33

Just so you don't think we're ignoring you, we are looking into this

**Isomorphic** · 10 Jan 2012, 15:22

We looked at this by incorporating the resources in a normal (non-Mavenized) project and didn't reproduce a problem.

One source of a difference (aside from Maven) is that we didn't have your SQL schema so we made our own. But this is unlikely to be the difference.

One thing to check on your end is whether the live response from the .jsp that loads your DataSources correctly shows the field as type:"date", or seems in any other way messed up (you could post it here).

**bbruyn** · 11 Jan 2012, 10:38

I'm not sure that makes much sense - sounds like something in the GWT stack is expecting a JavaScriptObject, but got an int back. The question is why does it want a JavaScriptObject. I don't doubt all this has something to do with the Maven setup. I've been looking, but I'm not smart enough to figure out the internals...

In any case, the .jsp result looks okay:

Code:

isc.DataSource.create({ fmt:"urn:jsptld:http://java.sun.com/jsp/jstl/fmt", ID:"Order", autoDeriveSchema:true, inheritsFrom:isc.DataSource.create({ serverType:"sql", generatedBy:"SC_SNAPSHOT-2012-01-05_v8.3d/PowerEdition Deployment 2012-01-05", schema:"PUBLIC", dbName:null, ID:"Order_inheritsFrom", dataSourceVersion:"1", fields:[ { primaryKey:true, name:"ORDERID", type:"integer" }, { name:"CUSTOMERNAME", length:255, type:"text" }, { name:"ORDERDATE", type:"date" }, { name:"TRACKINGNUMBER", type:"integer" } ] }) , fields:[ { canEdit:false, name:"ORDERID", primaryKey:true, type:"sequence", title:"Order #", prompt:"Order's unique identifier" }, { name:"CUSTOMERNAME", title:"Customer Name", prompt:"Customer's legal or DBA name" }, { name:"ORDERDATE", title:"Order Date", prompt:"Date the order was placed" }, { name:"TRACKINGNUMBER", title:"Tracking Number", prompt:"Tracking number provided by carrier at pickup from warehouse facility" } ], serverType:"sql" }) isc.DataSource.create({ fmt:"urn:jsptld:http://java.sun.com/jsp/jstl/fmt", ID:"OrderItem", autoDeriveSchema:true, inheritsFrom:isc.DataSource.create({ serverType:"sql", generatedBy:"SC_SNAPSHOT-2012-01-05_v8.3d/PowerEdition Deployment 2012-01-05", schema:"PUBLIC", dbName:null, ID:"OrderItem_inheritsFrom", dataSourceVersion:"1", fields:[ { primaryKey:true, name:"PK", type:"integer" }, { name:"ITEMDESCRIPTION", length:255, type:"text" }, { name:"QUANTITY", type:"integer" }, { name:"UNITPRICE", type:"float" }, { name:"ORDERID", type:"integer" } ] }) , fields:[ { hidden:true, name:"PK", primaryKey:true, type:"sequence", title:"Item #", prompt:"Order Item's unique identifier" }, { canEdit:false, foreignKey:"Order.ORDERID", name:"ORDERID", required:true, title:"Order #", prompt:"Order's unique identifier" }, { includeFrom:"Order.CUSTOMERNAME", name:"CUSTOMERNAME", title:"Customer Name", prompt:"Customer's legal or DBA name", canEdit:"false", type:"text" }, { name:"ITEMDESCRIPTION", required:true, title:"Description", prompt:"Short description of the item ordered" }, { name:"QUANTITY", required:true, title:"Quantity", prompt:"Number of units ordered" }, { name:"UNITPRICE", required:true, title:"Price per unit", prompt:"Dollar amount charged for each unit ordered" } ], serverType:"sql" })

With regard to the db schema - it is the same hsql schema provided in the SmartGWT samples, and is included in the test case.

**Isomorphic** · 11 Jan 2012, 15:41

Actually the .jsp response is not OK - look:

Code:

{ name:"ORDERDATE", title:"Order Date", prompt:"Date the order was placed" },

No type:"date". This would definitely cause the problem where the value of this field arrives at the server as a String.

You previously said that explicitly adding type="date" to the field definition in the .ds.xml does not solve the problem. If you add it now, do you see the .jsp response change to include type="date"? If not, maybe the problem has been that your .jsp responses have been *cached* somewhere (server or browser side) and this has been creating confusion when testing?

**bbruyn** · 11 Jan 2012, 16:03

Interesting. What should I make of the following then, from the same response?

Code:

{ name:"ORDERDATE", type:"date" }

**bbruyn** · 11 Jan 2012, 16:09

In any case, explicitly defining the field as type date

Code:

<field name="ORDERDATE" type="date">
            <title><fmt:message key="orderDate.title"/></title>
            <prompt><fmt:message key="orderDate.prompt"/></prompt>
</field>

does impact the response from the jsp

Code:

isc.DataSource.create({ fmt:"urn:jsptld:http://java.sun.com/jsp/jstl/fmt", ID:"Order", autoDeriveSchema:true, inheritsFrom:isc.DataSource.create({ serverType:"sql", generatedBy:"SC_SNAPSHOT-2012-01-05_v8.3d/PowerEdition Deployment 2012-01-05", schema:"PUBLIC", dbName:null, ID:"Order_inheritsFrom", dataSourceVersion:"1", fields:[ { primaryKey:true, name:"ORDERID", type:"integer" }, { name:"CUSTOMERNAME", length:255, type:"text" }, { name:"ORDERDATE", type:"date" }, { name:"TRACKINGNUMBER", type:"integer" } ] }) , fields:[ { canEdit:false, name:"ORDERID", primaryKey:true, type:"sequence", title:"Order #", prompt:"Order's unique identifier" }, { name:"CUSTOMERNAME", title:"Customer Name", prompt:"Customer's legal or DBA name" }, { name:"ORDERDATE", type:"date", title:"Order Date", prompt:"Date the order was placed" }, { name:"TRACKINGNUMBER", title:"Tracking Number", prompt:"Tracking number provided by carrier at pickup from warehouse facility" } ], serverType:"sql" }) isc.DataSource.create({ fmt:"urn:jsptld:http://java.sun.com/jsp/jstl/fmt", ID:"OrderItem", autoDeriveSchema:true, inheritsFrom:isc.DataSource.create({ serverType:"sql", generatedBy:"SC_SNAPSHOT-2012-01-05_v8.3d/PowerEdition Deployment 2012-01-05", schema:"PUBLIC", dbName:null, ID:"OrderItem_inheritsFrom", dataSourceVersion:"1", fields:[ { primaryKey:true, name:"PK", type:"integer" }, { name:"ITEMDESCRIPTION", length:255, type:"text" }, { name:"QUANTITY", type:"integer" }, { name:"UNITPRICE", type:"float" }, { name:"ORDERID", type:"integer" } ] }) , fields:[ { hidden:true, name:"PK", primaryKey:true, type:"sequence", title:"Item #", prompt:"Order Item's unique identifier" }, { canEdit:false, foreignKey:"Order.ORDERID", name:"ORDERID", required:true, title:"Order #", prompt:"Order's unique identifier" }, { includeFrom:"Order.CUSTOMERNAME", name:"CUSTOMERNAME", title:"Customer Name", prompt:"Customer's legal or DBA name", canEdit:"false", type:"text" }, { name:"ITEMDESCRIPTION", required:true, title:"Description", prompt:"Short description of the item ordered" }, { name:"QUANTITY", required:true, title:"Quantity", prompt:"Number of units ordered" }, { name:"UNITPRICE", required:true, title:"Price per unit", prompt:"Dollar amount charged for each unit ordered" } ], serverType:"sql" })

but the result is the same

**Isomorphic** · 11 Jan 2012, 16:40

Whoops, you are correct, the .jsp response is fine (it's correct that type="date" only appears in the implicit parent DataSource).

Just to clarify what you're seeing:

1) when you run the test case with what was intended to be the 2.5 or 3.0 release (modulo something weird with Eclipse/Maven) you see the date value arriving at the server as a String

2) when you run with the latest, you see the date arrive at the server as a date as expected (prints out in the server log like "new Date(5415421521)"), however, when you enter an invalid value while editing, there's a JavaScript exception *in GWT Development mode only*

All correct?

**bbruyn** · 11 Jan 2012, 19:01

Close. No problems with 2.5 - only with 3.0 and on.

Announcement

Exception thrown on ListGrid validation

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment