[JBoss JIRA] (AS7-6622) Integrate RESTEasy and Hibernate Validator for resource validation
by Emmanuel Bernard (JIRA)
Emmanuel Bernard created AS7-6622:
-------------------------------------
Summary: Integrate RESTEasy and Hibernate Validator for resource validation
Key: AS7-6622
URL: https://issues.jboss.org/browse/AS7-6622
Project: Application Server 7
Issue Type: Sub-task
Reporter: Emmanuel Bernard
Fix For: 8.0.0.Alpha1
JAX-RS describes how resources can be validated via the use of Bean Validation.
While some are method calls on CDI beans and thus can be handled by the CDI interceptor, fields and getter resources cannot be handled that way. Likewise @GET, @PUT etc methods are considered constrained methods even if they are getters and without user use of @ValidateExecutable.
We need to figure out something.
Adding [~bill.burke] to the loop
--
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
[JBoss JIRA] (AS7-4377) Failed to create messaging connection factory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4377?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated AS7-4377:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=908758
> Failed to create messaging connection factory
> ---------------------------------------------
>
> Key: AS7-4377
> URL: https://issues.jboss.org/browse/AS7-4377
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Heiko Braun
> Assignee: Jeff Mesnil
> Fix For: 7.1.2.Final (EAP)
>
>
> {noformat}
> [INFO] {
> [INFO] "compress-large-messages" => false,
> [INFO] "failover-on-initial-connection" => false,
> [INFO] "failover-on-server-shutdown" => false,
> [INFO] "use-global-pools" => true,
> [INFO] "address" => [
> [INFO] ("subsystem" => "messaging"),
> [INFO] ("hornetq-server" => "default"),
> [INFO] ("connection-factory" => "test")
> [INFO] ],
> [INFO] "operation" => "add",
> [INFO] "entries" => ["java:/testCF"],
> [INFO] "connector" => ["netty"]
> [INFO] }
> {noformat}
> leads to
> {noformat}
> 15:28:47,269 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "messaging"),
> ("hornetq-server" => "default"),
> ("connection-factory" => "TestCF")
> ]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.messaging.jms.ConnectionFactoryAdd.createConfiguration(ConnectionFactoryAdd.java:145)
> at org.jboss.as.messaging.jms.ConnectionFactoryAdd.performRuntime(ConnectionFactoryAdd.java:109)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294)
> at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201)
> at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208)
> at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> {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
[JBoss JIRA] (AS7-6621) Work on CDI + Bean Validation integration for method validation
by Emmanuel Bernard (JIRA)
Emmanuel Bernard created AS7-6621:
-------------------------------------
Summary: Work on CDI + Bean Validation integration for method validation
Key: AS7-6621
URL: https://issues.jboss.org/browse/AS7-6621
Project: Application Server 7
Issue Type: Sub-task
Components: EE
Reporter: Emmanuel Bernard
Assignee: David Lloyd
Fix For: 8.0.0.Alpha1
Bean Validation and CDI needs to integrate to validate method parameters and return values. This can be done via a portable extension but [~jason.greene] was mentioning doing something proprietary to speed up the bootstrap process.
--
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
[JBoss JIRA] (AS7-6620) DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-6620?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-6620:
--------------------------------
Description: This might be due to historical reasons for the TS to run faster, but this messes up clustering tests since shutdown is part of the test. (was: This might be due to historical reasons for the TS to run faster, but this messes up clustering tests when shutdown is part of the test.)
> DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows
> ---------------------------------------------------------------------------------------------
>
> Key: AS7-6620
> URL: https://issues.jboss.org/browse/AS7-6620
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.2.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> This might be due to historical reasons for the TS to run faster, but this messes up clustering tests since shutdown is part of the test.
--
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
[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10
by Frank Langelage (JIRA)
[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ]
Frank Langelage commented on AS7-6616:
--------------------------------------
Yes, your change solved my problem.
Thank for the very quick response.
> AS 8: Testsuite fails on Solaris SPARC 10
> -----------------------------------------
>
> Key: AS7-6616
> URL: https://issues.jboss.org/browse/AS7-6616
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 8.0.0.Alpha1
> Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41
> Reporter: Frank Langelage
> Assignee: jaikiran pai
> Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml
>
>
> Compiling the current sources from github fails for me on this environment.
> On Windows everything is fine.
> Compiling 7.2.0.Final works in this environment.
> But regarding this test, nothing seems to have changed in between.
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec
> Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
> Running org.jboss.as.naming.InitialContextTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE!
> Running org.jboss.as.naming.InitialContextFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
> Running org.jboss.as.naming.NamingEventCoordinatorTestCase
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec
> Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec
> Running org.jboss.as.naming.InMemoryNamingStoreTestCase
> Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec
> Running org.jboss.as.naming.ObjectFactoryTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
> Running org.jboss.as.naming.NamingContextTestCase
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec
> Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec
> Results :
> Tests in error:
> testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null
> Tests run: 70, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s]
> [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s]
> [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s]
> [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s]
> [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s]
> [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: EE ...................... SKIPPED
> [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
> [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Clustering Server API ... SKIPPED
> [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
> [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
> [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
> [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: Clustered registry service SKIPPED
> [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED
> [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
> [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
> [INFO] JBoss Application Server: Config Assembly ......... SKIPPED
> [INFO] JBoss Application Server: Command line interface .. SKIPPED
> [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED
> [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
> [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
> [INFO] JBoss Application Server: Clustered singleton services SKIPPED
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
> [INFO] JBoss Application Server: Config Admin ............ SKIPPED
> [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
> [INFO] JBoss Application Server: EE Deployment ........... SKIPPED
> [INFO] JBoss Application Server: Embedded ................ SKIPPED
> [INFO] JBoss Application Server: JAXR Client ............. SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JPA SPI ................. SKIPPED
> [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
> [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Weld Integration ........ SKIPPED
> [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED
> [INFO] JBoss Application Server: JDR ..................... SKIPPED
> [INFO] JBoss Application Server: JSF ..................... SKIPPED
> [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
> [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
> [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
> [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
> [INFO] JBoss Application Server: OSGi .................... SKIPPED
> [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED
> [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED
> [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED
> [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED
> [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
> [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
> [INFO] JBoss Application Server: System JMX Module ....... SKIPPED
> [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
> [INFO] JBoss Application Server: Build ................... SKIPPED
> [INFO] JBoss Application Server: Build Modular ........... SKIPPED
> [INFO] JBoss Application Server: Arquillian .............. SKIPPED
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
> [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
> [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED
> [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED
> [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED
> [INFO] JBoss Application Server: Distribution ............ SKIPPED
> [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
> [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED
> [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
> [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6:36.380s
> [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013
> [INFO] Final Memory: 122M/348M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures.
> [ERROR]
> [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-naming
--
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
[JBoss JIRA] (AS7-6619) Management API for Datasources subsystem is missing some properties
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6619?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6619:
----------------------------------------------
Zbyněk Roubalík <zroubali(a)redhat.com> made a comment on [bug 915288|https://bugzilla.redhat.com/show_bug.cgi?id=915288]
Description of problem:
Some properties which were present in previous versions of AS7 are missing in current release:
Parameter driver-name for operation 'get-installed-driver' is no longer available.
These value-type for 'reply-properties' for operation 'get-installed-driver' are no longer available: [jdbc-compliant, module-slot, driver-class-name, driver-module-name]
> Management API for Datasources subsystem is missing some properties
> -------------------------------------------------------------------
>
> Key: AS7-6619
> URL: https://issues.jboss.org/browse/AS7-6619
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Reporter: Zbyněk Roubalík
> Assignee: Stefano Maestri
>
> Some properties which were present in previous versions of AS7 are missing in current release:
> Parameter driver-name for operation 'get-installed-driver' is no longer available.
> These value-type for 'reply-properties' for operation 'get-installed-driver' are no longer available: [jdbc-compliant, module-slot, driver-class-name, driver-module-name]
--
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