yeah, the EOSchemaSynchronization is there I know, it's the (new) 
EOSynchronizationFactory that is missing


Am 19.01.2012 um 16:20 schrieb Ramsey Gurley:

> http://developer.apple.com/legacy/mac/library/documentation/InternetWeb/Reference/WO542Reference/com/webobjects/eoaccess/synchronization/EOSchemaSynchronization.html
> 
> It's there.  It's in the interfaces.  Just do a command-shift-T and you'll 
> find it.
> 
> Ramsey
> 
> On Jan 19, 2012, at 2:06 AM, Johann Werner wrote:
> 
>> Hi list,
>> 
>> as there are some people from Apple reading this mailing list I will just 
>> drop in my question and hoping to get any response.
>> 
>> Currently working with the different JDBC adaptors of Wonder I stumbled on 
>> the deprecation warnings of the classes
>> 
>> com.webobjects.eoaccess.EOSchemaGeneration
>> com.webobjects.eoaccess.EOSchemaSynchronization
>> com.webobjects.eoaccess.EOSynchronizationFactory
>> 
>> In the WO-API there is the notice that these classes have been replaced by 
>> classes in the com.webobjects.eoaccess.synchronization package. But 
>> unfortunately I cannot find the class 
>> com.webobjects.eoaccess.synchronization.EOSynchronizationFactory it seems 
>> that only the deprecated class exists. Is that an error in the API 
>> documentation, was it scheduled for WO 5.5 ;) or was it present in WO 5.4.2 
>> but then removed in 5.4.3?
>> 
>> jw
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/webobjects-dev/ramseygurley%40gmail.com
>> 
>> This email sent to [email protected]
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to