Does this only apply the first time the timer is sent ?
And which exception is thrown ?

On 8/11/06, Mouilleron Cedric <[EMAIL PROTECTED]> wrote:

Hi,

I'm trying to use the basic example with sm-jms component (in a
lightweight xml file).

When I'm loading the configuration file, all component are activated but
when the timer (first component) wakes up and sends the message into the
first sm-jms component, it cannot find this jms component so I get an
error.

When I changed the input timer by an input mail poller, the sample works
fine.
When I changed the timer destination service to the screen, its works
fine (message is printed on screen).
When I changed the timer destination service to an eip-splitter, it fails.
When I changed the timer destination service to an standard component
(router for example), it works fine.

The message sent by the timer are received only by ligthweigth component
and not standard one.

So, I think that the timer cannot send a message to a standard component.

Anybody has an idea ?

Cédric MOUILLERON

Bull R&D




--
Cheers,
Guillaume Nodet

Reply via email to