Dear All,

I have the following problem with hibernate:

I am using hibernate as persistent in a web system (i.e. on line access) with a centralized database, In our system the user rules are many and grow continuously, the thing which force us to make a view for each rule and of course a mapping file for that view the thing which force me to start up the tomcat each time I add new view which is un reasonable. For example, consider the case we have account table that contains all the accounts and each set of accounts for a specific district, the normal users can only access a specific set of accounts while the mangers can access another set of account and I can say each user may have its own set of accounts.

What I wonder is it possible to eliminate this problem without the need to startup the tomcat

Kind regards

ohamed,

I'm not sure I understand your problem, so I'm going to paraphrase it in English and ask you to confirm that I have the gist of it...

You are using hibernate with tomcat. You are using database views to enforce table-level-access-control to individual users.

The problem is, whenever you add a user you need to tailor-make an access-control view for that user, which also requires a new hibernate mapping creation... and you need to bounce tomcat so that it picks up your changes to the hibernate mapping file ${class}.hbm.xml, which is obviously not good for your uptime.

So you wonder if there is a way to make hibernate reload it's mapping file(s) "on the fly" (without restarting tomcat).... and you're starting to worry that you'll have to redesign your whole application just to meet these crazy security requirements.

Is this correct?

Keith.

Keith. Yes this is waht I mean .

Have you thought about recreating your sessionfactory, after modifying the hibernate.cfg.xml file referring to the new mappings?

sounds good to me... pls post if you get it working.

Hi Batmat. Yes i tried it, but i still have a problem.

What exception do you get?