January 2007 - 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, 4 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, 4 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3998) failing org.jboss.test.classloader.test.ScopingUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.classloader.test.ScopingUnitTestCase ----------------------------------------------------------- Key: JBAS-3998 URL: http://jira.jboss.com/jira/browse/JBAS-3998 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ClassLoading, Test Suite Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Test fails due to the commons-loggings upgrade. We need a patched commons-logging to solve this (see JBAS-3128). -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-139) StackOverflowError when traversing certain directories

by Scott M Stark (JIRA)

StackOverflowError when traversing certain directories ------------------------------------------------------ Key: JBMICROCONT-139 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-139 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Reporter: Scott M Stark Fix For: JBossMC_2_0_0_CR1 The current 2.0.0.snapshot version of the vfs fails under win32 for jrockit 1.5.0_06 with a StackOverflowError when the quartz-ra.rar is deployed: 16:05:27,344 ERROR [AbstractKernelController] Error installing to Start: name=jb oss.jca:name='quartz-ra.rar',service=RARDeployment state=Create mode=Manual requ iredState=Installed java.lang.StackOverflowError at java.lang.String.substring(II)Ljava.lang.String;(Unknown Source) at java.net.URLStreamHandler.parseURL(URLStreamHandler.java:220) at org.jboss.net.protocol.file.Handler.parseURL(Handler.java:47) at java.net.URL.<init>(URL.java:596) at java.net.URL.<init>(URL.java:465) at java.net.URL.<init>(URL.java:413) at sun.net.www.protocol.jar.Handler.parseAbsoluteSpec(Handler.java:89) at sun.net.www.protocol.jar.Handler.parseURL(Handler.java:64) at java.net.URL.<init>(URL.java:596) at java.net.URL.<init>(URL.java:465) at java.net.URL.<init>(URL.java:413) at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.getURL(Abstr actJarHandler.java:308) at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.createVirtua lFileHandler(AbstractJarHandler.java:370) at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.initJarFile( AbstractJarHandler.java:186) at org.jboss.virtual.plugins.context.jar.JarHandler.<init>(JarHandler.ja va:81) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:179) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:239) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:239) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:239) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:239) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:239) at org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtua lFileHandler(FileSystemContext.java:186) at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHa ndler.java:171) 16:05:27,344 INFO [RARDeployment] Required license terms exist, view vfsfile:/C :/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deploy/ quartz-ra.rar/META-INF/ra.xml 16:05:31,719 ERROR [AbstractKernelController] Error installing to Start: name=jb oss.jca:name='quartz-ra.rar#quartz-ra.rar',service=RARDeployment state=Create mo de=Manual requiredState=Installed java.lang.StackOverflowError 16:05:31,734 INFO [TomcatDeployment] deploy, ctxPath=/, warUrl=vfsfile:/C:/svn/ JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deploy/ROOT.w ar/ This is due to the following bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6192331 The problem is that a file returned via File.listFiles() is such that the File.exists() check fails, and there is recursion to try to resolve the file as a link against the parent. The link checking could be improved, or the resulting listFiles() validated before used. -- 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, 4 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, 4 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, 4 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, 4 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, 4 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, 4 months

3
2
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 January 2007