Hi Mario, The code for ULCSplitPane has changed between 6.1.2 and 6.1.3. The change is that after adding/removing a component or setting attribute (location, size) of divider, the divider location is set to unknown on the server side and the client is informed to sync the correct value in the next round trip by flushing the dirty data i.e. the client side values of divider attributes.
In you case a DirtyDataHandler seems to be null. I cannot imagine that the DirtyDataHandler of client side proxy of ULCSplitPane is null because it is initialized in postInitializeState of UISplitPane on the client side. You are saying that you have an extension for ULCSplitPane. Can you tell me: 1 What exactly are you doing in the extension? 2. Have you coded any explicit upload() on ULCSplitPane? 3. Are you using a DirtyDataHandler of your own somewhere in your extension? Kindly provide above details to help further investigation. It will be best if you can provide a snippet. Thanks and regards, Janak >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Mario H. >Castillo >Sent: Thursday, March 22, 2007 10:57 AM >To: [EMAIL PROTECTED] Com >Subject: [ULC-developer] Exception question.. > > >Janak, > >We have a splitpane class and splitpane extension with several >components in >between, in any case, when we switched from 6.1.2 to 6.1.3 we get the >following exception when >making an "invokeULC" call. > >1 22.03.2007 00:17:03.021 1,000 SEVERE Thread[AWT-EventQueue-2,6,main] >com.ulcjava.base.client.UISession$l_ b got exception while flushing dirty >data [java.lang.NullPointerException > at com.ulcjava.base.client.UISession$l_.b(UISession$l_.java:89) > at >com.ulcjava.base.client.UISession$l_.addPendingRequest(UISession$l_ >.java:49) > at com.ulcjava.base.client.UISession.a(UISession.java:295) > at com.ulcjava.base.client.UISession.send(UISession.java:24) > at com.ulcjava.base.client.UIProxy.invokeULC(UIProxy.java:55) > at com.ulcjava.base.client.UIProxy.invokeULC(UIProxy.java:214) >........ > >I have tried to duplicate the exception in a "simpler & smaller" >sample but >so far I have not been able to duplicate it. Any idea(s) about the >exception and what it might indicate? >Again, if we switch to 6.1.2 we do not recive this exception.... > >Mario >C/O Abacus Research. > >_______________________________________________ >ULC-developer mailing list >[email protected] >http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
