March 2011 - jboss-jira - Jboss List Archives

by Jesper Pedersen (JIRA)

JDBC3 ----- Key: JBJCA-25 URL: https://jira.jboss.org/jira/browse/JBJCA-25 Project: JBoss JCA Issue Type: Task Components: JDBC Reporter: Jesper Pedersen Assignee: Jesper Pedersen The JDBC3 based work -- 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-3) Add Maven based build system

by Jesper Pedersen (JIRA)

Add Maven based build system ---------------------------- Key: JBJCA-3 URL: https://jira.jboss.org/jira/browse/JBJCA-3 Project: JBoss JCA Issue Type: Sub-task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 Add Maven style build environment -- 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: (JBAS-5426) Define JCA SPI

by Jesper Pedersen (JIRA)

Define JCA SPI -------------- Key: JBAS-5426 URL: http://jira.jboss.com/jira/browse/JBAS-5426 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assigned To: Jesper Pedersen Fix For: JBossAS-5.0.0.CR1 We need to define a SPI for the JCA layer in order to better separate clients (f.ex. EJB3) of JCA from the actual implementation. The SPI will live in the jboss-integration module. -- 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

15 years, 1 month

2
7
0 / 0

[JBoss JIRA] Resolved: (JBJCA-26) Making JCA security more pluggable

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-26?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-26. ---------------------------------- Resolution: Out of Date > Making JCA security more pluggable > ---------------------------------- > > Key: JBJCA-26 > URL: https://issues.jboss.org/browse/JBJCA-26 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > We need a mechanism to make JCA security more pluggable. > This is to cater for use cases where some extra context needs to be used. > The connection manager only understands a subject. > The connection factory (e.g. DataSource) only understands the CRI (method parameters). > The pooling uses both without needing to understand what they are in detail. > This change would provide a "wrapper" connection manager that can do things > more associated to context, e.g. it could be connection factory specific, > i.e. it understands the CRI and can do things that the connection factory doesn't do > or it can do things based on information. > An example of other information would allowing a per deployment > security domain such that you have different pre-configured user/password per ejb. > With something like the following in META-INF/jboss-[web].xml > <jboss> > <enterprise-beans> > <session> > <ejb-name>Whatever</ejb-name> > ... > <resource-ref> > <res-ref-name>jdbc/DataSource</res-ref-name> > <jndi-name>java:/MySQLDS</jndi-name> > <security-domain>FooBar</security-domain> > </resource-ref> > </session> > </enterprise-beans> > </jboss> -- 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-26) Making JCA security more pluggable

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-26?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-26. -------------------------------- > Making JCA security more pluggable > ---------------------------------- > > Key: JBJCA-26 > URL: https://issues.jboss.org/browse/JBJCA-26 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > We need a mechanism to make JCA security more pluggable. > This is to cater for use cases where some extra context needs to be used. > The connection manager only understands a subject. > The connection factory (e.g. DataSource) only understands the CRI (method parameters). > The pooling uses both without needing to understand what they are in detail. > This change would provide a "wrapper" connection manager that can do things > more associated to context, e.g. it could be connection factory specific, > i.e. it understands the CRI and can do things that the connection factory doesn't do > or it can do things based on information. > An example of other information would allowing a per deployment > security domain such that you have different pre-configured user/password per ejb. > With something like the following in META-INF/jboss-[web].xml > <jboss> > <enterprise-beans> > <session> > <ejb-name>Whatever</ejb-name> > ... > <resource-ref> > <res-ref-name>jdbc/DataSource</res-ref-name> > <jndi-name>java:/MySQLDS</jndi-name> > <security-domain>FooBar</security-domain> > </resource-ref> > </session> > </enterprise-beans> > </jboss> -- 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] Updated: (JBJCA-27) Unification of Timer implementation for JBossAS

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-27?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen updated JBJCA-27: --------------------------------- Labels: community_contribution (was: ) Assignee: (was: Jesper Pedersen) > Unification of Timer implementation for JBossAS > ----------------------------------------------- > > Key: JBJCA-27 > URL: https://issues.jboss.org/browse/JBJCA-27 > Project: IronJacamar > Issue Type: Task > Components: Timer > Reporter: Weston M. Price > Labels: community_contribution > > * Unification of timers into a Quartz based implementation. Timer uses to unify include: > ** jPBM timers > ** EJB/EJB3 timers > ** jmx timers > ** jmx timer service > ** org.jboss.util.* custom timers > * Have a Quartz rar providing a message inflow adaptor that delivers a Quartz event. > * Expose the Quartz APIs as Seam components -- 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-17) JMS Message Inflow

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-17?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-17. -------------------------------- > JMS Message Inflow > ------------------ > > Key: JBJCA-17 > URL: https://issues.jboss.org/browse/JBJCA-17 > Project: IronJacamar > Issue Type: Task > Components: JMS > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672 > The JMS message inflow in the JMS resource adapter needs properly testing. > There are basic tests, but the following are missing: > 1) Complete tests of edge cases for each configuration parameter in the activation spec > 2) Failure tests to confirm the implementation handles error gracefully > 3) Stress tests to make sure there the implementation is stable > 4) Performance tests to optimize the implementation > Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 > style deployments and hence as the default configuration. > This should be possible provided the user has not created their own > container configuration that uses the old JMSContainerInvoker explicitly. -- 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-17) JMS Message Inflow

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-17?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-17. ---------------------------------- Resolution: Won't Fix HornetQ has their own resource adapter > JMS Message Inflow > ------------------ > > Key: JBJCA-17 > URL: https://issues.jboss.org/browse/JBJCA-17 > Project: IronJacamar > Issue Type: Task > Components: JMS > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672 > The JMS message inflow in the JMS resource adapter needs properly testing. > There are basic tests, but the following are missing: > 1) Complete tests of edge cases for each configuration parameter in the activation spec > 2) Failure tests to confirm the implementation handles error gracefully > 3) Stress tests to make sure there the implementation is stable > 4) Performance tests to optimize the implementation > Additionally, we need to confirm that it is possible to use this implementation for EJB2.0 > style deployments and hence as the default configuration. > This should be possible provided the user has not created their own > container configuration that uses the old JMSContainerInvoker explicitly. -- 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-22) Move the rars into their own project

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-22?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen resolved JBJCA-22. ---------------------------------- Assignee: Jesper Pedersen Resolution: Out of Date > Move the rars into their own project > ------------------------------------ > > Key: JBJCA-22 > URL: https://issues.jboss.org/browse/JBJCA-22 > Project: IronJacamar > Issue Type: Sub-task > Components: Build > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This new project will NOT depend upon > 1) CONNECTOR > 2) TRANSACTION > 3) REMOTING > or any other jboss project other than common or j2ee > The aim here is to avoid people placing bad dependencies inside the rars > and basically subverting the design of jca. -- 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-22) Move the rars into their own project

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-22?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen closed JBJCA-22. -------------------------------- > Move the rars into their own project > ------------------------------------ > > Key: JBJCA-22 > URL: https://issues.jboss.org/browse/JBJCA-22 > Project: IronJacamar > Issue Type: Sub-task > Components: Build > Reporter: Adrian Brock > Assignee: Jesper Pedersen > > This new project will NOT depend upon > 1) CONNECTOR > 2) TRANSACTION > 3) REMOTING > or any other jboss project other than common or j2ee > The aim here is to avoid people placing bad dependencies inside the rars > and basically subverting the design of jca. -- 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

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