July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-437) Dynamic AOP is not working with negative pointcut expressions

by Flavia Rainone (JIRA)

Dynamic AOP is not working with negative pointcut expressions ------------------------------------------------------------- Key: JBAOP-437 URL: http://jira.jboss.com/jira/browse/JBAOP-437 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5, 1.5.5.GA Reporter: Flavia Rainone The dynamic addition of pointcut expressions containing ! is not working. This error is reproducible only on classes that have been loaded before the operation. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1555) use 'synd=jboss' for google gadgets directory rss feed

by Boleslaw Dawidowicz (JIRA)

use 'synd=jboss' for google gadgets directory rss feed ------------------------------------------------------ Key: JBPORTAL-1555 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1555 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.1 Final, 2.8 Final use 'synd=jboss' in google gadgets directory rss feed so Google will be able to track us :) -- 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

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-436) Empty Constructor Chain on Generated Advisor Mode

by Flavia Rainone (JIRA)

Empty Constructor Chain on Generated Advisor Mode ------------------------------------------------- Key: JBAOP-436 URL: http://jira.jboss.com/jira/browse/JBAOP-436 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5 Reporter: Flavia Rainone Constructor chain is null if we add a binding like the following one: AdviceBinding binding = new AdviceBinding("!execution(* org.jboss.test.aop.dynamicgenadvisor.POJO->@org.jboss.test.aop.dynamicgenadvisor.NewAnnotation(..))", null); binding.addInterceptor(DummyInterceptor.class); AspectManager.instance().addBinding(binding); The error is also reproducible with this pointcut expression: "execution(org.jboss.test.aop.dynamicgenadvisor.POJO->*(..))" But not with "execution(org.jboss.test.aop.dynamicgenadvisor.POJO->new(..))". What happens is that initializeConstructorChain doesn't create a constructor chain, probably due to some inner mechanism of generated class advisors. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBRULES-217) Add 'accumulate' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-217?page=all ] Edson Tirelli updated JBRULES-217: ---------------------------------- Fix Version/s: 4.0.0.GA (was: 4.0.0.MR4) > Add 'accumulate' Conditional Element > ------------------------------------ > > Key: JBRULES-217 > URL: http://jira.jboss.com/jira/browse/JBRULES-217 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 4.0.0.GA > > > Add jess style accumulate functionality. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1570) make identity modules implementation handle CachedUserImpl properly

by Boleslaw Dawidowicz (JIRA)

make identity modules implementation handle CachedUserImpl properly ------------------------------------------------------------------- Key: JBPORTAL-1570 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1570 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6 Final Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.1 Final, 2.8 Final When CachedUserImpl object is passed to identity modules it should be handled properly - not throw 'java.lang.IllegalArgumentException: User is not a HibernateUserImpl user' exception In such cases a fresh instance need to be retrieved: user = userModule.findUserById(user.getId()); -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1130) TxInterceptor should log exceptions during prepare phase before setting tx.setRollbackOnly()

by Manik Surtani (JIRA)

TxInterceptor should log exceptions during prepare phase before setting tx.setRollbackOnly() -------------------------------------------------------------------------------------------- Key: JBCACHE-1130 URL: http://jira.jboss.com/jira/browse/JBCACHE-1130 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP3 Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 1.4.1.SP4, 2.1.0.GA Some Transaction Managers - such as WL - generate their own exceptions when tx.setRollbackOnly() is called - which doesn't give the tx interceptor a chance to log the real exception. -- 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

17 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-555) CreateTimer in ProtocolStack does not create threads that are demon - is there a reason why they shouldn't be demon threads.

by Dipak Kothari (JIRA)

CreateTimer in ProtocolStack does not create threads that are demon - is there a reason why they shouldn't be demon threads. ---------------------------------------------------------------------------------------------------------------------------- Key: JGRP-555 URL: http://jira.jboss.com/jira/browse/JGRP-555 Project: JGroups Issue Type: Bug Reporter: Dipak Kothari Assigned To: Bela Ban The method createTimer in ProtocolStack provides a ThreadFactory implementation which creates threads that are not demon. Is this a design decision? -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-174) Add API for dynamic aliases

by Adrian Brock (JIRA)

Add API for dynamic aliases --------------------------- Key: JBMICROCONT-174 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-174 Project: JBoss MicroContainer Issue Type: Sub-task Components: Dependency Reporter: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Besides the static aliases defined upfront in for example the beans xml, an additional feature is to be able to add dynamic aliases as well. For example. If a bean is deployed with something like: <bean name="POJOName"> <annotation>@JMX(objectName="com.acme:a=b")</annotation> Then that ObjectName could also be an alias for POJOName context added "dynamically" by the JMX Decorator. This would involve two new methods on the Controller interface: addAlias(Object alias, Object original); removeAlias(Object alias); Initially, for simplicty, we should apply the following constraints: 1) The "original" name must already exist. 2) The person that adds the alias is expected to remove the alias. A full solution would require keeping track of aliases and originals and also define a correct way of handling broken aliases with the caller having to do it themselves. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-173) Write tests for the JMX ObjectName fix using normal bean xml

by Adrian Brock (JIRA)

Write tests for the JMX ObjectName fix using normal bean xml ------------------------------------------------------------ Key: JBMICROCONT-173 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-173 Project: JBoss MicroContainer Issue Type: Sub-task Components: Dependency Reporter: Adrian Brock Fix For: JBossMC_2_0_0_CR1 There is a generic test for the problem fixed in JBMICROCONT-166 Need to write extra tests for this from the bean xml (BeanMetaData) to make sure we have caught everything. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1568) Pagination cannot handle more than 120 elements

by Thomas Heute (JIRA)

Pagination cannot handle more than 120 elements ----------------------------------------------- Key: JBPORTAL-1568 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1568 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6 Final Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.1 Final portlet instances tab the numbering uses negative number, it goes 0,20,40,60,80,100,120,-116,-96,-76,-56,36,-16,4,24 etc... -- 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

17 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007