How to use Criteria API from RMI client(doesnt know the DB info) and query at RMI server(knows the DB info.)
I have RMI application where the client queries the data object using the custom Search Object. I am evaluating the Hibernate for a possible ORM tool.
I would like to use the Criteria API that comes with Hibernate. I couldnt use the Criteria API at the RMI client as the Session.createCriteria needs DB/Mapping info which are only available at the serverside.
Advise me with the right approach.

I appreciate any input on this.

Thanks
Varnika.

Don't expose Hibernate APIs (your persistence layer!) directly to your client.

Sure I will spread the word!

You are right I may not be expossing the Persistance layer to the users
but I have to let the users to query(read only) domain object on which they build their applications on.
To acheive this I need to either detach the criteria API and make it serializable.
The thick RMI client that includes data object, changed criteria is distributed to users.

I work for non profit organization will it matter when it comes to liscencing If I distribute the changed and detached criteria API code in my codebase.

Appreciate your feedback.


--Varnika

Guys,
he criteria api is a very nice feature, and frankly, you guys didn't invent it. It's a nice way to query data, and is fairly data source/type independent. I have the same requirement where it'd be nice to expose this feature to my clients. Architectural discussions aside, is there a way to do it without rewriting the api, or picking it up and making everything serializable?

tnx.

Implement serializable wrapper, it must be trivial . I see nothing wrong to build queries on client, but probably this API is not serializable for reason.

Definitely sounds like a solution, just wondering why the hastle.

Tnx.