Add servlet API jar to \"Tapestry Framework\" jar list
Brought to you by:
glongman
Menu
▾
▴
#93 Add servlet API jar to \"Tapestry Framework\" jar list
I know this isn't strictly part of the Tapestry
framework, but it is accessible from every servlet
container. In most cases, you probably don't need to
or shouldn't use the servlet API directly, but in some
cases it's unavoidable, and Tapestry does work with it.
As such, I think adding this jar file in would be a
nice addition.
Logged In: YES
user_id=387057
The problem is..which version on the api jar?
Logged In: YES
user_id=131417
Are the newer ones not backward compatible? As far as from
where, I just assume the Tomcat one, but anything that
implements the appropriate spec would be fine.
Logged In: YES
user_id=387057
There is also a licensing issue with Sun supplied api
implementations that comes into play here. I have no
problems including jars covered by licenses like mpl, cpl, or
apache. I've never seen a Sun license that I want to go
anywhere near. Personal preference.
The solution would be to make it possible to add jar locations
to the framework library that are not included with the plugin.
That way you could add the servlet api once and Spindle
would put it in from then on.
This avoids me having to deal with sun licenses.
Logged In: YES
user_id=131417
That would be fine, but I'm a bit confused. Isn't Tomcat a
reference implementation of the servlet spec that's licensed
under the Apache license?
Logged In: YES
user_id=387057
I don't know what license the Apache folks are using the api
stuff with but the click through one I get from sun starts with:
1. LICENSE TO USE. Sun grants you a
non-exclusive and non-transferable license for the
internal use only of the accompanying software and
documentation and any error corrections provided
by Sun (collectively "Software"), by the number of
users and the class of computer hardware for which
the corresponding fee has been paid.
Note "internal use only".
There are conditions in the license that allow distribution:
2. License to Distribute Software. In addition to
the license granted in Section 1 (Software
Internal Use and Development License Grant) of
these Supplemental Terms, subject to the terms and
conditions of this Agreement, including but not
limited to Section 3 (Java Technology
Restrictions), Sun grants you a non-exclusive,
non-transferable, limited license to reproduce and
distribute the Software in binary form only,
provided that you (i) distribute the Software
complete and unmodified and only bundled as part
of your Programs, (ii) do not distribute
additional software intended to replace any
component(s) of the Software, (iii) do not remove
or alter any proprietary legends or notices
contained in the Software, (iv) only distribute
the Software subject to a license agreement that
protects Sun's interests consistent with the terms
contained in this Agreement, and (v) agree to
defend and indemnify Sun and its licensors from
and against any damages, costs, liabilities,
settlement amounts and/or expenses (including
attorneys' fees) incurred in connection with any
claim, lawsuit or action by any third party that
arises or results from the use or distribution of
any and all Programs and/or Software.
The things that bother me are:
(iv) only distribute the Software subject to a license
agreement that protects Sun's interests consistent with the
terms contained in this Agreement
and
(v) agree to defend and indemnify Sun and its licensors from
and against any damages, costs, liabilities, settlement
amounts and/or expenses (including attorneys' fees) incurred
in connection with any claim, lawsuit or action by any third
party that arises or results from the use or distribution of
any and all Programs and/or Software.
I'm not interested in becoming the "protector" of Sun's rights
or interesting in assuming the liability that is specified if I do
so.
Logged In: YES
user_id=387057
I think the solution here would be to make the Tapestry
library one of those new "User Libraries" (new to Eclipse
3.0) and then users can edit the contents at will.
Of course, time it tight and since User Libraries are new,
and pretty much undocmented, I'm not looking at attempting
this in the short term.
Logged In: YES
user_id=131417
That's actually how I'm using the Servlet API right now (by
adding it as a User library). This was actually pretty easy
to set up. I've been toying with the idea of a feature
request whereby if both JL (and of course, Jetty) and
Spindle are installed, that the jar file get added to the
classpath (thereby circumventing your distribution concern).
Of course, you probably wouldn't want to couple the plugins
like that . . .