You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2011/06/08 04:13:58 UTC

[jira] [Created] (GERONIMO-5998) Use the implementation configured in system property as the preference while searching the provider in the OSGi registy

Use the implementation configured in system property as the preference while searching the provider in the OSGi registy
-----------------------------------------------------------------------------------------------------------------------

                 Key: GERONIMO-5998
                 URL: https://issues.apache.org/jira/browse/GERONIMO-5998
             Project: Geronimo
          Issue Type: New Feature
      Security Level: public (Regular issues)
          Components: osgi
    Affects Versions: 3.0
            Reporter: Ivan
            Assignee: Ivan
             Fix For: 3.0


 In Geronimo, we always ship two saaj implementation, and in the past, we create wrapper implementations for those SPI, and configure them as system property. In the traditional service search strategy path, the configurations from system property have the highest priority. So we could control which implementation will be used After we switches to OSGi, a locator-registry solution is used for searching all the available service providers. For SAAJ provider, now we have two providers. and it seems that which one will be used is depending on which one is first registered in the global registry. 
    I am thinking two solutions for this, and I prefer the option b.
    a. Introduce the priority feature for the service providers, the implementation could state its priority in the MANIFEST.MF file.
    b. Still take advantage of the system property, while the spec API requires the implementation, if the system property is configured and the implementation exists in the registry, use that one.
http://apache-geronimo.328035.n3.nabble.com/How-to-switch-between-the-RI-SAAJ-and-Axis2-SAAJ-td3034398.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMO-5998) Use the implementation configured in system property as the preference while searching the provider in the OSGi registy

Posted by "Ivan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan resolved GERONIMO-5998.
----------------------------

    Resolution: Fixed

> Use the implementation configured in system property as the preference while searching the provider in the OSGi registy
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5998
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5998
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Ivan
>             Fix For: 3.0
>
>
>  In Geronimo, we always ship two saaj implementation, and in the past, we create wrapper implementations for those SPI, and configure them as system property. In the traditional service search strategy path, the configurations from system property have the highest priority. So we could control which implementation will be used After we switches to OSGi, a locator-registry solution is used for searching all the available service providers. For SAAJ provider, now we have two providers. and it seems that which one will be used is depending on which one is first registered in the global registry. 
>     I am thinking two solutions for this, and I prefer the option b.
>     a. Introduce the priority feature for the service providers, the implementation could state its priority in the MANIFEST.MF file.
>     b. Still take advantage of the system property, while the spec API requires the implementation, if the system property is configured and the implementation exists in the registry, use that one.
> http://apache-geronimo.328035.n3.nabble.com/How-to-switch-between-the-RI-SAAJ-and-Axis2-SAAJ-td3034398.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-5998) Use the implementation configured in system property as the preference while searching the provider in the OSGi registy

Posted by "Ivan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045769#comment-13045769 ] 

Ivan commented on GERONIMO-5998:
--------------------------------

Commit the changes to trunk at rev.1133244, now Geronimo finder will check the registry to find the expected provider, and it should be compatible with the old behavior.

> Use the implementation configured in system property as the preference while searching the provider in the OSGi registy
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5998
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5998
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Ivan
>             Fix For: 3.0
>
>
>  In Geronimo, we always ship two saaj implementation, and in the past, we create wrapper implementations for those SPI, and configure them as system property. In the traditional service search strategy path, the configurations from system property have the highest priority. So we could control which implementation will be used After we switches to OSGi, a locator-registry solution is used for searching all the available service providers. For SAAJ provider, now we have two providers. and it seems that which one will be used is depending on which one is first registered in the global registry. 
>     I am thinking two solutions for this, and I prefer the option b.
>     a. Introduce the priority feature for the service providers, the implementation could state its priority in the MANIFEST.MF file.
>     b. Still take advantage of the system property, while the spec API requires the implementation, if the system property is configured and the implementation exists in the registry, use that one.
> http://apache-geronimo.328035.n3.nabble.com/How-to-switch-between-the-RI-SAAJ-and-Axis2-SAAJ-td3034398.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (GERONIMO-5998) Use the implementation configured in system property as the preference while searching the provider in the OSGi registy

Posted by "Ivan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045768#comment-13045768 ] 

Ivan commented on GERONIMO-5998:
--------------------------------

Commit the changes to geronimo-osgi-registry-1.1-SNAPSHOT at rev.1133243

> Use the implementation configured in system property as the preference while searching the provider in the OSGi registy
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5998
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5998
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Ivan
>             Fix For: 3.0
>
>
>  In Geronimo, we always ship two saaj implementation, and in the past, we create wrapper implementations for those SPI, and configure them as system property. In the traditional service search strategy path, the configurations from system property have the highest priority. So we could control which implementation will be used After we switches to OSGi, a locator-registry solution is used for searching all the available service providers. For SAAJ provider, now we have two providers. and it seems that which one will be used is depending on which one is first registered in the global registry. 
>     I am thinking two solutions for this, and I prefer the option b.
>     a. Introduce the priority feature for the service providers, the implementation could state its priority in the MANIFEST.MF file.
>     b. Still take advantage of the system property, while the spec API requires the implementation, if the system property is configured and the implementation exists in the registry, use that one.
> http://apache-geronimo.328035.n3.nabble.com/How-to-switch-between-the-RI-SAAJ-and-Axis2-SAAJ-td3034398.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira