Your first request will be difficult to achieve in the current state.
JBI does not define any client api. The only way you can send
a jbi exchange is to use a binding component. Servicemix provides
a remote client api that you can use if you use the jms flow.
The two other things you try should cause no problems.
In both cases, you have to set up a binding component (either jms or soap)
that will route to your MessageExchangeListener component.
Cheers,
Guillaume Nodet
Brian Rook wrote:
I think that the problem was that I thought it was another component
that you 'drop-in' to jboss, but you actually run it from the
servicemix directory with activemq running. I'm trying to develop a
very simple 'drop-in' component to test how servicemix works and its
proving to be a little more difficult than I expected. It took a
couple of days to get a simple ejb/mdb call through just activemq and
understand how it works. For example this is what I'm trying to do
with servicemix(inside the jboss container with activemq):
create an ejb that makes a simple hello world JBI request/response
(InOut) call to a MessageExchangeListener.
create an ejb that makes a simple hello world JMS request/response
call to a MessageExchangeListener.
create an ejb that makes a simple hello world SOAP request/response
call to a MessageExchangeListener.
Are there any examples/tutorials for what I'm trying to do?
Thanks,
Brian
>>> [EMAIL PROTECTED] 12/14/05 3:44 PM >>>
(Funny, I was just playing with this a few minutes ago.) How long did you
wait for the service to come up? It takes a spell, not minutes, but more
seconds than you might expect. Until then, you get either "connection
refused"
on the client side, or the server side complaining that the component
has not
yet initialized.
