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.


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.

Joe

--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to