That would be a bug.  Please add it and I'll have it 
fixed in 2.2-alpha-1 (i.e., by the end of the week).

Over the course of 2.2, I hope to create more 
sophisticated test suites; perhaps creating mock objects 
for HttpSession, HttpServletRequest, etc., so that I can 
create unit tests for individual components.

--
[EMAIL PROTECTED]

http://tapestry.sf.net
> Today I tried to switch over from Tapestry 2.0.2a to Tapestry 2.0.5. Almost 
> everything worked out fine, but I found one problem. I use an Insert component 
> for the display of a date. I bound this component to a SimpleDateFormat. In 
> some cases the value to be displayed is null. In Tapestry 2.0.2a the value 
> simply won't be displayed. Since Tapestry 2.0.5 the component tries to format 
> the value although it is null. Is there a parameter to avoid this or do I have 
> to write my own component.
> 
> [EMAIL PROTECTED]
> Daedalos Consulting GmbH, Witten, Germany
> www.daedalos.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Oh, it's good to be a geek.
> http://thinkgeek.com/sf
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to