You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2008/02/12 18:31:08 UTC

[jira] Created: (AXIS2-3507) Writing JAXWS Clients - How to specify the axis2.xml and repository

Writing JAXWS Clients - How to specify the axis2.xml and repository
-------------------------------------------------------------------

                 Key: AXIS2-3507
                 URL: https://issues.apache.org/jira/browse/AXIS2-3507
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
            Reporter: Davanum Srinivas


As of right now, org.apache.axis2.jaxws.ClientConfigurationFactory uses System.getProperty on Constants.AXIS2_REPO_PATH and Constants.AXIS2_CONFIG_PATH to pick up the axis2.xml and the repo. Problem is if say one application needs 2 JAXWS clients with different repo's or different axis2.xml's (say one with security module enabled and one without) then they can't co-exist in the same JVM. (Example 2 WAR's running under tomcat). So we need some mechanism(s) to let the end user specify where to pick up the information from. For example in the servlet case from the servlet config, or from the thread class loader etc or a custom AxisConfigurator

thanks,
dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3507) Writing JAXWS Clients - How to specify the axis2.xml and repository

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568246#action_12568246 ] 

Davanum Srinivas commented on AXIS2-3507:
-----------------------------------------

#1: If the system properties are not specified, fall back to the axis2.xml inside the kernel jar
#2: Allow folks to use existing WarBasedAxis2Configurator, FileSystemConfigurator and URLBasedAxisConfigurator. Basically they can create an instance of either of these as follows:

WarBasedAxisConfigurator configurator = new WarBasedAxisConfigurator();
MetadataFactoryRegistry.put(ClientConfigurationFactory.class, new ClientConfigurationFactory(configurator));

whenever jaxws layer needs a ClientConfigurationFactory, it picks up the one from MetadataFactoryRegistry.

If folks want more control, they can extend ClientConfigurationFactory and specify it in META-INF/services/org.apache.axis2.metadata.registry.MetadataFactoryRegistry (This support already exists!)

That should cover all the bases. 

thanks,
dims

> Writing JAXWS Clients - How to specify the axis2.xml and repository
> -------------------------------------------------------------------
>
>                 Key: AXIS2-3507
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3507
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Davanum Srinivas
>
> As of right now, org.apache.axis2.jaxws.ClientConfigurationFactory uses System.getProperty on Constants.AXIS2_REPO_PATH and Constants.AXIS2_CONFIG_PATH to pick up the axis2.xml and the repo. Problem is if say one application needs 2 JAXWS clients with different repo's or different axis2.xml's (say one with security module enabled and one without) then they can't co-exist in the same JVM. (Example 2 WAR's running under tomcat). So we need some mechanism(s) to let the end user specify where to pick up the information from. For example in the servlet case from the servlet config, or from the thread class loader etc or a custom AxisConfigurator
> thanks,
> dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Resolved: (AXIS2-3507) Writing JAXWS Clients - How to specify the axis2.xml and repository

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

Davanum Srinivas resolved AXIS2-3507.
-------------------------------------

    Resolution: Fixed

Fixed in svn revision 620890

thanks,
dims

> Writing JAXWS Clients - How to specify the axis2.xml and repository
> -------------------------------------------------------------------
>
>                 Key: AXIS2-3507
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3507
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Davanum Srinivas
>
> As of right now, org.apache.axis2.jaxws.ClientConfigurationFactory uses System.getProperty on Constants.AXIS2_REPO_PATH and Constants.AXIS2_CONFIG_PATH to pick up the axis2.xml and the repo. Problem is if say one application needs 2 JAXWS clients with different repo's or different axis2.xml's (say one with security module enabled and one without) then they can't co-exist in the same JVM. (Example 2 WAR's running under tomcat). So we need some mechanism(s) to let the end user specify where to pick up the information from. For example in the servlet case from the servlet config, or from the thread class loader etc or a custom AxisConfigurator
> thanks,
> dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org