----- Original Message ----- From: "Brian Ewins" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 15, 2003 05:39 Subject: Re: Web services configuration?
> From the J2EE standpoint: > > As JAXRPC is part of the J2EE stack, you're supposed to use JNDI for > configuring a service to know about the environment it is running in; > though there are other kinds of config. Though of course Axis doesnt need j2ee, and even JAXRPC has to worry about client side stuff. > Envrironment-specific configuration is something you shouldn't put in a > web.xml, or anywhere else in your .war[1]. If you do so, you will need > to edit the contents of the .war after deployment, or create multiple > builds. This means that either upgrades will overwrite your config, or > that your test build is not the same as your live build - recipes for > disaster. I've been known to use hostname specific xml config files; the webapp gets its hostname then loads the file. This lets us build one file for multiple (known) installations, and stops us relying on operations to configure things. And it keeps all config data under SCM, which is nice. But it doesnt scale out...you cant change a config on a live cluster without redeploying. Ideally I'd like JNDI with versioning, and somehow the dev team get access to it too. > Runtime config is supposed to be done by JMX, but JMX says nothing about > persistence of configuration (other than 'use EJBs', I suppose), and > tool support for JMX isnt great yet. I'm thinking JMX support might be a nice add-on in axis1.2, but would need help there. We could use it for finding objects like AxisEngine and for internal notifications. >I had kinda hoped the Preferences > API would have helped here but it doesnt fit at all well with web apps. Not the base implementations, no. We'd need an XML file wrapper and a JNDI version.
