That does help, for sure; it's quicker to know which slash to add when I need to add one. I'd love to be sure that the absence of the trailing slash was reliable on Windows, and its presence reliable on *nix, but it seems better to check.

Cheers,
Martin

Robin Rigby wrote:
Martin

Does this help you?

<map:parameter name="system-property:file.separator"
value="{system-property:file.separator}"/>

Look at

blocks/cocoon-core-sample/cocoon-core-main-sample/src/main/resources/COB-INF
/modules/sitemap.xmap

Robin
-----Original Message-----
From: news [mailto:[email protected]] On Behalf Of Martin Holmes
Sent: 20 January 2009 16:49
To: [email protected]
Subject: Re: Determining the host OS

HI Steve,

Do you know how to call this in a sitemap? If I pass this into an XSLT transformation:

<map:parameter name="osName" value="{system-property:os.name}" />

the parameter is empty.

Cheers,
Martin

Stephen Winnall wrote:
There is a module called SystemPropertyModule which appears to do what you want. Just ask it for "os.name".

Steve

On 20 Jan 2009, at 01:09, Martin Holmes wrote:

HI folks,

I'm trying to write a Cocoon-2.1-based application which I want to be completely portable between Tomcats running on Linux, OSX and Windows. I'm having a problem with the use of slashes and backslashes, especially on Windows, where I've found that some relative paths are expressed with backslashes and some with forward slashes, and the {realpath:/} constant returns a value without a trailing slash (whereas on *nix there seems to always be a trailing slash.

I could solve these problems using Flowscript and XSLT if I could determine what host OS Cocoon is running on. However, I can't find a way to do that in the sitemap. There's the HostSelector, which tells me the domain of the host; and there's the BrowserSelector, which tells me the connecting client's browser; but there's no way I can find to discover what operating system Cocoon is running on.

Does anyone know a way to do this, preferably directly in the sitemap?

All help appreciated,
Martin


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to