This content has been marked as final.
Show 7 replies
-
1. Re: FS-listener IOException
beve May 21, 2008 5:48 AM (in response to ama1)Hi ama1,
try setting the 'is-gateway' to 'true'.
Regards,
Daniel -
2. Re: FS-listener IOException
ama1 May 21, 2008 5:53 AM (in response to ama1)Hi Daniel,
if I set gateway to true I get this deployment error:--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:deployment=jboss-esb.xml State: FAILED Reason: java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service configuration for Service 'myCategory:HOH' doesn't define a Message-Aware Listener (i.e. is-gateway='false'). I Depend On: jboss.esb:deployment=jbossesb.esb
-
3. Re: FS-listener IOException
beve May 21, 2008 5:56 AM (in response to ama1)If you take a look at the helloworld_file_action quickstart you can see an example of this. You should be able to modify it to suite your needs.
Let me know if you have any problems.
Regards,
Daniel -
4. Re: FS-listener IOException
ama1 May 21, 2008 5:59 AM (in response to ama1)Hi Daniel,
yes I had a look into that example. But the only think which looks different is the JMS-Listener. But it looked for me that this listener is just an alternative input channel for the actions?
Or is it mandatory? And if yes what exactly does the JMS do in this example? -
5. Re: FS-listener IOException
tfennelly May 21, 2008 6:10 AM (in response to ama1)"ama1" wrote:
Hi Daniel,
yes I had a look into that example. But the only think which looks different is the JMS-Listener. But it looked for me that this listener is just an alternative input channel for the actions?
Or is it mandatory? And if yes what exactly does the JMS do in this example?
You're right... this is one of the more confusing parts of the ESB configuration. Pre 4.3.GA (just about to be released - available from SVN), every service needed to have at least 1 "message aware listener" configured. Gateways are there to get message payloads onto the bus, but most of them do it via a message aware listener. If you think this is confusing, don't worry... you're not the only one :-)
So it works something like this:message --> [gateways-listener] --> [message-aware-listener] --> [action-pipeline]
So you need the message aware listener to get the message payload from the gateway to the action processing pipeline.
The good news is that v4.3 will make this a lot easier (and more performant) because it adds support for an InVM transport, which means that by default, every service will have an InVM message aware listener. For the user, this means they just need to configure the gateway and it will work - no need to configure the extra JMS message aware listener.
So you need to configure that JMS message aware listener for now, but you can remove it when you move to 4.3. -
6. Re: FS-listener IOException
beve May 21, 2008 6:14 AM (in response to ama1)But it looked for me that this listener is just an alternative input channel for the actions?
The JMS listener is a ESB-aware listener and not a gateway. The file listener in that example is a gateway and used to get messages into an ESB bus. This gateway takes the content in the file and packages it in an ESB Message object. It then passes the Message object to the JMS listener, which a ESB-aware listener.Or is it mandatory?
Well it has been, but there is a new feature in the main trunk for a in-vm transport where you don't need to configure the extra listener. Take a look at invm_transport1 for more details about this.
Regards,
Daniel -
7. Re: FS-listener IOException
ama1 May 21, 2008 6:20 AM (in response to ama1)Okay I understand the concept. I added a jms aware listener and my project works now :-)
Thanks to both of you!