On 9/12/06, pradeep <[EMAIL PROTECTED]> wrote:


Thank you.I got it working now. Thanks for your patience in answering my
queries.
More queries :)

1.Why do we need to specify both   destinationService="test:publisher" and
destinationEndpoint="endpoint". What is the difference between the two
attributes.


A JBI endpoint is uniquely identified by its service name + endpoint name.
In this specific case, you need both attribute to target the right endpoint
because 2 endpoints are activated with the same service name. So
the NMR chooses one.

2.
I am seeing that my publisher has gone to infinite loop. It doesn't stop
sending message. Here is my quatz setting.


First you need to correctly implement the MEP in your component.
You need to send back a done status to the consumer (quartz) and
be prepared to receive a done status from the producer (the publisher).
Currently, each time you receive the done status from the publisher,
you send another message, so it loops forever.

<sm:activationSpec destinationService="test:MyComponent"
destinationEndpoint="sampleendpoint">
        <sm:component>
          <bean
class="org.apache.servicemix.components.quartz.QuartzComponent">
            <property name="triggers">
              <map>
                <entry>
                  <key>
                    <bean class="org.quartz.SimpleTrigger">
                      <property name="repeatInterval" value="200000"/>
                      <property name="repeatCount" value="1"/>
                    </bean>
                  </key>
                    <bean class="org.quartz.JobDetail">
                      <property name="name" value="My Evaluation Job"/>
                      <property name="group" value="ServiceMix"/>
                    </bean>
                </entry>
              </map>
            </property>
          </bean>
        </sm:component>


Pradeep



gnodet wrote:
>
> Did you try adding the destinationEndpoint attribute as I advised ?
>
> <sm:activationSpec
>     service="test:MyComponent"
>     endpoint="sampleendpoint"
>     destinationService="test:publisher"
>     destinationEndpoint="endpoint">
>   <sm:component>
>     <bean class="MyComponent"/>
>   </sm:component>
> </sm:activationSpec>
>
>
>
> On 9/12/06, pradeep <[EMAIL PROTECTED]> wrote:
>>
>>
>> Thanks.I passed "null" to createinonlyexchange but I continue to get
the
>> error
>> error: javax.xml.bind.UnmarshalException: unexpected element (uri:"",
>> local:"my-msg")
>>
>> Pradeep
>>
>>
>> gnodet wrote:
>> >
>> > You need to specify the destinationEndpoint="endpoint"
>> > on your component activation spec and pass null in your
>> > component when calling
>> >     createInOnlyExchange(null, null, null);
>> >
>> > The reason is that the publisher activates two jbi endpoints.
>> > One is named "subscription" and is used by the WSN broker
>> > to send notifications when demand based publishing is used.
>> > Unfortunately, you hit the wrong endpoint.
>> >
>> > On 9/12/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> Thanks.I commented jmsFlow. I just sedaflow is the default.
>> >>
>> >> I see this in the log file (not the console) and onmessageExchange
is
>> >> seeing
>> >> recrusive behavior.why is this happening?
>> >>
>> >> 17:06:48,337 | DEBUG | Thread-14  | DeliveryChannelImpl      |
>> >> .messaging.DeliveryChannelImpl  343 | Sent: MessageExchange[
>> >>   id: ID:hostname-1035-1158060946103-10:243
>> >>   status: Error
>> >>   role: provider
>> >>   service: {http://servicemix.org/test}publisher
>> >>   endpoint: subscription
>> >>   in: <?xml version="1.0" encoding="UTF-8"?><my-msg>test</my-msg>
>> >>   error: javax.xml.bind.UnmarshalException: unexpected element
>> (uri:"",
>> >> local:"my-msg"). Expected elements are
>> >> <{http://www.w3.org/2005/08/addressing}Action>,<{
>> >> http://docs.oasis-open.org/wsrf/bf-2}BaseFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ConsumerReference>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}CreatePullPoint>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}CreatePullPointResponse>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}CreationTime>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}CurrentTime>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}DestroyPullPoint>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}DestroyPullPointResponse>,<{
>> >> http://www.w3.org/2005/08/addressing}EndpointReference>,<{
>> >> http://www.w3.org/2005/08/addressing}FaultTo>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Filter>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}FixedTopicSet>,<{
>> >> http://www.w3.org/2005/08/addressing}From>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}GetCurrentMessage>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}GetCurrentMessageResponse>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}GetMessages>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}GetMessagesResponse>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}InvalidFilterFault>,<{
>> >>
>> http://docs.oasis-open.org/wsn/b-2}InvalidMessageContentExpressionFault
>> >> >,<{
>> >>
>>
http://docs.oasis-open.org/wsn/b-2}InvalidProducerPropertiesExpressionFault
>> >> >,<{http://docs.oasis-open.org/wsn/b-2}InvalidTopicExpressionFault
>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}MessageContent>,<{
>> >> http://www.w3.org/2005/08/addressing}MessageID>,<{
>> >> http://www.w3.org/2005/08/addressing}Metadata>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}MultipleTopicsSpecifiedFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}NoCurrentMessageOnTopicFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}NotificationMessage>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}NotificationProducerRP>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Notify>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}NotifyMessageNotSupportedFault
>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}PauseFailedFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}PauseSubscription>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}PauseSubscriptionResponse>,<{
>> >> http://www.w3.org/2005/08/addressing}ProblemAction>,<{
>> >> http://www.w3.org/2005/08/addressing}ProblemHeader>,<{
>> >> http://www.w3.org/2005/08/addressing}ProblemHeaderQName>,<{
>> >> http://www.w3.org/2005/08/addressing}ProblemIRI>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ProducerProperties>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ProducerReference>,<{
>> >> http://www.w3.org/2005/08/addressing}RelatesTo>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Renew>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}RenewResponse>,<{
>> >> http://www.w3.org/2005/08/addressing}ReplyTo>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ResumeFailedFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ResumeSubscription>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}ResumeSubscriptionResponse>,<{
>> >> http://www.w3.org/2005/08/addressing}RetryAfter>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Subscribe>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}SubscribeCreationFailedFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}SubscribeResponse>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}SubscriptionManagerRP>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}SubscriptionPolicy>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}SubscriptionReference>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}TerminationTime>,<{
>> >> http://www.w3.org/2005/08/addressing}To>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Topic>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}TopicExpression>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}TopicExpressionDialect>,<{
>> >>
http://docs.oasis-open.org/wsn/b-2}TopicExpressionDialectUnknownFault
>> >,<{
>> >> http://docs.oasis-open.org/wsn/t-1}TopicNamespace>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}TopicNotSupportedFault>,<{
>> >> http://docs.oasis-open.org/wsn/t-1}TopicSet>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}UnableToCreatePullPointFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}UnableToDestroyPullPointFault>,<{
>> >>
>> http://docs.oasis-open.org/wsn/b-2}UnableToDestroySubscriptionFault>,<{
>> >>
>>
http://docs.oasis-open.org/wsn/b-2}UnacceptableInitialTerminationTimeFault
>> >>
>> >,<{http://docs.oasis-open.org/wsn/b-2}UnacceptableTerminationTimeFault
>> >> >,<{
http://docs.oasis-open.org/wsn/b-2}UnrecognizedPolicyRequestFault
>> >,<{
>> >> http://docs.oasis-open.org/wsn/b-2}Unsubscribe>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}UnsubscribeResponse>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}UnsupportedPolicyRequestFault>,<{
>> >> http://docs.oasis-open.org/wsn/b-2}UseRaw>
>> >> ]
>> >>
>> >>
>> >> Pradeep
>> >>
>> >> gnodet wrote:
>> >> >
>> >> > Btw, this exception is due to the fact that the jms flow
>> >> > does not have the exception is try to unmarshal in the classpath.
>> >> > I think the cause of this exception should be logged
>> >> > somewhere before.
>> >> > You could first try without the jms flow.
>> >> >
>> >> > On 9/12/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >>
>> >> >> Here are the files
>> >> >> http://www.nabble.com/user-files/235953/MyComponent.java
>> >> MyComponent.java
>> >> >> http://www.nabble.com/user-files/235954/servicemix_test.xml
>> >> >> servicemix_test.xml
>> >> >>
>> >> >> The exception in the  the console)
>> >> >> ERROR - JMSFlow                        - Caught an exception
>> unpacking
>> >> >> JMS
>> >> >> Message:
>> >> >> avax.jms.JMSException: Failed to build body from bytes. Reason:
>> >> >> java.io.IOException: javax.xml.bind.UnmarshalException
>> >> >>        at
>> >> >> org.apache.activemq.util.JMSExceptionSupport.create(
>> >> >> JMSExceptionSupport.java:32)
>> >> >>        at
>> >> >> org.apache.activemq.command.ActiveMQObjectMessage.getObject(
>> >> >> ActiveMQObjectMessage.java:172)
>> >> >>        at
>> >> >> org.apache.servicemix.jbi.nmr.flow.jms.JMSFlow.onMessage(
>> JMSFlow.java
>> >> :517)
>> >> >>        at
>> >> >> org.apache.activemq.ActiveMQMessageConsumer.dispatch(
>> >> >> ActiveMQMessageConsumer.java:795)
>> >> >>        at
>> >> >> org.apache.activemq.ActiveMQSessionExecutor.dispatch(
>> >> >> ActiveMQSessionExecutor.java:96)
>> >> >>        at
>> >> >> org.apache.activemq.ActiveMQSessionExecutor.iterate(
>> >> >> ActiveMQSessionExecutor.java:149)
>> >> >>        at
>> >> >> org.apache.activemq.thread.PooledTaskRunner.runTask(
>> >> PooledTaskRunner.java
>> >> >> :110)
>> >> >>        at
>> >> >> org.apache.activemq.thread.PooledTaskRunner.access$100(
>> >> >> PooledTaskRunner.java:25)
>> >> >>        at
>> >> >>
>> >>
>> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java
>> >> >> :43)
>> >> >>        at
>> >> >>
>> >> >>
>> >>
>>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
>> >> >> (ThreadPoolExecutor.java:650)
>> >> >>
>> >> >>        at
>> >> >>
>> >> >>
>> >>
>>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
>> >> >> (ThreadPoolExecutor.java:675)
>> >> >>        at java.lang.Thread.run(Thread.java:595)
>> >> >> aused by: java.io.IOException: javax.xml.bind.UnmarshalException
>> >> >>        at
>> >> >> org.apache.activemq.command.ActiveMQObjectMessage.getObject(
>> >> >> ActiveMQObjectMessage.java:168)
>> >> >>        ... 10 more
>> >> >> Let me if you need more info.
>> >> >>
>> >> >> Pradeep
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> gnodet wrote:
>> >> >> >
>> >> >> > Please post the xml configuration, your component code, and the
>> full
>> >> >> > exception.
>> >> >> >
>> >> >> > On 9/12/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >> >> >>
>> >> >> >>
>> >> >> >> Can someone help me?
>> >> >> >> thanks
>> >> >> >> Pradeep
>> >> >> >>
>> >> >> >> pradeep wrote:
>> >> >> >> >
>> >> >> >> > Thanks again. I am actually trying to publish to the
>> >> Proxycomponent
>> >> >> and
>> >> >> >> > not directly to the broker.
>> >> >> >> > 1. Quartz calls my component
>> >> >> >> > 2.my component calls proxy
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >  <sm:activationSpec service="test:publisher"
>> endpoint="endpoint">
>> >> >> >> >         <sm:component>
>> >> >> >> >           <bean
>> >> >> >> > class="org.apache.servicemix.wsn.spring.PublisherComponent">
>> >> >> >> >           <property name="topic" value="myTopic" />
>> >> >> >> >           </bean>
>> >> >> >> >         </sm:component>
>> >> >> >> >       </sm:activationSpec>
>> >> >> >> >
>> >> >> >> >             <sm:activationSpec service="test:MyComponent"
>> >> >> >> > endpoint="sampleendpoint"
destinationService="test:publisher"
>> >> >> >> >             >
>> >> >> >> >               <sm:component>
>> >> >> >> >                 <bean class="MyComponent">
>> >> >> >> >
>> >> >> >> >                 </bean>
>> >> >> >> >               </sm:component>
>> >> >> >> >       </sm:activationSpec>
>> >> >> >> >
>> >> >> >> >       <sm:activationSpec
destinationService="test:MyComponent"
>> >> >> >> > destinationEndpoint="sampleendpoint">
>> >> >> >> >         <sm:component>
>> >> >> >> >           <bean
>> >> >> >> > class="
org.apache.servicemix.components.quartz.QuartzComponent
>> ">
>> >> >> >> >             <property name="triggers">
>> >> >> >> >               <map>
>> >> >> >> >                 <entry>
>> >> >> >> >                   <key>
>> >> >> >> >                     <bean class="org.quartz.SimpleTrigger">
>> >> >> >> >                       <property name="repeatInterval"
>> >> value="2000"/>
>> >> >> >> >                       <property name="repeatCount"
>> value="20"/>
>> >> >> >> >                     </bean>
>> >> >> >> >                   </key>
>> >> >> >> >                     <bean class="org.quartz.JobDetail">
>> >> >> >> >                       <property name="name" value="My
>> Evaluation
>> >> >> Job"/>
>> >> >> >> >                       <property name="group"
>> value="ServiceMix"/>
>> >> >> >> >                     </bean>
>> >> >> >> >                 </entry>
>> >> >> >> >               </map>
>> >> >> >> >             </property>
>> >> >> >> >           </bean>
>> >> >> >> >         </sm:component>
>> >> >> >> >       </sm:activationSpec>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > gnodet wrote:
>> >> >> >> >>
>> >> >> >> >> If you try to publish directly to the broker
>> >> >> >> >> without the PublisherProxy, you  need to
>> >> >> >> >> send a valid ws-notification request to the broker ...
>> >> >> >> >> See [1] for some examples
>> >> >> >> >>
>> >> >> >> >> [1]
>> >> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>>
http://servicemix.goopen.org/sm30ug/servicemix-wsn2005.html#servicemix-wsn2005-Notify
>> >> >> >> >>
>> >> >> >> >> On 9/11/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> I am seeing this error in the log file
>> >> >> >> >>>   in: <?xml version="1.0" encoding="UTF-8"?><test-msg
>> >> >> xmlns="">Hey!
>> >> >> >> This
>> >> >> >> >>> is
>> >> >> >> >>> my ws-notification message</test-msg>
>> >> >> >> >>>   error: javax.xml.bind.UnmarshalException: unexpected
>> element
>> >> >> >> (uri:"",
>> >> >> >> >>> local:"test-msg"). Expected elements are
>> >> >> >> >>> <{http://www.w3.org/2005/08/addressing}Action>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsrf/bf-2}BaseFault>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}ConsumerReference>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}CreatePullPoint>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}CreatePullPointResponse
>> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}CreationTime>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}CurrentTime>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}DestroyPullPoint>,<{
>> >> >> >> >>>
http://docs.oasis-open.org/wsn/b-2}DestroyPullPointResponse
>> >,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}EndpointReference>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}FaultTo>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Filter>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}FixedTopicSet>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}From>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}GetCurrentMessage>,<{
>> >> >> >> >>>
>> >> http://docs.oasis-open.org/wsn/b-2}GetCurrentMessageResponse>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}GetMessages>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}GetMessagesResponse>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}InvalidFilterFault>,<{
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>> http://docs.oasis-open.org/wsn/b-2}InvalidMessageContentExpressionFault
>> >> >> >> >>> >,<{
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://docs.oasis-open.org/wsn/b-2}InvalidProducerPropertiesExpressionFault
>> >> >> >> >>>
>> >> >> >> >,<{
>> http://docs.oasis-open.org/wsn/b-2}InvalidTopicExpressionFault
>> >> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}MessageContent>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}MessageID>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}Metadata>,<{
>> >> >> >> >>>
>> >> >> http://docs.oasis-open.org/wsn/b-2}MultipleTopicsSpecifiedFault
>,<{
>> >> >> >> >>>
>> >> >> http://docs.oasis-open.org/wsn/b-2}NoCurrentMessageOnTopicFault
>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}NotificationMessage>,<{
>> >> >> >> >>>
>> http://docs.oasis-open.org/wsn/b-2}NotificationProducerRP>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Notify>,<{
>> >> >> >> >>>
>> >> http://docs.oasis-open.org/wsn/b-2}NotifyMessageNotSupportedFault
>> >> >> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}PauseFailedFault>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}PauseSubscription>,<{
>> >> >> >> >>>
>> >> http://docs.oasis-open.org/wsn/b-2}PauseSubscriptionResponse>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}ProblemAction>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}ProblemHeader>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}ProblemHeaderQName
>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}ProblemIRI>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}ProducerProperties>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}ProducerReference>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}RelatesTo>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Renew>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}RenewResponse>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}ReplyTo>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}ResumeFailedFault>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}ResumeSubscription>,<{
>> >> >> >> >>>
>> http://docs.oasis-open.org/wsn/b-2}ResumeSubscriptionResponse
>> >> >,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}RetryAfter>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Subscribe>,<{
>> >> >> >> >>>
>> >> >> http://docs.oasis-open.org/wsn/b-2}SubscribeCreationFailedFault
>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}SubscribeResponse>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}SubscriptionManagerRP
>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}SubscriptionPolicy>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}SubscriptionReference
>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}TerminationTime>,<{
>> >> >> >> >>> http://www.w3.org/2005/08/addressing}To>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Topic>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}TopicExpression>,<{
>> >> >> >> >>>
>> http://docs.oasis-open.org/wsn/b-2}TopicExpressionDialect>,<{
>> >> >> >> >>>
>> >> >>
>> http://docs.oasis-open.org/wsn/b-2}TopicExpressionDialectUnknownFault
>> >> >> >> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/t-1}TopicNamespace>,<{
>> >> >> >> >>>
>> http://docs.oasis-open.org/wsn/b-2}TopicNotSupportedFault>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/t-1}TopicSet>,<{
>> >> >> >> >>>
>> >> >> http://docs.oasis-open.org/wsn/b-2}UnableToCreatePullPointFault
>,<{
>> >> >> >> >>>
>> >> http://docs.oasis-open.org/wsn/b-2}UnableToDestroyPullPointFault
>> >> >> >,<{
>> >> >> >> >>>
>> >> >>
http://docs.oasis-open.org/wsn/b-2}UnableToDestroySubscriptionFault
>> >> >> >> >,<{
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://docs.oasis-open.org/wsn/b-2}UnacceptableInitialTerminationTimeFault
>> >> >> >> >>> >,<{
>> >> >> >>
>> http://docs.oasis-open.org/wsn/b-2}UnacceptableTerminationTimeFault
>> >> >> >> >>> >,<{
>> >> >> http://docs.oasis-open.org/wsn/b-2}UnrecognizedPolicyRequestFault
>> >> >> >> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}Unsubscribe>,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}UnsubscribeResponse>,<{
>> >> >> >> >>>
>> >> http://docs.oasis-open.org/wsn/b-2}UnsupportedPolicyRequestFault
>> >> >> >,<{
>> >> >> >> >>> http://docs.oasis-open.org/wsn/b-2}UseRaw>
>> >> >> >> >>> ]
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>> gnodet wrote:
>> >> >> >> >>> >
>> >> >> >> >>> > You can also take a look at
>> >> >> >> >>> >
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://svn.apache.org/viewvc/incubator/servicemix/trunk/servicemix-wsn2005/src/test/resources/org/apache/servicemix/wsn/spring.xml?revision=432892
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> > On 9/11/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >> >> >> >>> >>
>> >> >> >> >>> >>
>> >> >> >> >>> >> Forgot to mention that my component is now implementing
>> >> >> >> >>> ComponentSupport
>> >> >> >> >>> >> rather than just Pojosupport.
>> >> >> >> >>> >>
>> >> >> >> >>> >> pradeep wrote:
>> >> >> >> >>> >> >
>> >> >> >> >>> >> > Thanks again.  I tried this but it does not work. I
am
>> not
>> >> >> >> seeing
>> >> >> >> >>> my
>> >> >> >> >>> >> > messages being delivered (printed)to the
>> subscriber.what
>> >> is
>> >> >> >> wrong
>> >> >> >> ?
>> >> >> >> >>> >> >
>> >> >> >> >>> >> > InOut inout  =createInOutExchange(new
>> >> >> >> >>> >> > QName("http://servicemix.org/test","publisher";),
null,
>> >> null);
>> >> >> >> >>> >> >               System.out.println("inside
>> onMessageExchange
>> >> >> ");
>> >> >> >> >>> >> >               NormalizedMessage msg =
>> inout.createMessage
>> >> ();
>> >> >> >> >>> >> >
>> >> >> >> >>> >> >               msg.setContent(new StringSource("<msg
>> >> >> >> xmlns=''>Hey!
>> >> >> >> >>> This
>> >> >> >> >>> >> is my
>> >> >> >> >>> >> > ws-notification message</msg>"));
>> >> >> >> >>> >> >                inout.setInMessage(msg);
>> >> >> >> >>> >> >          send(inout);
>> >> >> >> >>> >> >
>> >> >> >> >>> >> >
>> >> >> >> >>> >> > gnodet wrote:
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >> The in message can only be set by the consumer (in
the
>> >> jbi
>> >> >> >> sense).
>> >> >> >> >>> >> >> Your component receives a jbi exchange, so it acts
as
>> a
>> >> >> >> provider.
>> >> >> >> >>> >> >> You must create a new jbi exchange.
>> >> >> >> >>> >> >> Although you must send a valid xml to the
>> >> >> PublisherComponent.
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >> On 9/11/06, pradeep <[EMAIL PROTECTED]> wrote:
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> Hello,
>> >> >> >> >>> >> >>> I am trying to write a component which sends the
>> message
>> >> to
>> >> >> >> the
>> >> >> >> >>> >> broker
>> >> >> >> >>> >> >>> but
>> >> >> >> >>> >> >>> I
>> >> >> >> >>> >> >>> am getting some exception.
>> >> >> >> >>> >> >>> javax.jbi.messaging.MessagingException: In not
>> supported
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>>
>> >> >>
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(
>> >> >> >> >>> >> >>> MessageExchangeImpl.java:308)
>> >> >> >> >>> >> >>>         at com.hp.MyComponent.onMessageExchange(
>> >> >> >> MyComponent.java
>> >> >> >> >>> :18)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
org.apache.servicemix.components.util.ComponentAdaptorMEListener.onMessageExchange
>> >> >> >> >>> >> >>> (ComponentAdaptorMEListener
>> >> >> >> >>> >> >>> .java:46)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >>
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound
>> >> >> >> >>> >> (
>> >> >> >> >>> >> >>> DeliveryChannelImpl.java:622)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting
>> >> (
>> >> >> >> >>> >> >>> AbstractFlow.java:168)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >> org.apache.servicemix.jbi.nmr.flow.jms.JMSFlow.access$301(
>> >> JMSFlow.java
>> >> >> >> >>> >> :72)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> org.apache.servicemix.jbi.nmr.flow.jms.JMSFlow$5.run(JMSFlow.java
>> >> :534)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
org.apache.geronimo.connector.work.WorkerContext.run(
>> >> >> >> >>> >> WorkerContext.java
>> >> >> >> >>> >> >>> :291)
>> >> >> >> >>> >> >>>         at
>> >> >> >> >>> >> >>>
>> >> >> >> >>> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run
>> >> (Unknown
>> >> >> >> >>> >> >>> Source)
>> >> >> >> >>> >> >>>         at java.lang.Thread.run(Thread.java:595)
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> public class MyComponent extends PojoSupport
>> implements
>> >> >> >> >>> >> >>> MessageExchangeListener {
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>>         public void
onMessageExchange(MessageExchange
>> >> >> >> exchange)
>> >> >> >> >>> >> >>>                         throws MessagingException {
>> >> >> >> >>> >> >>>                 // TODO Auto-generated method stub
>> >> >> >> >>> >> >>>                 System.out.println("inside
>> >> >> onMessageExchange
>> >> >> >> ");
>> >> >> >> >>> >> >>>                 NormalizedMessage msg =
>> >> >> exchange.createMessage
>> >> >> >> ();
>> >> >> >> >>> >> >>>                 exchange.setMessage(msg,"in");
>> >> >> >> >>> >> >>>                 msg.setContent(new
StringSource("Hey!
>> >> This
>> >> >> is
>> >> >> >> my
>> >> >> >> >>> >> >>> ws-notification
>> >> >> >> >>> >> >>> message"));
>> >> >> >> >>> >> >>>                 done(exchange);
>> >> >> >> >>> >> >>>         }
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> }
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> I have also attached the servicemix xml file.
>> >> >> >> >>> (servicemix_test.xml)
>> >> >> >> >>> >> >>>
>> >> http://www.nabble.com/user-files/235943/servicemix_test.xml
>> >> >> >> >>> >> >>> servicemix_test.xml . Please help me.
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> Thanks,
>> >> >> >> >>> >> >>> Pradeep
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> gnodet wrote:
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > On 9/11/06, pradeep <[EMAIL PROTECTED]>
wrote:
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>> >> Thank you verry much. I got it now.
>> >> >> >> >>> >> >>> >> In the example the message passed by quartz
>> component
>> >> is
>> >> >> >> >>> published
>> >> >> >> >>> >> to
>> >> >> >> >>> >> >>> the
>> >> >> >> >>> >> >>> >> topic. So in real life, some component of mine
>> will
>> >> >> publish
>> >> >> >> >>> the
>> >> >> >> >>> >> >>> message
>> >> >> >> >>> >> >>> >> to
>> >> >> >> >>> >> >>> >>
>> >> org.apache.servicemix.wsn.spring.PublisherComponentand
>> >> >> >> gets
>> >> >> >> >>> >> >>> delivered
>> >> >> >> >>> >> >>> to
>> >> >> >> >>> >> >>> >> the subscribers.
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > This is the easiest way, unless you really want
to
>> >> send
>> >> >> >> >>> publishing
>> >> >> >> >>> >> >>> > requests
>> >> >> >> >>> >> >>> > to the broker and deal with ws-notification
>> directly.
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > Is this dynamic way of sending/receiving messages
>> >> >> >> >>> >> >>> >>
>> >> http://servicemix.goopen.org/site/ws-notification.html
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > This is one of the way to do it if you are inside
>> the
>> >> jbi
>> >> >> >> bus.
>> >> >> >> >>> >> >>> > The benefit is that you don't have to deal with
the
>> >> xml
>> >> >> >> syntax
>> >> >> >> >>> at
>> >> >> >> >>> >> all.
>> >> >> >> >>> >> >>> > If you are outside the jbi bus, you need to
create
>> an
>> >> >> http
>> >> >> >> >>> binding
>> >> >> >> >>> >> >>> > for example (as shown in the ws-notification
>> example)
>> >> and
>> >> >> >> send
>> >> >> >> >>> >> >>> > http requests.
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > I will clean up the xml files when I get time.
>> Thanks
>> >> >> >> >>> again,Pradeep
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > Feel free to add / comment the wiki to improve
the
>> >> docs.
>> >> >> >> >>> >> >>> > I will start a more in-depth review of the
>> >> >> WS-Notification
>> >> >> >> >>> >> component
>> >> >> >> >>> >> >>> > itself.
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > gnodet wrote:
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > On 9/11/06, pradeep <[EMAIL PROTECTED]>
>> wrote:
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >> Thanks Guillaume Nodet. It has helped me to
>> >> >> understand
>> >> >> >> the
>> >> >> >> >>> >> example
>> >> >> >> >>> >> >>> >> much
>> >> >> >> >>> >> >>> >> >> better but I have more questions :)
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >> 1. You have mentioned that
"...WS-Notification
>> can
>> >> >> also
>> >> >> >> be
>> >> >> >> >>> used
>> >> >> >> >>> >> in
>> >> >> >> >>> >> >>> a
>> >> >> >> >>> >> >>> >> more
>> >> >> >> >>> >> >>> >> >> dynamic way by sending requests the the
>> >> >> WS-Notification
>> >> >> >> >>> Broker
>> >> >> >> >>> >> to
>> >> >> >> >>> >> >>> >> create
>> >> >> >> >>> >> >>> >> >> publishers and subscribers..".Can you please
>> tell
>> >> me
>> >> >> how
>> >> >> >> to
>> >> >> >> >>> do
>> >> >> >> >>> >> >>> that
>> >> >> >> >>> >> >>> ?
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > The best way would be to read the
>> WS-Notification
>> >> spec
>> >> >> >> and
>> >> >> >> >>> send
>> >> >> >> >>> >> the
>> >> >> >> >>> >> >>> >> > requests
>> >> >> >> >>> >> >>> >> > to the JBI endpoint.  The only particular
thing
>> is
>> >> how
>> >> >> >> the
>> >> >> >> >>> EPR
>> >> >> >> >>> >> for
>> >> >> >> >>> >> >>> >> > publishers
>> >> >> >> >>> >> >>> >> > and subscribers are created.  They will use
the
>> uri
>> >> >> >> >>> mechanism
>> >> >> >> >>> >> used
>> >> >> >> >>> >> >>> in
>> >> >> >> >>> >> >>> >> the
>> >> >> >> >>> >> >>> >> > example:
>> >> >> >> >>> >> >>> >> >    namespace /  service  / endpoint
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > 2. "...instance1 is part of the cluster but
does
>> >> not
>> >> >> have
>> >> >> >> >>> any
>> >> >> >> >>> >> WS-N
>> >> >> >> >>> >> >>> >> >> subscribers or publishers". My question  is -
>> why
>> >> do
>> >> >> we
>> >> >> >> >>> need
>> >> >> >> >>> >> this
>> >> >> >> >>> >> >>> >> >> instance.
>> >> >> >> >>> >> >>> >> >> What is that you are trying to demonstarte ?
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > It's not used and maybe should be removed.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > 3.   Can someone explain me this
>> >> >> >> >>> >> >>> >> >> <bean class="org.quartz.JobDetail">
>> >> >> >> >>> >> >>> >> >>                 <property name="name"
value="My
>> >> >> Example
>> >> >> >> >>> Job"/>
>> >> >> >> >>> >> >>> >> >>                 <property name="group"
>> >> >> >> value="ServiceMix"/>
>> >> >> >> >>> >> >>> >> >>               </bean>
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > These properties are needed for
Quartz.  AFAIK,
>> >> they
>> >> >> >> >>> uniquely
>> >> >> >> >>> >> >>> identify
>> >> >> >> >>> >> >>> >> the
>> >> >> >> >>> >> >>> >> > Job
>> >> >> >> >>> >> >>> >> > but are not used by ServiceMix.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > 4.
>> >> >> org.apache.servicemix.wsn.spring.PublisherComponentis
>> >> >> >> >>> the
>> >> >> >> >>> >> >>> >> publisher.
>> >> >> >> >>> >> >>> >> > How
>> >> >> >> >>> >> >>> >> >> do I write a custom publisher ?
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > You don't really need to, as the
>> PublisherComponent
>> >> is
>> >> >> a
>> >> >> >> >>> >> proxy.  It
>> >> >> >> >>> >> >>> >> > receive
>> >> >> >> >>> >> >>> >> > an
>> >> >> >> >>> >> >>> >> > incoming xml message and publish it on the
>> >> configured
>> >> >> >> >>> topic.  If
>> >> >> >> >>> >> >>> you
>> >> >> >> >>> >> >>> >> > really
>> >> >> >> >>> >> >>> >> > want to write your own, take a look at the
code
>> for
>> >> >> this
>> >> >> >> >>> >> component.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > 5. In the example "wsn-message.xml" is the XML
>> >> message
>> >> >> >> >>> passed.
>> >> >> >> >>> >> Who
>> >> >> >> >>> >> >>> >> reads
>> >> >> >> >>> >> >>> >> >> this XML message.Is it the publisher
component
>> ?
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > No one.  This xml is not used.  The quartz
>> >> component
>> >> >> send
>> >> >> >> a
>> >> >> >> >>> >> message
>> >> >> >> >>> >> >>> to
>> >> >> >> >>> >> >>> >> the
>> >> >> >> >>> >> >>> >> > publisher,
>> >> >> >> >>> >> >>> >> > which is wrapped in a publish request and sent
>> to
>> >> the
>> >> >> >> >>> >> notification
>> >> >> >> >>> >> >>> >> broker.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > 6. In the consumer side what does the
component
>> >> >> >> >>> >> >>> >> >> "org.apache.servicemix.tck.ReceiverComponent"
>> do
>> ?
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > Nothing it seems.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > If you have some time, please clean and
comment
>> the
>> >> >> >> >>> >> configuration
>> >> >> >> >>> >> >>> files
>> >> >> >> >>> >> >>> >> > and
>> >> >> >> >>> >> >>> >> > raise a JIRA
>> >> >> >> >>> >> >>> >> > with your patch.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > On a side note, most of the ws-notification
>> >> component
>> >> >> >> have
>> >> >> >> >>> an
>> >> >> >> >>> >> xbean
>> >> >> >> >>> >> >>> >> syntax
>> >> >> >> >>> >> >>> >> > which is not
>> >> >> >> >>> >> >>> >> > used in this example.
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > Thanks,
>> >> >> >> >>> >> >>> >> >> Pradeep
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >> gnodet wrote:
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >> > Just created this page which should help
you
>> >> >> >> understand
>> >> >> >> >>> the
>> >> >> >> >>> >> >>> basics
>> >> >> >> >>> >> >>> >> of
>> >> >> >> >>> >> >>> >> >> this
>> >> >> >> >>> >> >>> >> >> > example.
>> >> >> >> >>> >> >>> >> >> > This is just a draft and should be enhanced
>> in
>> >> the
>> >> >> >> >>> future.
>> >> >> >> >>> >> >>> >> >> > See
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>>
>> >> >> >> >>>
>> >> http://servicemix.goopen.org/sm30ug/ws-notification-clustered.html
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >> > On 9/10/06, pradeep <[EMAIL PROTECTED]
>
>> >> wrote:
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >> I am experimenting with ws-notifcation
>> example
>> >> >> >> provided
>> >> >> >> >>> with
>> >> >> >> >>> >> >>> the
>> >> >> >> >>> >> >>> >> >> >> download.
>> >> >> >> >>> >> >>> >> >> >> I
>> >> >> >> >>> >> >>> >> >> >> haven't understood how it is works, so
>> >> questions
>> >> >> >> >>> >> >>> >> >> >> 1. What is the purpose of running
>> >> >> >> >>> >> >>> instance1/servicemix1.xml.What
>> >> >> >> >>> >> >>> >> does
>> >> >> >> >>> >> >>> >> >> it
>> >> >> >> >>> >> >>> >> >> >> do
>> >> >> >> >>> >> >>> >> >> >> ?
>> >> >> >> >>> >> >>> >> >> >> 2. what does
>> >> >> >> >>> >> >>>
org.apache.servicemix.wsn.spring.PublisherComponentdo
>> >> >> >> >>> >> >>> >> ?
>> >> >> >> >>> >> >>> >> >> Is
>> >> >> >> >>> >> >>> >> >> >> it
>> >> >> >> >>> >> >>> >> >> >> the publisher? What about
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> org.apache.servicemix.wsn.spring.WSNSpringComponent?
>> >> >> >> >>> >> >>> >> >> >> 3.  sorry if this is stupid but if I need
to
>> >> >> publish
>> >> >> >> >>> >> >>> notification
>> >> >> >> >>> >> >>> >> what
>> >> >> >> >>> >> >>> >> >> >> are
>> >> >> >> >>> >> >>> >> >> >> the steps.
>> >> >> >> >>> >> >>> >> >> >>    a.replace
>> >> >> >> >>> >> >>> >>
>> >> org.apache.servicemix.wsn.spring.PublisherComponentwith
>> >> >> >> >>> >> >>> >> >> my
>> >> >> >> >>> >> >>> >> >> >> own
>> >> >> >> >>> >> >>> >> >> >>      implmentaion? if yes what has to be
>> done
>> >> ?
>> >> >> >> >>> >> >>> >> >> >>   b. Or reuse
>> >> >> >> >>> >> >>> org.apache.servicemix.wsn.spring.PublisherComponent
?
>> >> >> >> >>> >> >>> >> If
>> >> >> >> >>> >> >>> >> >> >> yes,
>> >> >> >> >>> >> >>> >> >> >> how do I write the code to send
>> notifications
>> ?
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >> 4. Same question as 3 for the consumer
>> >> (instance
>> >> 2
>> >> >> in
>> >> >> >> >>> the
>> >> >> >> >>> >> >>> example
>> >> >> >> >>> >> >>> >> ).
>> >> >> >> >>> >> >>> >> >> More
>> >> >> >> >>> >> >>> >> >> >> details required for
>> >> >> >> >>> >> >>> org.apache.servicemix.tck.ReceiverComponent.
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >> If someone could explain me the working of
>> the
>> >> >> >> example
>> >> >> >> >>> wiht
>> >> >> >> >>> >> >>> >> expnantion
>> >> >> >> >>> >> >>> >> >> of
>> >> >> >> >>> >> >>> >> >> >> the servicemix.xml's it would be great. I
>> have
>> >> to
>> >> >> >> admit
>> >> >> >> >>> that
>> >> >> >> >>> >> I
>> >> >> >> >>> >> >>> am
>> >> >> >> >>> >> >>> >> >> toally
>> >> >> >> >>> >> >>> >> >> >> confused. Thanks for your help.
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >> --
>> >> >> >> >>> >> >>> >> >> >> View this message in context:
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6233049
>> >> >> >> >>> >> >>> >> >> >> Sent from the ServiceMix - User forum at
>> >> >> Nabble.com
>> >> >> .
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >>
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >> > --
>> >> >> >> >>> >> >>> >> >> > Cheers,
>> >> >> >> >>> >> >>> >> >> > Guillaume Nodet
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >> >
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >> --
>> >> >> >> >>> >> >>> >> >> View this message in context:
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6241299
>> >> >> >> >>> >> >>> >> >> Sent from the ServiceMix - User forum at
>> >> Nabble.com
>> >> .
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >>
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> > --
>> >> >> >> >>> >> >>> >> > Cheers,
>> >> >> >> >>> >> >>> >> > Guillaume Nodet
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >> >
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>> >> --
>> >> >> >> >>> >> >>> >> View this message in context:
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6242722
>> >> >> >> >>> >> >>> >> Sent from the ServiceMix - User forum at
>> Nabble.com
>> .
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>> >>
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> > --
>> >> >> >> >>> >> >>> > Cheers,
>> >> >> >> >>> >> >>> > Guillaume Nodet
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>> >
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>> --
>> >> >> >> >>> >> >>> View this message in context:
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6243877
>> >> >> >> >>> >> >>> Sent from the ServiceMix - User forum at Nabble.com
.
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>>
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >> --
>> >> >> >> >>> >> >> Cheers,
>> >> >> >> >>> >> >> Guillaume Nodet
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >>
>> >> >> >> >>> >> >
>> >> >> >> >>> >> >
>> >> >> >> >>> >>
>> >> >> >> >>> >> --
>> >> >> >> >>> >> View this message in context:
>> >> >> >> >>> >>
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6244504
>> >> >> >> >>> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >> >>> >>
>> >> >> >> >>> >>
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> > --
>> >> >> >> >>> > Cheers,
>> >> >> >> >>> > Guillaume Nodet
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>>
>> >> >> >> >>> --
>> >> >> >> >>> View this message in context:
>> >> >> >> >>>
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6246370
>> >> >> >> >>> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >> >>>
>> >> >> >> >>>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Cheers,
>> >> >> >> >> Guillaume Nodet
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6262463
>> >> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6264120
>> >> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6264336
>> >> Sent from the ServiceMix - User forum at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>>
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6264632
>> Sent from the ServiceMix - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>

--
View this message in context:
http://www.nabble.com/Confused-about-ws-notification-tf2247458.html#a6265114
Sent from the ServiceMix - User forum at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to