First, thanks for the quick followup last week on the readyness of builds including ValidWhen. I started testing our application against this build this morning.
The one would-be showstopper for us (although we work around it) is that the current snapshot of commons-collections has a number of serialization bugs. We're using decorators fairly extensively for type-safety. Since they're not serializable, they cause NotSerializableException when returned from stateless session EJBs. We're currently using a collections 3.0 build that we've modified to make these serializable. But the Struts 1.2 nightly comes with the broken version. This bugzilla search shows the bugs we're working around: http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Commons&component=Collections&short_desc=serializable&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27Importance%27 The other thing I've noticed is that the validator includes a number of DTDs that don't seem to match the files they ship with. validator-rules.xml references the DTD "http://jakarta.apache.org/commons/dtds/validator_1_1.dtd";, and the distribution ships with 2 local DTDs for the validator, "validator-rules_1_1.dtd" and "validation_1_1.dtd". Neither of these match the reference in the rules.xml file. Developing behind our firewall, local DTDs are many developers' only option for validation. If I modify the rules.xml file to reference either of these DTDs, errors appear. Are these old DTDs, or am I missing something? Stu Robertson __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
