A taf file stores information that is only used by the dev studio and the
server ignores. The Dev Studio shows the <FullName> value in the Details
column, not the <DocumentName>.
The server uses this information from the branch action uses this to locate
the file on execution:
<DocumentName>/taf/loginlib.taf</DocumentName>
The Dev Studio uses this so it can find the file when editing:
<FullName>Macintosh HD\WebSTAR\~ridge\taf\loginlib.taf</FullName>
When you move files from OS 9 to OS X the path in <FullName> will more than
likely be different and the dev studio will prompt you to find it. The
DocumentName should remain the same and if the path is relative in the
calling taf you will not have to change your branch.
It is a good idea to use relative paths in the "Other" field of the "Path to
TAF on Server" to make the files portable across different web servers.
Also make sure that the path uses / chars as directory separators, not the
old : notation or a \ char.
Phil
On 14/2/03 3:24 PM, "Roland Dumas" <[EMAIL PROTECTED]> wrote:
> moving a taf from t2K to witango 5, I have a number of branch actions
> (yes, I know that there are better ways to do things.) The branch
> actions, in the dev studio allow for same path or other path. These
> tafs always show the absolute path of the development machine. That
> makes it impossible to move a taf to a machine with a different file
> structure.
>
> When I look at the xml in a text editor, I can see that what shows in
> the dev studio isn't what's actually operational. Example:
>
> <DocumentName>Server
> HD\Applications\4DWebstar\~ridge\taf\loginlib.tafloginlib.taf</
> DocumentName>
> <FullName>Macintosh HD\WebSTAR\~ridge\taf\loginlib.taf</FullName>
>
> So now I can see that the dev studio isn't showing what the real path
> is, which would count as a bug in my book.
>
> Pending a repair, can someone tell me how to put in a relative path
> that will work? Either same directory or child directory?
>
> I DON'T want an absolute path as it makes applications not
> transportable.
> Do I use forward or backward slashes for OS X?, etc...
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
