[jboss-jira] [JBoss JIRA] (AS7-6898) Update JCA management API

[Heiko Braun (JIRA)]

Heiko Braun created AS7-6898:
--------------------------------

             Summary: Update JCA management API
                 Key: AS7-6898
                 URL: https://issues.jboss.org/browse/AS7-6898
             Project: Application Server 7
          Issue Type: Feature Request
          Components: Domain Management, JCA
            Reporter: Heiko Braun
            Assignee: Brian Stansberry
             Fix For: 8.0.0.Beta1



On 04/05/2013 09:50 PM, Brian Stansberry wrote:
A couple points re: allowing teams who provide management tooling for
the AS to plan for AS 8:

1) Major subsystem changes


We will have some changes/additions to our JCA, ResourceAdapters and 
Datasources subsystems.

Here you have the main point I'm changing, and reasons for that. Those 
points should be quite stable, but I'l get back to you next week if I 
realize during implementation I need something else.

JCA:

Reasons: Adding support for Distrubuted Work Manager.
Changes: WorkManager will have more parameters to support distributable 
configuaration. There will be for sure those parameters (don't consider 
definition definitive, I'm still working on it):
DISTRIBUTED(SimpleAttributeDefinitionBuilder.create("distributed", 
ModelType.BOOLEAN)
                        .setDefaultValue(new ModelNode(false))
                        .setAllowExpression(true)
                        .setAllowNull(true)
                        .setMeasurementUnit(MeasurementUnit.NONE)
                        .setRestartAllServices()
                        .setRequires("selector", "policy")
                        .build()),
        SELECTOR(SimpleAttributeDefinitionBuilder.create("selector", 
ModelType.STRING)
                .setAllowExpression(true)
                .setAllowNull(true)
                .setMeasurementUnit(MeasurementUnit.NONE)
                .setRestartAllServices()
                .setXmlName("selector")
                .setValidator(new 
EnumValidator<SelectorValue>(SelectorValue.class, true, true ))
                .build()),
        POLICY(SimpleAttributeDefinitionBuilder.create("policy", 
ModelType.STRING)
                .setAllowExpression(true)
                .setAllowNull(true)
                .setMeasurementUnit(MeasurementUnit.NONE)
                .setRestartAllServices()
                .setXmlName("policy")
                .setValidator(new 
EnumValidator<PolicyValue>(PolicyValue.class, true, true))
                .build());

There will be also a parameter to point a channel name (JGroups Channel) 
that is defined in a new subresource at subsystem level (to be verified)

ResourceAdapters:
1)
Reasons: support inflow security
Changes: there will be a workmanager-security subresource into 
resource-adapter containing configuration for security. I've not yet a 
DMR definition, I'll send you in next days as an update. If you want to 
get an idea take a look to workmanagerType and referenced type in 
resource_adapters_1_1.xsd of Ironjacamar Beta4

2)
Reasons: changes to connection-definition to support new attributes:
changes: we will have new attributes called sharable (boolean), 
enlistment(boolean), initial-pool-size(int),
capacity-incrementer-class(string), 
capacity-incrementer-properties("type" => OBJECT, "value-type" => STRING),
capacity-decrementer-class(string), 
capacity-decrementer-properties("type" => OBJECT, "value-type" => STRING)

3)
Reasons: new flush strategy
Channges: constant accepted for flush-strategy will changes


Datasources
Reasons: changes to support new attributes:
changes: we will have new attributes called initial-pool-size(int),
capacity-incrementer-class(string), 
capacity-incrementer-properties("type" => OBJECT, "value-type" => STRING),
capacity-decrementer-class(string), 
capacity-decrementer-properties("type" => OBJECT, "value-type" => STRING),
url-property (string)


I'm working on all those points. I'll follow up on this thread if I 
realize I need more changes.

regards
S


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