cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-730) Support Lazy-Init'ed Bus Extensions
Date Sat, 03 Oct 2009 17:09:23 GMT

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

Daniel Kulp resolved CXF-730.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.3
         Assignee: Daniel Kulp

I've made a bunch of changes in 2.3 to make almost everything in CXF lazy-init=true and not
loaded till needed.

> Support Lazy-Init'ed Bus Extensions
> -----------------------------------
>
>                 Key: CXF-730
>                 URL: https://issues.apache.org/jira/browse/CXF-730
>             Project: CXF
>          Issue Type: Improvement
>          Components: Bus
>            Reporter: Andrea Smyth
>            Assignee: Daniel Kulp
>             Fix For: 2.3
>
>
> A bus extension, when marked as lazy-init, will not be accessible to clients unless the
bean is itself explicitly references elsewhere - which defeats the purpose of the bus extensions
concept by which it should be obtained from the bus, thus hiding the dependency on Spring.
> Making the bean implement BusExtension (from the api module), putting the bean definition
into a cache upon startup, and have the (Spring-based) bus get the bean from the application
context when not in its registry may be a solution ....

-- 
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