July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1854) Configure EJB3 MC beans to avoid AOPDependencyBuilder

by jaikiran pai (JIRA)

Configure EJB3 MC beans to avoid AOPDependencyBuilder ----------------------------------------------------- Key: EJBTHREE-1854 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1854 Project: EJB 3.0 Issue Type: Task Components: core, deployers Affects Versions: 1.1.7 Reporter: jaikiran pai Assignee: jaikiran pai This task is to keep track of the change(s) required for all EJB3 MC bean (programatic and xml based) to ensure that the AOPDependencyBuilder does not come into picture during deployment. Avoiding AOPDependencyBuilder has shown good performance improvements. There isn't a final decision yet on how to do this although MC provides @DisableAOP annotation to achieve this. The MC support for this is currently available in AS 5_x branch and needs to be ported to AS trunk before EJB3 can think of using this. Once there's a decision on what's the best approach to accomplish this, we can do the changes in EJB3. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1857) Track the upgrades during EJB3 plugin 1.0.10 release

by jaikiran pai (JIRA)

Track the upgrades during EJB3 plugin 1.0.10 release ---------------------------------------------------- Key: EJBTHREE-1857 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1857 Project: EJB 3.0 Issue Type: Task Components: plugin Reporter: jaikiran pai Assignee: jaikiran pai This issue is to track any updates to version dependencies during the EJB3 1.0.10 plugin release. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7090) org.jboss.jdbc.DerbyDatabase used by varia example has a bug and never attempts to shut down derby database

by Irena Shaigorodsky (JIRA)

org.jboss.jdbc.DerbyDatabase used by varia example has a bug and never attempts to shut down derby database ----------------------------------------------------------------------------------------------------------- Key: JBAS-7090 URL: https://jira.jboss.org/jira/browse/JBAS-7090 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Environment: JBoss 4.0.5.GA and JBoss 4.2.3.GA Reporter: Irena Shaigorodsky org.jboss.jdbc.DerbyDatabase used by varia example has a following bug. 1. connection member is created at service start-up 2. getConnection(String dbURL) creates new connection only if connection member is null 3. on service shut down when getConnection("jdbc:derby:;shutdown=true"); is called nothing happens and Derby is not brought down. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1866) EJB deployer require mapped name for SessionContext injection

by Rinat Gareev (JIRA)

EJB deployer require mapped name for SessionContext injection ------------------------------------------------------------- Key: EJBTHREE-1866 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1866 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: Rinat Gareev EJB deployer require mapped name for SessionContext injection EJB class: @Stateful @EJBs ({ @EJB (beanInterface = CoreSecurityFacade.class, beanName = "CoreSecurityFacadeBean", name = "ejb/CoreSecurityFacade"), @EJB (beanInterface = CoreApplicationsFacade.class, beanName = "CoreApplicationsFacadeBean", name = "ejb/CoreApplicationsFacade"), @EJB (beanInterface = CoreConfigFacade.class, beanName = "CoreConfigFacadeBean", name = "ejb/CoreConfigFacade") }) public class CoreFacadeFactoryBean implements CoreFacadeFactory, Serializable { @Resource private SessionContext ctx; ....content omitted } Root cause: Caused by: java.lang.RuntimeException: You did not specify a @Resource.mappedName() on private javax.ejb.SessionContext rs.diving.ubcc.core.core.core.CoreFacadeFactoryBean.ctx and there is no binding for enc name env/rs.diving.ubcc.core.core.core.CoreFacadeFactoryBean/ctx in XML at org.jboss.injection.ResourceHandler.handlePropertyAnnotation(ResourceHandler.java:684) at org.jboss.injection.ResourceHandler.handleFieldAnnotations(ResourceHandler.java:497) at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:160) at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:197) at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:590) at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527) ... 35 more -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBJCA-110) Use remotable POJO naming server

by Jesper Pedersen (JIRA)

Use remotable POJO naming server -------------------------------- Key: JBJCA-110 URL: https://jira.jboss.org/jira/browse/JBJCA-110 Project: JBoss JCA Issue Type: Task Components: Standalone Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Switch to a remotable POJO naming server and allow the user to bind the address via a "-b" startup option. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-213) Expose SchemaBindingValidator as an interface

by Ales Justin (JIRA)

Expose SchemaBindingValidator as an interface --------------------------------------------- Key: JBXB-213 URL: https://jira.jboss.org/jira/browse/JBXB-213 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.2.Beta1 Reporter: Ales Justin Assignee: Ales Justin Expose current class SchemaBindingValidator as an interface, moving the current impl to DefaultSchemaBindingValidator. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1865) Upgrade to hibernate-core 3.3.1.GA

by jaikiran pai (JIRA)

Upgrade to hibernate-core 3.3.1.GA ---------------------------------- Key: EJBTHREE-1865 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1865 Project: EJB 3.0 Issue Type: Thirdparty Change Components: core Affects Versions: 1.1.8 Reporter: jaikiran pai Assignee: jaikiran pai Right now the core depends on: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> <version>3.2.6.ga</version> </dependency> Furthermore, org.hibernate:hibernate is a banned dependency in AS https://jira.jboss.org/jira/browse/JBAS-6904 Move to org.hibernate:hibernate-core 3.3.1.GA -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1679) http://wiki.jboss.org/wiki/Wiki.jsp?page=HelpBugReport

by Adrian Woodhead (JIRA)

http://wiki.jboss.org/wiki/Wiki.jsp?page=HelpBugReport ------------------------------------------------------ Key: JBMESSAGING-1679 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1679 Project: JBoss Messaging Issue Type: Bug Affects Versions: 2.0.0.beta3 Reporter: Adrian Woodhead Assignee: Tim Fox Refer to http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242246#4242246 for more information, stack trace etc. In essence the problem seems to be messages with an expiry time set seem to have problems when pre-ack mode is used. -- 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

16 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBOOT-96) Extract initialization logic

by Andrew Lee Rubinger (JIRA)

Extract initialization logic ---------------------------- Key: JBBOOT-96 URL: https://jira.jboss.org/jira/browse/JBBOOT-96 Project: JBoss Bootstrap Issue Type: Task Components: impl-as, impl-base, impl-mc Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 2.0.0-beta-1 With JBBOOT-95 we now have pre/post states for server initialization. This means that the initialize() method must be marked final such that its logic containing when to fire the state changes cannot be overridden. We still need to provide a mechanism for subclasses of AbstractServer to carry out their own initialization logic, so extract this into a "doInitialize()", much like we have a "doStart()". -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-108) SJC: Add support for <constructor>

by Jesper Pedersen (JIRA)

SJC: Add support for <constructor> ---------------------------------- Key: JBJCA-108 URL: https://jira.jboss.org/jira/browse/JBJCA-108 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Add support for <constructor> constructs for beans. An example <bean name="LookupPool"> <constructor factoryMethod="newFixedThreadPool" factoryClass="java.util.concurrent.Executors"> <parameter>2</parameter> </constructor> </bean> -- 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

16 years, 10 months

1
1
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 July 2009