[Wonder-disc] Additional arguments when deploying servlet: ERXProperties not taking care of javax.naming.InitialContext?

[René B. <bo...@sa...>]

Hi,

As stated in 

http://wiki.objectstyle.org/confluence/display/WO/Deployment-Tomcat+Deployment#Deployment-TomcatDeployment-ApplicationSpecificConfiguration

"One way to configure your application specific parameters in a servlet container is to load your config into env-entry-s in your web.xml file"

The down side is, that you can't use  NSProperties.getProperty or EXProperties.stringForKey  to retrieve the value defined in  web.xml  (My target ApplicationServer is JBOSS. It would nice to hear, this is true for other application server... ) 

So, if you don't want to bother, if your application will be deployed the classic way or as a Servlet,  it would be nice if you can use EXProperties.stringForKey regardless if the source of values are the additional parameters or the web.xml file.

As I can't patch NSProperties.getProperty, I would suggest to extend ERXSystem.valueForKey rsp. valueForKeyPath to first look for the value in a javax.naming.InitialContext and if this fails retrieve the value via  NSProperties.getProperty.

Shall I open a ticket in Jiraa or are there better alternatives to consider?

regards,

René Bock
Software Engineering

--
Salient GmbH  -  the interactive advantage
http://www.salient.de				http://www.openforms.de