[jbosstools-issues] [JBoss JIRA] (JBIDE-10253) Clone as7 management plugin for as7.1

[Andre Dietisheim (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646086#comment-12646086 ] 

Andre Dietisheim edited comment on JBIDE-10253 at 11/28/11 4:01 PM:
--------------------------------------------------------------------

the above changes did not solve the problem so I had to revert to the version before my changes. 
I tracked the client code down to several component and I'm pretty sure that the correct jars are loaded, so IMHO this is not an osgi issue per se. I then started tracking the authentication issues that you get if you start an as71 (after having started an as7) and found the following code in the as71 client:

{code}
ManagementClientChannelStrategy#Establishing#getChannel():

 public ManagementChannel getChannel() throws IOException {
            AccessController.doPrivileged(new PrivilegedAction<Object>() {
                public Object run() {
                    if (Security.getProvider(saslProvider.getName()) == null) {
                        Security.insertProviderAt(saslProvider, 1);
                    }
                    return null;
                }
            });
{code}

This sets the provider for the whole JVM, no chance for plugin-separation. 
I then to set the sasl providers in each as7 management bundle, which should solve the auth issue, but I still have the issue. So I suspect that there are more similar approaches in the client jar. I am currently still talking to darran lofthouse in this matter. 
Rob now has a hack that solves the problem. IMHO this should be fine for m5, but we should elaborate on a real solution later.
                
      was (Author: adietish):
    the above changes did not solve the problem so I had to revert to the version before my changes. 
I tracked the client code down to several component and I'm pretty sure that the correct jars are loaded, so IMHO this is not an osgi issue per se. I then started tracking the authentication issues that you get if you start an as71 (after having started an as7) and found the following code in the as71 client:

ManagementClientChannelStrategy#Establishing#getChannel():

{code}
 public ManagementChannel getChannel() throws IOException {
            AccessController.doPrivileged(new PrivilegedAction<Object>() {
                public Object run() {
                    if (Security.getProvider(saslProvider.getName()) == null) {
                        Security.insertProviderAt(saslProvider, 1);
                    }
                    return null;
                }
            });
{code}

This sets the provider for the whole JVM, no chance for plugin-separation. 
I then to set the sasl providers in each as7 management bundle, which should solve the auth issue, but I still have the issue. So I suspect that there are more similar approaches in the client jar. I am currently still talking to darran lofthouse in this matter. 
Rob now has a hack that solves the problem. IMHO this should be fine for m5, but we should elaborate on a real solution later.
                  
> Clone as7 management plugin for as7.1
> -------------------------------------
>
>                 Key: JBIDE-10253
>                 URL: https://issues.jboss.org/browse/JBIDE-10253
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.M5
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira