Hi Elisabeth, Not only you have to provide a Coder on the client and the server, you also need to have the coder-registry-provider where you registered the coder on the client and the server. You'll find documentation on how to create your own coder and register it with the coder registry in the ULC Extension Guide of ULC 6.1.
For the DevelopmentRunner you can specify the coder-registry-provider through command line args as follows: -client-coder-registry-provider <class name> -server-coder-registry-provider <class name> I hope this helps. Thanks and regards, Janak PS; ULC 6.1.1 has been released. So if you are migrating from ULC 6.0.4 might as well migrate to 6.1.1. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kliman, Elizabeth Sent: Friday, August 11, 2006 2:32 AM To: [email protected] Subject: [ULC-developer] Migrating Date Component: no coder registered error Hi, I am trying to migrate my Date Component widget to ULC 6.1. On the code community site the Date Chooser widget has been upgraded, but the Date Component has not, so I am trying to convert it myself. (It would be greatly helpful if anyone has already done this!) I have run into the following error and I haven't been able to make any progress on it. I don't know where this is coming from because it is in the ULC code. Maybe you can provide some insight? 1 10.08.2006 11:44:49.541 1,000 SEVERE Thread[ULC Communication Controller Thread,6,main] com.ulcjava.base.client.UISession$k_ run exception occured [com.ulcjava.base.client.ConnectorException: error while sending requests at com.ulcjava.base.development.DevelopmentConnector.sendRequests(DevelopmentCo nnector.java:5) at com.ulcjava.base.client.UISession$k_.run(UISession$k_.java:107) at java.lang.Thread.run(Thread.java:534) Caused by: com.ulcjava.base.shared.internal.IllegalArgumentException: No coder registered for class sun.util.calendar.ZoneInfo at com.ulcjava.base.shared.internal.UlcObjectOutputStream.a(UlcObjectOutputStre am.java:165) at com.ulcjava.base.shared.internal.UlcObjectOutputStream.writeObject(UlcObject OutputStream.java:93) at com.ulcjava.base.shared.internal.UlcObjectOutputStream.writeObject(UlcObject OutputStream.java:122) at com.ulcjava.base.shared.streamcoder.MapCoder.writeObject(MapCoder.java:17) at com.ulcjava.base.shared.internal.UlcObjectOutputStream.writeObject(UlcObject OutputStream.java:96) at com.ulcjava.base.shared.streamcoder.AnythingCoder.writeObject(AnythingCoder. java:5) at com.ulcjava.base.shared.internal.UlcObjectOutputStream.writeObject(UlcObject OutputStream.java:96) at com.ulcjava.base.shared.streamcoder.MapCoder.writeObject(MapCoder.java:17) at com.ulcjava.base.shared.internal.UlcObjectOutputStream.writeObject(UlcObject OutputStream.java:96) at com.ulcjava.base.shared.internal.Request.writeRequests(Request.java:4) at com.ulcjava.base.development.DevelopmentConnector.a(DevelopmentConnector.jav a:9) at com.ulcjava.base.development.DevelopmentConnector.sendRequests(DevelopmentCo nnector.java:16) at com.ulcjava.base.client.UISession$k_.run(UISession$k_.java:107) at java.lang.Thread.run(Thread.java:534) ] We are using a TimeZone in a number of places for the Date Component and ZoneInfo is a subclass of TimeZone, so I guess that must be where the problem is coming from. I'm just not sure which reference is causing the issue or what it is trying to do that is causing the issue. I wrote up a coder for ZoneInfo to see if I could get that to work, but it didn't seem to work. I'm trying to run through the development launcher. Thanks. Elizabeth Kliman, B.Sc., SCJP Developer / Développeur Information Technology / Technologie de l'information Farm Credit Canada / Financement agricole Canada 1800 Hamilton Street, P.O. Box 4320 1800, rue Hamilton, C.P. 4320 Regina SK S4P 4L3 Tel/Tél. : (306) 780-3382 Fax/Télec. : (306) 780-5655 E-mail/Courriel : [EMAIL PROTECTED] Agriculture. It's all we do. L'agriculture... notre raison d'être. This message may contain information that is privileged, protected, confidential or subject to copyright. Using, disclosing, copying or distributing such information by anyone other than the intended recipient is strictly prohibited. If youve received this message in error, please delete it and notify me immediately. Le présent courriel contient des renseignements de nature privilégiée, protégée, confidentielle ou assujettie à des droits dauteur. Toute utilisation, communication, reproduction ou distribution de linformation contenue dans ce courriel par toute personne autre que le destinataire visé est strictement interdite. Si vous avez reçu ce courriel par erreur, veuillez le supprimer et men informer immédiatement. _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
