"eric.hubert" wrote :
| I also must admit I can't see any chutzpah on my side. I know the JBoss people as
very open-minded and technical interessted. From my point of view Hibernate and JBoss
Cache are application server independend projects and should be treated as such. Am I
wrong?
|
I don't personally have a problem with wanting to know about these things in general,
I know the guys at JBoss, at least the ones here don't either. But always I'm
impressed with people like yourself who come in and ask questions like yours which require
quite detailed answers. And not only that but who, unapologetically, assert they are
porting to a competitor's solution. Additionally, a fair bit of information already
exists on this topic, so it also seemed you hadn't bothered to RTFM. Or if you did,
you couldn't be bothered to say what you have read and tried. And, there are a lot of
stupid or lazy people who post on this forum so it's easy for people like you to be
confused with either.
So, that's basically where I'm coming from.
To sort of repeat Manik's advice: My advice is to get your EJB3 app running in Java SE
under Hibernate EntityManager using JBoss Cache. You should do this anyway so you have an
environment that is easy to test your configuration with. Then, it should be trivial to
port it to Glassfish by copying whatever persistence.xml and .jar files you are using.
I would also read the code that comes with Hibernate to figure out how Hibernate finds
TreeCache, because this would be the place application server integration differences
would appear:
TreeCacheProvider.java - source:
http://www.koders.com/java/fidC3D6379D1A1393672FFBF648FA69D06F8730C2D6.aspx
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106603#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...