I am not sure if the FSProvider coudl provide this kind of processing, however you might use FTP as well as a transport channel. Check the ftp-action in the quickstarts folder included in your jboss-esb-server-4.xx folder.
The second one, based on doc:
<jboss-esb.xml>: contains the service configuration (list ener and actions), as
well as provider configuration.
<deployment.xml>: is optional, but can be used for 2 reasons:
-make this .esb archive depend on other archi ves, to specify classloading
- make the deployment of this .esb archi ve scoped.
<java classes>: your custom action classes in standard package hierarchy.
: additional jar archi ves your actions depend on.
Btw, you just will declare you queues just once depending your esb module and the services running on that.
Thanks for you reply, i will try FTP adaptor.
For deployment.xml and queue-service.xml, i think the only thing i can find is same as what you said. In quickstart examples, for example, we have
* jbm-quene-services and
And contexts within these two files are totally different, e.g.what is "PostOffice" and "DestinationManager"?
Do we have docs specifically describe these files.
Thanks very much.
I have not found any suitable documentation abou that, maybe anybody from the development team could explain it much better.