You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2007/10/02 20:25:50 UTC

[jira] Assigned: (CXF-1060) Code depends on spring bean initialization order

     [ https://issues.apache.org/jira/browse/CXF-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp reassigned CXF-1060:
--------------------------------

    Assignee: Daniel Kulp

> Code depends on spring bean initialization order
> ------------------------------------------------
>
>                 Key: CXF-1060
>                 URL: https://issues.apache.org/jira/browse/CXF-1060
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding, Transports
>         Environment: sun jdk 1.5.0_11, windows xp prof., cxf-20070729
>            Reporter: Gyorgy Orban
>            Assignee: Daniel Kulp
>
> The following if statement in org.apache.cxf.binding.soap.SoapTransportFactory depends on the order of bean initialization in spring:
>     @PostConstruct
>     void registerWithBindingManager() {
>          ...
>         DestinationFactoryManager dfm = bus.getExtension(DestinationFactoryManager.class);
>         if (null != dfm) {
>             for (String ns : activationNamespaces) {
>                 dfm.registerDestinationFactory(ns, this);
>             }
>         }
>     }
> Basically it makes the assumption that if dfm is initialized then activationNamespaces is also initialized.
> When we use the spring jars bundled with cxf-20070729 everything works fine. If we switch to another version of spring (2.0.5), it throws NullPointerException. This is because dfm is initialized before activationNamespaces.

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