[JBoss JIRA] (WFLY-9439) Datasources are registered as singletons
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9439?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-9439:
----------------------------------------
This is not a bug. Each datasource exposes a (possibly) unique management API as the statistics it provides depend on the driver.
> Datasources are registered as singletons
> ----------------------------------------
>
> Key: WFLY-9439
> URL: https://issues.jboss.org/browse/WFLY-9439
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Michal Petrov
> Assignee: Stefano Maestri
>
> {code}
> /subsystem=datasources:read-children-types(include-singletons)
> {code}
> returns this
> {code}
> {
> "outcome" => "success",
> "result" => [
> "data-source",
> "data-source=ExampleDS",
> "jdbc-driver",
> "xa-data-source"
> ]
> }
> {code}
> This happens for any (xa-)data-source, not just the default one.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (ELY-1388) Clean up credential-store-type in schema
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1388?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved ELY-1388.
-----------------------------------
Resolution: Done
> Clean up credential-store-type in schema
> ----------------------------------------
>
> Key: ELY-1388
> URL: https://issues.jboss.org/browse/ELY-1388
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.2.0.Beta4
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta6
>
>
> The credential store type contains the following definition: -
> {code}
> <xsd:complexType name="credential-store-type">
> <xsd:annotation>
> <xsd:documentation>
> An individual credential store definition.
> </xsd:documentation>
> </xsd:annotation>
> <xsd:all minOccurs="0" maxOccurs="1">
> <xsd:element name="attributes" type="attributes-type"/>
> <xsd:element name="protection-parameter-credentials" type="client-credentials-type"/>
> <xsd:element name="providers" type="providers-type" />
> </xsd:all>
> <xsd:attribute name="name" type="xsd:string" use="required" />
> <xsd:attribute name="type" type="xsd:string" default="KeyStoreCredentialStore" use="optional">
> <xsd:annotation>
> <xsd:documentation>
> The credential store type, e.g. KeyStoreCredentialStore.
> </xsd:documentation>
> </xsd:annotation>
> </xsd:attribute>
> <xsd:attribute name="provider" type="xsd:string" use="optional">
> <xsd:annotation>
> <xsd:documentation>
> The name of the provider to use to
> instantiate the CredentialStoreSpi, if the provider is not
> specified then the first provider found that can
> create an instance of the specified 'type' will be
> used.
> </xsd:documentation>
> </xsd:annotation>
> </xsd:attribute>
> </xsd:complexType>
> {code}
> This effectively says the child elements are optional but if one is specified they all need to be specified, however they are all optional and can be specified individually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (ELY-1395) Incorrect type on <set-port /> element within authentication-configuration-type
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1395?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved ELY-1395.
-----------------------------------
Resolution: Done
> Incorrect type on <set-port /> element within authentication-configuration-type
> -------------------------------------------------------------------------------
>
> Key: ELY-1395
> URL: https://issues.jboss.org/browse/ELY-1395
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta6
>
>
> Presently it is defined as: -
> {code}
> <xsd:element name="set-port" type="port-number-simple-type" minOccurs="0"/>
> {code}
> It should be 'port-number-type' i.e.
> {code}
> <xsd:complexType name="port-number-type">
> <xsd:attribute name="number" type="port-number-simple-type" use="required"/>
> </xsd:complexType>
> <xsd:simpleType name="port-number-simple-type">
> <xsd:restriction base="xsd:positiveInteger">
> <xsd:minInclusive value="1"/>
> <xsd:maxInclusive value="65535"/>
> </xsd:restriction>
> </xsd:simpleType>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (ELY-1393) Allow match-host rule to match suffix wildcards and IP address ranges
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1393?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved ELY-1393.
-----------------------------------
Resolution: Done
> Allow match-host rule to match suffix wildcards and IP address ranges
> ---------------------------------------------------------------------
>
> Key: ELY-1393
> URL: https://issues.jboss.org/browse/ELY-1393
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.2.0.Beta6
>
>
> It would be nice if the match host rule could be expanded to match patterns as follows:
> * Allow {{*}} to match everything (this is already supported)
> * Allow strings of the form {{*.myhost.com}}
> * Allow IP address matching (this is already supported)
> * Allow CIDR block matching e.g. {{10.54.0.0/16}}
> This would allow authentication rules to be much simpler in some cases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months