----- Original Message -----
From: Jeff Prickett <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 15, 1999 11:28 AM
Subject: Accessing private member data in JDK1.2
>
> Scott,
>
> I found this link on Sun's Java Developer forum about exactly the
> thing we were talking about accessing private member data.
>
> http://forum.java.sun.com/forum?[EMAIL PROTECTED]^[email protected]/0
>
> It is a JDK1.2 specific fix to the problem. Unfortunately, I am hosting on
> a Linux platform with JDK1.1.7. I will be a real happy
> many when we have a 1.2 or 1.3 port for Linux :(. Well, I am off
> to check the 1.1.7 docs to see if there is anything similar in there.
>
>
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???
-scott-
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
