> The only solution I can see to this, is to make this classes more intelligent
in the way that subclasses TurbineUserPeer knows that
> it should make objects of a subclass of TurbineUser and not of TurbineUser
itself. Haven't really come up with an idea yet :-)
>
Actually, I think it already does this. ;-)
Look on line 234 of TurbineUserPeer.java. It's using the UserFactory to
instantiate a User class of the type specified in the properties file.
> ~ Leon
>
--
Christopher Elkins
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
