Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE:  RE: [VFS] Problem with creating a file system manager.
Date: Wed, 7 Feb 2007 16:03:26 +1030
Message-ID: 
 <3B6A54D3C6402045903B7563F5DA35C001E91199@ADLEX02.elderslimited.com.au>
In-Reply-To: A<eqacn9$bo$1@sea.gmane.org>
Thread-Topic: RE: [VFS] Problem with creating a file system manager.
Thread-Index: AcdKEaTEKqlyFEPVReW89FHs1PAHJwAZ1MSA
From: "Tony Cooke" <Tony.Cooke@elders.com.au>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>,
        <joerg.schaible@gmx.de>
X-SEF-CA8905A9-DEE5-4C4F-989B-67A01B8FD4A8: 1
X-SEF-Processed: 5_5_0_191__2007_02_07_16_03_16
X-Virus-Checked: Checked by ClamAV on apache.org

Hi again J=F6rg.

Well I tracked down the issue and it's not the security like I thought. =
It's the logging.

I'm using WebSphere Application Server (Portal runs on top of that) and =
there is a conflict with the loggers (the application uses log4j, VFS =
uses Apache logging and WebSphere has its own).

I just need to find out now how to fix this up. There's a bit of =
information on the Apache logging site and I'll need to go through it. =
Looks like a classloader issue

Thanks again for your help.

All the best,
Tony

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of J=F6rg Schaible
> Sent: Wednesday, 7 February 2007 3:39 AM
> To: commons-user@jakarta.apache.org
> Subject: RE: [VFS] Problem with creating a file system manager.
>=20
> Hi Tony,
>=20
> Tony Cooke wrote:
>=20
> >> Hi Tony,
> >
> > Hi J=F6rg.
> >
> >> I rather bet, you have an active SecurityManager that prohibits the
> >> access to the file system ... ;-)
> >
> > I thought this too but I'm unsure as to what access I have to give =
to
> > what. I haven't done too much (actually any) security through the =
JDK so
> I
> > don't know what rights to give over what.
>=20
> Best approach normally is to install a memory-based SecurityManager  =
in a
> standalone app. Then you can write a unit test and add all necessary
> rights
> programmatically unless your app works. See
> =
http://fisheye.codehaus.org/browse/~raw,r=3D1049/xstream/trunk/xstream/sr=
c/t
> est/com/thoughtworks/xstream/testutil/DynamicSecurityManager.java
> and
> =
http://fisheye.codehaus.org/browse/~raw,r=3D1069/xstream/trunk/xstream/sr=
c/t
> est/com/thoughtworks/acceptance/SecurityManagerTest.java
> for reference. The necessary permissions have to be added later to the
> policy file of the server though.
>=20
> >
> >> Try to enable security logs. There was a property mensioned in the =
JDK,
> >> but I don't know by heart.
> >
> > I'm not sure what to do but I'll take a look at this and see what I =
can
> > find. Google is my friend.
> >
> >> - J=F6rg
> >
> > Thanks J=F6rg for your help.
>=20
> You're welcome.
>=20
> - J=F6rg
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org