Hi John,
I did some tests omitting the maven jms transport dependency or the
import in the applicationcontext as I thought this could be the source
of your problem but did not have any luck in reproducing it.
Could you make a zip with a complete project that shows your problem and
provide it for us?
Greetings
Christian
jp4 schrieb:
Christian,
This is exactly what I have been attempting to do, and based on examples and
the documentation it was unclear to me whether or not this should work. I
already have service interfaces that have been generated by wsdl2java as
well as Impl classes. The Impl classes are already configured as spring
beans so I'd prefer to use the existing beans for both jms and http
processing if possible. I uploaded my latest configuration to this thread
earlier, but I still haven't been able to get it to work. I believe the
crux of the problem is that the destination that is being passed to the
JMSConfig is an instance of ServletDestination rather than an actual JMS
Destination. I'm hoping it's a simple config issue. Any suggestions would
be greatly appreciated.
Thanks,
John
--
Christian Schneider
---
http://www.liquid-reality.de
