"Elhanan" wrote : that's what i thought at first, but when i placed the one
in jboss-app i saw additional required jars (NoClassDefFound)
|
When configuring classloading, you should package the right "set" of jars. So if
you are trying to package your own version of hibernate, you should be sure that you
package the correct versions of hibernate "dependencies" too. Not doing so can
lead to some classes being picked up from the server's library and those classes may
be of a different version. All this can lead to classloading issues like
NoClassDefFoundError.
"Elhanan" wrote :
| once i removed all jars (and there half of them) can i be sure i would no longer have
differences in was ?
|
I assume, was = WebSphere Application Server? Ideally you shouldn't have any issues,
but it again depends on how you configure classloading there. Remember, jboss-app.xml will
be of no use there. You will have to go through their configuration guide to see how
classloading isolation can be achieved.
"Elhanan" wrote :
| also dont' know if this is the right place can you tell me what's the
diiffence between javaasists and cglib from hibernate's point of view? (meaning if
changing one, effects hibernate in functionality level.
|
Hibernate user forum would be a better place
https://forum.hibernate.org/viewforum.php?f=1
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249832#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...