February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-125) Batch Applications for the Java Platform (JSR-352)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-125?page=com.atlassian.jira.plugin.s... ] Shelly McGowan updated JBEE-125: -------------------------------- Component/s: jboss-batch-api > Batch Applications for the Java Platform (JSR-352) > --------------------------------------------------- > > Key: JBEE-125 > URL: https://issues.jboss.org/browse/JBEE-125 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-batch-api > Reporter: Shelly McGowan > Assignee: Cheng Fang > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-122) Concurrency Utilities for Java EE (JSR-236)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-122?page=com.atlassian.jira.plugin.s... ] Shelly McGowan updated JBEE-122: -------------------------------- Component/s: jboss-javaee-concurrency-api > Concurrency Utilities for Java EE (JSR-236) > -------------------------------------------- > > Key: JBEE-122 > URL: https://issues.jboss.org/browse/JBEE-122 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-javaee-concurrency-api > Reporter: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > These APIs are required as part of our Java EE 7 implementation. > They should be added to the org.jboss.spec project: > {code} > <dependency> > <groupId>org.jboss.spec.javax.enterprise.concurrent</groupId> > <artifactId>jboss-concurrent-api_1.0_spec</artifactId> > <version>1.0.0.Final-SNAPSHOT</version> > </dependency> > {code} > Project can be created in http://github.com/jboss/jboss-concurrent-api_spec -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) single 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 commented on AS7-6565: --------------------------------- Excellent! Thank you! > single 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: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-990) TestConnection override with CRI and Subject

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-990?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-990: ---------------------------------- Summary: TestConnection override with CRI and Subject (was: Test connection through CLI when <allow-multiple-users/> is applied to a datasource) Description: Create an override of the test connection method which operates on passed in ConnectionRequestInfo and Subject objects (was: Create a XA data-source(via CLI) which has the attribute <allow-multiple-users/> defined to true. Testing the connection using CLI shows the below error - ************************************** [standalone@localhost:9999 /] /subsystem=datasources/xa-data-source=OracleXA_DS:test-connection-in-pool() { "outcome" => "failed", "failure-description" => "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid", "rolled-back" => true } ************************************** On checking the description of the attribute ( /subsystem=datasources/xa-data-source=OracleXA_DS:read-resource-description(recursive=true) ) it says - "allow-multiple-users" => { "type" => BOOLEAN, "description" => "Specifies if multiple users will access the datasource through the getConnection(user, password) method and hence if the internal pool type should account for that" When testing the connection through "test-connection-in-pool" there is no way to provide username/password for the above mentioned getConnection() and hence connection fails.) Component/s: Core (was: JDBC) > TestConnection override with CRI and Subject > -------------------------------------------- > > Key: JBJCA-990 > URL: https://issues.jboss.org/browse/JBJCA-990 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.13.Final > Environment: JBoss EAP 6.0.1 > JBoss AS 7.1.3 > Reporter: Anurag Debnath > Assignee: Jesper Pedersen > Labels: eap6 > > Create an override of the test connection method which operates on passed in ConnectionRequestInfo and Subject objects -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-990) TestConnection override with CRI and Subject

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-990?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated JBJCA-990: --------------------------------------- Forum Reference: https://community.jboss.org/message/799863#799863 > TestConnection override with CRI and Subject > -------------------------------------------- > > Key: JBJCA-990 > URL: https://issues.jboss.org/browse/JBJCA-990 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.13.Final > Environment: JBoss EAP 6.0.1 > JBoss AS 7.1.3 > Reporter: Anurag Debnath > Assignee: Jesper Pedersen > Labels: eap6 > > Create an override of the test connection method which operates on passed in ConnectionRequestInfo and Subject objects -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-127) Java EE Connector Architecture (JSR-322)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-127?page=com.atlassian.jira.plugin.s... ] Shelly McGowan edited comment on JBEE-127 at 2/28/13 11:44 AM: --------------------------------------------------------------- Updates to v1.7: https://github.com/jboss/jboss-connector-api_spec/commit/d418fc003c237c86... https://github.com/jboss/jboss-connector-api_spec/commit/a58305db8b8c715e... Source from: ironjacamar-spec-api-1.1.0.Beta4-sources.jar was (Author: shelly.mcgowan): Updates to v1.7: https://github.com/jboss/jboss-connector-api_spec/commit/d418fc003c237c86... https://github.com/jboss/jboss-connector-api_spec/commit/a58305db8b8c715e... > Java EE Connector Architecture (JSR-322) > ---------------------------------------- > > Key: JBEE-127 > URL: https://issues.jboss.org/browse/JBEE-127 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Project repo exists: > https://github.com/jboss/jboss-connector-api_spec > Need updates to for v1.7. > {code} > <groupId>org.jboss.spec.javax.resource</groupId> > <artifactId>jboss-connector-api_1.7_spec</artifactId> > <version>1.0.0-SNAPSHOT</version> > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-127) Java EE Connector Architecture (JSR-322)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-127?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-127: ------------------------------------- Updates to v1.7: https://github.com/jboss/jboss-connector-api_spec/commit/d418fc003c237c86... https://github.com/jboss/jboss-connector-api_spec/commit/a58305db8b8c715e... > Java EE Connector Architecture (JSR-322) > ---------------------------------------- > > Key: JBEE-127 > URL: https://issues.jboss.org/browse/JBEE-127 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Project repo exists: > https://github.com/jboss/jboss-connector-api_spec > Need updates to for v1.7. > {code} > <groupId>org.jboss.spec.javax.resource</groupId> > <artifactId>jboss-connector-api_1.7_spec</artifactId> > <version>1.0.0-SNAPSHOT</version> > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-122) Concurrency Utilities for Java EE (JSR-236)

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBEE-122?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on JBEE-122: ---------------------------------- Pushed up the POM corrections. https://github.com/jboss/jboss-javaee-concurrency-api_spec/commit/804ae85... > Concurrency Utilities for Java EE (JSR-236) > -------------------------------------------- > > Key: JBEE-122 > URL: https://issues.jboss.org/browse/JBEE-122 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Reporter: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > These APIs are required as part of our Java EE 7 implementation. > They should be added to the org.jboss.spec project: > {code} > <dependency> > <groupId>org.jboss.spec.javax.enterprise.concurrent</groupId> > <artifactId>jboss-concurrent-api_1.0_spec</artifactId> > <version>1.0.0.Final-SNAPSHOT</version> > </dependency> > {code} > Project can be created in http://github.com/jboss/jboss-concurrent-api_spec -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5498) infinispan.DistributedCacheManagerTest unit tests fail with openjdk7

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-5498?page=com.atlassian.jira.plugin.s... ] Radoslav Husar resolved AS7-5498. --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) Resolution: Done Builds like charm now, AS 8 is now completely on JDK7. > infinispan.DistributedCacheManagerTest unit tests fail with openjdk7 > -------------------------------------------------------------------- > > Key: AS7-5498 > URL: https://issues.jboss.org/browse/AS7-5498 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering, Test Suite > Environment: affected master > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > Attachments: org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.txt, TEST-org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest.xml > > > Noticed by alexey > [rhusar@rhusar jboss-as]$ java -version > java version "1.7.0_06-icedtea" > OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-x86_64) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > {noformat} > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-clustering-web-infinispan --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/rhusar/git/jboss-as/clustering/web-infinispan/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-clustering-web-infinispan --- > [INFO] Compiling 6 source files to /home/rhusar/git/jboss-as/clustering/web-infinispan/target/test-classes > [INFO] > [INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-clustering-web-infinispan --- > [INFO] Surefire report directory: /home/rhusar/git/jboss-as/clustering/web-infinispan/target/surefire-reports > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.as.clustering.web.infinispan.FineSessionAttributeStorageTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.334 sec > Running org.jboss.as.clustering.web.infinispan.CoarseSessionAttributeStorageTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec > Running org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest > Tests run: 22, Failures: 2, Errors: 6, Skipped: 0, Time elapsed: 0.42 sec <<< FAILURE! > Running org.jboss.as.clustering.web.infinispan.SimpleExternalizerTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec > Running org.jboss.as.clustering.web.infinispan.SessionAttributeStorageFactoryTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec > Running org.jboss.as.clustering.web.infinispan.SessionMapEntryTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec > Results : > Failed tests: getSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 1688182366> was not:<null> > getMissingSessionDataNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): expected same:<Mock for IncomingDistributableSessionData, hashCode: 981356300> was not:<null> > Tests in error: > removeSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) > removeSessionLocal(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) > removeSessionLocalNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) > evictSession(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) > evictSessionNoOwner(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest): (..) > getSessionIds(org.jboss.as.clustering.web.infinispan.DistributedCacheManagerTest) > Tests run: 33, Failures: 2, Errors: 6, Skipped: 0 > {noformat} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1000) Track component updates

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1000: -------------------------------------- Summary: Track component updates Key: JBJCA-1000 URL: https://issues.jboss.org/browse/JBJCA-1000 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta5 -- 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, 2 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