This is now fixed in subversion
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994616#3994616
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994616
___
jboss-user mailing list
Have dicovered the same effect this friday. Reflection code is running
standalone but not in jboss. Thanks for the fix.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994447#3994447
Reply to the post :
http://jira.jboss.com/jira/browse/JBAOP-329
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994303#3994303
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994303
___
jboss-user
BTW Generated Advisors are in beta/unreleased for the 1.5.x versions
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994304#3994304
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994304
The bug has been solved on 1.5 branch (using that workaround I told you of)
only for the default weaving configuration(which is, actually, the optimized
one with classic instrumentation, and not gen advisor instrumentation,
differently from what I told you before).
Please, follow these
Sorry for the delay.
The bug seems simple of solving, but I had a hard time trying to find out a way
of doing what I need to by using Javassist, until I realized that, currently,
it does not support the operation I need.
Maybe I'll add this operation to Javassist, but, in the mean time, there is
no problem for the delay, thanks a lot for your help! I really appreciate it!
Our project isn't going live for at least 4-6 months, still in the early stages
of development.
currently I'm using default settings for everything. i haven't had the time to
delve too deep into JBoss AOP (I plan to
hm, i might be far off, but if i remember correctly tomcat doesnt work well
with annotations (dont sue me if im wrong, its early in the morning).
could you try to deploy the code in jboss and not tomcat and see how it works?
since it works when you test is outside tomcat i believe that its no
I did a bit more testing and when I get rid of the @ReadLock bind in my
jboss-aop.xml, parameter annotations can be read correctly even when deployed
in Tomcat.
I'll try it on JBoss and see if I have more luck.
View the original post :
Hi! I think I've found the problem. Could you please just confirm to me that
the problem stays the same even if you run it as a simple java application,
without any server involved?
Besides, I need to know which version of JBoss AOP you are using, so I can fix
your version first.
View the
also forgot to add that i'm using version 1.5.2. Thanks for your help
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3991319#3991319
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3991319
hm, even though i havent tested it myself but i thought it should work. the
code you are calling is CtMethod/CtBehavior which is javassist, but thats not
your problem :)
have you tested .getAvailableParameterAnnotations() too?
if that doesnt work either, could i bother you to make a small test
What is the retention policy of your annotation @ReadLock?
Maybe you forgot to set it as RetentionPolicy.RUNTIME...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3991027#3991027
Reply to the post :
Thank you both for your replies.
flavia, all my annotations are set to RetentionPolicy.RUNTIME. If only that was
the issue... :)
stalep, I created a unit test and it read the annotation correctly. It seems
that when I deploy it to my app server (Tomcat) the annotation can't be read.
Here's a
14 matches
Mail list logo
