RE: How to rename file in FormFile in struts 1.1 final release

[Andrew Hill]

Yeh. In my case I wasnt event going that far, just jumping from a beta to a
final of 1.1

What bugs me though is that the method is still there and not deprecated.
The first I knew that there was a problem was when QA defected me for the
UnsupportedOperationException that gets thrown :-(

-Original Message-
From: Yansheng Lin [mailto:[EMAIL PROTECTED]
Sent: Thursday, 31 July 2003 23:01
To: 'Struts Users Mailing List'; [EMAIL PROTECTED]
Subject: RE: How to rename file in FormFile in struts 1.1 final release



Same thing happened to me too.  There is going to be a lot of debugging for
people used this function in 1.0.2 and want to switch to 1.1:).


-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: July 31, 2003 6:08 AM
To: Struts
Subject: How to rename file in FormFile in struts 1.1 final release


Whats the deal with
org.apache.struts.upload.CommonsMultipartRequestHandler.CommonsFormFile
being immutable?

Its broken my (production) code that was working with struts 1.1 b1 and
relied on using setFileName() :-(

What is the rationale for the FormFile interface still having these methods
when the standard implementation does not support them?


-
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: How to rename file in FormFile in struts 1.1 final release

[Yansheng Lin]

Same thing happened to me too.  There is going to be a lot of debugging for
people used this function in 1.0.2 and want to switch to 1.1:). 


-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED] 
Sent: July 31, 2003 6:08 AM
To: Struts
Subject: How to rename file in FormFile in struts 1.1 final release


Whats the deal with
org.apache.struts.upload.CommonsMultipartRequestHandler.CommonsFormFile
being immutable?

Its broken my (production) code that was working with struts 1.1 b1 and
relied on using setFileName() :-(

What is the rationale for the FormFile interface still having these methods
when the standard implementation does not support them?


-
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]

How to rename file in FormFile in struts 1.1 final release

[Andrew Hill]

Whats the deal with
org.apache.struts.upload.CommonsMultipartRequestHandler.CommonsFormFile
being immutable?

Its broken my (production) code that was working with struts 1.1 b1 and
relied on using setFileName() :-(

What is the rationale for the FormFile interface still having these methods
when the standard implementation does not support them?


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

RE: Repost: Validator indexed property not working in Struts 1.1 Final Release

[David Graham]

--- "Wu, Feng" <[EMAIL PROTECTED]> wrote:
> Thanks, I have opened a bug report on item one, it is at
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21254.  Regarding the
> second item, is there a paticular reason that the validator is designed
> to "stops validating a list of values on the first failure"?  

It's not really designed that way, it just doesn't work right now.  I
haven't investigated what it would take to make this work yet.

David

> This
> morning I actually modified Validator.java so that it validates all
> memebers of the list and saves error messages for them all.  So now I
> get it to display like this:
> 
> value is mandatory
> value is mandatory
> value is mandatory
> 
> This is of course not very clear to the user, because I really wanted is
> to display:
> 
> nameList value 1 is mandatory
> nameList value 2 is mandatory
> nameList value 3 is mandatory
> 
> I guess I still need to figure out a way of contructing the error
> messages in a different way so that it works for both indexed and
> non-indexed property.
> 
> On the other hand, the validwhen rules that's supposed to come after 1.1
> final, will it be able to handle this kind of validation?  How difficult
> it would be possible to plug that piece into Strut 1.1?  The reason I
> ask is because it will be much difficult for me to sell to the
> management the idea of delivering our project on nightly build than on
> Struts 1.1 final.
> 
> 
> Thanks a lot.
> 
> Feng
> 
> 
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 01, 2003 3:21 PM
> To: Struts Users Mailing List
> Subject: Re: Repost: Validator indexed property not working in Struts
> 1.1 Final Release
> 
> 
> --- "Wu, Feng" <[EMAIL PROTECTED]> wrote:
> > Seems like my previous email to the list did not make it.  Here it
> goes
> > again.  Thanks.
> > 
> > By the way, I can work around the problem of nested:messagePresent not
> > finding the ActionError by mannualy generating the property attribute
> > like this:
> > 
> > 
> > But this kind of defeated the purpose of nested tags, does it?
> 
> It is indeed broken in 1.1 final and 1.1 RC2 (1.1 RC1 works fine). 
> Please
> open a bug report on the tag so we can track this in bugzilla.
> 
> > 
> > I still could not figure out why there is only ActionError (for
> property
> > nameList[0].value) is in request scope when I should have three, since
> > nameList[1].value and nameList[2].value are blank and should fail
> > validation.
> 
> This is a current limitation of the validator.  It stops validating a
> list
> of values on the first failure.
> 
> David
> 
> > 
> > Thank you.
> > 
> > Feng
> > 
> > -Original Message-
> > From: Wu, Feng 
> > Sent: Monday, June 30, 2003 5:08 PM
> > To: 
> > Subject: Validator indexed property not working in Struts 1.1 Final
> > Release
> > 
> > 
> > Hi,
> > 
> > First, great works on Struts 1.1 final release.  Just in time since we
> > are designing a major project using Struts.
> > 
> > Got a couple questions regarding validator and indexed properties in
> > Struts 1.1 final release:
> > 
> > 1. Seems that the validation of indexed property in struts-validator
> > application (in type.jsp) is broken.  Specifically the page has an
> > indexed property nameList[].value.  After I switched to Struts 1.1
> > final, the error message no longer shows up.  Does any one has the
> same
> > problem?  I knew this was working in RC1.
> > 
> > In request scope, I saw ActionError saved for property
> > nameList[0].value.  In type.jsp the following code is used to output
> > errors for this property:
> > 
> >  
> > 
> > 
> >
> >   
> >
> > 
> >  
> > 
> > It seems nested:message can no longer match up "value" with
> > "nameList[0].value".
> > 
> > Any expert opinions on this?
> > 
> > 2. Related (this is not 1.1 final release specific), say I want to
> > display error messages for all the members of an indexed property,
> i.e.,
> > in the type.jsp example, I want to display like:
> > 
> > * nameList value 1 is mandatory
> > * nameList value 2 is mandatory
> > * nameList value 3 is mandatory
> > 
> > instead of just displaying "nameList value is mandatory" only once
> even

RE: Repost: Validator indexed property not working in Struts 1.1 Final Release

[Wu, Feng]

Thanks, I have opened a bug report on item one, it is at 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21254.  Regarding the second item, 
is there a paticular reason that the validator is designed to "stops validating a list 
of values on the first failure"?  This morning I actually modified Validator.java so 
that it validates all memebers of the list and saves error messages for them all.  So 
now I get it to display like this:

value is mandatory
value is mandatory
value is mandatory

This is of course not very clear to the user, because I really wanted is to display:

nameList value 1 is mandatory
nameList value 2 is mandatory
nameList value 3 is mandatory

I guess I still need to figure out a way of contructing the error messages in a 
different way so that it works for both indexed and non-indexed property.

On the other hand, the validwhen rules that's supposed to come after 1.1 final, will 
it be able to handle this kind of validation?  How difficult it would be possible to 
plug that piece into Strut 1.1?  The reason I ask is because it will be much difficult 
for me to sell to the management the idea of delivering our project on nightly build 
than on Struts 1.1 final.


Thanks a lot.

Feng


-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2003 3:21 PM
To: Struts Users Mailing List
Subject: Re: Repost: Validator indexed property not working in Struts
1.1 Final Release


--- "Wu, Feng" <[EMAIL PROTECTED]> wrote:
> Seems like my previous email to the list did not make it.  Here it goes
> again.  Thanks.
> 
> By the way, I can work around the problem of nested:messagePresent not
> finding the ActionError by mannualy generating the property attribute
> like this:
>   
> 
> But this kind of defeated the purpose of nested tags, does it?

It is indeed broken in 1.1 final and 1.1 RC2 (1.1 RC1 works fine).  Please
open a bug report on the tag so we can track this in bugzilla.

> 
> I still could not figure out why there is only ActionError (for property
> nameList[0].value) is in request scope when I should have three, since
> nameList[1].value and nameList[2].value are blank and should fail
> validation.

This is a current limitation of the validator.  It stops validating a list
of values on the first failure.

David

> 
> Thank you.
> 
> Feng
> 
> -Original Message-
> From: Wu, Feng 
> Sent: Monday, June 30, 2003 5:08 PM
> To: 
> Subject: Validator indexed property not working in Struts 1.1 Final
> Release
> 
> 
> Hi,
> 
> First, great works on Struts 1.1 final release.  Just in time since we
> are designing a major project using Struts.
> 
> Got a couple questions regarding validator and indexed properties in
> Struts 1.1 final release:
> 
> 1. Seems that the validation of indexed property in struts-validator
> application (in type.jsp) is broken.  Specifically the page has an
> indexed property nameList[].value.  After I switched to Struts 1.1
> final, the error message no longer shows up.  Does any one has the same
> problem?  I knew this was working in RC1.
> 
> In request scope, I saw ActionError saved for property
> nameList[0].value.  In type.jsp the following code is used to output
> errors for this property:
> 
>  
> 
> 
>
>   
>
> 
>  
> 
> It seems nested:message can no longer match up "value" with
> "nameList[0].value".
> 
> Any expert opinions on this?
> 
> 2. Related (this is not 1.1 final release specific), say I want to
> display error messages for all the members of an indexed property, i.e.,
> in the type.jsp example, I want to display like:
> 
> * nameList value 1 is mandatory
> * nameList value 2 is mandatory
> * nameList value 3 is mandatory
> 
> instead of just displaying "nameList value is mandatory" only once even
> though all three fields are blank.  Is there a simple way of doing that?
>  Again, looks like only nameList[0].value is used as the key to save an
> ActionError when all three fields are blank (thus all warranting error
> messages).
> 
> Is it the designed behavior to save only one ActionError for indexed
> property no matter how many actual members of the indexed property
> actually have?
> 
> Thanks very much.
> 
> Feng
> 
> 
> 
> 
> ***
> This e-mail and any files transmitted with it are intended 
> solely for the use of the addressee.  This e-mail may 
> contain confidential and/or legally privileged information.  
> Any review, transmission, disclosure, copying, or any action 
> taken or not taken, by oth

Re: Repost: Validator indexed property not working in Struts 1.1 Final Release

[David Graham]

--- "Wu, Feng" <[EMAIL PROTECTED]> wrote:
> Seems like my previous email to the list did not make it.  Here it goes
> again.  Thanks.
> 
> By the way, I can work around the problem of nested:messagePresent not
> finding the ActionError by mannualy generating the property attribute
> like this:
>   
> 
> But this kind of defeated the purpose of nested tags, does it?

It is indeed broken in 1.1 final and 1.1 RC2 (1.1 RC1 works fine).  Please
open a bug report on the tag so we can track this in bugzilla.

> 
> I still could not figure out why there is only ActionError (for property
> nameList[0].value) is in request scope when I should have three, since
> nameList[1].value and nameList[2].value are blank and should fail
> validation.

This is a current limitation of the validator.  It stops validating a list
of values on the first failure.

David

> 
> Thank you.
> 
> Feng
> 
> -Original Message-
> From: Wu, Feng 
> Sent: Monday, June 30, 2003 5:08 PM
> To: 
> Subject: Validator indexed property not working in Struts 1.1 Final
> Release
> 
> 
> Hi,
> 
> First, great works on Struts 1.1 final release.  Just in time since we
> are designing a major project using Struts.
> 
> Got a couple questions regarding validator and indexed properties in
> Struts 1.1 final release:
> 
> 1. Seems that the validation of indexed property in struts-validator
> application (in type.jsp) is broken.  Specifically the page has an
> indexed property nameList[].value.  After I switched to Struts 1.1
> final, the error message no longer shows up.  Does any one has the same
> problem?  I knew this was working in RC1.
> 
> In request scope, I saw ActionError saved for property
> nameList[0].value.  In type.jsp the following code is used to output
> errors for this property:
> 
>  
> 
> 
>
>   
>
> 
>  
> 
> It seems nested:message can no longer match up "value" with
> "nameList[0].value".
> 
> Any expert opinions on this?
> 
> 2. Related (this is not 1.1 final release specific), say I want to
> display error messages for all the members of an indexed property, i.e.,
> in the type.jsp example, I want to display like:
> 
> * nameList value 1 is mandatory
> * nameList value 2 is mandatory
> * nameList value 3 is mandatory
> 
> instead of just displaying "nameList value is mandatory" only once even
> though all three fields are blank.  Is there a simple way of doing that?
>  Again, looks like only nameList[0].value is used as the key to save an
> ActionError when all three fields are blank (thus all warranting error
> messages).
> 
> Is it the designed behavior to save only one ActionError for indexed
> property no matter how many actual members of the indexed property
> actually have?
> 
> Thanks very much.
> 
> Feng
> 
> 
> 
> 
> ***
> This e-mail and any files transmitted with it are intended 
> solely for the use of the addressee.  This e-mail may 
> contain confidential and/or legally privileged information.  
> Any review, transmission, disclosure, copying, or any action 
> taken or not taken, by other than the intended recipient, in 
> reliance on the information, is prohibited.  If you received 
> this e-mail in error, notify the sender and delete this e-mail 
> (and any accompanying material) from your computer and
> network. In addition, please be advised that 21st Century 
> Insurance Group reserves the right to monitor, access and 
> review all messages, data and images transmitted through 
> our electronic mail system. By using our e-mail system, you 
> consent to this monitoring. 
> ***
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

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

Repost: Validator indexed property not working in Struts 1.1 Final Release

[Wu, Feng]

Seems like my previous email to the list did not make it.  Here it goes again.  Thanks.

By the way, I can work around the problem of nested:messagePresent not finding the 
ActionError by mannualy generating the property attribute like this:


But this kind of defeated the purpose of nested tags, does it?

I still could not figure out why there is only ActionError (for property 
nameList[0].value) is in request scope when I should have three, since 
nameList[1].value and nameList[2].value are blank and should fail validation.

Thank you.

Feng

-Original Message-
From: Wu, Feng 
Sent: Monday, June 30, 2003 5:08 PM
To: 
Subject: Validator indexed property not working in Struts 1.1 Final
Release


Hi,

First, great works on Struts 1.1 final release.  Just in time since we are designing a 
major project using Struts.

Got a couple questions regarding validator and indexed properties in Struts 1.1 final 
release:

1. Seems that the validation of indexed property in struts-validator application (in 
type.jsp) is broken.  Specifically the page has an indexed property nameList[].value.  
After I switched to Struts 1.1 final, the error message no longer shows up.  Does any 
one has the same problem?  I knew this was working in RC1.

In request scope, I saw ActionError saved for property nameList[0].value.  In type.jsp 
the following code is used to output errors for this property:

 


   
  
   

 

It seems nested:message can no longer match up "value" with "nameList[0].value".

Any expert opinions on this?

2. Related (this is not 1.1 final release specific), say I want to display error 
messages for all the members of an indexed property, i.e., in the type.jsp example, I 
want to display like:

* nameList value 1 is mandatory
* nameList value 2 is mandatory
* nameList value 3 is mandatory

instead of just displaying "nameList value is mandatory" only once even though all 
three fields are blank.  Is there a simple way of doing that?  Again, looks like only 
nameList[0].value is used as the key to save an ActionError when all three fields are 
blank (thus all warranting error messages).

Is it the designed behavior to save only one ActionError for indexed property no 
matter how many actual members of the indexed property actually have?

Thanks very much.

Feng




***
This e-mail and any files transmitted with it are intended 
solely for the use of the addressee.  This e-mail may 
contain confidential and/or legally privileged information.  
Any review, transmission, disclosure, copying, or any action 
taken or not taken, by other than the intended recipient, in 
reliance on the information, is prohibited.  If you received 
this e-mail in error, notify the sender and delete this e-mail 
(and any accompanying material) from your computer and
network. In addition, please be advised that 21st Century 
Insurance Group reserves the right to monitor, access and 
review all messages, data and images transmitted through 
our electronic mail system. By using our e-mail system, you 
consent to this monitoring. 
***


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

Re: Congratulations on the struts 1.1 final release

[lcl]

Great job!
I am at China, where are you come from?

"Mounagurusamy, Jayakumar (HAL)" <[EMAIL PROTECTED]>
:[EMAIL PROTECTED]
> Congratulations, Struts team
>
> You guys have done a marvelous work, keep the good work and provide the
JAVA
> world with better solutions
>
> thanks
>
> Jay
>
>
> -- x-- x-- x-- x-- x--
> x-- x-- x--
> Jayakumar Mounagurusamy Email: [EMAIL PROTECTED]
> Senior Programmer Analyst Work: 206-298-3831
> Information Services Pager: 206-570-4532
> 300 Elliott Avenue West Extension: x3831
> Seattle WA 98119




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

Congratulations on the struts 1.1 final release

[Mounagurusamy, Jayakumar (HAL)]

Congratulations, Struts team

You guys have done a marvelous work, keep the good work and provide the JAVA
world with better solutions

thanks

Jay


-- x-- x-- x-- x-- x--
x-- x-- x-- 
Jayakumar Mounagurusamy Email:  [EMAIL PROTECTED]
Senior Programmer Analyst   Work:   206-298-3831
Information ServicesPager:  206-570-4532
300 Elliott Avenue West Extension: x3831
Seattle WA 98119


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

Re: Struts 1.1 Final release

[Donald Ball]

On 9/11/2002 at 10:06 AM Michael Lee wrote:

>Be nice
>There are no ship dates for jakarta stuff. It is released when it meets a
>certain level of quality/features.
>You can help it meet the ship date! It's open source!

It might have been more helpful to point the user towards the real release
plan:

http://jakarta.apache.org/struts/proposals/release-plan-1.1b2.html

not the "there is no release date" page (which is, imho, a total cop-out).

- donald


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Struts 1.1 Final release

[Michael Lee]

Be nice
There are no ship dates for jakarta stuff. It is released when it meets a
certain level of quality/features.
You can help it meet the ship date! It's open source!
I'm going to ask my bosses if I can release some of my code here as examples
(modified to protect our interests of course). Lots of good examples.

- Original Message -
From: "Andrew Hill" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 4:50 AM
Subject: RE: Struts 1.1 Final release


> I believe this has been "answered" a few million times, but since
searching
> the archive can be a tiresome experience (seriously. The archive search
> really does suck!) I shall repeat my previous answer.
>
> 
> The 12th of April 2156 at 15:28 in the afternoon.
> Or perhaps even sooner if its ready before then... ;-)
> 
>
> hehe
>
> For more info you can take a look at the faq:
> http://jakarta.apache.org/struts/kickstart.html#release
>
>
>
> -Original Message-
> From: Vikas Sangwan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 11, 2002 16:40
> To: Struts Users Mailing List
> Subject: Struts 1.1 Final release
>
>
>
> Hi,
> Can somebody tell me, when can we expect production release od Struts 1.1
?
> Thanks in advance.
> Vikas.
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>

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

RE: Struts 1.1 Final release

[Galbreath, Mark]

lamer

-Original Message-
From: Vikas Sangwan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 4:40 AM
To: Struts Users Mailing List
Subject: Struts 1.1 Final release



Hi, 

Can somebody tell me, when can we expect production release od Struts 1.1 ? 

Thanks in advance. 

Vikas. 

RE: Struts 1.1 Final release

[Andrew Hill]

I believe this has been "answered" a few million times, but since searching
the archive can be a tiresome experience (seriously. The archive search
really does suck!) I shall repeat my previous answer.


The 12th of April 2156 at 15:28 in the afternoon.
Or perhaps even sooner if its ready before then... ;-)


hehe

For more info you can take a look at the faq:
http://jakarta.apache.org/struts/kickstart.html#release



-Original Message-
From: Vikas Sangwan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 16:40
To: Struts Users Mailing List
Subject: Struts 1.1 Final release



Hi,
Can somebody tell me, when can we expect production release od Struts 1.1 ?
Thanks in advance.
Vikas.


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

RE: Struts 1.1 Final release

[Rene Eigenheer]

even if I'm not involved in the develoment, I found the answer ;-)))
 
http://jakarta.apache.org/struts/kickstart.html#release
<http://jakarta.apache.org/struts/kickstart.html#release> 

-Original Message-
From: Vikas Sangwan [mailto:[EMAIL PROTECTED]]
Sent: Mittwoch, 11. September 2002 10:40
To: Struts Users Mailing List
Subject: Struts 1.1 Final release



Hi, 

Can somebody tell me, when can we expect production release od Struts 1.1 ? 

Thanks in advance. 

Vikas. 


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

Struts 1.1 Final release

[Vikas Sangwan]

Title: Struts 1.1 Final release






Hi,


Can somebody tell me, when can we expect production release od Struts 1.1 ?


Thanks in advance.


Vikas.




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

Re: Struts 1.1 final release

[Craig R. McClanahan]

As is the usual case for open source software, there is no such date known
to anybody.  Finding bugs (and, even better, contributing patches) is the
best way to accellerate whatever date it turns out to be.

The next step in the chain will be a "beta 2" release, as soon as we get a
few more bugs swatted (see the STATUS file in the nightly source
distribution for the set of bug reports we are concerned about).  I would
imagine that there will be at least one more beta/release candidate type
build before we call it good.

Craig


On Mon, 29 Jul 2002, Melanie Harris wrote:

> Date: Mon, 29 Jul 2002 05:51:10 -0700 (PDT)
> From: Melanie Harris <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Struts 1.1 final release
>
>
> Struts User Group,
>
> I understand that Struts 1.1 is very stable at this point and is basically 
>considered a final build.  However, the vendor I am currently subcontracting for will 
>not let us move forward with Struts development using a beta build of struts.  This 
>is not good as 1.1 has a bunch of new features we would like to be using.  I know 
>this has been asked before but can someone please let me know when the "official" 
>final build of Struts 1.1 will be available (non beta)?
>
> thanks,
>
> -mel harris
>
>
>
> -
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better


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

Struts 1.1 final release

[Melanie Harris]

Struts User Group,

I understand that Struts 1.1 is very stable at this point and is basically considered 
a final build.  However, the vendor I am currently subcontracting for will not let us 
move forward with Struts development using a beta build of struts.  This is not good 
as 1.1 has a bunch of new features we would like to be using.  I know this has been 
asked before but can someone please let me know when the "official" final build of 
Struts 1.1 will be available (non beta)?

thanks,

-mel harris



-
Do You Yahoo!?
Yahoo! Health - Feel better, live better