March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBJCA-21) Move the rars into a separate project that does not depend on the connection manager implementation

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-21?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-21. -------------------------------- > Move the rars into a separate project that does not depend on the connection manager implementation > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-21 > URL: https://issues.jboss.org/browse/JBJCA-21 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > The resource adapter implementations should NOT depend upon the connection manager > implementation or transaction manager or any other jboss service. > This is the wrong way around. It is like coding an EJB to use specifics of a JBoss EJB container. > Related, each resource adapter should be useable in a standalone environment > (with an internal dummy connection manager) through the alternate api > See javax.resource.spi.ManagedConnectionFactory > /** > * Creates a connection factory instance. The connection manager is provided > * by the resource adapter. > * > * STANDALONE USE > * > * @return the connection factory > * @throws ResourceException for a generic error > * @throws ResourceAdapterInternalException for an internal error in the > * resource adapter > */ > public Object createConnectionFactory() throws ResourceException; > /** > * Creates a connection factory instance. the connection manager is provided > * by the application server > * > * APPLICATION SERVER/EXTERNAL CONNECTION MANAGER USE > * > * @param cxManager the connection manager > * @return the connection factory > * @throws ResourceException for a generic error > * @throws ResourceAdapterInternalException for an internal error in the > * resource adapter > */ > public Object createConnectionFactory(ConnectionManager cxManager) throws ResourceException; -- 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-21) Move the rars into a separate project that does not depend on the connection manager implementation

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-21?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-21. ---------------------------------- Assignee: Jesper Pedersen Resolution: Out of Date > Move the rars into a separate project that does not depend on the connection manager implementation > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-21 > URL: https://issues.jboss.org/browse/JBJCA-21 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > The resource adapter implementations should NOT depend upon the connection manager > implementation or transaction manager or any other jboss service. > This is the wrong way around. It is like coding an EJB to use specifics of a JBoss EJB container. > Related, each resource adapter should be useable in a standalone environment > (with an internal dummy connection manager) through the alternate api > See javax.resource.spi.ManagedConnectionFactory > /** > * Creates a connection factory instance. The connection manager is provided > * by the resource adapter. > * > * STANDALONE USE > * > * @return the connection factory > * @throws ResourceException for a generic error > * @throws ResourceAdapterInternalException for an internal error in the > * resource adapter > */ > public Object createConnectionFactory() throws ResourceException; > /** > * Creates a connection factory instance. the connection manager is provided > * by the application server > * > * APPLICATION SERVER/EXTERNAL CONNECTION MANAGER USE > * > * @param cxManager the connection manager > * @return the connection factory > * @throws ResourceException for a generic error > * @throws ResourceAdapterInternalException for an internal error in the > * resource adapter > */ > public Object createConnectionFactory(ConnectionManager cxManager) throws ResourceException; -- 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-24) Remote ConnectionFactory usage

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-24?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-24. ---------------------------------- Resolution: Out of Date > Remote ConnectionFactory usage > ------------------------------ > > Key: JBJCA-24 > URL: https://issues.jboss.org/browse/JBJCA-24 > Project: IronJacamar > Issue Type: Sub-task > Components: JDBC > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This needs doing properly. It should be applicable to any resource adapter > not hardwired into the jdbc rar. -- 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-24) Remote ConnectionFactory usage

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-24?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-24. -------------------------------- > Remote ConnectionFactory usage > ------------------------------ > > Key: JBJCA-24 > URL: https://issues.jboss.org/browse/JBJCA-24 > Project: IronJacamar > Issue Type: Sub-task > Components: JDBC > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This needs doing properly. It should be applicable to any resource adapter > not hardwired into the jdbc rar. -- 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-23) Fix the LocalTxDataSource

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-23?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-23. ---------------------------------- Resolution: Out of Date > Fix the LocalTxDataSource > ------------------------- > > Key: JBJCA-23 > URL: https://issues.jboss.org/browse/JBJCA-23 > Project: IronJacamar > Issue Type: Sub-task > Components: JDBC > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This needs moving somewhere else (varia?). > But since it is basically a hack, it needs doing properly, > see the linked task on how todo this properly. -- 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-23) Fix the LocalTxDataSource

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-23?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-23. -------------------------------- > Fix the LocalTxDataSource > ------------------------- > > Key: JBJCA-23 > URL: https://issues.jboss.org/browse/JBJCA-23 > Project: IronJacamar > Issue Type: Sub-task > Components: JDBC > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This needs moving somewhere else (varia?). > But since it is basically a hack, it needs doing properly, > see the linked task on how todo this properly. -- 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-268) Provide JCA 1.5 profile of the container

by Jesper Pedersen (JIRA)

Provide JCA 1.5 profile of the container ---------------------------------------- Key: JBJCA-268 URL: https://jira.jboss.org/jira/browse/JBJCA-268 Project: JBoss JCA Issue Type: Task Components: Build, Common, Core, Deployer, Documentation, Embedded Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.1.0.CR1 Create a JCA 1.5 profile of the container -- 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
1
0 / 0

[JBoss JIRA] Created: (JBJCA-507) Make ManagedConnectionFactory available under RAR connector in rhq plugin inventory

by Lin Gao (JIRA)

Make ManagedConnectionFactory available under RAR connector in rhq plugin inventory ----------------------------------------------------------------------------------- Key: JBJCA-507 URL: https://issues.jboss.org/browse/JBJCA-507 Project: IronJacamar Issue Type: Task Components: Management Reporter: Lin Gao Assignee: Jesper Pedersen Fix For: 1.0.0.CR1 Current ManagedConnectionFactory, AdminObject can not be displayed under RAR resource in RHQ plugin inventory because of WeakReference of JCA object in management model. The solution is: 1. Create a ManagementRepositoryMeta class to wrap needed information like class name of javax.resource.spi.ManagedConnectionFactory and associated rar unique id in the tree structure 2. Add a method: getManagementRepositoryMeta() to Discover interface so that the ManagementRepositoryMeta can be initialized when discovers ManagementRepository -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8928) read-attribute failing in both CLI and http api

by Max Rydahl Andersen (JIRA)

read-attribute failing in both CLI and http api ----------------------------------------------- Key: JBAS-8928 URL: https://issues.jboss.org/browse/JBAS-8928 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen Doing this shows there is an attribute named 'path': [~] subsystem=deployment-scanner,scanner=default:read-resource { "outcome" => "success", "result" => { "path" => "deployments", "scan-enabled" => true, "scan-interval" => 5000, "relative-to" => "jboss.server.base.dir" }, "compensating-operation" => undefined } but reading that attribute fails: ~] subsystem=deployment-scanner,scanner=default:read-attribute(name="path") { "outcome" => "failed", "failure-description" => "No known attribute called path" } When using http://localhost:9990/domain-api/subsystem/deployment-scanner/scanner/def... the same result is returned. In error log it shows: 16:44:53,691 ERROR [org.jboss.as.controller] (pool-4-thread-2) operation ("read-attribute") failed - address: ([ ("subsystem" => "deployment-scanner"), ("scanner" => "default") ]): java.lang.NullPointerException at org.jboss.as.server.ServerControllerImpl.doExecute(ServerControllerImpl.java:180) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:221) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:187) at org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:171) at org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:56) at org.jboss.as.domain.http.server.DomainHttpServer.handle(DomainHttpServer.java:95) at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) [:1.6.0_22] at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80) at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:85) [:1.6.0_22] at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:606) at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) [:1.6.0_22] at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:578) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:680) [:1.6.0_22] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBJCA-508) Expose JNDI name in XA SPI

by Jesper Pedersen (JIRA)

Expose JNDI name in XA SPI -------------------------- Key: JBJCA-508 URL: https://issues.jboss.org/browse/JBJCA-508 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta5 Expose the JNDI name in the XAResource and Xid implementations through a SPI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

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