Hi Chris, I have a chicken and egg problem in that i am trying to load a properties file but i need to determine where the property file is living before i can load it.
cheers, tom -----Original Message----- From: Chris Means [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 2 January 2002 14:56 To: [EMAIL PROTECTED] Subject: RE: startup variables Though there is an API for accessing the deployment descriptor, I didn't see anything obvious that allowed access to non-defined elements, and there didn't seem to be any general elements that could be used for start-up information. Though I haven't done it yet, I've just assumed I would use a properties file, and load startup stuff in that way. I'll be tackling that problem within about a week, so let us know how you fare. -Chris > -----Original Message----- > From: Schuring, Tom [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 01, 2002 9:31 PM > To: [EMAIL PROTECTED] > Subject: startup variables > > > hello, > > i am trying to figure out how to pass startup-variables to a > soap-service. > > I know with a web application i can add something like > <context-param> > <param-name>configFileLocation</param-name> > > <param-value>E:\\myapp\\config\\config.xml</param-value></context-param> > > to the web.xml file and in the servlet i can access the variable by > calling application.getInitParameter("configFileLocation") i can then > use that as a bootstrap to load the rest of my configuration settings. > > is there something similar that i can add to (for example) the > deployment descriptor so i will be able to pass in a bit of startup > information ? > > best regards, > tom >
