Hi all,
i am building some aspects to work with hibernate inside session beans.
I created an aspect factory that instantiates a Hibernate SessionFactory and
it's createPerVm methos instantiates a SessionFactory, binds it to an Aspect
that holds the reference to the SessionFactory.
The problem
My last message was messed because of the XML stuff of my build file...
Sorry for that.
| path id=competence.compilation.classpath
| pathelement path=${hibernate.lib.dir}/hibernate2.jar/
| pathelement path=${aop.lib.dir}/jboss-aop.jar/
|
I reworked my code in such a way that the invocation for the Configuration
class is out of the scope of the aopc compiler.
Now everything works fine.
Does anyone had any problems like this?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858523#3858523
Reply
It does not work...
there is a weird thing happening here...
I took of the references to the configuration object in my code, and every
thing works fine. Including code that uses classes of the Hibernate jar.
I use other concrete class for the package, and it worked too.
If I only declare a
I still does not understand what paths am I supposed to put on the task...
And still does not work...
The first two lines of the debug output:
[aopc] [debug] jboss.aop.class.path is NULL
[aopc]
I analysed the hibernate jar and saw that the
sf.net.hibernate.cfg.Configuration contains inner classes.
I tried to use a class of the log4j pack (the ConsoleAppender) and it worked
nice. And it does not have inner classes.
Any clues?
View the original post :
ok.
I will prepare the example with Hibernate and it to you.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858538#3858538
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858538
