tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Zeigler <robe...@scazdl.org>
Subject Re: 5.0.9 How to passivate null or empty fields safely?
Date Fri, 25 Jan 2008 14:16:45 GMT
You can work around the link issue temporarily by disabling  
"optimized" urls:
Add:
       
configuration.add(TapestryConstants.FORCE_ABSOLUTE_URIS_SYMBOL,"true");
to you "contributeApplicationDefaults".

Robert

On Jan 25, 2008, at 1/255:39 AM , Geoff Callender wrote:

> In 5.0.7 I'd passivate a null field as the string "null", and  
> interpret it appropriately in onActivate.  In 5.0.9 this causes NPE,  
> so I'm passivating as empty string instead, but that produces a URL  
> with multiple trailing slashes, which prevents assets being resolved  
> and PageLinks to render wrongly.  Both appear to have URLs based on  
> current point in the web context rather than the root of the web  
> context.
>
> Is there a better approach that I should be using to passivate null  
> and/or empty fields?
>
> Cheers,
>
> Geoff
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message