Hi Mario,
I don't understand why you want to write a coder for the enum type.
As I said in my earlier mail you need to define a coder for the class that
defines the enum within it. I.e. you should define a coder for your class A.
Your class A will have members of type PropertyIds and when you
serialize/deserialize A and these members will be written/read correctly.
Therefore, the only reason you should make your enum type public is when you
want to use thei type (A.PropertyIds) in another class.
BTW, the following does not make sense and is syntactically wrong too:
>Class a{
> String name
>
> static enum propertyids b{
> Dummy;
> }
> }
>
Thanks and regards,
Janak
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Mario H.
>Castillo
>Sent: Thursday, October 05, 2006 10:22 PM
>To: [EMAIL PROTECTED] Com
>Subject: [ULC-developer] Inner class encoder
>
>
>Janak,
>
>If I have the following module :
>
>Class a{
> String name
>
> static enum propertyids b{
> Dummy;
> }
> }
>
>
>How do write the coder for the inner "class propertyids" since I
>need access
>to the private class a.propertyids? For now, I made it public, but if
>I continue like this, I will have to expose all kinds of internals
>to build
>these coders. Any suggestions?
>
>Class a{
> String name
>
> public static enum propertyids b{
> Dummy;
> }
> }
>
>Mario
>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
