Re: [Wonder-disc] Wonder wants full class name for my entity

[Q <qd...@gm...>]

On 29/05/2009, at 9:39 PM, Mike Schrag wrote:

>>> But for the time being the class names for the entities do not have
>>> the package name.  Is there any way to bypass this for the time
>>> being so I can proceed with the conversion to Wonder of my
>>> application?  :-)
>>
>> No. And it will probably take all of 30 mins to fix the names if you
>> have < 200 entities...
> is there a reason this isn't an _NSUtilities.classWhatever? I don't
> remember .. I remember wrapping this in a nicer exception a while
> back, which i assume means I at least thought about this some.  does
> partial name break something down the chain?

Just to put in my 2c worth, using Class.forName(String)  is evil. It  
can potentially screw up anything making use of nested classloaders.  
It is generally preferred to use the Class.forName(String, boolean,  
ClassLoader) variant with the thread context  class loader first and  
then defer to the system classloader if necessary.  If  
_NSUtilities._classWithFullySpecifiedName(String) did this it wouldn't  
suck nearly as much.

-- 
Seeya...Q

Quinton Dolan - qd...@gm...
Gold Coast, QLD, Australia (GMT+10)
Ph: +61 419 729 806