You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Ivan <xh...@gmail.com> on 2012/07/04 17:40:39 UTC

Bus instance sharing among different ports ?

Hi, from the design side, is it too heavy to create one bus instance for
each web service port ? If does, let's say, I have many serviceBeans, some
of them are required to enable ws-security, and some of them may require to
enable ws-addressing, it is possible to do that with the same bus instance
and does it mean that all those interceptors and policy builder will be
involved in the message processing ?

Thanks.

-- 
Ivan

Re: Bus instance sharing among different ports ?

Posted by Freeman Fang <fr...@gmail.com>.
Hi,

The map between bus and endpoint is very flexible in CXF.
The multiple endpoints can share the same bus, and you can configure  
ws-security/ws-addressing per endpoint basis, so not all endpoints  
with same bus share same interceptors.

Freeman

On 2012-7-4, at 下午11:40, Ivan wrote:

> Hi, from the design side, is it too heavy to create one bus instance  
> for
> each web service port ? If does, let's say, I have many  
> serviceBeans, some
> of them are required to enable ws-security, and some of them may  
> require to
> enable ws-addressing, it is possible to do that with the same bus  
> instance
> and does it mean that all those interceptors and policy builder will  
> be
> involved in the message processing ?
>
> Thanks.
>
> -- 
> Ivan

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042











Re: Bus instance sharing among different ports ?

Posted by Ivan <xh...@gmail.com>.
Thanks for the idea of Endpoints. I knew that CXF supports ws-* discovery
in OSGi environment with blueprint or bundle listener. If I installs those
feature bundles, think that those features will be automatically added into
the default bus instance. Does it mean that, if I would like to configure
those things on the endpoint side, I may need to disable those kind of
discovery mechanism, or all those interceptors will be added in the
invocation chain ?

2012/7/5 Willem Jiang <wi...@gmail.com>

> Hi,
>
> You may consider to configure the feature on endpoints and then share the
> same bus across these endpoints.
>
>
> On 7/4/12 11:40 PM, Ivan wrote:
>
>> Hi, from the design side, is it too heavy to create one bus instance for
>> each web service port ? If does, let's say, I have many serviceBeans, some
>> of them are required to enable ws-security, and some of them may require
>> to
>> enable ws-addressing, it is possible to do that with the same bus instance
>> and does it mean that all those interceptors and policy builder will be
>> involved in the message processing ?
>>
>> Thanks.
>>
>>
>
> --
> Willem
> ------------------------------**----
> FuseSource
> Web: http://www.fusesource.com
> Blog:    http://willemjiang.blogspot.**com<http://willemjiang.blogspot.com>(English)
>          http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
>
>


-- 
Ivan

Re: Bus instance sharing among different ports ?

Posted by Willem Jiang <wi...@gmail.com>.
Hi,

You may consider to configure the feature on endpoints and then share 
the same bus across these endpoints.

On 7/4/12 11:40 PM, Ivan wrote:
> Hi, from the design side, is it too heavy to create one bus instance for
> each web service port ? If does, let's say, I have many serviceBeans, some
> of them are required to enable ws-security, and some of them may require to
> enable ws-addressing, it is possible to do that with the same bus instance
> and does it mean that all those interceptors and policy builder will be
> involved in the message processing ?
>
> Thanks.
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
          http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang