Thanks!
Also, I wrote down all the steps it took to install and run PojoCache in JBoss
4.0.5. Since I found the info scattered across various documents and questions
in the forum, it was a several day effort which could be cut to 15 mins with a
list of steps in one place. Would you like me to
Sure. Please open up a jira for it and attach your doc. I will then merge it
into the regular doc.
thanks again!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4004847#4004847
Reply to the post :
anonymous wrote : Yeah, I have just found it out from my own test here. What
happens is that tc5-cluster.aop contains a jboss-aop.xml as well. So either you
use it all the way, or you remove it from AS deployment.
Could you elaborate on this? Do the PojoCacheable classes always need to be
Jamie, what I was saying is that:
1. If you don't use http session clustering, you can remove tc5-cluster.aop
from your deploy directory and use your own jboss-aop.xml. That should work.
2. If you do, you will need to include tc5-cluster.aop in your classpath.
Furthermore, you will need
Have you tried it outside of AS first to see if that works? If it does, would
you mind giving me your sample war file that I can try it out here.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3999876#3999876
Reply to the post :
Application had been sent to your email. :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=309#309
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=309
___
jboss-user
Hi ben, the problem was resolved.
I just added a path to build.classpath, show below
| path id=build.classpath
| pathelement location=${basedir}/
| fileset dir=${jboss.home}/lib
| include name=**/*.jar/
| /fileset
|
Yeah, I have just found it out from my own test here. What happens is that
tc5-cluster.aop contains a jboss-aop.xml as well. So either you use it all the
way, or you remove it from AS deployment.
Thanks,
-Ben
View the original post :
It complains about when AOP trying to instrument a mixin, it does not find the
addObserver method.
This is probably due to classpath or version compatiblity. But I don't
understand where this mixin coming from?
How do you do pre-compilation of your POJO?
View the original post :
Thanks for your reply.
My POJO are Person.class, Student.class, Address.class
| Person.java
| @org.jboss.cache.aop.annotation.InstanceOfPojoCacheable
| public class Person implements Serializable {
| ...
| }
|
| Student.java
| public class Student extends Person {
| ...
| }
OK, this
| fileset dir=${jboss.home}/server/${jboss.server.config}/lib
| include name=**/*.jar/
| /fileset
|
has jbosscache jar (and jgroups) as well. So can you exclude them and try
again? Or is it in sync already?
View the original post :
Thanks.
I edited my build.xml below
| path id=build.classpath
| pathelement location=${basedir}/
| fileset dir=${jboss.home}/lib
| include name=**/*.jar/
| /fileset
| fileset
12 matches
Mail list logo
