Resurrecting an old thread. We recently upgraded from 5.0.18 to 5.1.0.x and
have unsuspectingly got hammered by this feature (bug).
When making application breaking changes like this between versions, it
would be nice if there was a warning or error message for it.
The docs are also out of date
Thank you! this helped me alot
Joachim Van der Auwera schrieb:
Delving further into this.
It works fine when adding the @Secure annotation on pages, it is the
global configuration which fails.
On closer investigation, it seems there is a change in where to provide
the global configuration.
Ok, on further investigation, the tapestry.secure-enabled=true cannot
make a difference as this was only added in 5.1.0.1.
When I add the following in my application module
public static void contributeAlias( ConfigurationAliasContribution
configuration )
{
BaseURLSource source
Delving further into this.
It works fine when adding the @Secure annotation on pages, it is the
global configuration which fails.
On closer investigation, it seems there is a change in where to provide
the global configuration.
When contributing to the application defaults (like below), it
