You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Jason Pell <ja...@pellcorp.com> on 2011/04/19 09:27:03 UTC
org.apache.cxf.endpoint.ServerRegistry bean not found in CXF 2.4.0
Hi,
I was using the org.apache.cxf.endpoint.ServerRegistry in my code in
2.3.3 and when I upgraded to 2.4.0 I can no longer access this bean.
Is there something specific I have to do now to get access to it?
Does it have a different bean id?
Re: org.apache.cxf.endpoint.ServerRegistry bean not found in CXF 2.4.0
Posted by Jason Pell <ja...@gmail.com>.
I could probably use a factory bean to do that so my existing code does not change I guess.
Thanks for the info
Sent from my iPhone
On Apr 20, 2011, at 2:29, Daniel Kulp <dk...@apache.org> wrote:
> On Tuesday 19 April 2011 3:27:03 AM Jason Pell wrote:
>> Hi,
>>
>> I was using the org.apache.cxf.endpoint.ServerRegistry in my code in
>> 2.3.3 and when I upgraded to 2.4.0 I can no longer access this bean.
>> Is there something specific I have to do now to get access to it?
>> Does it have a different bean id?
>
> With 2.4.0, pretty much the entire Bus is setup without Spring now (for
> performance and memory reasons as well as make it easier to port to other
> environments such as Blueprint). Thus, pretty much all the functionality is
> no longer defined as Spring beans. The only "real" bean left is the Bus
> itself.
>
> For your specific case, what you likely will need to do is inject the Bus
> itself into your code and then call bus.getExtension(ServerRegistry.class).
> That will give you the registry. (btw: that would still work with 2.3.x as
> well).
>
>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
Re: org.apache.cxf.endpoint.ServerRegistry bean not found in CXF 2.4.0
Posted by Daniel Kulp <dk...@apache.org>.
On Tuesday 19 April 2011 3:27:03 AM Jason Pell wrote:
> Hi,
>
> I was using the org.apache.cxf.endpoint.ServerRegistry in my code in
> 2.3.3 and when I upgraded to 2.4.0 I can no longer access this bean.
> Is there something specific I have to do now to get access to it?
> Does it have a different bean id?
With 2.4.0, pretty much the entire Bus is setup without Spring now (for
performance and memory reasons as well as make it easier to port to other
environments such as Blueprint). Thus, pretty much all the functionality is
no longer defined as Spring beans. The only "real" bean left is the Bus
itself.
For your specific case, what you likely will need to do is inject the Bus
itself into your code and then call bus.getExtension(ServerRegistry.class).
That will give you the registry. (btw: that would still work with 2.3.x as
well).
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com