I had a similar question, earlier... There is another issue here: you are
right that WAR files are expanded back into a folder - at least by default -
so one could still create a folder within the web app to write to, and which
is visible to browsers... Until one deploys an updated WAR file.
OTM jar files in both common/lib and my apps
/WEB-INF/lib
I am a little suspicious of the stack trace that says its
calling org.apache.naming.factory.TransactionFactory.getObjectInstance
shouldnt it be calling my own?
Thank you!
Moises Lejter
Phone: 608-827-7772
Email: [EMAIL PROTECTED]
] wrote in message
news:[EMAIL PROTECTED]...
Moises Lejter wrote:
Is there a best practice I should be considering here?
How about this for a quick and dirty approach.
Use two contexts. One for your app and one, with webDAV enabled, for
any uploaded content. That way, any application updates
