Thanks Guillaume, I have added a Jira regarding this issue.

Guillaume Nodet wrote:

On 3/1/06, Stefan Klinger <[EMAIL PROTECTED]> wrote:
Thanks again Guillaume,

Sorry for being a bit on the slow side, but I am still a bit confused.
Is there no other way than using the client for registering publishers
and creating subscriptions? I would like to have that information
provided to the component during initialisation if possible, and not
having to change client code when  things change.


Yeah, I do follow you.  Please raise a JIRA and hopefully I will
be able to handle that soon.  If you want to give it a try, feel
free to do so.

In what cases would I use the api provided in o.a.s.wsn.jbi ?


If you want to dynamically  create / pause / resume subscriptions,
this should be done in the WS Notification way: sending a message
to the Notification Broker to create a subscription, which you can
then suspend / resume at will.

Cheers,
Guillaume Nodet

Stefan
Guillaume Nodet wrote:

Just try the same thing as for other components:

<sm:activationSpec>
 <sm:component>
   <bean class="org.apache.servicemix.wsn.component.WSNComponent" />
 </sm:component>
</sm:activationSpec>

Note that you will have to use the client api in o.a.s.wsn.client to be
able
to register publisher or create subscriptions.

Cheers,
Guillaume Nodet

On 3/1/06, Stefan Klinger <[EMAIL PROTECTED]> wrote:


Thanks Guillaume,

I don't want to use the broker outside of jbi, I just would like to
install it as a jbi component using xbean within the servicemix.xml.
Should I configure it as a JSR181 component or are there other ways to
do it? Maybe a xml snippet would help...

Thanks again,
Stefan

Guillaume Nodet wrote:



Hi Stefan !

On 3/1/06, Stefan Klinger <[EMAIL PROTECTED]> wrote:




Hello,

I just wondered why there is no Spring WSNComponent in wsn2005, is
there
a particular reason for it as there seems to be a Spring component for
most other components?




I think the main reason is that it has not been done yet ;)
Depending on how you use the WSN component,  you should be able to


configure


it
in the main servicemix.xml without any problems.  You will be limited
to
use


dynamic publisher / subscriptions, as opposed to publisher /


subscriptions


that can be deployed
as service units.

Is it further possible to instantiate the JbiNotificationBroker from




Spring/XBean similar to an ActiveMQ Broker? Or is it supposed to be
installed as a JSR181 component?




I 'm not sure to clearly understand what you want.  Using it ouside the


JBI


environment
may be possible, but it requires some work.  Else, it really relies on


JBI,


so you have
to install it as a JBI component, or configure it in the main
servicemix.xmlfile with an
activationSpec.

Hope that helps,
Guillaume Nodet

Thanks,




Stefan











Reply via email to