-
1. Re: fs-provider
tfennelly May 8, 2008 6:16 PM (in response to lafbarbosa)Hmmm... not sure I understand your question... the ftp-provider is probably more in line with what you are looking for, perhaps?
The fs-providers only work wrt the local file system. -
2. Re: fs-provider
lafbarbosa May 9, 2008 6:27 AM (in response to lafbarbosa)Yeah, that's what I was thinking.
So, in this case, file system providers can be used only in the following scenario? Please, look:
machine A: client
machine B: JBossESB and endpoint where the service (provided by an fs-provider) is deployed.
That's the only one way to use fs-provider, right? -
3. Re: fs-provider
tfennelly May 9, 2008 7:16 AM (in response to lafbarbosa)Depends on what you mean (especially in your use of the word by "machine"). The fs-provider only works on the *local* filesystem. If you mean "machine" to be ESB/AS instances co-located on the same physical box, then yes... your statement seems to be correct. If you mean "machine" the same way as I do (box), then it's not valid - you need some way to bridge the 2 fiesystems (e.g. FTP).
-
4. Re: fs-provider
kconner May 12, 2008 7:04 AM (in response to lafbarbosa)BTW We now support FTPS/SFTP in addition to FTP. The 4.3CR1 release includes these transports.
-
5. Re: fs-provider
lafbarbosa May 14, 2008 2:09 PM (in response to lafbarbosa)Hi Fennelly,
Yes, I would mean to have JBossESB and the application that represents the endpoint (it could be a AS or another server where the service is available through JBossESB) running on the same physical box.
Thanks!
Now, I would like ask something related. I could see that the Programmers Guide shows the following:
Schedule Providers, which supply messages to action processing pipelines based on a schedule driven model i.e. where the underlying message delivery mechanism (e.g. the file system) offers no support for triggering the ESB when messages are available for processing, a scheduler periodically triggers the listener to check for new messages.
So, it mentions that a file system as a mechanism that no offers support for triggering the ESB when messages are available for processing.
In this way, when is recommended to use fs-provider and schedule-provider?
I ask it, but I saw in the same document that fs-provider is a bus provider. So, it should be a mechanism that no offers support for triggering the ESB when messages are available for processing. Isn't it?!
Thanks in advance! -
6. Re: fs-provider
lafbarbosa May 14, 2008 2:40 PM (in response to lafbarbosa)Thanks Kevin for the information about FTPS/SFTP support.
-
7. Re: fs-provider
tfennelly May 14, 2008 5:31 PM (in response to lafbarbosa)"lafbarbosa" wrote:
but I saw in the same document that fs-provider is a bus provider. So, it should be a mechanism that no offers support for triggering the ESB when messages are available for processing. Isn't it?!
The fs-listener is implemented as a ScheduleListener. This wasn't always the case however - used be just a threaded listener. So I think (but will check) that the fs-listner no longer references an fs-bus and so fs-bus and fs-provider are no longer in use and should be removed from the XSD. I'm not totally sure about this however and will check tomorrow. -
8. Re: fs-provider
kconner May 15, 2008 4:47 AM (in response to lafbarbosa)fs-bus and fs-provider are still used, they should not be removed from the schema.
The gateway currently maps onto a scheduled listener but the listener maps onto the message aware listener. -
9. Re: fs-provider
tfennelly May 15, 2008 4:52 AM (in response to lafbarbosa)"Kevin.Conner@jboss.com" wrote:
fs-bus and fs-provider are still used, they should not be removed from the schema.
The gateway currently maps onto a scheduled listener but the listener maps onto the message aware listener.
Sounds like I don't need to check... Kev's checking for me lol -
10. Re: fs-provider
kconner May 15, 2008 4:56 AM (in response to lafbarbosa)I was looking at that code yesterday, coincidentally :)
I thought I would save you some time ;) -
11. Re: fs-provider
tfennelly May 15, 2008 5:02 AM (in response to lafbarbosa)Thanks Kev :-)
So it seems a little inconsistent (from a user perspective at least)... the Fs Message Aware Listener using the fs-provider etc and the Fs Gateway Listener using the schedule provider :-( -
12. Re: fs-provider
kconner May 15, 2008 5:23 AM (in response to lafbarbosa)From a user's perspective it is consistent, nothing has changed. Both are still configured using the same fs-provider/fs-listener combination.
The mapping to the implementation has also remained, the only difference is that the implementation is now a scheduled event listener instead of a threaded, managed lifecycle. -
13. Re: fs-provider
lafbarbosa May 15, 2008 9:23 AM (in response to lafbarbosa)Hi guys,
Thanks for the explanation!
But, could one of you give some example about it? Just a jboss-esb.xml decribed here with comments about gateway and message aware listener?
Thanks in advance! -
14. Re: fs-provider
kconner May 16, 2008 5:24 AM (in response to lafbarbosa)The quickstarts are your friend :)
Check out helloworld_file_action.