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? -- =================================================================== David M. Karr ; Java/J2EE/XML/Unix/C++ [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
