December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-321) JoinPoint annotation

by Flavia Rainone (JIRA)

JoinPoint annotation -------------------- Key: JBAOP-321 URL: http://jira.jboss.com/jira/browse/JBAOP-321 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-319) Arg Annotation

by Flavia Rainone (JIRA)

Arg Annotation -------------- Key: JBAOP-319 URL: http://jira.jboss.com/jira/browse/JBAOP-319 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone Support of @Arg parameter annotation -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-323) Invocation Annotation

by Flavia Rainone (JIRA)

Invocation Annotation --------------------- Key: JBAOP-323 URL: http://jira.jboss.com/jira/browse/JBAOP-323 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Still need to decide a better name for this, to avoid name crashes (org.jboss.aop.advice.annotation.Invocation vs org.jboss.aop.joinpoint.Invocation) -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-716) Add a flag to disable replication event notification

by Ben Wang (JIRA)

Add a flag to disable replication event notification ---------------------------------------------------- Key: EJBTHREE-716 URL: http://jira.jboss.com/jira/browse/EJBTHREE-716 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Ben Wang This came up from an email thread: (1) By default, passivation events get called during replication cycle (2) There is a config setting to disable this (3) We should introduce JBoss-specific replication-only and passivation-only events that actually let you directly write/read the bytestream (4) I will work to get two sets of events into the next EJB spec, ie. introduce @PreReplicate / @PostReplicate or something like that We should now tie the replication to passivation events (there is no concrete spec but everyone else is doing it). But we should also have a flag to disable it if needs to. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3873) EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never

by Darran Lofthouse (JIRA)

EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3873 URL: http://jira.jboss.com/jira/browse/JBAS-3873 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA Reporter: Darran Lofthouse Assigned To: Scott M Stark Fix For: JBossAS-4.2.0.CR1 EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never. However for an EJB with a transaction attribute of Supports if it is called with a transaction calls to setRollbackOnly succeed. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-3892) Replace TxManager with JBoss Transactions 4.2.2

by Dimitris Andreadis (JIRA)

Replace TxManager with JBoss Transactions 4.2.2 ----------------------------------------------- Key: JBAS-3892 URL: http://jira.jboss.com/jira/browse/JBAS-3892 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transaction Manager Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (JBAS-3939) Upgrade jbossxb to v1.0.0.CR7

by Dimitris Andreadis (JIRA)

Upgrade jbossxb to v1.0.0.CR7 ----------------------------- Key: JBAS-3939 URL: http://jira.jboss.com/jira/browse/JBAS-3939 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XML services Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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, 5 months

3
15
0 / 0

[JBoss JIRA] Created: (JBCACHE-858) Investigate POJOCACHE failures

by Manik Surtani (JIRA)

Investigate POJOCACHE failures ------------------------------ Key: JBCACHE-858 URL: http://jira.jboss.com/jira/browse/JBCACHE-858 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.ALPHA1 Reporter: Manik Surtani Assigned To: Ben Wang Fix For: 2.0.0.ALPHA2 Ben, This pertains to the following tests: org.jboss.cache.pojo.collection.ReplicatedSyncMapTest org.jboss.cache.pojo.collection.ReplicatedSyncSetTest org.jboss.cache.pojo.region.LocalConcurrentTest These have been marked as "known issues" as of 2.0.0.Alpha1 so you won't see them in CC builds until you un-mark them as "known issues" in build.xml. -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-593) Analyse current JGroups stack usage

by Tim Fox (JIRA)

Analyse current JGroups stack usage ----------------------------------- Key: JBMESSAGING-593 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-593 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 Need to tune our JGroups stack config to get the best performance possible. Also we need to consider whether we really need to two stacks and if we do, then which protocols we can safely omit from one. We need Brian and/or Bela's help with this one. -- 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, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-556) Isolate JBossMQ-specific test

by Ovidiu Feodorov (JIRA)

Isolate JBossMQ-specific test ----------------------------- Key: JBMESSAGING-556 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-556 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Richard Achmatowicz Isolate JbossMQ specific tests so they'll be run as the JBossMQ functional testsuite, and NOT as integration tests. -- 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, 5 months

3
7
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 December 2006