Action.setLocale, fail early?

2003-08-29 Thread Rick Hightower
From Nightly build.

 

protected void setLocale(HttpServletRequest request, Locale locale) {

 

HttpSession session = request.getSession();

if (locale == null) {

locale = Locale.getDefault();

}

session.setAttribute(Globals.LOCALE_KEY, locale);

 

}

 

Comments on setLocale from Action..

 

If the locale is null, wouldn't it be better for the default to come from
the request as in request.getLocale(), which is the behavior of the tags
when the Locale at Globals.LOCALE_KEY is not in session scope.

 

Better Yet. Also if they call setLocale, shouldn't the local object be
non-null. My personal opinion on this stuff is that it should explode with
an illegal argument exception. (I remember a bug report that talked about
Struts quietly handing illegal situations)

 

if (locale == null) {

throw new java.lang.IllegalArgumentException(Locale was null);

}

 

 

As a developer when I misuse an API, I like to see it fail quickly. This way
I don't have to spend a lot of time debugging where I went wrong. Die early
and often in development not during QA or. gulp.. Production!

 

 

 

 

Rick Hightower

Chief Technology Officer

Trivera Technologies

http://www.triveratech.com

520 290 6855 (Phone)

520 977 8605 (Mobile)

 

 



Improve JSTL i18n support with Struts

2003-08-29 Thread Rick Hightower
I’d like to see Struts play nice with JSTL i18n support.

I have a suggestion along these lines. (This is prelim. I am going to write
some tests and do some prototyping but before I do… I’d like to hear if
there are any thoughts on this).

Currently when you call Action.setLocale you get this:

...class Action...
    protected void setLocale(HttpServletRequest request, Locale locale) {
 
    HttpSession session = request.getSession();
    if (locale == null) {
    locale = Locale.getDefault();
    }
    session.setAttribute(Globals.LOCALE_KEY, locale);
 
    }

I am suggesting this (for the release that embraces JSTL…. Struts 1.3 or
1.5).

import javax.servlet.jsp.jstl.core.Config; //get this guy to use its Locale
key as well
...class Action...
    protected void setLocale(HttpServletRequest request, Locale locale) {
 
    HttpSession session = request.getSession();
    if (locale == null) {
    locale = Locale.getDefault();//Don’t agree with this, but that
is a different story…
    }
    session.setAttribute(Globals.LOCALE_KEY, locale);
session.setAttribute(Config.FMT_LOCALE, locale); //See
this…. See this…. See this…
    }

The Config.FMT_LOCALE is similar to the Globals.LOCALE_KEY except that it is
for the JSTL tags, e.g.,

fmt:message key=title /

This is one possibility and the one that takes the least amount of effort.
Another possibility is to change all struts i18n tags to use
Config.FMT_LOCALE instead of Globals.LOCALE_KEY, which might be bad because
it would break existing projects.

I am going to write a prototype along these lines in the near future. I need
to test to see if fmt:message will work with Strut’s resource bundles. (I am
not sure it they will or not... I think they will with a little arm
twisting. I am still a little ignorant on the details... I got the big
picture... just not all the details.). Any suggestions from you i18n gurus
would be nice or if someone already started this... clue me in so I don't
waste time.

This could be a first step in getting rid of our good friend bean:message
and replacing him with fmt:message (or at least deprecating him a bit). :(

Don’t worry. I will add this to the Bugzilla feature request as soon as I
test it.

Rick Hightower
Chief Technology Officer
Trivera Technologies
http://www.triveratech.com
520 290 6855 (Phone)
520 977 8605 (Mobile)
 



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



cvs commit: jakarta-struts/doc/userGuide building_controller.xml

2003-08-29 Thread sraeburn
sraeburn2003/08/28 20:18:29

  Modified:doc/userGuide building_controller.xml
  Log:
  Fixed documentation typo
  PR: 22784
  
  Revision  ChangesPath
  1.66  +1 -1  jakarta-struts/doc/userGuide/building_controller.xml
  
  Index: building_controller.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/userGuide/building_controller.xml,v
  retrieving revision 1.65
  retrieving revision 1.66
  diff -u -r1.65 -r1.66
  --- building_controller.xml   26 Jul 2003 04:30:41 -  1.65
  +++ building_controller.xml   29 Aug 2003 03:18:29 -  1.66
  @@ -954,7 +954,7 @@
   exception 
 key=some.key 
 type=java.io.IOException 
  -  handler=com.yourcorp.ExceptionHandler
  +  handler=com.yourcorp.ExceptionHandler/
   /global-exceptions
   ]]/code/pre
   
  
  
  

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



DO NOT REPLY [Bug 22784] - exception tag not closed

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22784.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22784

exception tag not closed

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 03:21 ---
Thanks for spotting that, Gunther.

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



JSR 168 and Struts

2003-08-29 Thread Clay Richardson
I apologize if anyone has already asked this question, but I searched
the board and didn't see it.  Also, I tried the user forum first, but
figured maybe this was more appropriate.

 

JSR 168 has the following line in it (Section PLT.16.3):

 

Servlets and JSPs included from portlets should not use the servlet
RequestDispatcher forward method as its behavior may be
non-deterministic.

 

I am no expert on Struts, although I have used it quite a bit.  It seems
that if I wanted to wrap my Struts app in a Portlet and access various
actions through the PortletRequestDispatcher (the most logical
approach), I would run afoul of this warning.

 

Lacking an implementation to test my hypothesis (*$# IBM legal
department), I am unsure whether this actually fails or not.  My gut
instinct is that it probably wouldn't, but that it may not be reliable
across implementations of servlet and portlet containers.  

 

I wanted to get some thoughts from the Struts community about this
possible issue.  Also, I wanted to know what the impact would be of
using RequestDispatcher's include method instead?  Or at least providing
the facility to portlet developers?

 

I apologize if I have wrongly assumed anything in my question.  This is
my best estimate based on what I have read.

 

Thanks,

 

 

Clay Richardson

 

 

W. Clay Richardson

Adjunct Professor of Computer Science

Northern Virginia Graduate Center

Virginia Polytechnic Institute and State University

 

Oh, and how is education supposed to make me feel smarter?  Besides,
every time I learn something new, it pushes some old stuff out of my
brain.  Remember when I took that home wine-making course and I forgot
how to drive? - Homer J. Simpson

 

 

 

 



RE: JSR 168 and Struts

2003-08-29 Thread Rick Hightower
Regarding: Lacking an implementation to test my hypothesis (*$# IBM legal
department), I am unsure whether this actually fails or not.  My gut
instinct is that it probably wouldn't, but that it may not be reliable
across implementations of servlet and portlet containers.

Jaco Portal Server is a Java portal server which is compliant with the
Portlet Specification (JSR-168).
 
http://pharos.inria.fr/Java/display.jsp?id=c_14701

I have a client that is mixing Portlets and Struts. I am not an expert on
Portlets. 

They did a lot of research on the best ways to mix the two technologies
(white papers, prototypes, etc.). 



Rick Hightower
Chief Technology Officer
Trivera Technologies
http://www.triveratech.com
520 290 6855 (Phone)
520 977 8605 (Mobile)
 

-Original Message-
From: Clay Richardson [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 28, 2003 9:05 PM
To: [EMAIL PROTECTED]
Subject: JSR 168 and Struts

I apologize if anyone has already asked this question, but I searched
the board and didn't see it.  Also, I tried the user forum first, but
figured maybe this was more appropriate.

 

JSR 168 has the following line in it (Section PLT.16.3):

 

Servlets and JSPs included from portlets should not use the servlet
RequestDispatcher forward method as its behavior may be
non-deterministic.

 

I am no expert on Struts, although I have used it quite a bit.  It seems
that if I wanted to wrap my Struts app in a Portlet and access various
actions through the PortletRequestDispatcher (the most logical
approach), I would run afoul of this warning.

 

Lacking an implementation to test my hypothesis (*$# IBM legal
department), I am unsure whether this actually fails or not.  My gut
instinct is that it probably wouldn't, but that it may not be reliable
across implementations of servlet and portlet containers.  

 

I wanted to get some thoughts from the Struts community about this
possible issue.  Also, I wanted to know what the impact would be of
using RequestDispatcher's include method instead?  Or at least providing
the facility to portlet developers?

 

I apologize if I have wrongly assumed anything in my question.  This is
my best estimate based on what I have read.

 

Thanks,

 

 

Clay Richardson

 

 

W. Clay Richardson

Adjunct Professor of Computer Science

Northern Virginia Graduate Center

Virginia Polytechnic Institute and State University

 

Oh, and how is education supposed to make me feel smarter?  Besides,
every time I learn something new, it pushes some old stuff out of my
brain.  Remember when I took that home wine-making course and I forgot
how to drive? - Homer J. Simpson

 

 

 

 



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



DO NOT REPLY [Bug 21465] - Enhancement of the html:link tag

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21465.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21465

Enhancement of the html:link tag

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |



--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 09:46 ---
I do not quite understand why the resolution is wontfix, it is fixed already.
It just has to be added to the next release.

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



RE: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug 22519] - Allow multiple MessageResources files to be loaded under one key]

2003-08-29 Thread Andrew Hill
Yeh, I thought it was hilarious when I unwittingly clicked the link and got
bombarded with all those windows and the silly jingle! (Mind you I am easily
entertained ;-) and the guy who sits next to me thought it pretty darn
funny too...


-Original Message-
From: Brandon Goodin [mailto:[EMAIL PROTECTED]
Sent: Thursday, 28 August 2003 21:39
To: Struts Developers List
Subject: RE: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
22519] - Allow multiple MessageResources files to be loaded under one
key]


You guys need to lighten up. On every comp I have seen this link it was
easily shutdown. James, don't worry about it.

Brandon Goodin

 -Original Message-
 From: James Mitchell [mailto:[EMAIL PROTECTED]
 Sent: Thursday, August 28, 2003 7:19 AM
 To: Struts Developers List
 Subject: Re: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
 22519] - Allow multiple MessageResources files to be loaded under one
 key]


 Ya, I read from a different thread about what happens.  That didn't happen
 to me since I use Mozilla (with pop-ups blocked).

 Sorry about that, I wouldn't have sent it if I had known.


 --
 James Mitchell
 Software Engineer / Struts Evangelist
 http://www.struts-atlanta.org
 770-822-3359
 AIM:jmitchtx



 - Original Message -
 From: Robert Leland [EMAIL PROTECTED]
 To: Struts Developers List [EMAIL PROTECTED]
 Sent: Thursday, August 28, 2003 3:27 AM
 Subject: Re: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
 22519] - Allow multiple MessageResources files to be loaded under one key]


  James Mitchell wrote:
 
  Someone posted a link on another thread that might actually help in
  situations like this:
  
  http://www.originalicons.com/smile
  
  
  
  Not funny.
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]


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




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


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



Re: When is the next release?

2003-08-29 Thread Ted Husted
So, I'm getting back to work on this now.

I'm reviewing the documentation now, to be sure there aren't any 
dangling issues there before getting on with the usual Bugzilla / 
Changes gauntlet.

Following up on the post to the User list, I'm adding links to the 
Struts Wiki where people can post comments regarding any of the 
documentation pages.

I'm also updating the roadmap with some of the posts we've made here 
regarding Portlets, the Composable RequestProcessor, a Struts Context, 
and Struts 2. Please watch for the CVS updates to see if I've got our 
intentions right =:0)

-Ted.



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


DO NOT REPLY [Bug 22730] - Software caused connection abort: socket write error

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22730.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22730

Software caused connection abort: socket write error

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 13:39 ---
I have since then realize where the problem reside, what was causing the 
socket error to occur is that our Oracle server was shutting down at Night and 
in the mornig when we tried to use the software the error was occuring because 
the established connection in the struts-config.xml did not exist.  Is there a 
way to re-established those connection without stopping and restarting Tomcat? 

Thank you for your help.

Simon

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



Re: JSR 168 and Struts

2003-08-29 Thread BaTien Duong
Clay Richardson wrote:

I apologize if anyone has already asked this question, but I searched
the board and didn't see it.  Also, I tried the user forum first, but
figured maybe this was more appropriate.


JSR 168 has the following line in it (Section PLT.16.3):



Servlets and JSPs included from portlets should not use the servlet
RequestDispatcher forward method as its behavior may be
non-deterministic.
 

Yes, this is one of my concern as well and did not response to this 
question in user group since i have not put enough time in it.

It seems to me that Struts needs to be refactoring to be MVC for 
portlets since portlets can delegate the creation of content to servlet 
and JSP via PortletRequestDispatcher. If there is a proper hook then 
Tiles can still be an intelligent assembling part of the view. Craig is 
the best guy to iron these issues.

BaTien
DBGROUPS



I am no expert on Struts, although I have used it quite a bit.  It seems
that if I wanted to wrap my Struts app in a Portlet and access various
actions through the PortletRequestDispatcher (the most logical
approach), I would run afoul of this warning.


Lacking an implementation to test my hypothesis (*$# IBM legal
department), I am unsure whether this actually fails or not.  My gut
instinct is that it probably wouldn't, but that it may not be reliable
across implementations of servlet and portlet containers.  



I wanted to get some thoughts from the Struts community about this
possible issue.  Also, I wanted to know what the impact would be of
using RequestDispatcher's include method instead?  Or at least providing
the facility to portlet developers?


I apologize if I have wrongly assumed anything in my question.  This is
my best estimate based on what I have read.


Thanks,





Clay Richardson





W. Clay Richardson

Adjunct Professor of Computer Science

Northern Virginia Graduate Center

Virginia Polytechnic Institute and State University



Oh, and how is education supposed to make me feel smarter?  Besides,
every time I learn something new, it pushes some old stuff out of my
brain.  Remember when I took that home wine-making course and I forgot
how to drive? - Homer J. Simpson








 



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


cvs commit: jakarta-struts/doc/userGuide index.xml

2003-08-29 Thread husted
husted  2003/08/29 07:27:25

  Modified:doc  acquiring.xml index.xml learning.xml project.xml
using.xml volunteers.xml
   doc/proposals release-plan_1_2_0.xml workflow.xml
   doc/resources consultants.xml models.xml powered.xml
project.xml
   doc/stylesheets faqs.xsl news.xsl proposals.xsl
resources.xsl struts.xsl userGuide.xsl
   doc/userGuide index.xml
  Log:
  + Routine updates
  
  Revision  ChangesPath
  1.13  +3 -3  jakarta-struts/doc/acquiring.xml
  
  Index: acquiring.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/acquiring.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- acquiring.xml 4 Jul 2003 17:37:32 -   1.12
  +++ acquiring.xml 29 Aug 2003 14:27:24 -  1.13
  @@ -18,7 +18,7 @@
   section name=Acquiring Struts href=Acquiring
   
   p
  -The lastest iproduction release/i of Struts is
  +The latest iproduction release/i of Struts is
   available in a convenient binary distribution and also with complete
   source code. 
   /p
  @@ -34,12 +34,12 @@
   
   li
   a href=http://jakarta.apache.org/site/binindex.cgi;
  -bStruts Binary Distribution - Latest release/b/a
  +bStruts Binary Distribution - Latest stable release/b/a
   /li
   
   li
   a href=http://jakarta.apache.org/site/sourceindex.cgi;
  -bStruts Source Code Distribution - Latest Release/b/a
  +bStruts Source Code Distribution - Latest stable release/b/a
   /li
   
   /ul
  
  
  
  1.46  +10 -10jakarta-struts/doc/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/index.xml,v
  retrieving revision 1.45
  retrieving revision 1.46
  diff -u -r1.45 -r1.46
  --- index.xml 4 Jul 2003 17:37:32 -   1.45
  +++ index.xml 29 Aug 2003 14:27:24 -  1.46
  @@ -34,17 +34,17 @@
   a 
href=http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/web-tier/web-tier5.html;
   bModel-View-Controller/b/a (MVC) design paradigm.
   /p
  +
   p
  -Struts provides its own bController/b component and integrates with
  -a href=userGuide/preface.html#layersother technologies/a to provide 
  -the Model and the View.
  -For the bModel/b, Struts can interact with any 
  -a href=resources/models.htmlstandard data access technology/a, 
  -including Enterprise Java Beans, JDBC, and Object Relational Bridge.
  -For the bView/b, Struts works well with JavaServer Pages,
  -including a href=./faqs/kickstart.html#jsfJSTL and JSF/a,
  -as well as Velocity Templates, XSLT, and
  -a href=resources/views.htmlother presentation systems/a.
  +Struts provides its own bController/b component and integrates with a 
href=userGuide/preface.html#layers
  +other technologies/a to provide the Model and the View.
  +For the bModel/b, Struts can interact with standard a 
href=resources/models.htmldata access
  +technologies/a, like Enterprise Java Beans and JDBC, as well as most any 
third-party packages, like
  +Hibernate, iBATIS, or Object Relational Bridge.
  +For the bView/b, Struts works well with JavaServer Pages, including
  +a href=./faqs/kickstart.html#jsfJSTL and JSF/a, as well as Velocity 
Templates, XSLT, and
  +a href=resources/views.htmlother presentation systems
  +/a.
   /p
   
   p
  
  
  
  1.11  +42 -21jakarta-struts/doc/learning.xml
  
  Index: learning.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/learning.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- learning.xml  26 Jul 2003 03:56:26 -  1.10
  +++ learning.xml  29 Aug 2003 14:27:24 -  1.11
  @@ -62,13 +62,14 @@
   /p
   
   p
  -Our bDeveloper Guides/b are detailed technical references to the 
  -extensions and components provided in the Struts distribution. 
  -Included are package overviews and API referencea for each of the Struts 
  -taglibs, along with guides to the Struts Utilities and the Struts 
  -Validator. 
  -The Developer Guides are designed as a day-to-day reference to help you 
  -get the most out of the standard packages.
  +Our bDeveloper Guides/b are detailed technical references to the 
extensions and components provided in the
  +Struts distribution.
  +Included are package overviews and API reference for each of the Struts 
taglibs, along with guides to the
  +Struts Utilities and the Struts Validator.
  +The Developer Guides are 

cvs commit: jakarta-struts/doc status.xml

2003-08-29 Thread husted
husted  2003/08/29 07:27:09

  Modified:doc  status.xml
  Log:
  + Add draft of 1.x.x whiteboard
  
  Revision  ChangesPath
  1.34  +81 -35jakarta-struts/doc/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- status.xml11 Aug 2003 11:34:39 -  1.33
  +++ status.xml29 Aug 2003 14:27:09 -  1.34
  @@ -45,9 +45,14 @@
   
   ul
   lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;product=Strutsamp;order=%27Importance%27;Open
 reports/a/li
  -lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;order=%27Importance%27;Open
 problem reports/a/li
  -lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_severity=Enhancementamp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;order=%27Importance%27;Open
 enhancement requests/a/li
  -lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVEDamp;resolution=LATERamp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;order=%27Importance%27;Reports
 to be handled LATER/a/li
  +lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;bug_severity=Normalamp;bug_severity=Minoramp;email1=amp;emailtype1=substringamp;emailassigned_to1=1amp;email2=amp;emailtype2=substringamp;emailreporter2=1amp;bugidtype=includeamp;bug_id=amp;changedin=amp;votes=amp;chfieldfrom=amp;chfieldto=Nowamp;chfieldvalue=amp;product=Strutsamp;short_desc=amp;short_desc_type=allwordssubstramp;long_desc=amp;long_desc_type=allwordssubstramp;bug_file_loc=amp;bug_file_loc_type=allwordssubstramp;keywords=amp;keywords_type=anywordsamp;field0-0-0=noopamp;type0-0-0=noopamp;value0-0-0=amp;cmdtype=doitamp;order=%27Importance%27;Open
 problem reports/a
  +ul
  +lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;product=Strutsamp;bug_severity=Blockeramp;bug_severity=Criticalamp;bug_severity=Majoramp;order=%27Importance%27;major
 problem reports/a/li
  +lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;product=Strutsamp;bug_severity=Blockeramp;bug_severity=Normalamp;bug_severity=Minoramp;order=%27Importance%27;minor
 problem reports/a/li
  +/ul
  +/li
  +lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;product=Strutsamp;bug_severity=Enhancementamp;order=%27Importance%27;Open
 enhancement reports/a/li
  +lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVEDamp;resolution=LATERamp;resolution=REMINDamp;product=Strutsamp;order=%27Importance%27;Reports
 to be handled LATER/a/li
   

RE: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug 22519] - Allow multiple MessageResources files to be loaded under one key]

2003-08-29 Thread Rick Hightower
I instant messaged the link to my boss. We laughed about it as well.
Then I showed my wife and sister-in-law. My wife didn't think it was funny.
I enjoyed it a little too much.

Rick Hightower
Chief Technology Officer
Trivera Technologies
http://www.triveratech.com
520 290 6855 (Phone)
520 977 8605 (Mobile)
 

-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 29, 2003 4:53 AM
To: Struts Developers List
Subject: RE: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
22519] - Allow multiple MessageResources files to be loaded under one key]

Yeh, I thought it was hilarious when I unwittingly clicked the link and got
bombarded with all those windows and the silly jingle! (Mind you I am easily
entertained ;-) and the guy who sits next to me thought it pretty darn
funny too...


-Original Message-
From: Brandon Goodin [mailto:[EMAIL PROTECTED]
Sent: Thursday, 28 August 2003 21:39
To: Struts Developers List
Subject: RE: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
22519] - Allow multiple MessageResources files to be loaded under one
key]


You guys need to lighten up. On every comp I have seen this link it was
easily shutdown. James, don't worry about it.

Brandon Goodin

 -Original Message-
 From: James Mitchell [mailto:[EMAIL PROTECTED]
 Sent: Thursday, August 28, 2003 7:19 AM
 To: Struts Developers List
 Subject: Re: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
 22519] - Allow multiple MessageResources files to be loaded under one
 key]


 Ya, I read from a different thread about what happens.  That didn't happen
 to me since I use Mozilla (with pop-ups blocked).

 Sorry about that, I wouldn't have sent it if I had known.


 --
 James Mitchell
 Software Engineer / Struts Evangelist
 http://www.struts-atlanta.org
 770-822-3359
 AIM:jmitchtx



 - Original Message -
 From: Robert Leland [EMAIL PROTECTED]
 To: Struts Developers List [EMAIL PROTECTED]
 Sent: Thursday, August 28, 2003 3:27 AM
 Subject: Re: [OT] As the Struts world turns [was: Re: DO NOT REPLY [Bug
 22519] - Allow multiple MessageResources files to be loaded under one key]


  James Mitchell wrote:
 
  Someone posted a link on another thread that might actually help in
  situations like this:
  
  http://www.originalicons.com/smile
  
  
  
  Not funny.
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]


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




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


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



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



DO NOT REPLY [Bug 22812] New: - requiredif failed if it is not the first criteria

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22812.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22812

requiredif failed if it is not the first criteria

   Summary: requiredif failed if it is not the first criteria
   Product: Struts
   Version: 1.1 Final
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Validator Framework
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I have a field check like this:

  field property=periodTo depends=requiredif,date

  arg0 key=clientSearchArticleForm.periodTo/
  var
var-namefield[0]/var-name
var-valuedateType/var-value
  /var
  var
var-namefieldIndexed[0]/var-name
var-valuetrue/var-value
  /var
  var
var-namefieldTest[0]/var-name
var-valueEQUAL/var-value
  /var
  var
var-namefieldValue[0]/var-name
var-value5/var-value
  /var
  var
var-namedatePatternStrict/var-name
var-value/MM/dd/var-value
  /var
  /field

This will success as the requiredif is the first criteria. however, if I 
change the first line 
From:

  field property=periodTo depends=requiredif,date
  (requiredif is the first criteria)
To:
  field property=periodTo depends=date, requiredif
  (requiredif is the second criteria)

It will fail to check.

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



DO NOT REPLY [Bug 22814] New: - bug on linkTag

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22814.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22814

bug on linkTag

   Summary: bug on linkTag
   Product: Struts
   Version: 1.1 Final
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Custom Tags
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


use this tag in my jsp page (detailModif.jsp) :

html:link 
href=javascript:setAction('modif');
name=detailTravelForm 
bean:message key=link.edition /
/html:link

and get this error :

javax.servlet.jsp.JspException: Cannot cast to Map for name=detailTravelForm 
property=null scope=null Start server side stack trace: 
javax.servlet.jsp.JspException: Cannot cast to Map for name=detailTravelForm 
property=null scope=null at 
org.apache.struts.util.RequestUtils.computeParameters(RequestUtils.java:290) at 
org.apache.struts.taglib.html.LinkTag.calculateURL(LinkTag.java:462) at 
org.apache.struts.taglib.html.LinkTag.doStartTag(LinkTag.java:353) at 
jsp_servlet._travel.__detailModif._jspService(__detailModif.java:299)

null property seems to be the reason (not mandatory in tld file).

Thanks.

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



DO NOT REPLY [Bug 22309] - bean:include extending for sticky cluster node

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22309.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22309

bean:include extending for sticky cluster node





--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 17:19 ---
Looks good.  Thanks!!!

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



Re: Action.setLocale, fail early?

2003-08-29 Thread David Graham
--- Rick Hightower [EMAIL PROTECTED] wrote:
 From Nightly build.
 
  
 
 protected void setLocale(HttpServletRequest request, Locale locale)
 {
 
  
 
 HttpSession session = request.getSession();
 
 if (locale == null) {
 
 locale = Locale.getDefault();
 
 }
 
 session.setAttribute(Globals.LOCALE_KEY, locale);
 
  
 
 }
 
  
 
 Comments on setLocale from Action..
 
  
 
 If the locale is null, wouldn't it be better for the default to come
 from
 the request as in request.getLocale(), which is the behavior of the tags
 when the Locale at Globals.LOCALE_KEY is not in session scope.

What about the situation where you pass in null to clear the Locale from
the session?  The method currently assumes that passing null means use a
default instead of trusting the user that what they passed in is what
they want in the session.  Maybe passing null should mean that any Locale
in the session is to be removed.  The saveErrors() and saveMessages()
methods behave that way so it's inconsistent for setLocale() to behave
differently.

Regardless, changing this now would break backwards compatibility but it's
something to think about in 2.x.

David

 
  
 
 Better Yet. Also if they call setLocale, shouldn't the local object be
 non-null. My personal opinion on this stuff is that it should explode
 with
 an illegal argument exception. (I remember a bug report that talked
 about
 Struts quietly handing illegal situations)
 
  
 
 if (locale == null) {
 
 throw new java.lang.IllegalArgumentException(Locale was
 null);
 
 }
 
  
 
  
 
 As a developer when I misuse an API, I like to see it fail quickly. This
 way
 I don't have to spend a lot of time debugging where I went wrong. Die
 early
 and often in development not during QA or. gulp.. Production!
 
  
 
  
 
  
 
  
 
 Rick Hightower
 
 Chief Technology Officer
 
 Trivera Technologies
 
 http://www.triveratech.com
 
 520 290 6855 (Phone)
 
 520 977 8605 (Mobile)
 
  
 
  
 
 


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



RE: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] - Enhancement of the html:link tag)

2003-08-29 Thread David Graham
--- Rick Hightower [EMAIL PROTECTED] wrote:
 I am not a voter, but I think
 
 Comments below...
 
 
 Rick Hightower
 Chief Technology Officer
 Trivera Technologies
 http://www.triveratech.com
 520 290 6855 (Phone)
 520 977 8605 (Mobile)
  
 
 -Original Message-
 From: Steve Raeburn [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, August 27, 2003 9:20 PM
 To: Struts Developers List
 Subject: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] -
 Enhancement of the html:link tag)
 
 I'm not singling Vic out for this (honest) but...
 
 The standard advice we are now giving everyone is use JSTL, which I
 wholeheartedly agree with and have said myself. However, I think we need
 to
 make sure that we still adequately support non-JSTL solutions and
 continue
 to consider bug fixes/enhancements to Struts tags EVEN where it would
 duplicate JSTL functionality because Struts still supports JSP
 1.1/Servlet2.2.
 
  I don't think fixing non-JSTL tags should take priority. I
 think deprecated tags like logic:iterate, and their ilk should receive
 very
 little attention. BTW I am going to make a concerted effort to
 contribute to
 this project. Please excuse me while I am new if I make any snafu. (I
 have
 some stuff and ideas in the works. Mostly bug fix type ideas.)
 
 I haven't considered whether this particular enhancement would fall into
 the
 category of something we should do, it just prompted me to raise the
 issue.
 
 If we've reached the stage where the recommendations we are making
 *require*
 JSTL, then I think it's time to be honest about the required platform
 for
 Struts and up it to 1.1/2.3
 
  I think Struts 1.2 and higher should *require* JSTL
 tags,
 and overlapping Struts tags should be deprecated (aren't they already).
 If
 this is not feasible for Struts 1.2, then Struts 1.3 or 1.5 or
 1.whatever.


What's the rush?  Why does Struts 1.x need to require JSTL?  They are
independent technologies that can be used together if the developer
chooses.  The Struts tags work in their current form and I agree that
enhancing them is time better spent elsewhere.  But fixing bugs is still
necessary so that the tags are as stable as possible for the people still
stuck on Servlet 2.2 containers.

IMO, Struts 2.x should attempt to get out of the taglib business
altogether.  Until then, we should just let the tags be and maintain
Struts 1.x as Servlet 2.2 minimum requirement.

David


 
 Use JSTL instead of Struts-Equivalent Tags
   Use core:out instead of bean:write 
   Use core:set instead of bean:define 
   Use JSTL core:if and core:forEach instead of Struts logic:*
   Use frmt tags in place of bean:message (if possible)
   Use JSTL EL Engine in Your Own Custom Tags
 
 I don't know how well the JSTL i18n support plays with the Struts i18n
 support as I am only familiar with the latter and not the former at
 least
 not on a carnal level.
 
 Steve
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
  Sent: August 27, 2003 8:28 PM
  To: [EMAIL PROTECTED]
  Subject: DO NOT REPLY [Bug 21465] - Enhancement of the html:link tag
 
 
  DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
  RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21465.
  ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
  INSERTED IN THE BUG DATABASE.
 
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21465
 
  Enhancement of the html:link tag
 
  [EMAIL PROTECTED] changed:
 
 What|Removed |Added
  --
  --
   Status|ASSIGNED|RESOLVED
   Resolution||WONTFIX
 
 
 
  --- Additional Comments From [EMAIL PROTECTED]
  2003-08-28 03:27 ---
  You can/should use JSTL instead.
  .V
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



Re: Improve JSTL i18n support with Struts

2003-08-29 Thread David Graham
This all seems reasonable but needs to wait for Struts 2.x.  1.x must
remain on Servlet 2.2 to maintain backwards compatibility.  IMO, 2.x is
the best time to change the Servlet level because we'll be breaking
compatibility at that time anways.

David

--- Rick Hightower [EMAIL PROTECTED] wrote:
 I’d like to see Struts play nice with JSTL i18n support.
 
 I have a suggestion along these lines. (This is prelim. I am going to
 write
 some tests and do some prototyping but before I do… I’d like to hear if
 there are any thoughts on this).
 
 Currently when you call Action.setLocale you get this:
 
 ...class Action...
     protected void setLocale(HttpServletRequest request, Locale locale)
 {
  
     HttpSession session = request.getSession();
     if (locale == null) {
     locale = Locale.getDefault();
     }
     session.setAttribute(Globals.LOCALE_KEY, locale);
  
     }
 
 I am suggesting this (for the release that embraces JSTL…. Struts 1.3 or
 1.5).
 
 import javax.servlet.jsp.jstl.core.Config; //get this guy to use its
 Locale
 key as well
 ...class Action...
     protected void setLocale(HttpServletRequest request, Locale locale)
 {
  
     HttpSession session = request.getSession();
     if (locale == null) {
     locale = Locale.getDefault();//Don’t agree with this, but
 that
 is a different story…
     }
     session.setAttribute(Globals.LOCALE_KEY, locale);
 session.setAttribute(Config.FMT_LOCALE, locale); //See
 this…. See this…. See this…
     }
 
 The Config.FMT_LOCALE is similar to the Globals.LOCALE_KEY except that
 it is
 for the JSTL tags, e.g.,
 
 fmt:message key=title /
 
 This is one possibility and the one that takes the least amount of
 effort.
 Another possibility is to change all struts i18n tags to use
 Config.FMT_LOCALE instead of Globals.LOCALE_KEY, which might be bad
 because
 it would break existing projects.
 
 I am going to write a prototype along these lines in the near future. I
 need
 to test to see if fmt:message will work with Strut’s resource bundles.
 (I am
 not sure it they will or not... I think they will with a little arm
 twisting. I am still a little ignorant on the details... I got the big
 picture... just not all the details.). Any suggestions from you i18n
 gurus
 would be nice or if someone already started this... clue me in so I
 don't
 waste time.
 
 This could be a first step in getting rid of our good friend
 bean:message
 and replacing him with fmt:message (or at least deprecating him a bit).
 :(
 
 Don’t worry. I will add this to the Bugzilla feature request as soon as
 I
 test it.
 
 Rick Hightower
 Chief Technology Officer
 Trivera Technologies
 http://www.triveratech.com
 520 290 6855 (Phone)
 520 977 8605 (Mobile)
  
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



RE: Action.setLocale, fail early?

2003-08-29 Thread Rick Hightower
Good point. I did not think of that. (I guess I won't be adding an
enhancement request).

Did you get a chance to look at the i18N/JSTL support email?

Rick Hightower
Chief Technology Officer
Trivera Technologies
http://www.triveratech.com
520 290 6855 (Phone)
520 977 8605 (Mobile)
 

-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 29, 2003 10:19 AM
To: Struts Developers List
Subject: Re: Action.setLocale, fail early?

--- Rick Hightower [EMAIL PROTECTED] wrote:
 From Nightly build.
 
  
 
 protected void setLocale(HttpServletRequest request, Locale locale)
 {
 
  
 
 HttpSession session = request.getSession();
 
 if (locale == null) {
 
 locale = Locale.getDefault();
 
 }
 
 session.setAttribute(Globals.LOCALE_KEY, locale);
 
  
 
 }
 
  
 
 Comments on setLocale from Action..
 
  
 
 If the locale is null, wouldn't it be better for the default to come
 from
 the request as in request.getLocale(), which is the behavior of the tags
 when the Locale at Globals.LOCALE_KEY is not in session scope.

What about the situation where you pass in null to clear the Locale from
the session?  The method currently assumes that passing null means use a
default instead of trusting the user that what they passed in is what
they want in the session.  Maybe passing null should mean that any Locale
in the session is to be removed.  The saveErrors() and saveMessages()
methods behave that way so it's inconsistent for setLocale() to behave
differently.

Regardless, changing this now would break backwards compatibility but it's
something to think about in 2.x.

David

 
  
 
 Better Yet. Also if they call setLocale, shouldn't the local object be
 non-null. My personal opinion on this stuff is that it should explode
 with
 an illegal argument exception. (I remember a bug report that talked
 about
 Struts quietly handing illegal situations)
 
  
 
 if (locale == null) {
 
 throw new java.lang.IllegalArgumentException(Locale was
 null);
 
 }
 
  
 
  
 
 As a developer when I misuse an API, I like to see it fail quickly. This
 way
 I don't have to spend a lot of time debugging where I went wrong. Die
 early
 and often in development not during QA or. gulp.. Production!
 
  
 
  
 
  
 
  
 
 Rick Hightower
 
 Chief Technology Officer
 
 Trivera Technologies
 
 http://www.triveratech.com
 
 520 290 6855 (Phone)
 
 520 977 8605 (Mobile)
 
  
 
  
 
 


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



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



cvs commit: jakarta-struts/doc status.xml

2003-08-29 Thread husted
husted  2003/08/29 09:49:40

  Modified:doc  status.xml
  Log:
  + Add draft of 1.x.x whiteboard
  
  Revision  ChangesPath
  1.35  +21 -256   jakarta-struts/doc/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- status.xml29 Aug 2003 14:27:09 -  1.34
  +++ status.xml29 Aug 2003 16:49:40 -  1.35
  @@ -142,17 +142,35 @@
   ul
   liMove to Commons Resources/li
   liMove taglibs into separate JARs/li
  -liConsider new Request Processor, if available/li
  +liEnhance all configs to extend one configuration element 
from another,
  +as is done with Tiles Definitions/li
   /ul
   /li
   
   liStruts 1.4.x -
   More substantial enhancements to product base
   ul
  +liConsider new Request Processor, if available/li
   liConsider migration to an Action context/li
   /ul
   /li
   
  +liOther potential enhancements for the 1.x.x series
  +ul
  +liMove to a 
href=http://xml.apache.org/forrest/;Forrest/a or a 
href=http://maven.apache.org/;Maven/a for project management/li
  +liConsider adopting several popular extensions, including:
  +ul
  +lia href=http://sslext.sourceforge.net/;SSL Ext/a/li
  +lia 
href=http://strutstestcase.sourceforge.net/;TestCase/a/li
  +lia href=http://stxx.sourceforge.net;Stxx/a (XLST)/li
  +lia 
href=http://www.livinglogic.de/Struts/;Workflow/a/li
  +lia href=http://struts.sf.net;Cocoon Plugin/a/li
  +lia href=http://struts.sf.net;Scriptable Actions using 
BSF/a (Bean Scripting Framework)/li
  +/ul
  +/li
  +/ul
  +/li
  +
   /ul
   
 !--
  @@ -185,16 +203,6 @@
   /li
   
   li
  -Better support for XLST technology (e.g. stxx)
  -/li
  -
  -li
  -Better support for unit testing within the framework (e.g.
  -a href=http://sourceforge.net/projects/strutstestcase/;Struts 
TestCase/a)
  -or perhaps even a distinct unit testing framework.
  -/li
  -
  -li
   Encouraging the use of a 
href=http://sourceforge.net/projects/xdoclet/;XDoclet/a and other code generation 
technologies to streamline development.
   /li
   
  @@ -295,252 +303,9 @@
   
   /section
   
  -section href=releases name=Release Guidelines
  -
  -p
  -A a href=http://jakarta.apache.org/commons/versioning.html;point 
release/a
  -should be made before and after any product change that is not a 
fully-compatible change
  -(see link). This includes moving a dependency from an internal package 
to an external product,
  -including products distributed through the Jakarta Commons.
  -We should place any fully-compatible changes in the hands of the 
community
  -before starting on a change that is only interface or 
external-interface compatible.
  -/p
  -p
  -A fully-compatible point release does not always need a preview beta 
or milestone release.
  -If appropriate, a Release Candidate can be cut, uploaded to the Release 
Manager's home directory
  -on cvs.apache.org (~/public_html), and voted to be released to the 
general public from there.
  -/p
  -
  -p
  -Any release should follow the same general process used by the Jakarta 
Commons
  -and the Apache HTTP Server project.
  -/p
  -
  -ul
  -li
  - a href=http://jakarta.apache.org/commons/releases/;Releasing 
Common Components/a
  -/li
  -li
  -a 
href=http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases;Signing a release 
version/a
  -ul
  -li
  -smallThe MD5 tool is installed on daedalus, and you can 
create the digests for Struts releases there./small
  -/li
  -/ul
  -/li
  -li
  -a href=http://httpd.apache.org/dev/release.html;Apache HTTPD 
Server Release Guidelines/a
  -/li
  -/ul
  -
  -p
  -Additional remarks:
  -/p
  -
  -ul
  -li
  -Remember to update the a href=news/index.htmlStatus section of 
the News page/a when cutting any 

cvs commit: jakarta-struts/doc/resources examples.xml extensions.xml tools.xml tutorials.xml views.xml

2003-08-29 Thread husted
husted  2003/08/29 09:50:09

  Modified:doc  learning.xml project.xml volunteers.xml
   doc/resources examples.xml extensions.xml tools.xml
tutorials.xml views.xml
  Log:
  Routine updates
  
  Revision  ChangesPath
  1.12  +2 -2  jakarta-struts/doc/learning.xml
  
  Index: learning.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/learning.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- learning.xml  29 Aug 2003 14:27:24 -  1.11
  +++ learning.xml  29 Aug 2003 16:50:08 -  1.12
  @@ -220,10 +220,10 @@
   /p
   
   p
  -The a 
href=http://nagoya.apache.org/wiki/apachewiki.cgi?StrutsProjectPages;Struts Wiki/a 
is a relatively
  +The Struts a 
href=http://nagoya.apache.org/wiki/apachewiki.cgi?StrutsProjectPages;bWiki/b/a 
is a relatively
   new addition to our documentation.
   Any member of the community (that means you!) is invited to post new 
material to the Wiki.
  -However, the Wiki is not the place to ask questions of your own.
  +However, the Wiki is not the place to ask incidental questions.
   bAll support questions should be directed to the a href=ListsStruts 
User list/a or
   a href=resources/resources.htmlother support forum/a/b.
   /p
  
  
  
  1.40  +4 -0  jakarta-struts/doc/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/project.xml,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- project.xml   29 Aug 2003 14:27:24 -  1.39
  +++ project.xml   29 Aug 2003 16:50:08 -  1.40
  @@ -34,6 +34,10 @@
name=Roadmap
   href=status.html
   /
  +item
  + name=Releases
  +href=releases.html
  +/
   /menu
   
   menu name=Community
  
  
  
  1.31  +10 -17jakarta-struts/doc/volunteers.xml
  
  Index: volunteers.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/volunteers.xml,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- volunteers.xml29 Aug 2003 14:27:24 -  1.30
  +++ volunteers.xml29 Aug 2003 16:50:08 -  1.31
  @@ -12,29 +12,22 @@
   section name=Community Support href=support
   
   p
  -As of June 25, 2003, there were 2744 subscribers to STRUTS-USER (plus 
an unknown
  -number who read it through newsfeed mirrors).  It's the largest
  -user mailing list at Jakarta, exceeding TOMCAT-USER that has ~2400.
  +In June 2003, there were nearly 2800 subscribers to STRUTS-USER.
  +It's the largest user mailing list at Jakarta, exceeding the 
TOMCAT-USER list of about 2400 subscribers.
  +In addition to the regular subscribers, an unknown number of developers 
read the lists through newsfeed
  +mirrors and through several list archives.
   /p
   
   p
  -Since Apache now uses a mirroring system, the precise number of 
downloads counts
  -is unknown, but in the Summer of 2002, Struts was averaging
  -8500 downloads per month. In liklihood, we well exceed that now.
  +According to recently released
  +a 
href=http://www.apache.org/~vgritsenko/stats/projects/struts;statistics/a, Struts 
downloads range
  +between 10,000 and 30,000 a week, roughly the same as Jakarta Tomcat.
   /p
   
   p
  -Some high level traffic statistics for the Struts web site
  -are
  -a href=http://www.apache.org/~vgritsenko/stats/index.html;
  -now available./a
  -/p
  -
  -p
  -There are a great number of third-party extensions are available for 
Struts,
  -along with an equally vast number of articles and books.
  -We try to list as many of these as we can in the
  -a href=resources/index.htmlResources area/a.
  +There are a great number of third-party extensions are available for 
Struts, along with an equally vast
  +number of articles and several books
  +We try to list as many of these as we can in the a 
href=resources/index.htmlResources area/a.
   /p
   
   /section
  
  
  
  1.7   +1 -1  jakarta-struts/doc/resources/examples.xml
  
  Index: examples.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/resources/examples.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- examples.xml  12 Aug 2003 09:50:54 -  1.6
  

RE: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] - Enhancement of the html:link tag)

2003-08-29 Thread Craig R. McClanahan
On Fri, 29 Aug 2003, David Graham wrote:

 Date: Fri, 29 Aug 2003 10:26:54 -0700 (PDT)
 From: David Graham [EMAIL PROTECTED]
 Reply-To: Struts Developers List [EMAIL PROTECTED],
  [EMAIL PROTECTED]
 To: Struts Developers List [EMAIL PROTECTED]
 Subject: RE: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465]
 - Enhancement of the html:link tag)

 --- Rick Hightower [EMAIL PROTECTED] wrote:
  I am not a voter, but I think
 
  Comments below...
 
 
  Rick Hightower
  Chief Technology Officer
  Trivera Technologies
  http://www.triveratech.com
  520 290 6855 (Phone)
  520 977 8605 (Mobile)
 
 
  -Original Message-
  From: Steve Raeburn [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, August 27, 2003 9:20 PM
  To: Struts Developers List
  Subject: Support for non-JSTL tags (was RE: DO NOT REPLY [Bug 21465] -
  Enhancement of the html:link tag)
 
  I'm not singling Vic out for this (honest) but...
 
  The standard advice we are now giving everyone is use JSTL, which I
  wholeheartedly agree with and have said myself. However, I think we need
  to
  make sure that we still adequately support non-JSTL solutions and
  continue
  to consider bug fixes/enhancements to Struts tags EVEN where it would
  duplicate JSTL functionality because Struts still supports JSP
  1.1/Servlet2.2.
 
   I don't think fixing non-JSTL tags should take priority. I
  think deprecated tags like logic:iterate, and their ilk should receive
  very
  little attention. BTW I am going to make a concerted effort to
  contribute to
  this project. Please excuse me while I am new if I make any snafu. (I
  have
  some stuff and ideas in the works. Mostly bug fix type ideas.)
 
  I haven't considered whether this particular enhancement would fall into
  the
  category of something we should do, it just prompted me to raise the
  issue.
 
  If we've reached the stage where the recommendations we are making
  *require*
  JSTL, then I think it's time to be honest about the required platform
  for
  Struts and up it to 1.1/2.3
 
   I think Struts 1.2 and higher should *require* JSTL
  tags,
  and overlapping Struts tags should be deprecated (aren't they already).
  If
  this is not feasible for Struts 1.2, then Struts 1.3 or 1.5 or
  1.whatever.


 What's the rush?  Why does Struts 1.x need to require JSTL?  They are
 independent technologies that can be used together if the developer
 chooses.  The Struts tags work in their current form and I agree that
 enhancing them is time better spent elsewhere.  But fixing bugs is still
 necessary so that the tags are as stable as possible for the people still
 stuck on Servlet 2.2 containers.


I don't think it's even necessary to *deprecate* the old tags.  There are
lots of existing apps that use them, and it is rather unfriendly to force
people to change all their pages to update to a later Struts build.

We should be fixing bugs in the existing tags ... but I don't see much use
in adding a whole bunch of new ones.

I'm -1 on making Struts 1.2.x dependent on Servlet 2.3 / JSP 1.2.  If
we're going to maintain backwards compatibility in this sequence, we need
to maintain the same base platform as well.

 IMO, Struts 2.x should attempt to get out of the taglib business
 altogether.  Until then, we should just let the tags be and maintain
 Struts 1.x as Servlet 2.2 minimum requirement.

Earlier, we had talked about using Servlet 2.4 and JSP 2.0 as the basis
for Struts 2.x, and I still like that approach, because these specs are
close to being finalized, and will certainly be final before we need them.

The interesting part of this is going to be the timing -- I would
anticipate we'll continue doing production quality releases of 1.2.x,
while starting to do some experimental builds in 2.x, in overlapping
times.  But that's dependent on what the committers are willing and able
to work on, of course.


 David

Craig (whose time will free up later on as JavaServer Faces gets done)

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



cvs commit: jakarta-struts/doc releases.xml

2003-08-29 Thread husted
husted  2003/08/29 09:49:28

  Added:   doc  releases.xml
  Log:
  + Create releases page from lower portion of status page.
  
  Revision  ChangesPath
  1.1  jakarta-struts/doc/releases.xml
  
  Index: releases.xml
  ===
  ?xml version=1.0?
  document url=./releases.xml
  
  !--
  //  78
  --
  
  properties
  titleRelease Guidelines - The Apache Struts Web Application Framework/title
  authorTed Husted/author
  /properties
  
  body
  chapter href=status name=Release Guidelines
  
  section href=status name=Release Guidelines
  
  p
  This document describes the Struts a href=#Releasesrelease process/a and 
our a href=#Codingcoding
  conventions/a.
  /p
  
  /section
  
  section href=Releases name=Release Guidelines
  
  p
  A a href=http://jakarta.apache.org/commons/versioning.html;point 
release/a
  should be made before and after any product change that is not a 
fully-compatible change
  (see link). This includes moving a dependency from an internal package 
to an external product,
  including products distributed through the Jakarta Commons.
  We should place any fully-compatible changes in the hands of the 
community
  before starting on a change that is only interface or 
external-interface compatible.
  /p
  p
  A fully-compatible point release does not always need a preview beta 
or milestone release.
  If appropriate, a Release Candidate can be cut, uploaded to the Release 
Manager's home directory
  on cvs.apache.org (~/public_html), and voted to be released to the 
general public from there.
  /p
  
  p
  Any release should follow the same general process used by the Jakarta 
Commons
  and the Apache HTTP Server project.
  /p
  
  ul
  li
   a href=http://jakarta.apache.org/commons/releases/;Releasing 
Common Components/a
  /li
  li
  a 
href=http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases;Signing a release 
version/a
  ul
  li
  smallThe MD5 tool is installed on daedalus, and you can create 
the digests for Struts releases there./small
  /li
  /ul
  /li
  li
  a href=http://httpd.apache.org/dev/release.html;Apache HTTPD 
Server Release Guidelines/a
  /li
  /ul
  
  p
  Additional remarks:
  /p
  
  ul
  li
  Remember to update the a href=news/index.htmlStatus section of 
the News page/a when cutting any milestone.
  For a final release, also update the /doc/project.xml with the 
current release number.
  /li
  li
  The release process can seem daunting when you review it for the 
first time.
  But, essentially, it breaks down into three phases of just a few 
steps each:
  ul
  liBuilding - Bugzilla, dependencies, release notes, JAR 
manifest, licenses, copyrights, and build (using the release target)./li
  liTesting - JUnit, Cactus, web apps (for all supported 
containers). /li
  liDistributing - Checksum, sign, mirror, release, update 
Struts site, update Jakarta site, announce./li
  /ul
  /li
  li
  Our dependencies on external JARs (including Commons JARs) should
  be in line with our own release status.
  Our nightly build can be dependant on another nightly build.
  Our beta can be dependant on another beta,
  but should avoid a dependance on a nightly build.
  Our release candidate can have a dependance on another RC,
  but should not have a dependance on a beta (and certainly bnot/b 
a nightly build).
  Our final release can only have dependencies on other final releases.
  /li
  li
  Use your own discretion as to detail needed by the Release Notes.
  A high-level description of the changes is more important than 
providing uninterpreted detail.
  At a minimum, new features and deprecations should be summarized,
  since these are commonly asked questions.
  Ideally, the release notes should be maintained continuously for the 
nightly build
  so that we do not need to quickly assembled them on the eve of a 
Release.
  /li
  li
  Test building the 

RE: Improve JSTL i18n support with Struts

2003-08-29 Thread Rick Hightower
Okay. No problem. I will still work on this (I need it) maybe I'll just
come up with a Best Practice for using JSTL i18N support with Struts or
something along those lines.

It seems like any JSTL integration is going to wait until Struts 2.0. I
understand the reasoning behind this. It makes a lot of sense to me to wait
till 2.0



//session.setAttribute(Config.FMT_LOCALE, locale);


Rick Hightower
Chief Technology Officer
Trivera Technologies
http://www.triveratech.com
520 290 6855 (Phone)
520 977 8605 (Mobile)
 

-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 29, 2003 10:33 AM
To: Struts Developers List
Subject: Re: Improve JSTL i18n support with Struts

This all seems reasonable but needs to wait for Struts 2.x.  1.x must
remain on Servlet 2.2 to maintain backwards compatibility.  IMO, 2.x is
the best time to change the Servlet level because we'll be breaking
compatibility at that time anways.

David

--- Rick Hightower [EMAIL PROTECTED] wrote:
 I’d like to see Struts play nice with JSTL i18n support.
 
 I have a suggestion along these lines. (This is prelim. I am going to
 write
 some tests and do some prototyping but before I do… I’d like to hear if
 there are any thoughts on this).
 
 Currently when you call Action.setLocale you get this:
 
 ...class Action...
     protected void setLocale(HttpServletRequest request, Locale locale)
 {
  
     HttpSession session = request.getSession();
     if (locale == null) {
     locale = Locale.getDefault();
     }
     session.setAttribute(Globals.LOCALE_KEY, locale);
  
     }
 
 I am suggesting this (for the release that embraces JSTL…. Struts 1.3 or
 1.5).
 
 import javax.servlet.jsp.jstl.core.Config; //get this guy to use its
 Locale
 key as well
 ...class Action...
     protected void setLocale(HttpServletRequest request, Locale locale)
 {
  
     HttpSession session = request.getSession();
     if (locale == null) {
     locale = Locale.getDefault();//Don’t agree with this, but
 that
 is a different story…
     }
     session.setAttribute(Globals.LOCALE_KEY, locale);
 session.setAttribute(Config.FMT_LOCALE, locale); //See
 this…. See this…. See this…
     }
 
 The Config.FMT_LOCALE is similar to the Globals.LOCALE_KEY except that
 it is
 for the JSTL tags, e.g.,
 
 fmt:message key=title /
 
 This is one possibility and the one that takes the least amount of
 effort.
 Another possibility is to change all struts i18n tags to use
 Config.FMT_LOCALE instead of Globals.LOCALE_KEY, which might be bad
 because
 it would break existing projects.
 
 I am going to write a prototype along these lines in the near future. I
 need
 to test to see if fmt:message will work with Strut’s resource bundles.
 (I am
 not sure it they will or not... I think they will with a little arm
 twisting. I am still a little ignorant on the details... I got the big
 picture... just not all the details.). Any suggestions from you i18n
 gurus
 would be nice or if someone already started this... clue me in so I
 don't
 waste time.
 
 This could be a first step in getting rid of our good friend
 bean:message
 and replacing him with fmt:message (or at least deprecating him a bit).
 :(
 
 Don’t worry. I will add this to the Bugzilla feature request as soon as
 I
 test it.
 
 Rick Hightower
 Chief Technology Officer
 Trivera Technologies
 http://www.triveratech.com
 520 290 6855 (Phone)
 520 977 8605 (Mobile)
  
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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



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



cvs commit: jakarta-struts/doc/userGuide index.xml preface.xml

2003-08-29 Thread husted
husted  2003/08/29 13:14:19

  Modified:doc/news index.xml
   doc/proposals release-plan_1_2_0.xml
   doc/resources related.xml related_books.xml resources.xml
sigs.xml taglibs.xml utilities.xml
   doc/userGuide index.xml preface.xml
  Log:
  Routine updates
  
  Revision  ChangesPath
  1.27  +3 -0  jakarta-struts/doc/news/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/news/index.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- index.xml 26 Jul 2003 03:56:24 -  1.26
  +++ index.xml 29 Aug 2003 20:14:19 -  1.27
  @@ -33,6 +33,9 @@
   li
 See the a href=http://cvs.apache.org/viewcvs/jakarta-struts/;Struts 
CVS/a for the current development codebase.
 /li
  +li
  +   See the a href=../releases.htmlRelease Guides/a for our release 
process and coding conventions.
  +/li
   /ul
   
   hr size=1 noshade=/
  
  
  
  1.4   +5 -1  jakarta-struts/doc/proposals/release-plan_1_2_0.xml
  
  Index: release-plan_1_2_0.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/proposals/release-plan_1_2_0.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- release-plan_1_2_0.xml29 Aug 2003 14:27:24 -  1.3
  +++ release-plan_1_2_0.xml29 Aug 2003 20:14:19 -  1.4
  @@ -15,6 +15,10 @@
 /p
   
 p
  +  THIS IS AN UNRATIFIED DRAFT DOCUMENT PROVIDED FOR DISCUSSION PURPOSES 
ONLY!
  +  /p
  +
  +  p
 The objective of the strongStruts 1.2.0/strong release is to 
provide an official version of all the
 changes that have been made to the main trunk of the jakarta-struts 
CVS since the release of Struts 1.1
 Final.
  
  
  
  1.2   +24 -22jakarta-struts/doc/resources/related.xml
  
  Index: related.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/resources/related.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- related.xml   23 Jun 2002 15:08:10 -  1.1
  +++ related.xml   29 Aug 2003 20:14:19 -  1.2
  @@ -10,38 +10,40 @@
   chapter name=Struts Resources href=http://husted.com/struts/resources; 
   
   section name=Other Struts-Related Articles
  -pbWeb DbForms by Joachim Peer/bbr/
  +pbWeb DbForms by Joachim Peer/bbr /
 - a 
href=http://www.onjava.com/lpt/a//onjava/2001/07/18/dbforms.html;http://www.onjava.com/lpt/a//onjava/2001/07/18/dbforms.html/a/p
  -pbExpresso Extends Struts through Integration Roadmap/bbr/
  -  - a 
href=http://www.jcorporate.com/html/products/expresso.html;http://www.jcorporate.com/html/products/expresso.html/a
 br/
  +pbExpresso Extends Struts through Integration Roadmap/bbr /
  +  - a 
href=http://www.jcorporate.com/html/products/expresso.html;http://www.jcorporate.com/html/products/expresso.html/a
 br /
 - a 
href=http://www.jcorporate.com/doc/roadmap.html;http://www.jcorporate.com/doc/roadmap.html/a/p
  -pbDynamic Value Object/b  by raffaele spazzoli br/
  +pbDynamic Value Object/b  by raffaele spazzoli br /
 - a 
href=http://www.theserverside.com/patterns/thread.jsp?thread_id=2722;http://www.theserverside.com/patterns/thread.jsp?thread_id=2722/a/p
  -pbCoarse Grained BMP beans with Dependent Value Objects/b by Floyd 
Marinescubr/
  +pbCoarse Grained BMP beans with Dependent Value Objects/b by Floyd 
Marinescubr /
 - a 
href=http://www.theserverside.com/patterns/depbmp.jsp;http://www.theserverside.com/patterns/depbmp.jsp/a/p
  -pbView Helper/b - Design patternsbr/
  +pbView Helper/b - Design patternsbr /
 - a 
href=http://developer.java.sun.com/developer/restricted/patterns/ViewHelper.html;http://developer.java.sun.com/developer/restricted/patterns/ViewHelper.html/a/p
  -pbRuby Web Application Framework/b - A framework for developing web/wap 
applications founded in the Ruby programming language, based on the Jakarta Struts 
project.br/
  +pbRuby Web Application Framework/b - A framework for developing web/wap 
applications founded in the Ruby programming language, based on the Jakarta Struts 
project.br /
 - a 
href=http://sourceforge.net/projects/ruby-waf/;http://sourceforge.net/projects/ruby-waf//a/p
  -pbBuilding Web Applications in Java /b - by Brad Coxbr/
  -  - a 
href=http://virtualschool.edu/wap/html/problem.html;http://virtualschool.edu/wap/index.html/abr/
  +pbBuilding Web Applications in Java /b - by Brad Coxbr /
  +  - a 
href=http://virtualschool.edu/wap/html/problem.html;http://virtualschool.edu/wap/index.html/abr
 /
 - overview of article: a href=http://www.mail-archive.com/[EMAIL 

cvs commit: jakarta-struts/doc status.xml

2003-08-29 Thread husted
husted  2003/08/29 13:14:06

  Modified:doc  status.xml
  Log:
  Add draft of 1.x.x whiteboard
  
  Revision  ChangesPath
  1.36  +17 -10jakarta-struts/doc/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -r1.35 -r1.36
  --- status.xml29 Aug 2003 16:49:40 -  1.35
  +++ status.xml29 Aug 2003 20:14:05 -  1.36
  @@ -35,7 +35,7 @@
   
   /section
   
  -section href=bugzilla name=Bugzilla Queries
  +section href=Bugzilla name=Bugzilla Queries
   
   p
   The Struts development teams uses the a 
href=http://jakarta.apache.org/site/bugs.html;Apache Bug Database/a (Bugzilla)
  @@ -58,7 +58,7 @@
   
   /section
   
  -section href=struts_1_x name=Struts 1.x
  +section href=Struts_1_x name=Struts 1.x
   
   p
   The platform requirements throughout the Struts 1.x series will remain the 
same (Servlet 2.2 / JSP 1.1).
  @@ -114,7 +114,7 @@
   
   /section
   
  -section href=struts_1_x_whiteboard name=Struts 1.x Whiteboard
  +section href=Struts_1_x_whiteboard name=Struts 1.x Whiteboard
   
   p
   These are some general ideas we have about what may happen in the 
Struts 1.x series.
  @@ -150,8 +150,10 @@
   liStruts 1.4.x -
   More substantial enhancements to product base
   ul
  -liConsider new Request Processor, if available/li
  -liConsider migration to an Action context/li
  +liConsider new Request Processor, if available (which might 
be based on the Commons Chain
  +of Responsiblity package)/li
  +liConsider migration to an Action context (which also might 
be based no the Commons Chain
  +of Responsiblity package)/li
   /ul
   /li
   
  @@ -225,7 +227,7 @@
   
   /section
   
  -section href=struts_2_0 name=Struts 2.0.x
  +section href=Struts_2_0 name=Struts 2.0.x
   
   p
   Struts 2.x (aka Struts Next Generation) will include broader enhancements.
  @@ -287,12 +289,17 @@
   
   /section
   
  -section href=proposals name=Relevant Proposals
  +section href=Proposals name=Relevant Proposals
   
   ul
   
   li
  -a href=proposals/release-plan-1.1.htmlRelease Plan 1.1/a
  +a 
href=http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/chain/;Commons Chain of 
Responsiblity
  +package/a
  +/li
  +
  +li
  +a href=proposals/release-plan_1_2_0.htmlRelease Plan 1.2.0/a -- 
unratified DRAFT document
   /li
   
   li
  @@ -310,7 +317,7 @@
   /section
   
   section
  -pfont size=-2Website updated from CVS: 2003 AUG 11 by husted./font/p
  +pfont size=-2Website updated from CVS: 2003 AUG 29 by husted./font/p
   pfont size=-2Javadocs updated from CVS: 2003 JUN 29 by mcooper./font/p
   /section
   
  
  
  

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



DO NOT REPLY [Bug 22730] - Software caused connection abort: socket write error

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22730.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22730

Software caused connection abort: socket write error

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 17:33 ---
Please ask Struts questions on struts-user and Tomcat questions on the 
tomcat-user mailing list.

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



cvs commit: jakarta-struts/doc/userGuide index.xml preface.xml

2003-08-29 Thread husted
husted  2003/08/29 15:13:16

  Modified:doc  index.xml status.xml volunteers.xml
   doc/faqs kickstart.xml
   doc/resources models.xml project.xml taglibs.xml
   doc/userGuide index.xml preface.xml
  Log:
  Routine updates
  
  Revision  ChangesPath
  1.47  +6 -0  jakarta-struts/doc/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/index.xml,v
  retrieving revision 1.46
  retrieving revision 1.47
  diff -u -r1.46 -r1.47
  --- index.xml 29 Aug 2003 14:27:24 -  1.46
  +++ index.xml 29 Aug 2003 22:13:16 -  1.47
  @@ -164,5 +164,11 @@
  /p
   /section
   
  +section
  +p
  +a href=faqs/kickstart.html#jsfWhat about JSTL and JavaServer Faces?/a
  +/p
  +/section
  +
   /body
   /document
  
  
  
  1.37  +12 -10jakarta-struts/doc/status.xml
  
  Index: status.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- status.xml29 Aug 2003 20:14:05 -  1.36
  +++ status.xml29 Aug 2003 22:13:16 -  1.37
  @@ -159,16 +159,18 @@
   
   liOther potential enhancements for the 1.x.x series
   ul
  -liMove to a 
href=http://xml.apache.org/forrest/;Forrest/a or a 
href=http://maven.apache.org/;Maven/a for project management/li
  +liMove to a 
href=http://xml.apache.org/forrest/;Forrest/a or
  +a href=http://maven.apache.org/;Maven/a for project 
management/li
   liConsider adopting several popular extensions, including:
  -ul
  -lia href=http://sslext.sourceforge.net/;SSL Ext/a/li
  -lia 
href=http://strutstestcase.sourceforge.net/;TestCase/a/li
  -lia href=http://stxx.sourceforge.net;Stxx/a (XLST)/li
  -lia 
href=http://www.livinglogic.de/Struts/;Workflow/a/li
  -lia href=http://struts.sf.net;Cocoon Plugin/a/li
  -lia href=http://struts.sf.net;Scriptable Actions using 
BSF/a (Bean Scripting Framework)/li
  -/ul
  +ul
  +lia href=http://sslext.sourceforge.net/;SSL 
Ext/a/li
  +lia 
href=http://strutstestcase.sourceforge.net/;TestCase/a/li
  +lia href=http://stxx.sourceforge.net;Stxx/a 
(XLST)/li
  +lia 
href=http://www.livinglogic.de/Struts/;Workflow/a/li
  +lia href=http://struts.sf.net;Cocoon 
Plugin/a/li
  +lia href=http://struts.sf.net;Scriptable Actions 
using BSF/a (Bean Scripting
  +Framework)/li
  +/ul
   /li
   /ul
   /li
  
  
  
  1.32  +1 -1  jakarta-struts/doc/volunteers.xml
  
  Index: volunteers.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/volunteers.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- volunteers.xml29 Aug 2003 16:50:08 -  1.31
  +++ volunteers.xml29 Aug 2003 22:13:16 -  1.32
  @@ -12,7 +12,7 @@
   section name=Community Support href=support
   
   p
  -In June 2003, there were nearly 2800 subscribers to STRUTS-USER.
  +In August 2003, there were 2700 subscribers to STRUTS-USER (including 
the digest version).
   It's the largest user mailing list at Jakarta, exceeding the 
TOMCAT-USER list of about 2400 subscribers.
   In addition to the regular subscribers, an unknown number of developers 
read the lists through newsfeed
   mirrors and through several list archives.
  
  
  
  1.9   +4 -4  jakarta-struts/doc/faqs/kickstart.xml
  
  Index: kickstart.xml
  ===
  RCS file: /home/cvs/jakarta-struts/doc/faqs/kickstart.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- kickstart.xml 26 Jul 2003 03:56:25 -  1.8
  +++ kickstart.xml 29 Aug 2003 22:13:16 -  1.9
  @@ -40,7 +40,7 @@
   lia href=#turbineWhat's the difference between Struts and Turbine?  
What's the difference between Struts and Expresso?/a/li
   lia href=#taglibsWhy aren't the Struts tags maintained as part of the 
Jakarta Taglibs project?/a/li
   lia href=#xhtmlAre the Struts tags XHTML compliant?/a/li
  -lia href=#jsfWhat about the JSTL and JavaServer Faces?/a/li
  +lia href=#jsfWhat about JSTL and JavaServer Faces?/a/li
   lia href=#ideIs 

DO NOT REPLY [Bug 22814] - bug on linkTag

2003-08-29 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22814.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22814

bug on linkTag

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-08-29 22:27 ---
This is a user question.
Please discuss these question on the struts-user
list before reporting it as a bug. Also please
search the user list for tips:
http://marc.theaimsgroup.com/?l=struts-userw=4r=1s=patrice.haidant%
40sacem.frq=a
You'll also need more detail when asking a question
on the list.

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