Re: Importing existing JSPs etc. into new project

Joe,

my own way of simplifying this is to use:

I have created utility classes that use
ClassLoader.getSystemClassLoader().getResourceAsStream(propertiesFile);

This will then search the classpath for the specified file, in this case a
properties file, allowing me to use the classpath like a library list for
properties files

This make it very easy for me to have different properties files for dev,
uat and live environments, just by changing the properties files on the
classpath

cheers

Colin.W



----- Original Message -----
From: "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, December 18, 2003 6:22 PM
Subject: RE: [WDSCI-L] Importing existing JSPs etc. into new project


> Quick summary:
>
> To move to WDSC, you must become J2EE compliant
>   All document objects go into the "Web Content" folder
>   All classes and jars go under "WEB-INF"
>     All classes go into the folder "classes" under WEB-INF
>     All jar files go into the folder "lib" under WEB-INF
>
> The difficult part is properties files, or anything you open using the
> java.io.File classes and a relative path.  Any file accessed using the
> java.io.File class goes much higher in the hierarchy, under the
> application folder.  You will not be able to include these in your web
> project.
>
> Joe
>
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>