you make a valid point.  I had just copied that interface from the
jakarta-taglibs project.  It is an interface - not a class.  I'll admit, I
don't know too much about licensing.  I was just assuming that it's legal to
create a physical manifestion of interfaces defined by Sun.  The actual
implementation is done in an anonymous inner class.  How else would we stick to
the standards defined by jstl?  Isn't this the whole point of the JCP?  The
community defines the spec, which can be implemented by anyone.  As a side
note, the servletapi in the maven repository does not contain this interface. 
Essentially the only difference in not having this dependency vs. having it is
the namespace.  The dependency doesn't change, it's just whether the name is:
javax.servlet.jsp.jstl.core.LoopTagStatus
or
org.apache.commons.jelly.whatever.LoopTagStatus

-Ben

Quoting Paul Libbrecht <[EMAIL PROTECTED]>:

> As Hans said,
>
> We don't want to introduce such a dependency in the core jelly.
> It used to be a problem because it wasn't maven distributable... now it
> looks like it actually is maven distributed (under the project-name
> servletapi).
> I'd like to have a kind of better confirmation than just seeing it in
> the maven repository before comitting to such a jump. (the licenses in
> the maven repo are... Apache license! I doubt this is from Sun).
>
> Do note that, if you want to use it from jexl, it is probably
> irrelevant wether it is actually of the given class or just implements
> all the methods with same signature. So, before the immensely long time
> someone of Sun actually claims the Apache license is correct, it might
> be faster to just write an class with the same methods...
>
> paul
>
>
> Le 4 oct. 04, à 13:08, Ben Anderson a écrit :
>
> > no, it belongs in javax.servlet.
> > http://java.sun.com/products/jsp/jstl/1.1/docs/api/javax/servlet/jsp/
> > jstl/core/LoopTagSupport.html
>
>
> ---------------------------------------------------------------------
> 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