Fine, thanks!
FYI:
I'm using jboss 4.0.4GA in a Debian Linux box, Sun's JDK 1.4 and the latest
jboss-aop deployer: 1.5.0GA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012429#4012429
Reply to the post :
Just for your information,
the above problem occurs with this configuration
app/deploy/mywebapp.war
app/deploy/app_aspect.aop
app/deploy/app_aspect/META-INF/jboss-aop.xml
I also tried to deploy the aspect using the other scheme:
app/deploy/mywebapp.war
app/deploy/app_aspect.jar - this
It looks like core.services.document.DocumentServiceParameters is contained
both in your .aop file as well as in your war's WEB-INF/lib or WEB-INF/classes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012485#4012485
Reply to the post :
Yes, sure, it is. That's because if I don't include the class in the .aop or
.jar that contains the interceptor, it throws a ClassNotFoundException.
There must be a way to make the interceptor to be executed in the same
classloader as the class that contains (in this case) the method
pepelu wrote :
| Including the aop deployment files and descriptor under the .war of the
application seems to be the right solution, but I tried that without sucess...
|
| Wich are the chances of deploying the aspects as part of a war application?
THis is currently not possible, as a
I asked for the posibility of deploying the aspect inside a .war file because
of this content in the jboss-aop reference documentation:
http://labs.jboss.com/portal/jbossaop/docs/1.5.0.GA/docs/aspect-framework/reference/en/html/running.html#d0e3109
There states:
anonymous wrote : That is you
I believe this quote stems from an older version of JBoss AS where the
UseJBossWebLoader=true in
deploy/server/jbossweb-tomcat.sar/META-INF/jboss-service.xml.
In this cases the cl used for the WEB-INF/lib and WEB-INF/classes is a
UnifiedClassLoader.
With this setting set to false,
Hi!
I didn't understand exactly your application.
Is your interceptor receiving a MethodInvocation right?
And the method was supposed to receive, as first parameter, an instance of
DocumentServiceParameters?
Now, you see on a print that the output is of type DocumentServiceParametrs, as
Hi,
All your asumptions are right, I've made the changes and the result shows
that both classes are from different classloaders (as one might think), this is
the output:
17:45:54,255 INFO [STDOUT] class
core.services.document.DocumentServiceParameters WebappClassLoader
| delegate:
This is weird. I need to verify what is going on...
ASAP, I'll give you a feedback.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012254#4012254
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4012254
10 matches
Mail list logo
