[JBoss JIRA] Created: (AS7-1789) Fix JCA description providers for the improved validation in jboss-as-subsystem-test
by Kabir Khan (JIRA)
Fix JCA description providers for the improved validation in jboss-as-subsystem-test
-------------------------------------------------------------------------------------
Key: AS7-1789
URL: https://issues.jboss.org/browse/AS7-1789
Project: Application Server 7
Issue Type: Feature Request
Components: JCA
Reporter: Kabir Khan
Assignee: Stefano Maestri
Fix For: 7.1.0.Alpha1
I added some tests called DataSourcesSubsystemTestCase, JcaSubsystemTestCase and ResourceAdaptersTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days.
To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows:
{code}
@Override
protected ValidationConfiguration getModelValidationConfiguration() {
return null;
}
@Override
protected boolean isValidateOperations() {
//TODO fix providers https://issues.jboss.org/browse/AS7-1789
return false;
}
{code}
Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples.
The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (AS7-1799) Fix the XTS subsystem test
by Kabir Khan (JIRA)
Fix the XTS subsystem test
---------------------------
Key: AS7-1799
URL: https://issues.jboss.org/browse/AS7-1799
Project: Application Server 7
Issue Type: Feature Request
Reporter: Kabir Khan
Assignee: Stefano Maestri
Fix For: 7.1.0.Alpha1
I added a test called TransactionSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days.
To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows:
{code}
@Override
protected ValidationConfiguration getModelValidationConfiguration() {
return null;
}
{code}
Returning null basically turns off validation of the providers. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples.
The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (AS7-1786) Fix OSGi description providers for the improved validation in jboss-as-subsystem-test
by Kabir Khan (JIRA)
Fix OSGi description providers for the improved validation in jboss-as-subsystem-test
-------------------------------------------------------------------------------------
Key: AS7-1786
URL: https://issues.jboss.org/browse/AS7-1786
Project: Application Server 7
Issue Type: Feature Request
Reporter: Kabir Khan
Assignee: Thomas Diesler
Fix For: 7.1.0.Alpha1
I am adding some more validation of the model. This will be committed to upstream in the next few days. To make the security tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows:
{code}
@Override
protected ValidationConfiguration getModelValidationConfiguration() {
return null;
}
{code}
Returning null basically turns off validation of the providers. These are the errors that happen (this might change a bit before I commit the final version of the validation stuff):
{code}
VALIDATION ERRORS IN MODEL:
Invalid key 'attributes' found for child type 'configuration' @[("subsystem" => "osgi")]
No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true,"acces
s-type" => "read-only","storage" => "configuration"} for attribute 'entries'[
("subsystem" => "osgi"),
("configuration" => "*")
]
No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true} for o
peration parameter 'add.entries' @[
("subsystem" => "osgi"),
("configuration" => "*")
]
Invalid key 'attributes' found for child type 'property' @[("subsystem" => "osgi")]
Invalid key 'attributes' found for child type 'module' @[("subsystem" => "osgi")]
{code}
The work in progress lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (JBBUILD-702) Create prototype modular build
by Paul Gier (JIRA)
Create prototype modular build
------------------------------
Key: JBBUILD-702
URL: https://issues.jboss.org/browse/JBBUILD-702
Project: JBoss Build System
Issue Type: Task
Reporter: Paul Gier
Assignee: Paul Gier
Based on some discussion about how to improve the upstream JBoss builds, we should create a prototype build that meets the following requirements:
* Downloads a set of component versions from 2 BOMs (stable and latest)
* Uses the stable BOM (bill of materials) for compile classpath
* Runs the unit/integration tests with both the stable and latest BOM
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months