svn commit: r178611 - /struts/core/trunk/doc/announce.xml

2005-05-25 Thread niallp
Author: niallp
Date: Wed May 25 23:40:46 2005
New Revision: 178611

URL: http://svn.apache.org/viewcvs?rev=178611&view=rev
Log:
Update announcement page for Struts 1.2.7

Modified:
struts/core/trunk/doc/announce.xml

Modified: struts/core/trunk/doc/announce.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/announce.xml?rev=178611&r1=178610&r2=178611&view=diff
==
--- struts/core/trunk/doc/announce.xml (original)
+++ struts/core/trunk/doc/announce.xml Wed May 25 23:40:46 2005
@@ -9,6 +9,22 @@
 
 
 
+26 May 2005 - Struts 1.2.7 (General Availability)
+
+The Struts team is pleased to announce the release of Struts 1.2.7 for
+General Availability. This release includes new
+functionality, as well as numerous fixes for bugs which were reported
+against the previous release, and supersedes the earlier 1.2.4 version
+as the latest official release of Struts from The Apache Software
+Foundation.
+
+
+The binary, source and library distributions are available from the
+http://struts.apache.org/download.cgi";>Struts download 
page.
+The http://struts.apache.org/userGuide/release-notes.html";>Release Notes
+are available on the Struts web site.
+
+
 31 March 2005 - New Struts PMC Chair
 
 http://struts.apache.org/volunteers.html#martinc";>Martin 
Cooper has been appointed



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



svn commit: r178600 - in /struts/core/trunk/doc: acquiring.xml download.xml

2005-05-25 Thread niallp
Author: niallp
Date: Wed May 25 22:59:14 2005
New Revision: 178600

URL: http://svn.apache.org/viewcvs?rev=178600&view=rev
Log:
Update Acquiring/Download for Struts 1.2.7

Modified:
struts/core/trunk/doc/acquiring.xml
struts/core/trunk/doc/download.xml

Modified: struts/core/trunk/doc/acquiring.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/acquiring.xml?rev=178600&r1=178599&r2=178600&view=diff
==
--- struts/core/trunk/doc/acquiring.xml (original)
+++ struts/core/trunk/doc/acquiring.xml Wed May 25 22:59:14 2005
@@ -49,17 +49,17 @@
 
   
 http://struts.apache.org/download.cgi";>
-  Struts 1.2.4
+  Struts 1.2.7
 
   
 
   
   
-Beta Releases
+Older Releases are available from the 
 
   
-http://struts.apache.org/download.cgi";>
-  Struts 1.2.6 (Beta)
+http://archive.apache.org/dist/struts/";>
+  Archive Site
 
   
 

Modified: struts/core/trunk/doc/download.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/download.xml?rev=178600&r1=178599&r2=178600&view=diff
==
--- struts/core/trunk/doc/download.xml (original)
+++ struts/core/trunk/doc/download.xml Wed May 25 22:59:14 2005
@@ -52,10 +52,10 @@
 
 
 
-
+
 
 
-Struts 1.2.4 is the latest production release of Struts. It is 
available
+Struts 1.2.7 is the latest production release of Struts. It is 
available
 in a binary distribution, a source distribution, and a minimal library
 distribution.
 
@@ -65,14 +65,14 @@
 Binaries:
 
 
-jakarta-struts-1.2.4.zip
 
-[http://www.apache.org/dist/struts/binaries/jakarta-struts-1.2.4.zip.asc";>PGP]
-[http://www.apache.org/dist/struts/binaries/jakarta-struts-1.2.4.zip.md5";>MD5]
+struts-1.2.7.zip 
+[http://www.apache.org/dist/struts/binaries/struts-1.2.7.zip.asc";>PGP]
+[http://www.apache.org/dist/struts/binaries/struts-1.2.7.zip.md5";>MD5]
 
 
-jakarta-struts-1.2.4.tar.gz
 
-[http://www.apache.org/dist/struts/binaries/jakarta-struts-1.2.4.tar.gz.asc";>PGP]
-[http://www.apache.org/dist/struts/binaries/jakarta-struts-1.2.4.tar.gz.md5";>MD5]
+struts-1.2.7.tar.gz 
+[http://www.apache.org/dist/struts/binaries/struts-1.2.7.tar.gz.asc";>PGP]
+[http://www.apache.org/dist/struts/binaries/struts-1.2.7.tar.gz.md5";>MD5]
 
 
 
@@ -80,14 +80,14 @@
 Source:
 
 
-jakarta-struts-1.2.4-src.zip
 
-[http://www.apache.org/dist/struts/source/jakarta-struts-1.2.4-src.zip.asc";>PGP]
-[http://www.apache.org/dist/struts/source/jakarta-struts-1.2.4-src.zip.md5";>MD5]
+struts-1.2.7-src.zip 
+[http://www.apache.org/dist/struts/source/struts-1.2.7-src.zip.asc";>PGP]
+[http://www.apache.org/dist/struts/source/struts-1.2.7-src.zip.md5";>MD5]
 
 
-jakarta-struts-1.2.4-src.tar.gz
 
-[http://www.apache.org/dist/struts/source/jakarta-struts-1.2.4-src.tar.gz.asc";>PGP]
-[http://www.apache.org/dist/struts/source/jakarta-struts-1.2.4-src.tar.gz.md5";>MD5]
+struts-1.2.7-src.tar.gz
 
+[http://www.apache.org/dist/struts/source/struts-1.2.7-src.tar.gz.asc";>PGP]
+[http://www.apache.org/dist/struts/source/struts-1.2.7-src.tar.gz.md5";>MD5]
 
 
 
@@ -95,14 +95,14 @@
 Library:
 
 
-jakarta-struts-1.2.4-lib.zip
 
-[http://www.apache.org/dist/struts/library/jakarta-struts-1.2.4-lib.zip.asc";>PGP]
-[http://www.apache.org/dist/struts/library/jakarta-struts-1.2.4-lib.zip.md5";>MD5]
+struts-1.2.7-lib.zip 
+[http://www.apache.org/dist/struts/library/struts-1.2.7-lib.zip.asc";>PGP]
+[http://www.apache.org/dist/struts/library/struts-1.2.7-lib.zip.md5";>MD5]
 
 
-jakarta-struts-1.2.4-lib.tar.gz
 
-[http://www.apache.org/dist/struts/library/jakarta-struts-1.2.4-lib.tar.gz.asc";>PGP]
-[http://www.apache.org/dist/struts/library/jakarta-struts-1.2.4-lib.tar.gz.md5";>MD5]
+struts-1.2.7-lib.tar.gz
 
+[http://www.apache.org/dist/struts/library/struts-1.2.7-lib.tar.gz.asc";>PGP]
+[http://www.apac

svn commit: r178595 [2/2] - /struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml /struts/core/trunk/doc/userGuide/release-notes.xml

2005-05-25 Thread niallp
Modified: struts/core/trunk/doc/userGuide/release-notes.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/userGuide/release-notes.xml?rev=178595&r1=178594&r2=178595&view=diff
==
--- struts/core/trunk/doc/userGuide/release-notes.xml (original)
+++ struts/core/trunk/doc/userGuide/release-notes.xml Wed May 25 22:47:48 2005
@@ -4,234 +4,751 @@
 Struts Release Notes (since 1.2.4)
   
  
+ 
   
-
-This section contains release notes for changes that have taken
-place since
-Version 1.2.4.
-
-
-The number in [square brackets] refers to the Subversion
-revision number. References to "#12345" are to the
-http://issues.apache.org/";>Bugzilla ticket number (if
-any).
-
-
-To keep up-to-date on all changes to Struts, subscribe to the
-dev@ list.
-
+  
+  This section contains release notes for changes that have taken
+  place since
+  Version 1.2.4.
+  To keep up-to-date on all changes to Struts, subscribe to the
+  dev@ list.
+  
+  
+  Notes on upgrading are maintained in the
+  http://wiki.apache.org/struts/StrutsUpgrade";>Wiki 
Upgrade pages.
+  The wiki is a community maintained resource - please feel free 
to add your
+  input so that everyone can benefit from the collective 
experience.
+  
+  
+ For the version requirements of each library, see the 
+ Installation chapter.
+  
+ 
   
 
- 
+  
+  
+  The purpose of this section is to highlight the new features 
since the
+  Version 1.2.4 release. For detailed information concerning 
changes 
+  see the Detailed Changes section.
+  
+  Dependencies
+  
+  Struts has changed its dependencies on the following software 
components:
+  
+  
+   Commons BeanUtils dependency changed to Version 
1.7.0
+   Commons Digester dependency changed to Version 1.6
+   Commons Validator dependency changed to Version 
1.1.4
+   Dependency on Commons Collections has been removed
+   Dependency on Commons Lang has been removed
+  
+
+  Core Struts
+  Saving Messages in the Session
+  
+  A new method to store errors in the Session 
[saveErrors(HttpSession, ActionMessages)]
+  has been added to Action along with the automatic removal 
of these errors once they have been
+  accessed. This is equivalent to the facility for messages 
that was included in the Version 1.2.4
+  release.
+  
 
- 
-2004-11-20 [105966] - Resolve #31642, " always
-include Session id (if any) even for external Urls (href 
attribute)".
- 
-
- 
-2004-11-20 [105965] - Resolve #32283, "Two slashes created by
-TagUtils.getActionMappingURL for webapps in root context".
- 
-
- 
-2004-11-20 [105963] - Resolve #32265 "add a warning to reset
-FormFile".
- 
-
- 
-2004-11-19 [105907] - Resolve #32323, "Shale mailreader example
-should define the servlet version as 2.4".
- 
-
- 
-2004-11-19 [105888] - Changes to update maven build after SVN 
layout
-re-org.
- 
-
- 
-2004-11-19 [105881] - Remove redundant definitions of
-maven.repo.central and maven.repo.central.directory.
- 
-
- 
-2004-11-18 [105785] - Added ability to load struts, validator, and
-tiles config files from classloader if not found in the servlet
-context.
- 
-
- 
-2004-11-18 [105787] - Better handling of servlet initialization
-errors to mark the servlet as unavailable and notify the developer
-of the probable cause.
- 
-
- 
-2004-11-18 [76271] - Add missing base class for Shale test cases.
- 
-
- 
-2004-11-16 [76098] - Resolve #32134, "Must use contextRelative to
-forward to Actions in Default module".
- 
-
- 
-2004-11-13 [57587 - 65927 (not consecutive)] - Subversion 
repository
-rearranged into separate core, el, faces and sandbox subprojects.
- 
-
- 
-2004-11-09 [57108] - Resolve #31983, "Validator validwhen
-documentation typo".
- 
-
- 
-2004-11-09 [57099] - Resolve #32123, "DigestingPlugIn can't load a
-digester rule file"

svn commit: r178595 [1/2] - /struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml /struts/core/trunk/doc/userGuide/release-notes.xml

2005-05-25 Thread niallp
Author: niallp
Date: Wed May 25 22:47:48 2005
New Revision: 178595

URL: http://svn.apache.org/viewcvs?rev=178595&view=rev
Log:
Copy Release Notes to current branch

Added:
struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml   (with props)
Modified:
struts/core/trunk/doc/userGuide/release-notes.xml

Added: struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml?rev=178595&view=auto
==
--- struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml (added)
+++ struts/core/trunk/doc/userGuide/release-notes-1.2.7.xml Wed May 25 22:47:48 
2005
@@ -0,0 +1,754 @@
+
+
+  
+Struts Release Notes (since 1.2.4)
+  
+ 
+ 
+  
+  
+  This section contains release notes for changes that have taken
+  place since
+  Version 1.2.4.
+  To keep up-to-date on all changes to Struts, subscribe to the
+  dev@ list.
+  
+  
+  Notes on upgrading are maintained in the
+  http://wiki.apache.org/struts/StrutsUpgrade";>Wiki 
Upgrade pages.
+  The wiki is a community maintained resource - please feel free 
to add your
+  input so that everyone can benefit from the collective 
experience.
+  
+  
+ For the version requirements of each library, see the 
+ Installation chapter.
+  
+ 
+  
+
+  
+  
+  The purpose of this section is to highlight the new features 
since the
+  Version 1.2.4 release. For detailed information concerning 
changes 
+  see the Detailed Changes section.
+  
+  Dependencies
+  
+  Struts has changed its dependencies on the following software 
components:
+  
+  
+   Commons BeanUtils dependency changed to Version 
1.7.0
+   Commons Digester dependency changed to Version 1.6
+   Commons Validator dependency changed to Version 
1.1.4
+   Dependency on Commons Collections has been removed
+   Dependency on Commons Lang has been removed
+  
+
+  Core Struts
+  Saving Messages in the Session
+  
+  A new method to store errors in the Session 
[saveErrors(HttpSession, ActionMessages)]
+  has been added to Action along with the automatic removal 
of these errors once they have been
+  accessed. This is equivalent to the facility for messages 
that was included in the Version 1.2.4
+  release.
+  
+
+  Re-directing ActionForward
+  
+  ActionRedirect is a subclass of ActionForward which is 
designed for use in redirecting requests, 
+with support for adding parameters at runtime. See 
the javadoc for more details.
+  
+
+  Download Action
+  
+  DownloadAction is an abstract action that provides the 
nuts and bolts for downloading 
+  files. See the javadocs and http://wiki.apache.org/struts/StrutsFileDownload";>Wiki
+  for further information.
+  
+
+  Dispatch Helper
+  
+  ActionDispatcher is a helper class for providing 
DispatchAction type behaviour
+  without having to inherit from DispatchAction. See the 
javadoc for more details.
+  
+
+  Lazy Validator Form
+  
+  A DynaBean flavour ActionForm which doesn't need its 
properties to be
+  defined and provides Lazy List and Lazy Map 
behaviours.
+  
+   Config Files in jars
+  
+  Config files (i.e. Struts config, Validator config and Tiles 
config files) can now be stored in jars.
+  Struts checks the servlet context, as before but if not found 
Struts now tries the classloader to try
+  and get them.
+  
+  Tag Library Changes
+  Highlighting Errors
+  
+  Struts can now automatically highlight error fields using the 
new errorKey,
+  errorStyle, errorStyleClass and 
errorStyleId attributes on the HTML
+  Input Tags. See the User Guide 
for details of these attributes.
+  
+  Readonly / Disabled Forms
+  
+  It is now possible to either disable or make read 
only all fields for a form
+  using the new readonly and disabled attributes on 
the  tag.
+  N.B.The readonly attribute only affects  
, 
+  and  as per the HTML 4 specification.
+  See the User Guide for 
details of these attributes.
+  
+
+  HTML Tag Refactoring
+  
+  Ma

Re: svn commit: r178550 - in /struts/core/trunk/src: share/org/apache/struts/config/ActionConfig.java share/org/apache/struts/config/BaseConfig.java share/org/apache/struts/config/FormBeanConfig.java test/org/apache/struts/config/TestActionConfig.java test/org/apache/struts/config/TestFormBeanConfig.java

2005-05-25 Thread Riyaz Mansoor


just a thought.

ie, not expose the "properties" object (as it is) by the 
getProperties,setProperties methods. by my last viewing of the Config 
classes, only ActionConfig uses "properties" and needs to change for 
this - not much.


get/setProperties can be replaced by

void inheritProperties(childConfig) {
// for each "xx" property in (parent) class
// if childConfig.getProperty("xx") == null
// copy the arbitrary property
}


imho, i think this is a good way to do this, provides separation between 
BaseConfig and its extending classes


is it worth submitting a patch?

riyaz


[EMAIL PROTECTED] wrote:

Author: hrabago
Date: Wed May 25 16:35:00 2005
New Revision: 178550

URL: http://svn.apache.org/viewcvs?rev=178550&view=rev
Log:
Copy arbitrary properties of inherited form bean properties, action mapping 
forwards and exception handlers.

Modified:
struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java
struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java
struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java
struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java
struts/core/trunk/src/test/org/apache/struts/config/TestFormBeanConfig.java

 
 /**

  * Return the entire set of properties configured for this object.
- * At this time, this only needs to be exposed 
- * to support inheritance, so choosing a conservative access modifier ("protected"). 
+ * At this time, this only needs to be exposed to support inheritance, 
+ * so choosing a conservative access modifier ("protected"). 
  * @return

  */
 protected Properties getProperties() {
@@ -123,6 +123,15 @@
 }
 
 
+/**

+ * Set the entire set of properties configured for this object.
+ * At this time, this only needs to be exposed to support inheritance, 
+ * so choosing a conservative access modifier ("protected"). 
+ */

+protected void setProperties(Properties properties) {
+this.properties = properties;
+}
+



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



Re: [Shale] Questions and suggestion to Clay

2005-05-25 Thread gvanmatre
Manfred,

>> A simpler solution might be to let an extending meta component or element
>> override the component type. This way we could morph a outputText into an
>> inputText.
>> 
>> 
>> 
>>
>>
>> This would give us the same flexibility but still make sure that the meta
>> component is associated with a JSF component. The only problem I see is
>> that this could be misused.  For example, someone could extend a panelGrid
>> and override the type to an inputText.
>>
>> If we allowed this flexibility, I think we would have to give up on the
>> strong checking of setting properties and just ignore the ones that don't
>> fit the component.
>
>And the people would spend a lot of time with the search for typos.


I agree.  The more help the better.  I saw a demo of Tapestry a couple of weeks
ago.  It sure goes out of its way to communicate all that it can when it comes
to exception handling, probably something we should keep in mind too.


>
>Another solution could be the definition of a pseudo component, which has a
>special processing in CreateComponentCommand (or its own chain command).
>
>  componentType="org.apache.shale.clay.component.container"/>


This approach would also work.  I don't think that anything would stop you from 
including a nested clay component too.  I like the simple mapping of the 
componentType
to a pure JSF component and think that enabling componentType inheritance would 
be a 
pretty slick solution.  Morphing JSF components, it sounds cool. I remember 
when 
MS Access 95 added Morphing to their IDE designer.

>> After the fix to the inheritance is applied, I think that this would be
>> resolved. It would allow you to define a panelGrid with a lablel and text
>> field as elements and then extend the pannel adding other elements.
>
>Still a problem if I want to reuse the components in different combinations.
>- complexAmount and complexPerson
>- complexPerson and complexAddress
>- complexPerson, complexAddress and complexAmount
>- ...


Your example was cut off.  I don't see why these component definitions 
can not be grouped and used these ways.  A component could be nested within 
several other components.  The only restriction I see is with 
circular associations for both generalization and aggregation relationships.  
This restriction has more to do with using recursion to fix-up the inheritance
and build the component tree.


I started a clay test case that extends AbstractViewControllerTestCase.  This 
guy
has mock JSF classes making it pretty easy to snap togather stand alone junit 
tests.  I think that this would be a great place to white board the kinds of 
issues
that you have outlined without a lot of code - besides all the other benefits 
of 
automated testing.

I'll upload my starter test in a ticket this week.  Hopefully we can get a 
committer 
to take a look at our outstanding patchs soon.  That would make it easier for 
us to collaborate going forward :-)

Gary

svn commit: r178572 - /struts/build/trunk/KEYS

2005-05-25 Thread niallp
Author: niallp
Date: Wed May 25 20:45:56 2005
New Revision: 178572

URL: http://svn.apache.org/viewcvs?rev=178572&view=rev
Log:
Add my public key

Modified:
struts/build/trunk/KEYS

Modified: struts/build/trunk/KEYS
URL: 
http://svn.apache.org/viewcvs/struts/build/trunk/KEYS?rev=178572&r1=178571&r2=178572&view=diff
==
--- struts/build/trunk/KEYS (original)
+++ struts/build/trunk/KEYS Wed May 25 20:45:56 2005
@@ -110,3 +110,38 @@
 XlF0aQ==
 =8WZU
 -END PGP PUBLIC KEY BLOCK-
+
+
+Type Bits/KeyID Date   User ID 
+DSS  1024/C56014B2 2004-11-12  Niall Pemberton (Code signing) <[EMAIL 
PROTECTED]>
+
+-BEGIN PGP PUBLIC KEY BLOCK-
+Version: PGP 8.1 - not licensed for commercial use: www.pgp.com
+
+mQGiBEGVK0ERBADwhGhmOMvSgvGaqHW3ial0NS80ZXyE1EeNL6ke/WrXHB4dT6if
+inoAuUgRz3v9Na4rjSQ8YVFjn3NaZq1i8RM2KJOUU8ZkJ2AsrH6fqStjofLTd5ng
+iQaq2wLM5rTQfdjLsGQb1iDNDyCXU56+/l4mFZ2JiEGCq3Re9EFHelRBKQCg/7k0
+BIfyoFVTHw39PKaDBmCYF2sD/3CMD0J/WldhBM7gLOndH9/YEQaEMy+PJNXcfTWN
+WLygGPSOQdNBulyLkvcFIZjUTxFVakh7FbjMq3dsAP1oqthwmK7L8A1zsvRgp/TI
+4YMHkZSkgcs0PBBby+h/lpgRrWmtwjTPzql/K5xX4VSRS+umHye/7R+4ZEH7mABa
+m/ZABADkPGG2ECvfjNosPQDHZVFuF9oVaske0OjzxI+rU6sR1fJKtbOPl9d+bgz+
+df7rZ3mwppkPX2r/muUbd0CM1Se10sK7ZAoPYmWqHX+vB/oj3Jq+iqb6M5mDZzEz
+6h4hdnaGERyxbktZvhRV7Psco9CGi8o7RFUQTR79Y5ElnBavqLQyTmlhbGwgUGVt
+YmVydG9uIChDb2RlIHNpZ25pbmcpIDxuaWFsbHBAYXBhY2hlLm9yZz6JAF0EEBEC
+AB0FAkGVK0EHCwkIBwMCCgIZAQUbAwUeAQAKCRAYYcMixWAUsgCiAKCD
+27/cQbPNPTEFFK/9wn7TwQIaZgCfbDN9CZ5xJDbQpLNRKDqasXF7g7C5Ag0EQZUr
+QRAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bL
+Q6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8
+g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3k
+kQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs
+3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRd
+QZ+cfL2JSyIZJrqrol7DVekyCzsAAgIIAMOpC9D4T2fxDyNJj35iGHmilIEwfKuO
+5wymOOsA7NZf5rFSRwFcBhAR7sZmwu6/6nwIH0lvvy4+F20iwqmmSFkrupX2ONyD
+iGFw+KXuXAp1pEIo/ody8UUerg5ga+XMIXhxLgdrDBVOZSYokEdfnl2JDzSuBYFU
+KRy1nm6DgwJU39I/IEUfmk7OXll6n0gPlBLF6Z+uOd232ShC15EZhM52+MchliWi
+1tjJZmkZWrmL3OtTOxSvM9eUkmW6uqInLaZxHH5IJwcXDc2t42UFe1jlmdwZQ9Zy
+kOutbG5kvNf5y58W6L/QErNuStqJVwbB5BEYYzJxEXnb7+2r5ZgcItaJAEwEGBEC
+AAwFAkGVK0EFGwwACgkQGGHDIsVgFLIZNACfa78K8/MrBG/UVSQ9hHvnWP08
+bAMAniQ+3a5yjxqf2k73+ipTq+VlSvfz
+=4ydx
+-END PGP PUBLIC KEY BLOCK-



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



DO NOT REPLY [Bug 34849] - Expression Language Field Validator

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34849





--- Additional Comments From [EMAIL PROTECTED]  2005-05-26 04:41 ---
I am still quite interested in seeing this integrated into Struts, because I
believe people will find it extremely useful; however, in looking into actually
plugging it in, I realize that it actually brings with it dependencies upon
commons-lang and commons-collections as well as commons-jexl (assuming that we
copy EnumeratedMap from taglibs-standard instead of depending upon it.)  

Because of this, I feel the need to get more opinions and comments before
committing any changes.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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



DO NOT REPLY [Bug 33202] - DispatchChainAction needs review

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33202


[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|dev@struts.apache.org   |[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2005-05-26 03:29 ---
I propose removing the DispatchChainAction and ChainAction from Struts; this
functionality is obsolete now that you can define a chain/command in the action
mapping directly, and since these classes have never been released, I think we
should kill them before we consign ourselves to support them.  If there is no
feedback to the contrary in the next few days I will remove them from the
repository.

If anyone believes we are obligated to deprecate them and leave them for a
while, please speak up.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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



commons-beanutils needs maintainers

2005-05-25 Thread Simon Kitching
Hi All,

The struts project is one of the main users of commons-beanutils
library, and the original source of the code.

However there doesn't seem to be anyone maintaining commons-beanutils
any more, and the bugzilla list is now up to 88 items.

I'm willing to spend some time on this, and James Carman has also
volunteered. But it would be great if a few Struts developers could also
join us. I'm sure there would be no problem getting regular struts
developers commit access to jakarta-commons.

And of course it's in the interest of struts for beanutils to be
maintained!

Discussion will occur on the regular commons-dev list. Emails related to
beanutils will always have [beanutils] in the subject line, so you can
apply filtering to cut out any unwanted commons mail traffic.

I hope to see a few of you on that list...

Regards,

Simon



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



Re: copy properties for inheritance (Re: svn commit: r178550)

2005-05-25 Thread Hubert Rabago
On 5/25/05, Joe Germuska <[EMAIL PROTECTED]> wrote:
> I was wondering about this:
> 
> >  BeanUtils.copyProperties(copy, baseHandler);
> >  this.addExceptionConfig(copy);
> >-
> >+copy.setProperties(baseHandler.getProperties());
> >+
> 
>  doesn't the strategy you implemented clobber properties which are
> set on the extending/copy?  Shouldn't this process somehow honor
> properties which were already set in the copy?  I think it should go
> through the list of property names in the baseHandler and, where the
> property is not already defined in the copy, in those cases it should
> copy them.
> 

This part of the code executes when the extending config object
(ActionConfig in this case) isn't overriding baseHandler:

// Do we have this handler?
ExceptionConfig copy =
this.findExceptionConfig(baseHandler.getType());

if (copy == null) {

// We don't have this, so let's copy it
copy = (ExceptionConfig) RequestUtils
.applicationInstance(baseHandler.getClass().getName());

BeanUtils.copyProperties(copy, baseHandler);
this.addExceptionConfig(copy);
copy.setProperties(baseHandler.getProperties());

} else {

// process any extension that this config might have
copy.processExtends(getModuleConfig(), this);

}


Hubert

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



[Struts Wiki] Update of "StrutsRelease127" by MartinCooper

2005-05-25 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by MartinCooper:
http://wiki.apache.org/struts/StrutsRelease127

The comment on the change is:
New Bugzilla version added.

--
  
  || '''#''' || '''Description''' || '''Completed''' ||
  || B1. || Create Sums and Sign Distributions [2] || (./) ||
- || B2. || Request new Bugzilla version level (1.2.7) || No ||
+ || B2. || Request new Bugzilla version level (1.2.7) || (./) ||
  || B3. || Update "Acquiring" page on website and Test Downloads || No ||
  
  == Vote (B) ==

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



[Struts Wiki] Update of "StrutsRelease127" by NiallPemberton

2005-05-25 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by NiallPemberton:
http://wiki.apache.org/struts/StrutsRelease127

The comment on the change is:
Update results of quality vote

--
  || A1. || Tag release in svn: STRUTS_1_2_7 || (./) ||
  || A2. || Run Distribution Target || (./) ||
  || A3. || Upload Distribution to 
cvs.apache.org:/www/cvs.apache.org/dist/struts/1.2.7 || (./) ||
- || A4. || Post release-quality vote on dev@ and user@ lists || No ||
+ || A4. || Post release-quality vote on dev@ and user@ lists || (./) ||
  
  == Vote (A) ==
  
  || PMC Member || Quality ||
+ || mrdon || '''GA''' ||
+ || jmitchell || '''GA''' ||
+ || niallp || '''GA''' ||
+ 
+ Voting thread is 
[http://www.mail-archive.com/dev%40struts.apache.org/msg09214.html here]
  
  If release vote fails, including for a lack of quorum, remove from dist 
  folder.  
@@ -109, +114 @@

  == Point Release Checklist (B) ==
  
  || '''#''' || '''Description''' || '''Completed''' ||
- || B1. || Create Sums and Sign Distributions [2] || No ||
+ || B1. || Create Sums and Sign Distributions [2] || (./) ||
  || B2. || Request new Bugzilla version level (1.2.7) || No ||
  || B3. || Update "Acquiring" page on website and Test Downloads || No ||
  

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



[RESULT] [VOTE] Struts 1.2.7 Quality

2005-05-25 Thread Niall Pemberton
Its been 72 hours since the vote on the quality of Struts 1.2.7 was posted:

http://www.mail-archive.com/dev%40struts.apache.org/msg09214.html

The following votes were received::

PMC Member Don Brown voted for "GA" quality
PMC Member James Mitchell voted for "GA" quality
PMC Member Niall Pemberton voted for "GA" quality

Therefore with three votes for "GA" quality from PMC members and no other
votes, Struts 1.2.7 will be the current "GA" quality release.

Niall Pemberton




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



copy properties for inheritance (Re: svn commit: r178550)

2005-05-25 Thread Joe Germuska

I was wondering about this:


 BeanUtils.copyProperties(copy, baseHandler);
 this.addExceptionConfig(copy);
-
+copy.setProperties(baseHandler.getProperties());
+


 doesn't the strategy you implemented clobber properties which are 
set on the extending/copy?  Shouldn't this process somehow honor 
properties which were already set in the copy?  I think it should go 
through the list of property names in the baseHandler and, where the 
property is not already defined in the copy, in those cases it should 
copy them.


I haven't studied this, so forgive me if I'm overlooking something

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]



svn commit: r178550 - in /struts/core/trunk/src: share/org/apache/struts/config/ActionConfig.java share/org/apache/struts/config/BaseConfig.java share/org/apache/struts/config/FormBeanConfig.java test/org/apache/struts/config/TestActionConfig.java test/org/apache/struts/config/TestFormBeanConfig.java

2005-05-25 Thread hrabago
Author: hrabago
Date: Wed May 25 16:35:00 2005
New Revision: 178550

URL: http://svn.apache.org/viewcvs?rev=178550&view=rev
Log:
Copy arbitrary properties of inherited form bean properties, action mapping 
forwards and exception handlers.

Modified:
struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java
struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java
struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java
struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java
struts/core/trunk/src/test/org/apache/struts/config/TestFormBeanConfig.java

Modified: struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java?rev=178550&r1=178549&r2=178550&view=diff
==
--- struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java 
(original)
+++ struts/core/trunk/src/share/org/apache/struts/config/ActionConfig.java Wed 
May 25 16:35:00 2005
@@ -711,7 +711,8 @@
 
 BeanUtils.copyProperties(copy, baseHandler);
 this.addExceptionConfig(copy);
-
+copy.setProperties(baseHandler.getProperties());
+
 } else {
 
 // process any extension that this config might have
@@ -758,7 +759,8 @@
 BeanUtils.copyProperties(copy, baseForward);
 
 this.addForwardConfig(copy);
-
+copy.setProperties(baseForward.getProperties());
+
 } else {
 
 // process any extension for this forward

Modified: struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java?rev=178550&r1=178549&r2=178550&view=diff
==
--- struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java 
(original)
+++ struts/core/trunk/src/share/org/apache/struts/config/BaseConfig.java Wed 
May 25 16:35:00 2005
@@ -114,8 +114,8 @@
 
 /**
  * Return the entire set of properties configured for this object.
- * At this time, this only needs to be exposed 
- * to support inheritance, so choosing a conservative access modifier 
("protected"). 
+ * At this time, this only needs to be exposed to support inheritance, 
+ * so choosing a conservative access modifier ("protected"). 
  * @return
  */
 protected Properties getProperties() {
@@ -123,6 +123,15 @@
 }
 
 
+/**
+ * Set the entire set of properties configured for this object.
+ * At this time, this only needs to be exposed to support inheritance, 
+ * so choosing a conservative access modifier ("protected"). 
+ */
+protected void setProperties(Properties properties) {
+this.properties = properties;
+}
+
 /**
  * Compare the properties of this config with that of the given and
  * copy those that are not present.  This method is used by subclasses

Modified: 
struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java?rev=178550&r1=178549&r2=178550&view=diff
==
--- struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java 
(original)
+++ struts/core/trunk/src/share/org/apache/struts/config/FormBeanConfig.java 
Wed May 25 16:35:00 2005
@@ -21,6 +21,7 @@
 
 
 import java.util.HashMap;
+import java.util.Properties;
 import java.lang.reflect.InvocationTargetException;
 
 import org.apache.commons.beanutils.DynaBean;
@@ -272,6 +273,7 @@
 
 BeanUtils.copyProperties(prop, baseFpc);
 this.addFormPropertyConfig(prop);
+prop.setProperties(baseFpc.getProperties());
 }
 
 }

Modified: 
struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java
URL: 
http://svn.apache.org/viewcvs/struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java?rev=178550&r1=178549&r2=178550&view=diff
==
--- struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java 
(original)
+++ struts/core/trunk/src/test/org/apache/struts/config/TestActionConfig.java 
Wed May 25 16:35:00 2005
@@ -86,12 +86,14 @@
 baseConfig.addForwardConfig(forward);
 
 forward = new ForwardConfig("failure","/failure.jsp",false);
+forward.setProperty("forwardCount", "10");
 baseConfig.addForwardConfig(forward);
 
 // setup an exception handler
 ExceptionConfig exceptionConfig = new ExceptionConfig(

Jdbc2

2005-05-25 Thread jeff ort
I am noticing that the Ant build scripts reference an optional jdbc20ext.jar
file, but the Maven build process does not.  I was wondering if there was a
reason why this was not used in the Maven build process?



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



DO NOT REPLY [Bug 35071] New: - Email validation fails for top level domains > 3 chars

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35071

   Summary: Email validation fails for top level domains > 3 chars
   Product: Struts
   Version: Unknown
  Platform: Other
OS/Version: Windows XP
Status: NEW
  Severity: normal
  Priority: P2
 Component: Validator Framework
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


An email such as [EMAIL PROTECTED] will fail the current javascript
validation.  Top level domains are not restricted to emails with 3 or less
characters on any documentation I could find.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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



Re: [Shale] Questions and suggestion to Clay

2005-05-25 Thread Manfred Klug
>> - There is a problem with properties. A component is possibly based
>> on the generic attribute map and has no setter for a property. e.g.
>> functionName property in ValidatorScript.
>>
>> At the moment Clay has no knowledge about such attributes and it's
>> impossible to do a type conversion.
>> [snip]
>
> This is defiantly a shortcoming. Originally I was thinking about allowing
> custom chain commands to be registered by the clay component like the
> Shale servlet filter provides. That would allow custom commands to be
> plugged into the chains used to construct the subtree. The same solution
> would work for registering custom builders rules used to associate an
> html element with a faces component when using the html layout strategy.

 This could be a useful feature to manage complicated components, but I
 think this is a bit oversized for the attribute problem.
>>>
>>> I'm not sure how we would allow for mapping non standard action event
>>> properties without this unless we went with Craig's suggestion of using
>>> the attributes map. Is that what your point toward? If so, this should
>>> belong in PropertyValueCommand.
>>
>> We must use the attribute map anyway either in Clay or in the custom
>> builder.
>
> After the PropUtils patch is applied, an exception will be raised if the
> attribute was not found.

Yes, the patch was the reason why I have found the problem.

> We could catch the exception and just add the property to the
> attributes map?

Yes, or we could always use the attribute map unless there is no attribute
definition. The required patch for PropUtils is relatively simple. The only
problem is the missing type information.

> Should we try to validate that there is a matching method on the component?

>> - I think something like namespaces is needed for the jsfid attribut to
>>   avoid name collisions between components of different sources.
>
> I believe that the component type registered in the faces config would 
> have
> to be unique but I guess that you could choose to use the same jsfid? One
> approach might be to prefix the jsfid with a unique prefix (sunOutputText,
> myfacesOutputText).

 Yes, this is a possible solution. But I know from own experience that
 different
 people have different opinions about prefixes (short and cryptic against 
 long
 and meaningful).
>>>
>>> I think that if we had namespaces, we would have to create a composite id's
>>> for the component. It would need to be the jsfid and a namespace.
>>
>> Yes.
>>
>>> This would need to be considered when realizing inheritance. For example, 
>>> you
>>> might have two outputText components registered under different namespaces.
>>> I'm not sure how the extends attribute alone would identify the correct 
>>> super
>>> component unless it was assumed that you could only extend components 
>>> defined
>>> in the same namespace? That might work.
>>
>> The extends attribute is a jsfid, so it needs namespaces too.
>>
>> I think something like this should work:
>>
>> 
>> 
>> 
>> 
>>
>> > componentType="javax.faces.HtmlInputText"/>
>> 
>>
>> 
>> 
>> > value="theJsfHtmlNamespace"/>
>> 
>>
>> > extends="standardJsfHtmlComponents:inputText">
>> ...
>> 
>> 
>>
>> [snip]
>
> That looks good.   Should we make some assumptions if the component jsfid
> or extends attribute did not specify a qualifier? Or, throw an exception
> that they must have a namespace?  I kind of like the assumed default for
> the people that won't take advantage of the feature, but one could argue
> for consistency.

I also think that we shouldn't force the people to use namespaces. But we
could allow a default value.


...


Which is empty if nothing is specified.

>> - I think that it would be a nice possibility to have a component
>> without componentType to define components without common parent.
>> Something like this:
>
> A simpler solution might be to let an extending meta component or element
> override the component type. This way we could morph a outputText into an
> inputText.
> 
> 
>  componentType="javax.faces.HtmlInputText"/>
>
>
> This would give us the same flexibility but still make sure that the meta
> component is associated with a JSF component. The only problem I see is
> that this could be misused.  For example, someone could extend a panelGrid
> and override the type to an inputText.
>
> If we allowed this flexibility, I think we would have to give up on the
> strong checking of setting properties and just ignore the ones that don't
> fit the component.

And the people would spend a lot of time with the search for typos.

Another solution could be the definition of a pseudo component, which has a
special processing in CreateComponentCommand (or its own chain command).

  

  

  


  



  

DO NOT REPLY [Bug 35069] New: - [shale] Dialog should allow flexible entry points

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35069

   Summary: [shale] Dialog should allow flexible entry points
   Product: Struts
   Version: Nightly Build
  Platform: PC
OS/Version: other
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


It would be nice to be able to specify an entry point for a dialog.  The "start"
attribute is fine as a default but it would be nice to use an outcome such as
dialog:foo:step3 to jump right to apply the step3 transition.

This is useful if you have a series of dialogs with several steps (say 10 steps)
and later on you want to edit only a portion of that information.  If you had
this ability you could have a link or button that would launch the dialog
directly into the step that you wanted.  I have some other ideas about
dynamically specifying the end state as well but I will save that for a later
bug report.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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



DO NOT REPLY [Bug 35068] New: - [shale] Position (inner class) should implement Serializable

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35068

   Summary: [shale] Position (inner class) should implement
Serializable
   Product: Struts
   Version: Nightly Build
  Platform: PC
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


At one point Tomcat complained about not being able to serialize
Status$Position.  This class should really implement Serializable otherwise any
class that implements Status and makes use of Position (such as Status) cannot
be serialized.

Also, this got me thinking about why Position is declared as part of the Status
interface.  Presumably there is a good reason but I can't think of any
advantages to this offhand.  In fact its a little bit disconcerting for the
average user (me) who has not ever seen an inner class in an interface before. 
Obviously its permissable but I think we should consider making it its own class
unless there is a compelling reason to have it this way.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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



DO NOT REPLY [Bug 35066] New: - [shale] Serious issue with dialog state

2005-05-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35066

   Summary: [shale] Serious issue with dialog state
   Product: Struts
   Version: Nightly Build
  Platform: PC
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


Consider the following example:

Start up the usecases example and begin creating a new profile.  Stop when you
get to page 2.  Now open a new tab (use Firefox) and click the logon dialog
again.  You get an exception:

java.lang.IllegalArgumentException: Position[dialogName=Edit
Profile,stateName=Page 2],outcome=dialog:Log On

This is because you have initiated the same dialog without finishing the
previous dialog.  This is not as crazy of a test as it might seem.  Consider
what would happen if you opened the dialog in popup window (instead of a browser
tab) and the user closed the window prematurely ... same problem.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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