struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (David M. Karr)
Subject Re: [VOTE] Declare Struts 1.1b3 as Struts 1.1 RC1
Date Sun, 19 Jan 2003 22:44:11 GMT
>>>>> "Ted" == Ted Husted <> writes:

    Ted> Is the struts-el taglib now actually broken because html:link gained a missing
    Ted> property? Or does it simply fail to meet one of our expectations for the taglib?

No, I certainly wouldn't call it "broken", just that it wouldn't support an
attribute that is supported in the base library.

    Ted> I am of the opinion that all the taglibs should be packaged separately. In this
    Ted> way, that fixes and enhancements that do not affect the core Action and Config
    Ted> packages could be released more easily. The conventional taglibs have stayed
    Ted> put so far since they arguably do no harm and provide a convenience to a great
    Ted> many users.

I suppose if "core" Struts was separated from the tag library, then both tag
libraries could be released together in a single package.

    Ted> But we now have the situation where you would be obligated to vote against a
    Ted> release because changes to one package where not reflected in another package,
    Ted> which at this time lives in the contrib folder. I submit this that this is the
    Ted> type of coupling that MVC was invented to defeat, and that we not taking our
    Ted> own advice =:0)

The problem is that Struts-EL is not coupled with the MVC parts, just with the
tag library.

    Ted> Craig plans on releasing the Struts-JSF tablib separately, why can't we do the
    Ted> same with Struts-EL?

I don't know enough about what exactly Struts-JSF will be doing to really
compare it, but I would guess that it won't be as intimately tied to the Struts
MVC core or to the Struts tag library, which would make it logical to be
released separately.

My other concern about doing this is that we'll be changing the packaging
structure of Struts, just before a release.  I think I see some of your point
about packaging the MVC core separately from the tag libraries, but I think the
Struts tag library should be packaged with Struts-EL.  In any case, I'm
concerned about changing the release and packaging structure so close to a

David M. Karr          ; Java/J2EE/XML/Unix/C++   ; SCJP; SCWCD

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message