Evidently what I need to do is not a great fit for Wicket, but it is only a 
small
part of a page in a larger application for which Wicket is a good fit.  So I'm
trying to force this requirement to fit...please bear with me :>

I need to load an external site into an iframe within a Wicket page. This
would be really easy, except for:
1. A POST to the URL is required, not a GET
2. The URL is not known until runtime
3. The values of the fields are not known until runtime


I have this mostly hacked-together and working, except that Wicket is
renaming my fields - pre-pending the form name  :(


The relevant part of my HTML looks like this:

        <form wicket:id="form" action="#" method="post" target="appframe" 
id="formid">
            <input wicket:id="signed_request" type=hidden name="signed_request" 
value="">
        </form>

        <iframe name="appframe" width="100%" height="600">
        </iframe>

And there is some javascript that executes the post into the iframe in 
body.onload.


The relevant bit of the page code looks like this:

        WebMarkupContainer form = new WebMarkupContainer("form");
        form.add(new AttributeModifier("action", url));
        add(form);

        HiddenField<String> signed_request = new 
HiddenField<String>("signed_request", _signed_request);
        form.add(signed_request);

Everything works, except that the field "signed_request" gets renamed to 
"form:signed_request".

Any ideas how to get around this?  Or perhaps a better approach?


TIA!
Chris





-- 
------------------------------------------------------------------------ -
Chris Merrill                           |  Web Performance, Inc.
[email protected]                |  http://webperformance.com
919-433-1762                            |  919-845-7601

Web Performance: Website Load Testing Software & Services
------------------------------------------------------------------------ -

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to