I think I should show you a simple example code:
|
| public class A{
| @InterceptMe
| public void sayHello(){
| System.out.println(hello);
| }
| }
|
| public class B extends A{
| @InterceptMe
| public void sayHello(){
|
I have found the following statement in the docs:
It is also perfectly reasonable to mix and match compile time and load time
though. If you have load-time transformation enabled, precompiled aspects are
not transformed when they are loaded and ignored by the classloader
transformer.
But I
Are there any updates on this topic?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222370#4222370
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4222370
___
jboss-user mailing
As far as I know you can only set pointcuts for an annotation, but not for its
attributes. So you have to intercept all @Mixins annotations and then you can
check out which attributes are set in your aspect/interceptor:
| MethodInvocation methodInvocation = (MethodInvocation) invocation;
Since this has happened more than one time, I guess there should be a solution
for the problem:
http://www.jboss.com/index.html?module=bbop=viewtopict=146554
http://www.jboss.com/index.html?module=bbop=viewtopict=146001
The jbossall-client.jar is needed if I like to run my EJBs on the jboss
[EMAIL PROTECTED] wrote : the problem was that AOPLogger would globally
overwrite the loggerplugin settings even though it was only ment to do that for
aopclasses if only the NullLoggerPlugin was used. we want this so that people
using aop standalong have a easy way to display debug information
[EMAIL PROTECTED] wrote :
| | all(com.gm.tnt..)
| |
| should work, although I think that is aop 2.0.0 only:
|
http://www.jboss.org/jbossaop/docs/2.0.0.GA/docs/aspect-framework/reference/en/html/pointcuts.html#pointcuts-wilcards
|
|
But doesnt the doc say that it wont work?
What do you mean by the other debug messages? You didnt mention any debug
messages in your first post :)
Do you mean some kind of those debug messages:
http://www.jboss.com/index.html?module=bbop=viewtopict=146079start=0
Then you should use log4j and turn off the aop logger or wait for a new
I had exactly the same problem :)
The problem is here:
Exception in thread AWT-EventQueue-0 java.lang.NoSuchMethodError: org.jboss.ao
p.ClassAdvisor$1.(Lorg/jboss/aop/ClassAdvisor;Lorg/jboss/aop/AspectManager
You have the AspectManager class 2 times in your classpath.
The first one is in your
Thanks for your feedback :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4192747#4192747
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4192747
___
jboss-user mailing list
Just another opinion:
http://www.jboss.com/index.html?module=bbop=viewtopict=135287
[EMAIL PROTECTED] wrote : Ah I figured it out - AOPLogger is replacing
NullLoggerPlugin with SystemOutLoggerPlugin. That seems undesirable, but it's
more of an AOP problem than a MC problem it seems.
View the
I think I found the problem in the following class:
| package org.jboss.aop.util.logging;
|
| /**
| * A thin wrapper around the jboss logging framework, so that if a proper
logger is not installed
| * we get the output redirected to System.out.
| *
| * @author a href=[EMAIL
Just some more info:
The sysouts come from the class:
| package org.jboss.aop.util.logging;
|
| /**
| *
| * @author a href=[EMAIL PROTECTED]Kabir Khan/a
| * @version $Revision: 1.1 $
| */
|
| public class SystemOutLoggerPlugin implements LoggerPlugin
The methods used
No idea? This might be a reason why I have to rollback to 1.5.6. :/ But I'd
like to use an up to date version.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4191635#4191635
Reply to the post :
[EMAIL PROTECTED] wrote : It is a consistency bug that has been fixed,
actually.
|
| In the previous version, that method would result in null on one cenario
and in an empty array on a different weaving mode.
|
| Now, we got rid of this inconsistency by making it always return an
btw. those sysouts are on my clientside console - for example in eclipse.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4191160#4191160
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4191160
As stated in my previous posts I upgraded from Jboss AOP 1.5.6.GA to 2.0.0.GA
I run my project as ejb in Jboss AS 4.2.2.GA(I upgraded the aop deployer to
2.0.0.GA)
With 1.5.6.GA I had no sysouts on my clientside console. But since the update I
get sysouts like the following on my clientside
[EMAIL PROTECTED] wrote : Are you running aop on the client side with verbose
mode enabled?
Yap a part of the aop classes are on the clientside, but I think I did not
enable verbose mode:
I am using precompiled classes with:
aopc compilerclasspathref=aopc.classpath verbose=true
but
aopc
I am trying to upgrade jboss-aop-1.5.6.GA to 2.0.0.GA.
Currently I am using the following libs in my eclipse project:
- trove.jar
- javassist.jar
- jboss-aop-jdk50.jar
In order to upgrade, I replaced those jars with the three new ones. But when I
execute the aopc precompile task, I get the
Yap, I have a Jbossall-client.jar in my classpath, which has an Aspectmanager
inside. I deleted it from the jar and now the error is gone.
But I get other errors. Seems that the 2.0.0. GA release needs more libs than
1.5.6. GA. For example the jboss-mdr.jar is needed...
View the original post :
So the upgrade from jboss aop 1.5.6. to 2.0.0. did finally work.
Now I have a question to a different behavior:
| public class Foo implements Interceptor
|
| public Object invoke(Invocation invocation) throws Throwable {
| MethodInvocation methodInvocation = (MethodInvocation)
Some Feedback:
I used Tomcat 5.5 + Axis 1.4 and deployed the real project(which is aopc
precompiled) with the ContextListener.
This resulted in a infinite loop, because the interceptor was bound 2 times
with the methods.
So with tomcat + axis + precompiled classes the ContextListener ist not
DerMas wrote : Some Feedback:
|
| I used Tomcat 5.5 + Axis 1.4 and deployed the real project(which is aopc
precompiled) with the ContextListener.
| This resulted in a infinite loop, because the interceptor was bound 2 times
with the methods.
| So with tomcat + axis + precompiled classes
Never mind, I just added all libs to the aop classpath and now I dont need to
exclude anything. I guess thats ok, since its precompiled and not loadtime
weaving.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4184468#4184468
Reply to the post :
Ok thanks, so I guess I'll have to use XML Bindings and cant use Annotations?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4183474#4183474
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4183474
Ok thx. I think I am going to give the xml binding a try :) I am going to give
you some feedback wether its working or not and how.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4183484#4183484
Reply to the post :
Interesting question. I have the same problem with libs in my project.
Aopc tries to weave them, which results in errors such as:
| [aopc] Exception in thread main javassist.NotFoundException:
org.somepackage.foo.Barclass
|
With loadtime weaving everything works fine with the vm argument:
Works with my sample Project with xml bindings :)
| public class ContextListener implements ServletContextListener {
|
| public void contextInitialized(ServletContextEvent arg0) {
| try {
| AspectXmlLoader.deployXML(new
[EMAIL PROTECTED] wrote : Can't remember about aop 1.5.x, but in aop 2.0.0.GA
we support system properties in aop.xml. Here's an example from our testsuite:
[...]
|
Maybe I missunderstood your example, but in order to get my VM arguments:
| -Djboss.aop.exclude=org
|
Everything works fine with Jboss AS 4.2.2
I have an EJB.jar with my not intercepted classes(+META-INF) and an
intercepted.aop with the classes that are intercepted by Jboss aop(+ META-INF
with an empty jboss-aop.xml(I am using annotations)).
I put both with my libs META-INF into one
[EMAIL PROTECTED] wrote : AFAIK Tomcat cannot deploy .ear files. You need a
full application server for that
Is there any other possibility to deploy an application with working Jboss AOP
interceptions in Tomcat?
I have heard something about filters?!?
View the original post :
I'd like to define a pointcut which intercepts only annotations with a
specified argument.
I have this annotation:
| public @interface myAnnotation {
|
| MyValue value() default MyValue.CONSTANT;
|
| }
|
So a annotated method would look like this:
|
How can I define a pointcut which intercepts only methods with the argument
MyValue.BAR?
eg:
|
| @myAnnotation (MyValue.BAR)
| public void foo() {
| System.out.println(HelloWorld);
| }
|
| @myAnnotation (MyValue.NOT)
| public void foofoo() {
|
It's going to create a huge if block, but it works, thx ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182634#4182634
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4182634
___
34 matches
Mail list logo
