No, the servlet shouldn't be in WEB-INF/lib as yes, it would interfere. I was thinking about src/lib or src/build...something away from the loaded libraries as it should only be used for building the code.

Don

Martin Cooper wrote:
On Tue, 22 Feb 2005 13:51:07 -0800, Don Brown <[EMAIL PROTECTED]> wrote:

Why not pick the lowest we support (2.3), and provide instructions in
the readme if how to upgrade.  Other versions would only be an issue if
they tried to use newer servlet features in their code, and if so, they
are probably comfortable enough to replace a servlet jar.


I'm not so sure about that. Wouldn't they run into classloader issues
if the 2.3 jar is bundled in the war file, but the container is a 2.4
container?

--
Martin Cooper



Don

Martin Cooper wrote:

On Mon, 21 Feb 2005 22:14:31 -0800, Don Brown <[EMAIL PROTECTED]> wrote:


I was looking at updating the Blank application and had a few questions:

1. Can I get rid of the data source stuff including the jdbc
extensions?  Hasn't data sources been deprecated for quite a while now?

2. Any way we could ship with servlet.jar?  It would be nice if this
could be completely self-contained.


That sounds like a nice idea, but I don't see how it would really work
in practice. The problem is that we'd have to pick one version of the
Servlet API, so it would be broken for everyone who uses a different
version. That's likely a backwards step in getting people up and
running quickly.

--
Martin Cooper




3. Does it need to come with chain-config.xml?  Most people won't need
to customize this.

4. I take it the build is currently broken as the built war seems to
be missing things like WEB-INF/src  Is anyone currently working on
fixing it?  If not, I can give it a go.

5. A minor thing, but I'd also like to make the default "dist"
directory be a relative directory to avoid, hopefully, all external
directory modifications.

Thanks,

Don

---------------------------------------------------------------------
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]


--------------------------------------------------------------------- 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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to