Re: @RequireHttps - forms misbehaving

[gilberthuph]

I'm having the same problem and I can reproduce this in a quickstart, I just
want to check before creating a jira:

- In my quickstart I'm calling setRedirect(true) within the form submit
button's onSubmit(), is this the correct place to force a redirect?
- SignInPage has the @RequireHttps annotation, *should* the code below
result in immediate switch to https or am I missing something?

Button submitButton = new Button("submit") {
   @Override
   public void onSubmit() {
   setRedirect(true);
   setResponsePage(new SignInPage());
   }
};
-- 
View this message in context: 
http://old.nabble.com/%40RequireHttps---forms-misbehaving-tp26845496p27984631.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: validation message-keys differences on m3 to rc2

[gilberthuph]

I'm having exactly the same problem after moving from 1.4-rc1 -> 1.4-rc2

Here's the extract from my properties file TaxiBookingPage.xml.


http://java.sun.com/dtd/properties.dtd";>

You must
enter the number of vehicles
.. snip ..


RC1

The key "generalDetails.numberOfVehiclesRequired.Required" is found
immediately and the appropriate message retrieved.

11:00:38.595 [http-8180-3] DEBUG org.apache.wicket.Session - Getting
page [path = 4:taxiBookingForm, versionNumber = 0]
11:00:38.609 [http-8180-3] DEBUG
org.apache.wicket.resource.loader.ComponentStringResourceLoader - Found
resource from: com/rp/webapp/taxi/TaxiBookingPage.; key:
generalDetails.numberOfVehiclesRequired.Required


RC2

Does not attempt to look up
"generalDetails.numberOfVehiclesRequired.Required" but the key
"taxiBookingForm.numberOfVehiclesContainer.numberOfVehiclesRequiredBorder.generalDetails.numberOfVehiclesRequired.Required"
which is not found.

10:47:47.902 [http-8180-1] DEBUG org.apache.wicket.Localizer - Locate
property: key: 'Required'; Component: '[MarkupContainer [Component id =
generalDetails.numberOfVehiclesRequired]]'
10:47:47.903 [http-8180-1] DEBUG
org.apache.wicket.resource.loader.ComponentStringResourceLoader - component:
'[MarkupContainer [Component id =
generalDetails.numberOfVehiclesRequired]]'; key: 'Required'
10:47:47.903 [http-8180-1] DEBUG
org.apache.wicket.resource.loader.ComponentStringResourceLoader - key:
'taxiBookingForm.numberOfVehiclesContainer.numberOfVehiclesRequiredBorder.generalDetails.numberOfVehiclesRequired.Required';
class: 'com.rp.webapp.taxi.TaxiBookingPage'; locale: 'en_GB'; Style: 'null'
10:47:47.903 [http-8180-1] DEBUG
org.apache.wicket.resource.loader.ComponentStringResourceLoader - Found
properties file: 'com/rp/webapp/taxi/TaxiBookingPage.' but it doesn't
contain the property

So it seems the lookup algorithm hasn't changed but the message key.

Is this a bug or should we now be using the full form-relative key as shown
above?



Alexander Lohse wrote:
> 
> I could not find any reported changes concerning validation message  
> keys from version 1.4-m3 to 1.4-rc2, but I have the following  
> "required" key in my application resources that does not work anymore.
> .. trim ..
> 

-- 
View this message in context: 
http://www.nabble.com/validation-message-keys-differences-on-m3-to-rc2-tp22155986p22431244.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org