Bug 778054 (SOA-580) - Additional point to document in "Table 1.22. NotifyFTP" in the ESB Message Action Guide
Summary: Additional point to document in "Table 1.22. NotifyFTP" in the ESB Message Ac...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-580
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation, JBossESB
Version: 4.2 CP02
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2 CP02
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-12 16:25 UTC by Len DiMaggio
Modified: 2014-10-19 23:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-24 19:19:48 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778773 0 high CLOSED Remote directory cannot be relative for (S)FTP(S) gateway 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-580 0 None None None Never

Internal Links: 778773

Description Len DiMaggio 2008-06-12 16:25:27 UTC
Date of First Response: 2008-06-23 09:40:45
project_key: SOA

Reference user forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137274

In "Table 1.22. NotifyFTP" in the ESB Message Action Guide, we should mention that the directory in the FTP URL is absolute, not relative (to the designated user's home dir).

Comment 1 Len DiMaggio 2008-06-16 12:22:42 UTC
Not believed to be a regression relative to GA/CP01 - removed CP02 in 'fixed in' field.  

Comment 2 Joshua Wulf 2008-06-23 13:40:45 UTC
Text now reads: 

"URL - a valid FTP URL of the form ftp://username:password@hostname/path. (Note that this path is absolute, and not relative to the user's home directory)"

Comment 3 Len DiMaggio 2008-06-24 19:19:48 UTC
Verified resolved in the doc for CP02 CR4.

Comment 4 Len DiMaggio 2009-03-13 13:56:01 UTC
Link: Added: This issue related SOA-1228



Note You need to log in before you can comment on or make changes to this bug.