I submitted this to the JavaServer Pages (JSP) and JSTL Sun Discussion Forum (hope this was the right one!) for input from other developers. I'm waiting to see if this should be submitted as a JDK 1.4.2_06 bug.

By the way, I wouldn't sweat this issue too much. The "currentView" property name can be found in other enterprise software, so it may have just been a needle-in-the-haystack find. There have been no other issues since we upgraded....

[EMAIL PROTECTED] wrote:

NO DOUBT!
Let us know as we are making plans to make the same upgrade in early January. 
So really only 2 weeks from now and this worries me now.
So you have my attention. :-)

--------------------
Mick Knutson
Wells Fargo Business Direct
(415) 222-1020

"This message may contain confidential and/or privileged information. If you are not 
the addressee or authorized to receive this for the addressee, you must not use, copy, 
disclose, or take any action based on this message or any information herein. If you have 
received this message in error, please advise the sender immediately by reply e-mail and 
delete this message. Thank you for your cooperation."
--------------------



-----Original Message-----
From: Jim Barrows [mailto:[EMAIL PROTECTED]
Sent: Friday, December 17, 2004 12:39 PM
To: Struts Users Mailing List
Subject: RE: Struts and JDK 1.4.2_06


Sounds like one for sun, and of course let us know.

That's really weird.



-----Original Message-----
From: Mike Darretta [mailto:[EMAIL PROTECTED]
Sent: Friday, December 17, 2004 1:16 PM
To: Struts Users Mailing List
Subject: Re: Struts and JDK 1.4.2_06


I did a clean build, recompile, etc. Note that I am able to go back to the previous name "currentView", cause the exception, then rename the property and things would work just fine.


Mike

Durham David R Jr Contr 805 CSPTS/SCE wrote:



Are there any thoughts on how a form bean property name

could conflict


with a JDK release?




Did you recompile the entire project with the new JDK? I

wouldn't think


that should matter, but perhaps it does in your case.


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



Reply via email to