Server Classes in Data Client

[Lance Finney]

I'm probably overlooking something basic here, so please bear with me.
I'm planning to have an interface on the client side called DataClient. I'll have a LocalClient Class and a NetworkClient class that communication with the server differently.
Here's some of the interface:

package suncertify.client;
public interface DataClient {
    public String[] getHeaders();
    public String[][] getData();
    public String[][] criteriaFind(String criteria);
    public void modify(DataInfo newData);
}

This obviously won't compile because it doesn't know what DataInfo is. Should I import suncertify.db.DataInfo into this interface? If so, doesn't that unneccesarily couple the client to the server?
I'd rather not import them, but the requirements state "This implementation should include a class that implements the same public methods as the suncertify.db.Data class, although it will need different constructors to allow it to support the network configuration. "
Any thoughts?

[kerry shih]

I ran into the same problem. I decided that it was justifyable to have the coupling as the app requires local and remote access. Assuming that this functionality must exist within the same build you would HAVE to have those classes in the client code. We have to remember that this project is not a lesson in RMI bootstrapping with a completely clean client.
Hope this helps