Hi JB,

Thank you for taking an interest.

I think that my bean's communications path is: (I'm still new at this!)

bean -> eip -> smx:jms -> external application.

The external application receives the reply.

The code used is shown below. Note getService() returns the name of my
eip:content-based-router.

<-- java code -->
ClientFactory factory = (ClientFactory)(new
InitialContext().lookup(ClientFactory.DEFAULT_JNDI_NAME));
ServiceMixClient client = factory.createClient();
                        
InOnly outExch = client.createInOnlyExchange();
NormalizedMessage outMsg = outExch.getInMessage();
outMsg.setProperty("org.apache.servicemix.jms.destination", "some.target");
outMsg.setContent(new StringSource("Hello World"));
                        
outExch.setService(getService());
if(client.sendSync(outExch))
        exchange.setError(new MessagingException("Failed to forward to
configuration manager"));
<-- java code - end ->

Stuart
 

-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]] 
Sent: 30 April 2009 15:25
To: [email protected]
Subject: Re: Have I got a coding/config problem?

Hi Stuart,

Is your servicemix-bean SU communite with a servicemix-jms component or
directly with AMQ ?

Regards
JB

Stuart Roe wrote:
> Hi all,
>  
> I'm new to SMX3 and have been looking at the verious queues created in 
> AMQ and I've noticed that when my servicemix-bean element is 
> communicating a new queue called 
> 'org.apache.servicemix.jca.ID_<ip>-120f7212883-0_<n>' where <ip> is my 
> machine's ip and <n> is  sequential increasing number. There is a 
> similarly named 'org.apache.servicemix.jms.ID:<ip>-120f7212883-0_<n>'
queue also being created.
>  
> Is this correct or am I doing something wrong, like not calling 
> close() against some resource?
>  
> Stuart.
> 

Reply via email to