> -----Original Message----- > From: Joe Germuska [mailto:[EMAIL PROTECTED]
==////== > > > At 4:34 PM +0000 1/17/05, Pilgrim, Peter wrote: > > > -----Original Message----- > >> From: James Mitchell [mailto:[EMAIL PROTECTED] > >==////=== > >> > >> The source repository is under a bit of restructuring right > >> now, we will try > >> to get those back online ASAP. > >> > >> Can you use this for now? > >> > >> http://struts.apache.org/api/index.html > >> > > > >I actually had a look there earlier, I was looking for classes like > >"**/*(Chain|Command)*.java". Did not see any thing like this pattern. > >I wrongly assumed the javadoc was 1.2 only. > > > >In truth I descended to the "src" folder from the repository trunk. > >The ``struts-src=20050117.zip'' is about 27MB but the zip file does > >contain HTML JavaDoc, JAR files, TLDs, Chains configuration, various > >Command and Chain implementations and the source code for > >everything. Whether it actually executes properly is another thing! > > I haven't yet committed any of the code I was posting about last week > (I've had a drought of free time to keep working on it). Therefore, > what's in CVS is essentially struts-chain merged into the core and > specified as the default request processing mode, plus a few small > enhancements. This code has been fairly stable for a while > (independent of the merge) so I am pretty comfortable guessing that > it will function as expected. > Should we wait until your commtit code has been marged? > Given that there hasn't been a whole lot of feedback on that code, > I'm going to try to zero in on getting it committed as soon as I can > go through a few more basic checks, with the belief that more people > will notice any problems if it's in the repository! Note that I'm > not only looking for bugs, but also critiques of a couple of design > decisions, so in contrast to the last year or more of Struts > development, it will be important to take to heart typical warnings > about API stability, at least in these new areas. > I think the daily snapshot of the binary only release should be changed to include the generated javadoc of the whole API, especially for those developers who definitely do not want to work with the source code directly. I am interesting in developing some Struts chain code because I have some requests to build database table report and browsing on-line applications. Small scale web apps, so it is an opportunity to test the ease of development and compare how we use to do it in 1.1 and against what we could do now. Also if you do deliver binaries, then javadoc writing has to be up to scratch. Most of the committers in Struts have been writing copious javadoc that is very well documented about the purpose of a class and method, and including exceptions. Thanks! When I downloaded the struts-src-20050117.zip file it had JAR binaries related to struts-faces and shale. So I am confused. Are these binaries built against the lastest sources themselves or are they themselves legacy. -- Peter Pilgrim Operations/IT - Credit Suisse First Boston, 10 South Colonnade, London E14 4QJ, United Kingdom Tel: +44-(0)207-883-4497 ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
