If, as you say you can reproduce this in your storefront app no matter
where you use it then you may want to reduce this to a testcase and
create a jira issue from it.

You are already writing that you can reproduce it and consequently it
would be only a matter of removing all distracting detail from your
storefront until further simplification is no longer possible. I can't
see how otherwise anyone could help you with your issue.

In any case, glitches like you mention should not happen whether the
problem is in the Wicket framework domain or in the application
domain. If it is in the application domain, as it would usually be the
case because Wicket is mature, then there would still be a benefit of
publishing the issue e.g. in a Wiki article so that others would not
make the same mistake.

Good luck!


On Fri, 18 Dec 2009 14:58:15 -0700, you wrote:

>I was unable to re-create it in a simple web app w/ a few pages.  However,
>no matter where I use it in my storefront app, it happens.
>It's very strange because it starts a page "late".  I put the annotation on
>the User Account page, yet it doesn't switch to https until I reach the
>*following* page in the checkout process.  I just stuck it on the general
>Login page that exists outside of the checkout process...and when I click
>the link from the home page to go to the Login page using
>setResponsePage(new Login()), it doesn't switch to https.  Instead, I enter
>the user/pass and submit...THEN it goes to https, then I'm able to re-enter
>and login.
>Very strange behavior...I have no idea what might be causing it.
>I use various Panels throughout the side, would that have any influence on
>it?  For example, the link in the header to go to the Login page is inside
>of a straightforward Panel.  The entire site uses markup inheritance as
>On Fri, Dec 18, 2009 at 9:29 AM, VGJ <zambi...@gmail.com> wrote:
>> I'll create one and post it, if I can.
>> -v
>> On Fri, Dec 18, 2009 at 9:21 AM, Igor Vaynberg 
>> <igor.vaynb...@gmail.com>wrote:
>>> can you recreate in a quickstart?
>>> -igor
>>> On Fri, Dec 18, 2009 at 7:56 AM, VGJ <zambi...@gmail.com> wrote:
>>> > I'm now using @RequireHttps to switch to https on certain pages but it's
>>> not
>>> > quite working right.
>>> >
>>> > In our storefront app, I'm switching to https at the point in the
>>> checkout
>>> > process where you view your cart, and then proceed to a page to either
>>> login
>>> > or create an account.  When I submit my username and password, the
>>> > validation fires as if I entered nothing into the form.  Enter it a
>>> second
>>> > time and it works - the validation doesn't trigger.  Everything was
>>> entered
>>> > correctly the first time around...so it's as if the form is being posted
>>> on
>>> > its own, when the page loads?  Every page with @RequireHttps that has a
>>> > form, does this.
>>> >
>>> > What do I need to do to change to accommodate validation under
>>> @RequireHttps
>>> > pages?
>>> >
>>> > Currently you just see a lot of forms w/ fields like this:
>>> >
>>> > add(new TextField("username").setRequired(true));
>>> >
>>> > ...with a pretty common feedback panel:
>>> >
>>> >            <div id="feedbackPanel">
>>> >              <span wicket:id="feedbackPanel" class="warning" />
>>> >            </div>
>>> >
>>> > Thanks!
>>> >
>>> > -v
>>> >
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org

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

Reply via email to