September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1790) Provide support for resolving @EJB/ejb-local-ref references to no-interface view

by jaikiran pai (JIRA)

Provide support for resolving @EJB/ejb-local-ref references to no-interface view -------------------------------------------------------------------------------- Key: EJBTHREE-1790 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1790 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec allows no-interface view reference, using a @EJB and through ejb-local-ref. We need to have a resolver (similar to FirstMatchEjbReferenceResolver) which does this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-859) Message: add LOOPBACK flag

by Bela Ban (JIRA)

Message: add LOOPBACK flag -------------------------- Key: JGRP-859 URL: https://jira.jboss.org/jira/browse/JGRP-859 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When LOOPBACK is set in a message, the UNICAST.loopback and TP.loopback flags are overridden and a message is looped back up the stack, regardless of the value of the property. This is useful for example for VIEW and SUSPECT messages, where a socket could be disconnected (e.g. cable plugged) and we still need to be able to receive our own messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1933) EJB 3.1 - Support deployment of EJBs packaged in .war files

by jaikiran pai (JIRA)

EJB 3.1 - Support deployment of EJBs packaged in .war files ------------------------------------------------------------ Key: EJBTHREE-1933 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1933 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB 3.1 As per the EJB 3.1 spec section 20.4, implement the support for deploying EJBs packaged in .war files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2109) Upgrade to jboss-ejb3-timerservice-spi 1.0.1 to utilize the MultiTimeoutMethodTimedObjectInvoker for EJB containers

by jaikiran pai (JIRA)

Upgrade to jboss-ejb3-timerservice-spi 1.0.1 to utilize the MultiTimeoutMethodTimedObjectInvoker for EJB containers ------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2109 URL: https://jira.jboss.org/browse/EJBTHREE-2109 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 EJBTHREE-2108 introduced MultiTimeoutMethodTimedObjectInvoker. Upgrade to this latest version of jboss-ejb3-timerservice-spi to utilize this MultiTimeoutMethodTimedObjectInvoker in EJB3 core containers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2093) Log the jndi names to which the singleton bean's views are being bound

by jaikiran pai (JIRA)

Log the jndi names to which the singleton bean's views are being bound ---------------------------------------------------------------------- Key: EJBTHREE-2093 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2093 Project: EJB 3.0 Issue Type: Task Components: singleton Affects Versions: EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai For non-Singleton beans, we log the JNDI names to which a bean's views are being bound at INFO. However for singleton beans we currently don't do this. It's pretty useful for an end user to quickly find out the jndi names on the console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2075) Track dependency upgrades for EJB3_1 1.0.8

by jaikiran pai (JIRA)

Track dependency upgrades for EJB3_1 1.0.8 ------------------------------------------ Key: EJBTHREE-2075 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2075 Project: EJB 3.0 Issue Type: Task Components: ejb3_1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 Track dependency upgrades for ejb3_1 1.0.8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2118) Integrate BeanManager with core Container(s)

by jaikiran pai (JIRA)

Integrate BeanManager with core Container(s) -------------------------------------------- Key: EJBTHREE-2118 URL: https://jira.jboss.org/browse/EJBTHREE-2118 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai As discussed over IRC, core containers (org.jboss.ejb3.Container) == org.jboss.ejb3.context.spi.BeanManager. This currently hasn't yet being integrated. Integrating the core containers with the BeanManager will pave the way for allowing to deprecate the TimerServicePropertyInjector and instead use JNDIPropertyInjector, to inject TimerService via ENC (see EJBTHREE-2113 for the details). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2113) TimerService is not available at java:comp/TimerService

by jaikiran pai (JIRA)

TimerService is not available at java:comp/TimerService ------------------------------------------------------- Key: EJBTHREE-2113 URL: https://jira.jboss.org/browse/EJBTHREE-2113 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-0.1.2, EJB3_1 1.0.7, Plugin 1.0.19 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 Although we allow TimerService to be injected into beans through @Resource, we don't really pull it from the java:comp/TimerService. Infact, java:comp/TimerService is not really bound for any of the EJB types. The injection works because of a special org.jboss.injection.TimerServicePropertyInjector which bypasses the ENC during injection. TimerServicePropertyInjector will henceforth be deprecated and TimerService injection should henceforth happen through java:comp/TimerService. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2129) Integrate async with Singleton container

by jaikiran pai (JIRA)

Integrate async with Singleton container ---------------------------------------- Key: EJBTHREE-2129 URL: https://jira.jboss.org/browse/EJBTHREE-2129 Project: EJB 3.0 Issue Type: Task Components: singleton Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 EJBTHREE-1721 introduces async into core containers. This affects singleton containers too. The necessary changes will be tracked in this JIRA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2169) @Startup @Singleton beans should be started after the auto-timers have been initialized

by jaikiran pai (JIRA)

@Startup @Singleton beans should be started after the auto-timers have been initialized --------------------------------------------------------------------------------------- Key: EJBTHREE-2169 URL: https://jira.jboss.org/browse/EJBTHREE-2169 Project: EJB 3.0 Issue Type: Bug Components: singleton Reporter: jaikiran pai Assignee: jaikiran pai When a @Startup @Singleton is created (i.e. the @PostConstruct is invoked), the auto-timers should already have been created and functional. Currently, the instance gets created even before the auto-timers are processed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 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 September 2010