Costin,
If it's the java util collection classes you mean, they were included
from 1.2 and higher weren't they ? For the XML parser crimson was
needed, because it was a 1.3 compliant JDK.
Agreed about them not being in the spec, but things like basic/form auth
are in the spec and they can be removed. Basically the goal was making
it so only core components were required (or anything that was too
difficult to abstract).
(actually it was a guy called Petr Andre who managed to get it running
in the CDC environment, not me but we emailed to discuss getting around
some of the incompatibilities).
Rick
Costin Manolache wrote:
Looks interesting, pretty good footprint.
One correction - none of the features you mention are part of the
Servlet spec actually, at
least AFAIK. My understanding is that JNDI is required only if running
in a J2EE env, and reloading, JSP, SSL, clustering are not required.
How did you get it to run in CDC - don't you need the collection
classes from JDK1.4 ?
Costin
On 4/24/06, Rick Knowles <[EMAIL PROTECTED]> wrote:
(Forgive a shameless plug, but seems it might be relevant to this thread)
I just thought I'd mention Winstone (winstone.sourceforge.net) for this
application too - there have been some people running it successfully on
J2ME CDC 1.0 PP 1.0. It also lets you cut out some parts of the spec you
don't want (eg JSP, JNDI, servlet reloading, SSL, clustering) by
deleting packages from the jarfile. Latest version is v0.8.1, but the
CVS version is stable too.
Thanks,
Rick
Costin Manolache wrote:
Not sure Jetty is fit for embedded use either.
http://khttp.objectweb.org/ - or something similar, capable of running
in CVM or even KVM - could be a viable solution for java on low end
devices.
The real problem is not the size of tomcat itself - but the number of
JVM classes it uses and all the layers and features that need to be
loaded.
What people fail to understand very often is that flash has very
different characteristics from a hard drive, and a 200MHz processor
and 32MB ( or even 400MHz/64MB ) are slightly different from a 2G Hz/
1 G RAM or even a low end - 1GHz/256M :-)
Costin
On 4/23/06, Preston L. Bannister <[EMAIL PROTECTED]> wrote:
How small does it need to be?
If you really need a full HTTP + servlets configuration then it might be
easier to use one of the smaller Jetty configurations (
http://jetty.mortbay.org/ ).
Do you really need servlets (i.e. is this webapp meant to run anywhere)?
Dropping the standard servlet interface will slim things down.
Do you really need the ability to handle heavy traffic? Both Tomcat and
Jetty put extra effort into handling large numbers of connections with high
throughput - which translates to bigger code and data. If you don't need
this ability, then a simpler HTTP server could be a better bet.
--
Servlet v2.4 container in a single 160KB jar file ? Try Winstone
(http://winstone.sourceforge.net/)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Servlet v2.4 container in a single 160KB jar file ? Try Winstone
(http://winstone.sourceforge.net/)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
