<div>
Because HttpSession.getSessionCont<wbr />ext() is deprecated.<br />
<br />
Use either application.getRealPath(&quot;/<wbr />&quot;) (for JSPs) or this.getServletContext().g<wbr />etRealPath<wbr />(&quot;/&quot;) for servlets.
</div>


Because HttpSession.getSessionContext() is deprecated.

Use either application.getRealPath("/") (for JSPs) or this.getServletContext().getRealPath("/") for servlets.

<div>
Weblogic will always return null if it's deployed as a WAR as well (according to all the sites I could find via google) :-/<br />
<br />
Apparently this is right according to the spec, and all other app servers are doing it wrong...<br />
<br />
Tim
</div>


Weblogic will always return null if it's deployed as a WAR as well (according to all the sites I could find via google) :-/

Apparently this is right according to the spec, and all other app servers are doing it wrong...

Tim

<div>
<div class="content wysiwyg-content">
Hello,<br />
I have a properties file that I need to access within my web application. &nbsp;I built it on JBuilder using Tomcat 4.1, and I call the following method to derive the path for my properties file...<br />
<br />
session.getServletContext(<wbr />).getRealP<wbr />ath(&quot;/&quot;) + &quot;/properties/myprops.prope<wbr />rties&quot;;<br />
<br />
In any case, it doesn't work when I deploy it to BEA. &nbsp;The method return a NULL. &nbsp;Any clue on how to retreive the application path of my project within BEA. &nbsp;Thanks.<br />
<br />

</div>
</div>


Hello,
I have a properties file that I need to access within my web application.  I built it on JBuilder using Tomcat 4.1, and I call the following method to derive the path for my properties file...

session.getServletContext().getRealPath("/") + "/properties/myprops.properties";

In any case, it doesn't work when I deploy it to BEA.  The method return a NULL.  Any clue on how to retreive the application path of my project within BEA.  Thanks.



BEA getRealPath for properties file

JavaServer Pages (JSP) allow the development of dynamically generated web pages. It uses the Java programming language; JSP pages are translated into servlets at runtime, with each servlet being cached and reused until the JSP is modified. JSP allows Java code to be interleaved with static web markup content, so the resulting page can be compiled and executed on the server to deliver the content.