Hello,

i'm trying to do the following. But i have no clue how to handle this.

Lets say you've got Employees and Jobs. An Employee has one job, a job has many employees.

If you want to add an employee, first you've got to choose the job you are about to assign... and keep track of this choice. But, if you are using Many-to-one hibernate relationship, you've got to keep somewhere the object Job, and then, when you save the Employee, take it from somewhere.

The same applies to... when you load an Employee for modification, if you don't keep the Job somewhere and then restore it, you end up loosing it... but you can't put an entire object in a hidden form field.

How would you solve this ???????. Store the 'last-seen-job' in a session variable, both, when you add an employee, or when you load it for update, or there is some easier way ??

THANK YOU!!!!!

It would seem that you still have 2 seconds of work to do yet in this thread: http://forum.hibernate.org/viewtopic.php?t=946585

Then we can move on to your next question!

Maybe im missing ur question, but this sounds like a UI Issue. you could have a drop down of the jobs from a JOBS table and display it when you add/modify the employee.

Sorry... but i don't get what you mean... :S

I've checked my last post and i've noticed i didn't rate Steven reply, if you meant that, i'm deeply sorry, i didn't even realize of that jdl..!!!


The problem i've got with a simple drop-down menu, is that... in the Employee class, i've got a reference to the Job like this:

private Job j;

and with a simple drop-down, i can't pass a Job property... just the JobID i guess :S

I'm deeply sorry... truly, i wasn't aware of the rating stuff. I've rated ALL the posts on my list.

Once you get the JobID from ur drop down list, figure out the job using a
session.load(<JobID>, Job.class) to get the Job object and assign it to ur Employee - Job mapping.

That's a good idea. But... i was thinking, wouldn't it be an un-needed query ??. I mean, you've already got the ID you should set to the class.. i actually don't need to re-load the object from the DB... except for Hibernate, that needs the 'real' object instead of the key.

But... that way it can work perfect. I'll give it a shot!!. Thank you :D

No, load() only creates a proxy. It doesn't execute a query unless you access its non-id properties, which makes it useful for establishing associations without doing a query.

Thank you Nebob!