There is indeed quite a bit of static configuration in JXPath: First of all, JXPath as a whole is built according to the SPI pattern. It consists of a bunch of abstract APIs and a concrete implementation replaceable at runtime. That binding is done globally (at the ClassLoader level).
Then there are NodeFactories, DynamicPropertyHandlers and some other stuff. Thus, my recommendation would be to put it on the apps' classpaths. This will also insultate those apps from future changes in JXPath. - Dmitri ----- Original Message ----- From: "Will Jaynes" <[EMAIL PROTECTED]> To: "Jakarta Commons Users List" <[EMAIL PROTECTED]> Sent: Sunday, December 21, 2003 2:05 PM Subject: [jxpath] jar suitable for app server level? > I'd like to start using JXPath in most of my web apps. I wonder if the > jxpath jar is suitable for deployment at the server level rather than > having to include it within each web app. Is there anything (singletons, > classloader issues) that might be problamatical putting the jar at the > server level? > > Will > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
