Announcement

**Isomorphic** · 21 May 2013, 08:14

Use the latest patched build - see SmartClient.com/builds.

**DSingh** · 28 May 2013, 07:37

Still facing the same issue.

What will be the ETA for production release of SmartGwt 4.0 version?

Regards
Deepak

**Isomorphic** · 28 May 2013, 12:26

There was a fix in this area 3 days, please try the latest patched build.

**DSingh** · 28 May 2013, 22:49

Still Having the ISSUE.
I have downloaded Latest build of SmartGWT 4.0. I am using Power edition.

For your reference I have component XML in which I have Canvas Form Layout With Id "ABCD". In Java side I have loaded the component XML and Trying to Create Form With ID "ABCD" it is not allowing me to do so.

Steps to recreate this issue :
1. Create compoennt XML with some Compoent Say Form with ID= XYZ.
2. In Java side Load it.
3. Create Form Component With Same Id.(XYZ)

Please see the below error stack....

java.lang.IllegalStateException: Cannot change configuration property '_autoAssignedID' to false now that component LOGIN_FORM has been created.
at com.smartgwt.client.widgets.BaseWidget.error(BaseWidget.java:673)
at com.smartgwt.client.widgets.BaseWidget.error(BaseWidget.java:661)
at com.smartgwt.client.widgets.BaseWidget.setAttribute(BaseWidget.java:931)
at com.smartgwt.client.widgets.BaseWidget.setID(BaseWidget.java:377)
at com.archway.smartgwt.client.FWWidgetProperties.setProperties(FWWidgetProperties.java:101)
at com.archway.smartgwt.client.FWDynamicForm.<init>(FWDynamicForm.java:59)
at com.archway.smartgwt.client.estore.ESLogin.drawLoginSection(ESLogin.java:63)
at com.archway.smartgwt.client.estore.ESMain.drawLoginSection(ESMain.java:138)
at com.archway.smartgwt.client.FWMain$1.execute(FWMain.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:338)
at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:219)
at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:571)
at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:279)
at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:242)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:293)
at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547)
at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
at java.lang.Thread.run(Thread.java:662)

Regards,
DSingh

**DSingh** · 29 May 2013, 23:05

Any update on above issue?

**Isomorphic** · 30 May 2013, 10:06

We are currently investigating this issue and will let you know when we have any information

Regards
Isomorphic Software

**DSingh** · 11 Jun 2013, 22:19

Any update on this?

**Isomorphic** · 12 Jun 2013, 13:59

Firstly a clarification:
Your description here:

1. Create compoennt XML with some Compoent Say Form with ID= XYZ.
2. In Java side Load it.
3. Create Form Component With Same Id.(XYZ)

Sounds like you might be getting a legitimate reported ID collision. In other words, something like this:

XML code:

Code:

<Canvas ID="ABCD" backgroundColor="pink"/>

Then in Java you load this XML [via loadScreen, say]

Then you create a new widget with the same ID in Java

Code:

Canvas javaABCD = new Canvas();
javaABCD.setID("ABCD");
// ... other code

In this case there's a legitimate collision between the ABCD canvas created in JavaScript (loaded form XML) and the new version created directly in Java. Widget IDs need to be unique across the page, so when you assign the same ID to 2 separate Canvases, the creation of the second will automatically cause the destruction of the first (which could lead to odd behaviors in your app if the app has not been structured in a way which expects this).

Having said all that, we have had another report of what appears to be this same warning being fired inappropriately and have been attempting to reproduce this problem.
See this thread.

We now have what appears to be a reproducible case to work with and are continuing to investigate.
It seems very likely that you are seeing the same problem as the one reported here. However, if you could show us a way to reproduce the problem as you're seeing it, we can confirm this for certain.

Regards
Isomorphic Software

Announcement

Migrating to 4.0

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment