[esb-issues] [JBoss JIRA] Commented: (JBESB-2812) LocalFileNameMessageComposer FileNotFoundException
[
https://jira.jboss.org/jira/browse/JBESB-2812?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2812:
-------------------------------------
There is definitely confusion here and we will try to address it.
The LocalFileMessageComposer is passing in the name of the working file but, as you point
out, there is a race if the async behaviour is used.
The sync behaviour itself has issues, given that it serialises every request.
The mep cannot be used for this, however, and an explanation of why can be found in the
forum discussion on the HTTP gateway
(http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157057)
LocalFileNameMessageComposer FileNotFoundException
--------------------------------------------------
Key: JBESB-2812
URL: https://jira.jboss.org/jira/browse/JBESB-2812
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.6
Environment: JBossESB 4.6 on JBossAS 4.2.3
Reporter: Andrew Lovell
When trying to use the LocalFileNameMessageComposer I get FileNotFoundException's in
the actions this is because by the time the action is invoked the file is transfered to
the post dir and is no longer where expected.
This behaviour makes for confusing functionality. When one needs to process a huge file
(and CANNOT use smooks) it is not a simple matter of creating an action and using it....
it becomes necessary to create a custom Composer as well as an Action.
It would be preferable if the LocalFileNameMessageComposer either supplied the post
version of the file or delayed the file move to when the actions on the pipeline have
completed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira