Have a look at this plugin. When you submit your modal page you can access the data you submitted in your form by reading it from the session state. You can create a partial page refresh action that trigger on close of the modal page.
Thanks for the suggestion, "255c8c25-bb21-4bc4-b082-2c68fd4fe7a6"
I mean Vincent; just kidding, despite the sw upgrades and new look,
the Oracle forums still forget who we are now and then it seems ;-)
Of course, Skillbuilders! I've used their excellent "super-lov" plugin
in the past and had noticed the modal one. Definitely worth a try.
People at their site (or on the page you provided) seem to have
issues with this plugin under APEX4.2, though.
Can anyone comment?
Plugin issues could be related to jQuery and jQuery_UI libraries that are included with each version of APEX. So for an older version of APEX you could try tton manually upgrade your js libraries, or -if you're affraid the newer libraries might affect the rest of your application(s), you can just include the newer library versions in the pages that use your modal dialogs.
Alternatively you can create your own modal page with jQuery UI, which isn't to hard, but a little more time consuming. See for a very rudimentary version: http://apex.oracle.com/pls/apex/f?p=vincentdeelen:modal_form_jquery
I've used the modal page plugin since it was available, and it runs fine on 4.2 (yes, 4.2.2 too). Of course, as Vincent says, it might act up if you add newer versions of the jQuery libraries, but this is something you can usually resolve (after all, the plugin uses apex.jQuery if I'm not mistaken) and is really not the fault of the plugin but rather a consideration of the developer/client. You can indeed create your own modal dialog technique but honestly, why reinvent the wheel unless you're doing this as an exercise or total necessity.
I've used the plugin in several applications under apex 4.2+, without any problems.
The plugin version 2.0 uses jQuery Colorbox for the modal display instead of jQuery UI in v 1.0. Colobox has some known issues with jQuery 1.6, which could explain bugy performance in older APEX versions.