March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBJCA-12) Programmatic Connection Definition Deployment

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-12?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-12. -------------------------------- > Programmatic Connection Definition Deployment > --------------------------------------------- > > Key: JBJCA-12 > URL: https://issues.jboss.org/browse/JBJCA-12 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48673 > Provide a mechanism where ConnectionFactorys/DataSources (Connection Definitions) > can be deployed/undeployed programmatically. > The basic design is as follows: > 1) Provide a mechanism to instantiate MetaData for a connection factory. > This information is the same as the -ds.xml deployment format. > The MetaData can be logically divided into at least the following categories: > * RAR/ConnectionDefinition identification > * ManagedConnectionFactory > * Pool > * Security > * ConnectionManager > * Proxy/JNDI binding > 2) Write an optimized version of the MetaData for the DataSource deployments > which are really a simplified version of the ConnectionFactory deployments with some > hardwiring. > 3) Write a service that deploys the ConnectionFactory (creates MBeans) > from the MetaData and undeploys them based on their id (jndi binding). > 4) Convert the ConnectionFactory deployer to construct the MetaData from the -ds.xml > files and invoke the service new service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBJCA-19) RAR MetaData Repository

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-19?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-19. ---------------------------------- Resolution: Out of Date > RAR MetaData Repository > ----------------------- > > Key: JBJCA-19 > URL: https://issues.jboss.org/browse/JBJCA-19 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48681 > Implement a RAR MetaData repository. > There are two use cases of this object: > * A tool wants to retrieve information about how to configure a RAR deployment > either inbound/outbound or admin object > * Avoiding the need to specify the rar-name in jboss.xml, -ds.xml or admin object deployments when > only one rar implements the connection definition or message listener. > Design: > 1) When a RAR is deployed/undeployed update the repository with information about the RAR including > cross references by > * ConnectionDefinition > * MessageListener > * AdminObject > 2) When an MDB is deployed without identifying the rar, use the repository to try to guess the RAR > 3) When a ConnectionFactory is deployed without identifying the rar, use the repository to try to guess the RAR > 4) When an AdminObject is deployed without identifying the rar, use the repository to try to guess the RAR > The algorithm to guess the RAR is > a) Is there only one RAR implementing the object > b) If there is more than one RAR, is there a specific RAR in the same top level deployment (EAR) > as the referencing deployment -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBJCA-19) RAR MetaData Repository

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-19?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-19. -------------------------------- > RAR MetaData Repository > ----------------------- > > Key: JBJCA-19 > URL: https://issues.jboss.org/browse/JBJCA-19 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48681 > Implement a RAR MetaData repository. > There are two use cases of this object: > * A tool wants to retrieve information about how to configure a RAR deployment > either inbound/outbound or admin object > * Avoiding the need to specify the rar-name in jboss.xml, -ds.xml or admin object deployments when > only one rar implements the connection definition or message listener. > Design: > 1) When a RAR is deployed/undeployed update the repository with information about the RAR including > cross references by > * ConnectionDefinition > * MessageListener > * AdminObject > 2) When an MDB is deployed without identifying the rar, use the repository to try to guess the RAR > 3) When a ConnectionFactory is deployed without identifying the rar, use the repository to try to guess the RAR > 4) When an AdminObject is deployed without identifying the rar, use the repository to try to guess the RAR > The algorithm to guess the RAR is > a) Is there only one RAR implementing the object > b) If there is more than one RAR, is there a specific RAR in the same top level deployment (EAR) > as the referencing deployment -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBJCA-12) Programmatic Connection Definition Deployment

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-12?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-12. ---------------------------------- Resolution: Out of Date > Programmatic Connection Definition Deployment > --------------------------------------------- > > Key: JBJCA-12 > URL: https://issues.jboss.org/browse/JBJCA-12 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > Priority: Minor > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48673 > Provide a mechanism where ConnectionFactorys/DataSources (Connection Definitions) > can be deployed/undeployed programmatically. > The basic design is as follows: > 1) Provide a mechanism to instantiate MetaData for a connection factory. > This information is the same as the -ds.xml deployment format. > The MetaData can be logically divided into at least the following categories: > * RAR/ConnectionDefinition identification > * ManagedConnectionFactory > * Pool > * Security > * ConnectionManager > * Proxy/JNDI binding > 2) Write an optimized version of the MetaData for the DataSource deployments > which are really a simplified version of the ConnectionFactory deployments with some > hardwiring. > 3) Write a service that deploys the ConnectionFactory (creates MBeans) > from the MetaData and undeploys them based on their id (jndi binding). > 4) Convert the ConnectionFactory deployer to construct the MetaData from the -ds.xml > files and invoke the service new service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-482) Add spy functionality to JDBC resource adapter

by Jesper Pedersen (JIRA)

Add spy functionality to JDBC resource adapter ---------------------------------------------- Key: JBJCA-482 URL: https://issues.jboss.org/browse/JBJCA-482 Project: IronJacamar Issue Type: Task Components: JDBC Reporter: Jesper Pedersen Assignee: Jesper Pedersen Add functionality to the JDBC resource adapter such that statements executed are logged against a special logger instance - if enabled (boolean spy). Default value is false. General methods - like execute(String) and close() - should be logged at INFO level. Control methods - like rollback() and commit() - should be logged at DEBUG level. It should be possible to identify the statements based on the deployed datasource name. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-260) Create a WorkManager implementation that uses JBoss Threads

by Jesper Pedersen (JIRA)

Create a WorkManager implementation that uses JBoss Threads ----------------------------------------------------------- Key: JBJCA-260 URL: https://jira.jboss.org/jira/browse/JBJCA-260 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Create a WorkManager implementation that make use of the JBoss Threads project. -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-237) ResourceAdapterAssociation

by Jesper Pedersen (JIRA)

ResourceAdapterAssociation -------------------------- Key: JBJCA-237 URL: https://jira.jboss.org/jira/browse/JBJCA-237 Project: JBoss JCA Issue Type: Task Components: Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Make sure that the ResourceAdapterAssociation interface is probably handled -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-258) Bind connection factories into JNDI

by Jesper Pedersen (JIRA)

Bind connection factories into JNDI ----------------------------------- Key: JBJCA-258 URL: https://jira.jboss.org/jira/browse/JBJCA-258 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Bind each connection factory into JNDI. Also set the naming reference in each connection factory. -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-106) SJC: Add support for property maps

by Jesper Pedersen (JIRA)

SJC: Add support for property maps ---------------------------------- Key: JBJCA-106 URL: https://jira.jboss.org/jira/browse/JBJCA-106 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Add support for property maps, so they can be passed in the configuration. The remotable naming server is an example of an use-case. -- 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

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-31) Testsuite

by Jesper Pedersen (JIRA)

Testsuite --------- Key: JBJCA-31 URL: https://jira.jboss.org/jira/browse/JBJCA-31 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Parent task for the test suite for the core implementation -- 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

15 years, 1 month

1
3
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 March 2011