I'm using Hibernate entitymanager together with wls10. Works great, entitymanager is created from META-INF/persistence.xml and so on.

Unfortunately (as according to spec) entitymanager injection/context is only available for certain types of classes(example beans,mdb's etc). Otherwise it is not available.

Now, I could use hibernate.session_factory_name property to bind hibernate sessionfactory into wls jndi tree. Again ,works great.

Now, I've got access to sessionfactory in my class inside the container. Is it now possible to get the entitymanager(factory)/Do I have to create new one (new EntityManagerImpl(...) or is this idea just stupid?

To me if looks like if you can look up session factory you should be able to look up entity manager factory. What is your context? Where do you want to do this? Also read the whole way down this post and see if it puts you in any direction: http://forums.java.net/jive/thread.jspa?threadID=16808


Farzad-

Hi!
within ejb3 context. I've got some utility classes(pojos) that need to access the entitymanager.

Then I would assume those utility classes are used in some context of an ejb call then you would be able to add the resource ref in the ejb configuration file and have the utility class look up the entity manager factory. The url I sent before has some details on how to do this.

I hope this helps.

Farzad-

Well no;) Sorry, perhaps I explained this bit wrongly;
Inside ear I've got classes for example commonj.timers. So they are not part of traditional ejb call.

Now my persistence.xml and entities have been part of the ejb.jar. I dont wether it would make a difference if I move them to the ear level (would that bind entitymanager(factory) to the jndi...)

Ok, this was in the documentation, funny how I didnt notice that in the beginning.

I heard somewhere this is best useful outside a container environment. I am not exactly sure what its side effects might be though.



Farzad-