[jboss-jira] [JBoss JIRA] (ELY-11) Interoperability Testing
Darran Lofthouse (JIRA)
issues at jboss.org
Fri Jun 13 11:57:39 EDT 2014
[ https://issues.jboss.org/browse/ELY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse updated ELY-11:
--------------------------------
Description:
This does not necessarily belong here as it may be an independent project of it's own but for now here it is.
WildFly-Elytron and WildFly-SASL are going to be used with different providers of the SPI exposed by these projects, rather than waiting until we are integrating within WildFly we should create project(s) to test the interoperability of these two projects with potential projects that will implement the SPI.
The interoperability testing will predominantly validate two areas: -
1 - The SPIs being exposed by these project for the integration of different providers is actually valid.
2 - The implementation and APIs of the related providers are in fact capable of meeting the requirements for WildFly.
The sooner we can identify any mis-match in this area the better to give us time to work out the solution.
was:
This does not necessarily belong here as it may be an independent project of it's own but for now here it is.
WildFly-Elytron and WildFly-SASL are going to be used with different providers of the SPI exposed by these projects, rather than waiting until we are integrating within WildFly we should create project(s) to test the interoperability of these two projects with potential projects that will implement the SPI.
> Interoperability Testing
> ------------------------
>
> Key: ELY-11
> URL: https://issues.jboss.org/browse/ELY-11
> Project: WildFly Elytron
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Darran Lofthouse
> Fix For: 1.0.0.Beta1
>
>
> This does not necessarily belong here as it may be an independent project of it's own but for now here it is.
> WildFly-Elytron and WildFly-SASL are going to be used with different providers of the SPI exposed by these projects, rather than waiting until we are integrating within WildFly we should create project(s) to test the interoperability of these two projects with potential projects that will implement the SPI.
> The interoperability testing will predominantly validate two areas: -
> 1 - The SPIs being exposed by these project for the integration of different providers is actually valid.
> 2 - The implementation and APIs of the related providers are in fact capable of meeting the requirements for WildFly.
> The sooner we can identify any mis-match in this area the better to give us time to work out the solution.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list