geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3368) Axis2ClientConfigurationFactory not always being used in certain platforms
Date Thu, 02 Aug 2007 16:24:52 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517313
] 

Jarek Gawor commented on GERONIMO-3368:
---------------------------------------

I was able to replicate this problem if the web service and the service-ref client was deployed
as two separate modules (but not if both were in one module). 
Fixes committed to trunk: revision 562146 and 2.0 branch: revision 562167


> Axis2ClientConfigurationFactory not always being used in certain platforms
> --------------------------------------------------------------------------
>
>                 Key: GERONIMO-3368
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3368
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0
>            Reporter: Lin Sun
>            Assignee: Jarek Gawor
>             Fix For: 2.0
>
>         Attachments: G-3368.patch
>
>
> On Windows 2003 & Linux, GBean TomcatWebAppContext will be started before Axis2ConfigGBean.
Class org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl will be loaded when the
geronimo kernel starts TomcatWebAppContext, look at the following codes in DescriptionFactoryImpl:
>     private static ClientConfigurationFactory clientConfigFactory = ClientConfigurationFactory.newInstance();
> This will make class DescriptionFactoryImpl can not load Axis2ClientConfigurationFactory
which is registered into MetadataFactoryRegistry in Axis2ConfigGBean. So DescriptionFactoryImpl
still use the old ClientConfigurationFactory, not Axis2ClientConfigurationFactory.
> On Windows XP, GBean TomcatWebAppContext will be started after Axis2ConfigGBean so the
client configurationcontext is working as expected.
> GBean TomcatWebAppContext and Axis2ConfigGBean have the same priority, it's not mandatory
for geronimo kernel to start Axis2ConfigGBean firstly. The patch will set priority of Axis2ConfigGBean
as GBeanInfo.PRIORITY_CLASSLOADER.

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


Mime
View raw message