Ah, for the days of C++ : )
#define private public
> I'm not really sure how we should handle this issue yet. my work with
> PowerBuilder, as i have said before has given me some bad habits. in
> PowerBuilder you can declare class attribute to "Public Read" and
> "Private/Protected write". AFAIK, there is not an equivalent to this in
> java. AFAIK using reflection... if i'm not mistaken either John McNally or
> Brett McLaughlin has reservations about using it because of performance
> issues, but i'm not sure i agree. On the topic of serializing, IMOP this
> gets a -1 for a number of reasons... performance, concurrency, etc...
>
> i have been kickin' around the idea of just making it understood that any
> descendant classes of PersistenceObject must conform to the JavaBean spec.
> so that if there is an object attribute that needs to be persistent, say
> like employeeId, there must be a corresponding method name setEmployeeId(int
> idArg). What do you think???
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
