Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <struts-dev@jakarta.apache.org>
Message-ID: <3D772825.30307@apache.org>
Date: Thu, 05 Sep 2002 05:47:17 -0400
From: Ted Husted <husted@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
MIME-Version: 1.0
To: Struts Developers List <struts-dev@jakarta.apache.org>
Subject: Re: Struts-EL: Status and moving forward
References: <86lm6hdm38.fsf@earthlink.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

If you're ready to offer it to the project, ZIP it up as a distribution 
that we can download from somewhere and post it as an enhancement to 
bugzilla. Then we can have a look and decide about importing it into the 
Struts CVS.

If you'd like to kick it around some more first, instead of posting to 
bugzilla, post an ANNOUNCEMENT to the user list.

In either case, I'd be happy to help out with the JavaDoc, so you don't 
have to get bogged down in that.

-Ted.


David M. Karr wrote:

> I've gotten to the point with my Struts-EL contribution that I'd like some
> advice on how I can move forward with finalizing this.
> 
> I've finished the code for all the tags, except I have to put in any required
> standard headers and add javadoc (and I'd like to know what is really needed
> here, from a Jakarta policy point of view), although there's really not much to
> the code that is novel at all.  With some work (including an extension or two
> to the taglib XML descriptor), the code for the tags could be generated.  The
> only tag where I've added (none removed) an attribute is the "logic-el:match"
> tag, where I've added an "expr" attribute, to take an EL value, as opposed to
> getting the value to compare from a cookie, header, bean property, or request
> parameter.
> 
> I've finished converting all the original pages from the "exercise-taglib", and
> I've added one other, and added a "Show Source" feature for all the tests.
> 
> I've built a set of Cactus unit tests, covering many of the tags, but there's
> still quite a few which haven't been covered yet (the original Struts tests
> hardly cover any).
> 
> I'm almost done with writing a README file that explains the purpose of the
> library, and details some of the "porting decisions", which is a list of the
> original Struts tags which I did NOT port to Struts-EL (because JSTL covers
> their functionality).
> 
> My current work isn't in CVS, and is based on the 1.1-b2 code base.
> 
> I'd like to get this "out there" in the hands of people who can use it, and who
> can help to evolve it forward.
> 
> Advice?  Help?  Direction?
> 
> 


-- 
Ted Husted, Husted dot Com, Fairport NY US
co-author, Java Web Development with Struts
Order it today:
<http://husted.com/struts/book.html>


--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>