Re: Unexpected EOGeneralAdaptorException [SOLVED]

Hi Chuck,


>> So I don't really know how to debug this...
>>
> The first thing to think about is that the display in EOModeler is  
> configurable and that you may not be displaying the part that is  
> different.  In cases like this, I prefer to look directly at  
> the .plist in .eomodeld folder.  Open it up in a text editor and  
> check for any differences (other than name and column name) between  
> three three "exactly the same" attributes.  I suspect that you will  
> see something is different.
All 3 attributes "comes" from a prototype (thanks to your book;)), so  
I have:
----
         {columnName = "DELETED_ON"; name = deletedOn; prototypeName  
= dateTime; },
         {
             columnName = "LAST_UPDATE_PROFILE";
             name = lastUpdateProfile;
             prototypeName = dateTime;
         },
         {
             columnName = "REGISTRATION_DATE";
             name = registrationDate;
             prototypeName = dateTime;
         }
----
I don't really know why they don't show up with the exact same layout  
(line breaks)
So this comes from the parent class Person

the 2 subclasses are Employee and Member, here's what I have:
----
         {
             adaptorValueConversionMethodName = toString;
             allowsNull = Y;
             columnName = "DELETED_ON";
             externalType = DATETIME;
             internalInfo = {"_nameInObjectStore" = DELETED; };
             name = deletedOn;
             serverTimeZone = "Europe/Paris";
             valueClassName = NSCalendarDate;
             valueFactoryMethodName = "valueOf:";
             valueType = T;
         },

         {
             allowsNull = Y;
             columnName = "LAST_UPDATE_PROFILE";
             externalType = DATETIME;
             internalInfo = {"_nameInObjectStore" =  
"LAST_UPDATE_PROFILE"; };
             name = lastUpdateProfile;
             serverTimeZone = "Europe/Paris";
             valueClassName = NSCalendarDate;
             valueType = T;
         },
----

So I have an unexpected thing going in there...
I removed the extra lines and corrected the _nameInObjectStore and  
now it works...
I checked the inspector in EOModeler before changing things, and  
nothing was written/selected for the conversion method nor the  
factory method...

Anyway, thanks a lot Chuck for your help, I really owe you more than  
a beer!

>> I don't know why it's complaining about a String in fact:(
>>
> I see this sort of thing when something is wrong in the attribute  
> definition, usually the value type or internal type.
>
>
>> PS: Are you going again to WWDC? Any plan to make a training like  
>> last year?
>>
> I was planning on it, but we just got some new contracts so I will  
> have to see how they work out.  If I do go, I will probably arrange  
> some training sessions.  Any requests?  :-)

I didn't think about anything special, but I'll try to think about it  
and probably others will come up with ideas:)
What comes to me at this point are more "best practice" about  
modeling, like what's the best way to handle a multilingual  
application using both localized.strings files and localized  
wocomponent, or some pointer on how to factor code for easy reuse, etc
A couple other things are coming:
-hands on ajax with WO, but towards making it works when Javascript  
is not enabled/available. For example Apple updated their store with  
a couple of ajax stuff (like when you want to know more about the  
hard drive on a MacBook Pro configuration page), but if you turn off  
Javascript, it would open another window with only the extra content,  
so not an option in fact.
Personally I'm a lot concerned about accessibility and everything has  
to work without Javascript enabled for any administration or related  
in Europe for example, so it's a really big concern. Maybe also  
discuss about the session management when using ajax.
-I'd also loved to see things about SVG (there's introductory stuff  
on Mendis' book)
-and some also on image manipulation, like can we use something else  
than awt so we don't need to have the headless issue and also awt is  
using really too much memory, so maybe something more efficient.  
Handling of different file format (jpg, png, etc) as input and/or  
output, etc.

In fact there's a lot I can think about;)

I hope you'll be there:)
I'm actually preparing an email to post to both list to see if we  
could "merge" some stuff, like providing the extra tickets from  
premium member who won't go and by 5-packs tickets (maybe with an  
extra discount) to dispatch to all the ones who need one and can't  
pay the "regular" price. It costs a lot when coming from other part  
of the world than America;)

Xavier