February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6580) Do not add transitive dependency to deployments for system dependencies or user dependencies

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6580?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-6580: ------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 8.0.0.Alpha1) > Do not add transitive dependency to deployments for system dependencies or user dependencies > -------------------------------------------------------------------------------------------- > > Key: AS7-6580 > URL: https://issues.jboss.org/browse/AS7-6580 > Project: Application Server 7 > Issue Type: Enhancement > Components: Class Loading > Reporter: James Perkins > Assignee: James Perkins > Fix For: 7.3.0.Alpha1 > > > Currently the {{ModuleSpecProcessor}} adds transitive dependencies to a deployment if the module spec is specified to add them (looks like only RAR's from what I can see). This includes transitive dependencies that are declared in a {{jboss-deployment-structure.xml}} or ones automatically added by the container. > Change to only allow class-path entries to be transitive if the module spec defines they should be. System and user specified dependencies should not be transitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6580) Do not add transitive dependency to deployments for system dependencies or user dependencies

by James Perkins (JIRA)

James Perkins created AS7-6580: ---------------------------------- Summary: Do not add transitive dependency to deployments for system dependencies or user dependencies Key: AS7-6580 URL: https://issues.jboss.org/browse/AS7-6580 Project: Application Server 7 Issue Type: Enhancement Components: Class Loading Reporter: James Perkins Assignee: James Perkins Fix For: 8.0.0.Alpha1 Currently the {{ModuleSpecProcessor}} adds transitive dependencies to a deployment if the module spec is specified to add them (looks like only RAR's from what I can see). This includes transitive dependencies that are declared in a {{jboss-deployment-structure.xml}} or ones automatically added by the container. Change to only allow class-path entries to be transitive if the module spec defines they should be. System and user specified dependencies should not be transitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] Tom Eicher updated AS7-6565: ---------------------------- Affects Version/s: 8.0.0.Alpha1 > jdbc driver deployed inside ear takes name of ear > ------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6566) -ds.xml file using driver-class silently ignored

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/AS7-6566?page=com.atlassian.jira.plugin.s... ] Tom Eicher updated AS7-6566: ---------------------------- Affects Version/s: 8.0.0.Alpha1 > -ds.xml file using driver-class silently ignored > ------------------------------------------------ > > Key: AS7-6566 > URL: https://issues.jboss.org/browse/AS7-6566 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > When a datasource is defined within a {{*-ds.xml}} file, it is supposed to provide a {{<driver>}} element and not a {{<driver-class>}} (at least that is what the forum reference sais.) > Anyways, a such a datasource is completely silently ignored. > The failed datasource deployment should be recognized, logged and handled as such. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen reassigned AS7-6565: ------------------------------------ Assignee: Stefano Maestri (was: Jesper Pedersen) > jdbc driver deployed inside ear takes name of ear > ------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Tom Eicher > Assignee: Stefano Maestri > > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] Tom Eicher reopened AS7-6565: ----------------------------- reproduces in 8.0.0.Alpha1-SNAPSHOT of 2013-02-20. {code} 21:10:09,333 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) ... JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.jdbc-driver.postgresql_9_1_901_jdbc4_jar (missing) dependents: [service jboss.data-source.java:/jboss/datasources/myDS] {code} > jdbc driver deployed inside ear takes name of ear > ------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Tom Eicher > Assignee: Jesper Pedersen > > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6572) AS8 Java Security Manager Container Task

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/AS7-6572?page=com.atlassian.jira.plugin.s... ] Anil Saldhana updated AS7-6572: ------------------------------- Forum Reference: https://community.jboss.org/wiki/AS8JBossSecurityManagerDiscussion > AS8 Java Security Manager Container Task > ---------------------------------------- > > Key: AS7-6572 > URL: https://issues.jboss.org/browse/AS7-6572 > Project: Application Server 7 > Issue Type: Feature Request > Components: Security > Reporter: Anil Saldhana > Assignee: Anil Saldhana > Fix For: 8.0.0.Alpha1 > > > Container task to manage the various tasks needed for Java Security Manager related requirements from EE7 as well as JBoss Modules perspective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6566) -ds.xml file using driver-class silently ignored

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/AS7-6566?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen reassigned AS7-6566: ------------------------------------ Assignee: Stefano Maestri (was: Jesper Pedersen) > -ds.xml file using driver-class silently ignored > ------------------------------------------------ > > Key: AS7-6566 > URL: https://issues.jboss.org/browse/AS7-6566 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Tom Eicher > Assignee: Stefano Maestri > > When a datasource is defined within a {{*-ds.xml}} file, it is supposed to provide a {{<driver>}} element and not a {{<driver-class>}} (at least that is what the forum reference sais.) > Anyways, a such a datasource is completely silently ignored. > The failed datasource deployment should be recognized, logged and handled as such. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6566) -ds.xml file using driver-class silently ignored

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/AS7-6566?page=com.atlassian.jira.plugin.s... ] Tom Eicher reopened AS7-6566: ----------------------------- reproduces in 8.0.0.Alpha1-SNAPSHOT of 2013-02-20. As soon as I give a {{<driver-class>}} there is no mention of my DS in the log, it's just missing. > -ds.xml file using driver-class silently ignored > ------------------------------------------------ > > Key: AS7-6566 > URL: https://issues.jboss.org/browse/AS7-6566 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Tom Eicher > Assignee: Jesper Pedersen > > When a datasource is defined within a {{*-ds.xml}} file, it is supposed to provide a {{<driver>}} element and not a {{<driver-class>}} (at least that is what the forum reference sais.) > Anyways, a such a datasource is completely silently ignored. > The failed datasource deployment should be recognized, logged and handled as such. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6579) Deployment permissions to be merged with module permissions

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-6579: ---------------------------------- Summary: Deployment permissions to be merged with module permissions Key: AS7-6579 URL: https://issues.jboss.org/browse/AS7-6579 Project: Application Server 7 Issue Type: Sub-task Components: Security Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 8.0.0.Alpha1 Deployment permissions (META-INF/permissions.xml) need to be converted/merged into module level permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

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 February 2013