Hi all,

I'm using the "native" generator class for the Id's in many classes and it works fine ... however in some situations I want to assign an ID manually but seems that save() doesn't consider the assigned id.

MyClass obj = new MyClass()
obj.setName("name");
session.save(obj) ; #Generate an ID (1)

I try :

obj.setId(1);
obj.setName("name");
session.save(obj) ; #Also generate an ID (2)

It is possible to keep the "native" generator and also be able to inform ID manually ?

No.
What is your need, do you want to skip some ids ?
Do you want to use already defined ids ?
Those ids are considered technical stuffs, no need to manage them.

I have a client-server system.
I use the same classes/mappings for two applications ... one application create the user/groups in they database (Server) ... another app (Desktop) get those users/groups throught HTTP (XML) and insert in a local database ...
When I update the Desktop database I need to compare the actual groups with the groups from Server ... if I insert the groups in the local database with a diferent id (generated) I can't compare the information ... by using the ID.

I have an idea ... I will create two mapping files for the same class .. one to the Server that uses the "native generator" and another to the Desktop that uses an "assigned generator" ...

Thanks,

Why not using 2 slightly different mappings ?
Server = native
Client = assigned

That's the way you use it if I understand it well : Client never create an object that hasn't been created by Server before