Hello,
i have several doubts regarding the DBAccess interface that the Data class must implement. This information is included in the server section of the document.
The problem arises related to the automatic check of the requirements.
I supose this class is going to be dinamically loaded from the server VM, or it's going to be exported to be tested in a client machine.
I decided using RMI, so in the first i should decide to wrap the Data object class in another (Remote) object and then give the client other remote interface more elaborated because this interface doesn't seem to be logic, ie i think locking methods should not be public to the client.
The second case is that worries me.
If this is the remote interface, what about RemoteExceptions? And why let a client lock a record without any other consideration?
I'm not sure at all is clear what i'm asking.
Thanks jRanchers
[ December 13, 2004: Message edited by: Ignacio del Valle ]
i have several doubts regarding the DBAccess interface that the Data class must implement. This information is included in the server section of the document.
The problem arises related to the automatic check of the requirements.
I supose this class is going to be dinamically loaded from the server VM, or it's going to be exported to be tested in a client machine.
I decided using RMI, so in the first i should decide to wrap the Data object class in another (Remote) object and then give the client other remote interface more elaborated because this interface doesn't seem to be logic, ie i think locking methods should not be public to the client.
The second case is that worries me.
If this is the remote interface, what about RemoteExceptions? And why let a client lock a record without any other consideration?
I'm not sure at all is clear what i'm asking.
Thanks jRanchers
[ December 13, 2004: Message edited by: Ignacio del Valle ]