Mailing-List: contact jcs-users-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JCS Users List" <jcs-users@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of Aaron.Smuts@travelocity.com
 designates 151.193.220.19 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: cache.ccf resolution via classpath?
Date: Wed, 31 Aug 2005 14:38:27 -0500
Message-ID: 
 <F117F441A30ACD42A50F285320C40E614368E9@sgtulmsp04.Global.ad.sabre.com>
Thread-Topic: cache.ccf resolution via classpath?
Thread-Index: AcWuWO5uZrkZIsmJTqqNH8BGbDA6UwAAFDywAAJ7gUA=
From: "Smuts, Aaron" <Aaron.Smuts@travelocity.com>
To: "JCS Users List" <jcs-users@jakarta.apache.org>

The jisp disk cache is not production ready.  Jisp has all sorts of
issues.  I may drop it altogether rather than trying to get it work. =20


By default the maven build will check the remote repository.  There is s
2.5.1 there.  See:

http://www.ibiblio.org/maven/jisp/jars/

Are you trying to build with ant?  If so, stop and just use maven. =20

Aaron

> -----Original Message-----
> From: Tim Cronin [mailto:tcronin@interwoven.com]
> Sent: Wednesday, August 31, 2005 2:27 PM
> To: JCS Users List
> Subject: RE: cache.ccf resolution via classpath?
>=20
>=20
> Thanks, yes it would be nice if you could configure the exact path.
>=20
> I'm trying to build jcs now.
>=20
> Do you have a copy of jisp 2.5 all that's on the site is 3.0 and
> It's incompatible (lot's of errors).
>=20
>=20
>=20
> -----Original Message-----
> From: Mitch Gorman [mailto:gorman@sportsline.com]
> Sent: Wednesday, August 31, 2005 1:22 PM
> To: JCS Users List
> Subject: Re: cache.ccf resolution via classpath?
>=20
> Tim Cronin wrote:
>=20
> > It's still the same.
> >
> > I got the latest code from the svn repos and CompositeCacheManager
> > Hasn't changed.
> >
> > InputStream is =3D getClass().getResourceAsStream( propFile );
> >
>=20
>     personally, i got a little frustrated with that mechanism.  our
SAs
> are rather anal about enforcing standardized application deployment
> locations, which means i needed to be able to specify on the
commandline
>=20
> to my app exactly where the various config files it needs will be
> residing.
>=20
>     therefore, i kluged CompositeCacheManager.java (1.2.6.5, not that
it
>=20
> matters, probably) like so:
>=20
>=20
>=20
>     public void configure( String propFile )
>     {
>         log.debug( "Creating cache manager from config file: " +
> propFile );
>=20
>         Properties props =3D new Properties();
>=20
>         InputStream is =3D getClass().getResourceAsStream( propFile );
>         try {
>             if (is =3D=3D null)
>                 is =3D new FileInputStream(new File(propFile));
>         } catch (FileNotFoundException fe) {
>             if (log.isErrorEnabled()) {
>                 log.error("Cannot locate properties file " +
propFile);
>             }
>         }
>         try
>         {
>             props.load( is );
> etc., etc., etc.
>=20
>     now, i pass it in to my via commons-cli, call
> JCS.setConfigFilename(), and everything's hunky-dory;  no more
worrying
> about making sure it's in the right location in the classpath.
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org

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