June 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: (JBAS-4476) Switch to JBoss Cache 2.0.0.CR2

by Brian Stansberry (JIRA)

Switch to JBoss Cache 2.0.0.CR2 ------------------------------- Key: JBAS-4476 URL: http://jira.jboss.com/jira/browse/JBAS-4476 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4475) Convert JGroups multiplexer service to a -beans.xml

by Brian Stansberry (JIRA)

Convert JGroups multiplexer service to a -beans.xml --------------------------------------------------- Key: JBAS-4475 URL: http://jira.jboss.com/jira/browse/JBAS-4475 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 Needed so we can inject a POJO JChannelFactory into services. Besides, all the other clustering services use the MC format. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4482) Add compatibility runs against 4.2.0.GA in Branch_4_2

by Dimitris Andreadis (JIRA)

Add compatibility runs against 4.2.0.GA in Branch_4_2 ----------------------------------------------------- Key: JBAS-4482 URL: http://jira.jboss.com/jira/browse/JBAS-4482 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.GA Reporter: Dimitris Andreadis Assigned To: Rajesh Rajasekaran Fix For: JBossAS-4.2.1.CR1 We need to add a test against the released 4.2.0.GA version -- 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
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-992) The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject implementations returns always new proxies for EJB3

by Roland Räz (JIRA)

The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject implementations returns always new proxies for EJB3 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-992 URL: http://jira.jboss.com/jira/browse/EJBTHREE-992 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Roland Räz The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject implementations returns always new proxies. The api states "Obtain a reference to the EJB object that is currently associated with the instance". My interpretation is that this api should always return a proxy to the current instance. At least for stateful session beans a proxy for the actual session bean should be returned else the bean instance has no mean to return a reference to itself (except when the stateful session bean is passed as parameter). -- 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
1
0 / 0

[JBoss JIRA] Created: (JBRULES-921) Use one ClassLoader for all extractor bytecode generation

by Mark Proctor (JIRA)

Use one ClassLoader for all extractor bytecode generation --------------------------------------------------------- Key: JBRULES-921 URL: http://jira.jboss.com/jira/browse/JBRULES-921 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.0.MR3 Currently we generate a classloader per extractor, so we should try and re-use a global cache. -- 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
1
0 / 0

[JBoss JIRA] Closed: (JBRULES-315) Support to Expression and Nested Accessors

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-315?page=all ] Edson Tirelli closed JBRULES-315. --------------------------------- Resolution: Done Support to expressions added. Example: rule "eval rewrite" when $o : OrderItem( order.number == 10 ) then results.add( $o ); end rule "eval rewrite2" when $o1 : OrderItem( order.number == 11, $seq : seq == 1 ) $o2 : OrderItem( order.number == $o1.order.number, seq != $seq ) then results.add( $o2 ); end rule "eval rewrite3" when $o1 : OrderItem( order.number == 12, seq == 1 ) $o : Order( items[1] == $o1 ) then results.add( $o ); end rule "eval rewrite4" when OrderItem( $nbr : order.number == 13, seq == 1 ) $o : Order( number == $nbr ) then results.add( $o ); end rule "map access" when $m : Map( this['name'] == "Edson", this.surname == "Tirelli", this['age'] == 28 ) then results.add( $m ); end > Support to Expression and Nested Accessors > ------------------------------------------ > > Key: JBRULES-315 > URL: http://jira.jboss.com/jira/browse/JBRULES-315 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Michael Neale > Assigned To: Edson Tirelli > Priority: Minor > Fix For: 4.0.0.MR3 > > > Would be nice to have a feature like: > Map(this.foo == bar) as being accessed as: map.get("foo") > This can work as in the ClassFieldInspector it can tell that there is no "getFoo" method, but there is a get(xxx) method - hence it can pass in the key as the field name (as a string). > A limitation may be that we want to use a prev bound variable as a key, but I can't see how that will work short of adding new syntax (this currently stays within the current grammar which is good - and looking up fields via a String key is more then useful !). -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBRULES-315) Support to Expression and Nested Accessors

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-315?page=all ] Edson Tirelli updated JBRULES-315: ---------------------------------- Summary: Support to Expression and Nested Accessors (was: map lookup access for fields) Description: Would be nice to have a feature like: Map(this.foo == bar) as being accessed as: map.get("foo") This can work as in the ClassFieldInspector it can tell that there is no "getFoo" method, but there is a get(xxx) method - hence it can pass in the key as the field name (as a string). A limitation may be that we want to use a prev bound variable as a key, but I can't see how that will work short of adding new syntax (this currently stays within the current grammar which is good - and looking up fields via a String key is more then useful !). was: Would be nice to have a feature like: Map(foo == bar) as being accessed as: map.get("foo") This can work as in the ClassFieldInspector it can tell that there is no "getFoo" method, but there is a get(xxx) method - hence it can pass in the key as the field name (as a string). A limitation may be that we want to use a prev bound variable as a key, but I can't see how that will work short of adding new syntax (this currently stays within the current grammar which is good - and looking up fields via a String key is more then useful !). > Support to Expression and Nested Accessors > ------------------------------------------ > > Key: JBRULES-315 > URL: http://jira.jboss.com/jira/browse/JBRULES-315 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Michael Neale > Assigned To: Edson Tirelli > Priority: Minor > Fix For: 4.0.0.MR3 > > > Would be nice to have a feature like: > Map(this.foo == bar) as being accessed as: map.get("foo") > This can work as in the ClassFieldInspector it can tell that there is no "getFoo" method, but there is a get(xxx) method - hence it can pass in the key as the field name (as a string). > A limitation may be that we want to use a prev bound variable as a key, but I can't see how that will work short of adding new syntax (this currently stays within the current grammar which is good - and looking up fields via a String key is more then useful !). -- 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
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-991) Broken javax.ejb.SessionContext.getBusinessObject() for EJB3 stateful local Interfaces

by Roland Räz (JIRA)

Broken javax.ejb.SessionContext.getBusinessObject() for EJB3 stateful local Interfaces -------------------------------------------------------------------------------------- Key: EJBTHREE-991 URL: http://jira.jboss.com/jira/browse/EJBTHREE-991 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Roland Räz javax.ejb.SessionContext.getBusinessObject() results in a NullPointerException when used in a stateful session bean without remote interface. Reason: in org.jboss.ejb3.stateful.StatelessContainer.getBusinessObject() iterates over the remote Interfaces instead of the local interfaces after checking that the local interfaces are != null. -- 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: (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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007