1) I removed jboss-web-cluster.sar from the distribution and it
worked fine.
2) I used the following jboss-aop.xml for aopc compilation and it worked fine.
|
|
|
|
|
|
|
|
|
|
|
|
|
org.jboss.aspects.patterns.observab
You could also make them compatible by adding the following to your compile
time aop config:
|
|
|
org.jboss.aspects.patterns.observable.Subject
| org.jboss.aspects.patterns.observable.SubjectImpl
| new
org.jboss.aspects.patterns.observable.Subje
I think there is a conflict with jboss-aop.xml from tc5 (used for field session
replication). There we introduced SubjectInterceptor for the POJO.
I'd suggest you try first by running in default mode (i.e., no clustering). If
it is working, and you don't need tc5, then remove tc5-clsuter.sar. Th
The pojo/ClientSession class is only shipped in DemoService.jar
I use the farm directory to deploy the service in my two-node cluster.
If the problem is due to class loading, is there a way to enable classloader
traces in JBoss ?
View the original post :
http://www.jboss.com/index.html?module=b
Are you certain that there is no other pojo.ClienSession class in the entire
system?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063723#4063723
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063723
_
Sorry i did not describe correctly what i did.
No original class is packaged in the final jar...
The original class is:
ClientSession.class (non instrumented)
which becomes after aopc compilation:
ClientSession.class (instrumented)
ClientSession$sessionId_Get.class
ClientSession$sessionId_Set.
"mbroons" wrote : I'm facing some trouble trying to use PojoCache with
| I packaged all class files (original classes + generated classes) in a
| single DemoService.jar file
|
Are you really combining both classes directories? Compile-time weaving
modifies the classes, so you do not want
