Well, I've just looked at the code, and I have absolutely no idea how
such a problem can happen.
The deployment code is in
o.a.s.framework.DeploymentService#deployServiceAssembly
and this error is only thrown when the component returns a null
ServiceUnitManager,
which is not possible for the wsn2005 :-(
I guess you will have to remote debug ...
On 3/22/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote:
Hi,
I'm currently attempting to deploy a "Subscribe" service unit to a
servicemix-wsn2005 component (SM version: 3.1-incubating).
I generate the SU with Maven tooling and then create "... one ... (file)
with an xml extension, ... containing a single WS-Notification request.
The currently supported set of requests include:
* Subscribe"
(see
http://incubator.apache.org/servicemix/servicemix-wsn2005.html#servicemi
x-wsn2005-CreatePullPoint)
However, when I deploy the SU, I get an error*), telling me that
servicemix-wsn2005 does not accept deployments. I also provide the
contents of my xml-file**) and my servicemix.xml component
configuration***). Please note that the same subscription - done via
static, servicemix.xml configuration - is working fine.
Any ideas of what is going wrong? Does the naming of the XML file
containing the Subscribe request matter?
Thanks in advance,
Ciao, Philipp
*)
>>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message";
version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Target component servicemix-wsn2005 for service unit
subscriber-nypdTopic-instance1-su does not accept
deployments</loc-message>
</msg-loc-info>
</task-status-msg>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
</jbi-task-result>
</jbi-task>
<<
**) file nypdTopic-subscription.xml
>>
<?xml version="1.0" encoding="UTF-8"?>
<wsnt:Subscribe
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2";
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
<wsnt:ConsumerReference>
<wsa:Address>
http://t-systems.es/test/inst1Trace/inst1TraceEndpoint
</wsa:Address>
</wsnt:ConsumerReference>
<wsnt:Filter>
<wsnt:TopicExpression
Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Simple";>
myTopic
</wsnt:TopicExpression>
</wsnt:Filter>
</wsnt:Subscribe>
<<
***) servicemix.xml excerpt
>>
...
<!-- WS-Notification component -->
<sm:activationSpec
componentName="servicemix-wsn2005">
<sm:component>
<wsn:component
connectionFactory="#connectionFactory">
<!-- working:
<wsn:requests>
<wsn:subscribe
consumer="http://t-systems.es/test/inst1Trace/inst1TraceEndpoint";
topic="myTopic"
/>
</wsn:requests>
-->
</wsn:component>
</sm:component>
</sm:activationSpec>
...
<<
> -----Mensaje original-----
> De: Rossmanith, Philipp
> Enviado el: jueves, 15 de marzo de 2007 18:38
> Para: [email protected]
> Asunto: how-to implement runtime notifications based on
MessageExchange
> content
> Importancia: Baja
>
>
> Hi,
>
> We have a project where we want to enable on-demand notifications
about
> messages being sent in the bus.
>
>
> The idea is that a subscribing component/subscriber (possibly outside
> the bus) provides a specification/subscription of what he is looking
for
> through a call to a provider service/notification broker; the
> notification broker monitors the messages passing the bus, checks if
> they match the subscription and - given that the subscriber avails of
> the proper permissions - forwards the message to the subscriber.
>
> What would be the best way to implement this pattern?
>
> So far, I am considering 2 alternatives:
> - Changing org.apache.servicemix.jbi.nmr.SubscriptionManager and
> org.apache.servicemix.jbi.framework.SubscriptionRegistry to allow for
> content-based subscriptions
> - Using servicemix-wsn2005; however, I understand that this would
> require the messages to be sent to a defined topic rather than based
on
> message characteristics
>
> Any comments/thoughts on this would be welcome.
>
> Thanks in advance,
> Ciao,
> Philipp
This e-mail may contain confidential or privileged information. Any
unauthorised
copying, use or distribution of this information is strictly prohibited.
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
