Daniel,
Just curious, have you been able to reproduce the issue using the files
a provided?
Regards,
Gero
Gero Vermaas wrote:
Mmm... that a tough question cause I refactored the examples to Maven
based build, but... I reproduced the issue in the original samples,
see attached the modified/added files. For completeness I also created
a zip file containing both sample projects, this can be downloaded at
http://gerodt.homeip.net/wsn-samples.zip (this file is ~45M, but the
attached files should enable you to reproduce it).
Changed in wsn-consumer:
* Added 'run' target in build.xml
Changed in wsn-producer:
* Added file 'troubleTicketCreateEvent.xml' to root dir of the
wsn-producer project (next to build.xml etc)
* Added copy step to to build.xml include
'troubleTicketCreateEvent.xml' in WEB-INF/classes
* Changed the run() method in
src/org/apache/ws/muse/test/wsrf/MyCapabilityImpl.java to
include the contents of 'troubleTicketCreateEvent.xml' in the
notify message (and added imports)
Build and deploy both wars (I used tomcat) and then do a 'ant run' for
the wsn-consumer.
If you take the original wsn-producer.war file you will see 'INFO:
Received message:... ' messages in the catalina.out file of Tomcat.
The messages are logged by the ConsumerCapabilityImpl class of the
wsn-consumer.
Once you deploy the modified wsn-producer that sends the contents of
the 'troubleTicketCreateEvent.xml' as notification, the 'INFO:
Received message:... ' messages will no longer be logged and the
accept() and process() messages in the consumer are no longer being
invoked.
Thanks for looking into it.
Regards,
Gero
