On 3/17/09 4:32 PM, BJBg wrote:
We are using Felix 1.4.1 under Debian.
To answer Stuart's comments on the protected area, this is not the problem as the getDataFile("/") shall return the root of the bundle's private area which is by default the felix-cache, which is of course, R/W.... zone

To be clear, "/" will not return the root of the bundle's private area, that is not what the spec says. It says "" will return the root of the private area. All paths passed into getDataFile() should be relative.

I will try to test with Felix 1.4.1 too.

-> richard

-- Bruno

Richard S. Hall a écrit :
It works for me under Linux (Fedora 10). Which version of Felix are you using?

-> richard

On 3/17/09 2:44 PM, BJBg wrote:
On Linux,
   context.getDataFile("")
returns null as well.

So what is an empty string ?

-- Bruno


Richard S. Hall a écrit :
I should also add, if you want to get the root of your bundle's private area, you should use an empty string per the spec.

-> richard

On 3/17/09 2:34 PM, Richard S. Hall wrote:
On 3/17/09 2:33 PM, Richard S. Hall wrote:
The spec says the path should be relative. Felix returns null for non-relative paths.

On Windows, you probably get different behavior because it looks for File.separatorChar, which is "\\" on Windows, not "/", so "/" is non-relative under Windows.

That should say, "...so "/" is relative under Windows."

-> richard


-> richard

On 3/17/09 2:17 PM, BJBg wrote:
Dear all,

Have you experienced the OSGi command
       context.getDataFile("/")
on Linux with Felix ?

The result seems quite different if you are on Windows or Linux.
- On Windows, the beahaviour is OK.
- On Linux, the method returns "null".

Any idea ?

B.

---------------------------------------------------------------------
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]




---------------------------------------------------------------------
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]


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

Reply via email to