So, has no one else had this problem? Or, is no one using the
components? Should I just be using jms-endpoints?
On Jul 5, 2006, at 3:40 PM, kitplummer wrote:
I've got a service that is sending a message to a JMSSenderComponent.
Unfortunately, the sender service is receiving the message on its
OnMessageListener.
What have I wired up incorrectly? Any thing obvious in this stuff:
<sm:activationSpec componentName="eMAF.TaskStatus.Sender"
service="emaf:eMAF.TaskStatus.Sender">
<sm:component><bean
class="org.apache.servicemix.components.jms.JmsSenderComponent">
<property name="template">
<bean
class="org.springframework.jms.core.JmsTemplate">
<property
name="connectionFactory">
<ref
local="jmsFactory"/>
</property>
<property
name="defaultDestinationName"
value="eMAF.TaskStatus"/>
<property name="pubSubDomain"
value="true"/>
</bean>
</property>
</bean></sm:component>
</sm:activationSpec>
Here's the message setup:
public static void sendMessage(ComponentContext context, String
endpoint,
String content)
throws MessagingException {
if (context != null) {
log.info("Sending Message...");
DeliveryChannel deliveryChannel =
context.getDeliveryChannel();
MessageExchangeFactory factory =
deliveryChannel.createExchangeFactory();
InOnly exchange = factory.createInOnlyExchange();
NormalizedMessage message = exchange.createMessage();
exchange.setInMessage(message);
// This sends the message to a known endpoint
// Without this line the message goes to the service's
defined
// destinationService in the xbean wiring file
QName service = new QName("http://emaf.ap.raytheon.com/";,
endpoint);
exchange.setService(service);
message.setContent(new StringSource(content));
deliveryChannel.send(exchange);
} else {
log.error("NO CONTEXT!!!");
}
}
I don't have anything wiring the eMAF.TaskStatus topic back to the
service,
so I'm stumped.
TIA,
Kit
--
View this message in context: http://www.nabble.com/Sender-is-Rxing-
Own-Message...-tf1897580.html#a5190909
Sent from the ServiceMix - User forum at Nabble.com.
