April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-845) Add xa recovery test that uses XAResourceRecovery instance to interact

by Tim Fox (JIRA)

Add xa recovery test that uses XAResourceRecovery instance to interact ---------------------------------------------------------------------- Key: JBMESSAGING-845 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-845 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-384) Add around xml tag

by Flavia Rainone (JIRA)

Add around xml tag ------------------ Key: JBAOP-384 URL: http://jira.jboss.com/jira/browse/JBAOP-384 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 Add an "around" tag for around advices, just like before and after: <around name="..." aspect="..."> This tag is equivlent to the advice tag (so, we can say that around advices are the default type). With this tag, the user can write clearer xml files, if he/she wants to specify the type of the advice to be an around type. This tak includes a simple update to the documentation (introduce around in annotated-parameters tutorial chapter, and in the reference manual, xml chapter) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-365) Prompt user for location of jboss repository directory

by Paul Gier (JIRA)

Prompt user for location of jboss repository directory ------------------------------------------------------ Key: JBBUILD-365 URL: http://jira.jboss.com/jira/browse/JBBUILD-365 Project: JBoss Build System Issue Type: Feature Request Components: jboss-deploy-maven-plugin Reporter: Paul Gier Assigned To: Paul Gier Fix For: jboss-deploy-maven-plugin-1.3 The current error handling is not very clear when the deployment directory is not specified. Maybe the user can be prompted if they want to either ignore the jboss jar deployment, or specify a location for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-398) No such field: jboss

by Flavia Rainone (JIRA)

No such field: jboss -------------------- Key: JBAOP-398 URL: http://jira.jboss.com/jira/browse/JBAOP-398 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4, 1.5.5.GA Reporter: Flavia Rainone Fix For: 2.1.0.GA, 1.5.6.GA If a POJO class being instrumented has a field called "org", jboss aop will eventually throw an exception with this error message (it might be after setting a field wrapper body, or after CtCasslass.toByteCode() , for example). An example is: javassist.CannotCompileException: [source error] no such field: jboss at javassist.CtBehavior.setBody(CtBehavior.java:364) at javassist.CtBehavior.setBody(CtBehavior.java:333) at org.jboss.aop.instrument.OptimizedFieldAccessTransformer.buildWrappers(OptimizedFieldAccessTransformer.java:278) at org.jboss.aop.instrument.OptimizedFieldAccessTransformer.doBuildFieldWrappers(OptimizedFieldAccessTransformer.java:100) at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:102) at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:724) at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:107) at org.jboss.aop.AspectManager.translate(AspectManager.java:910) at org.jboss.aop.AspectManager.transform(AspectManager.java:853) at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:88) at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:75) The moment in which the exception is being thrown seems to have to do with what joinpoint of POJO class are being instrumented. If the "org" field is being intercepted, the moment in which the field wrapper body is being set is the moment in which javassist throws the exception. If the field "org" is not being intercepted, it seems that the moment in which the exception is being thrown is right after jboss aop instrumentation execution, when toByteCode method is invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1029) Review unit tests around isolation levels

by Manik Surtani (JIRA)

Review unit tests around isolation levels ----------------------------------------- Key: JBCACHE-1029 URL: http://jira.jboss.com/jira/browse/JBCACHE-1029 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR2, 2.0.0.GA Current set of unit tests don't cover all supported isolation levels in all supported usage scenarios (node deleted, modified, created), and various combinations of the transaction succeeding or rolling back. This would probably uncover faults in some of our implementations such as REPEATABLE_READ with node creation (see forum thread) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-373) Extract interfaces to be used for JoinPointInfo when used with Before/After/Throwing

by Kabir Khan (JIRA)

Extract interfaces to be used for JoinPointInfo when used with Before/After/Throwing ------------------------------------------------------------------------------------ Key: JBAOP-373 URL: http://jira.jboss.com/jira/browse/JBAOP-373 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
13
0 / 0

[JBoss JIRA] Created: (JBAOP-389) Args array should be null on field read joinpoints

by Flavia Rainone (JIRA)

Args array should be null on field read joinpoints -------------------------------------------------- Key: JBAOP-389 URL: http://jira.jboss.com/jira/browse/JBAOP-389 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 We need to make the arguments array as a null array on field read joinpoints. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-455) Problem with retransmission: message not found

by Bela Ban (JIRA)

Problem with retransmission: message not found ---------------------------------------------- Key: JGRP-455 URL: http://jira.jboss.com/jira/browse/JGRP-455 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Sometimes a sender cannot find a message with a seqno as requested by a receiver. The seqno requested (47176) was already purged, sent_msgs: [48059 - 48090] (32) This could be either an issue in STABLE, which prematurely purges messages although not all members agreed on the highest seqnos seen, or NAKACK, which might incorrectly 'change' seqnos. Very hard to reproduce ! Trace: 42032 [ERROR] [OOB Thread,perf,10.68.32.33:32968] NAKACK.handleXmitReq(): - (requester=10.68.28.33:33763, local_addr=10.68.32.33:32968) message 10.68.32.33:32968::47176 not found in sent msgs [48059 - 48090] (32) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
18
0 / 0

[JBoss JIRA] Created: (JBAOP-391) Default instrumentation mode unexpected

by Flavia Rainone (JIRA)

Default instrumentation mode unexpected --------------------------------------- Key: JBAOP-391 URL: http://jira.jboss.com/jira/browse/JBAOP-391 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Fix For: 2.0.0.alpha5 In the before/after advice examples, I needed to set the instrumentation mode in the build.xml file, because jboss-aop wasn't running in generated-advisor mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1309) portal 2.4 and JBoss AS 4.2

by Prabhat Jha (JIRA)

portal 2.4 and JBoss AS 4.2 --------------------------- Key: JBPORTAL-1309 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1309 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.1 SP1 Reporter: Prabhat Jha We would like to be able to have some (future) version of portal 2.4 to be compatible with JBoss AS 4.2. Currently, jboss-portal.sar does not get deployed. Please see http://jira.jboss.com/jira/browse/JBPAPP-59 for detail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 1 month

3
19
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007