java programmer wrote:
<snip>
> "webapps" should never have made it
> into the spec. Name three well known
> web sites running in a mass virtual hosted
> environment and deployed as "webapps" with
> a web.xml file to boot ! Hell, name *any*.
</snip>
Hi,
We're the main european hub for bioinformatics research and resources,
the fact that webapps exist and can be packaged is incredibly useful to
us. The management of different projects, produced by different groups
but wishing to reside in the same container, would otherwise be annoying
and tedious, with the webapp concept it's relatively trivial. This is
not running in a virtual hosted environment because we're sitting on top
of the academic backbone here and run our own machines, but the point
still holds; there are definite circumstances where modular applications
are of extremely high value.
Cheers,
Tom
oh, and btw :
> And the kicker is the gratuitous, idiotic
> use of XML for _configuration_. For you to say:
No problem with XML for config, it's just a more specific case of text
config files, and at least the structure is easy to use. Conceptually,
if you're configuring a system that is intrinsically hierarchical,
doesn't it make sense to use a configuration mechanism that shared this
property?
> > servlet.xml cannot have DTD, since people can
> > add their own stuff
> > (classes), instantiate it in server.xml, and name it
> > the way they want,
>
> shows that you have no conceptual idea what xml is
> intended for.
However, this is true :)
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
