Most often we don't want users to see the parameters in the URL. But when I
tried using
setResponsePage(PageA.class, pageParameters) and after mounting the page in
my application I see the parameters in the URL.
So I was referring to
http://stackoverflow.com/questions/6390953/how-can-i-create-
Don't mark the fields as required and check the fields during the submit of the
save and throw appropriate error message. The save as draft would not check the
fields. It is not the most elegant solution but it works and is easy to
implement.
On Mar 31, 2012, at 10:18 PM, "Emmanouil Batsis (M
I have a usecase for saving a draft of a form before actually submitting it.
I'm trying to figure out how to only skip the "required" validators
using a "save draft" submit button in my form. Disabling default form
processing sounds like using a bazooka to shoot down a fly considering
my form
The method says "Java", not "JavaScript".
The page that extracts the extra info uses JavaScript to do that, so
it is enabled.
2012/3/31 Andre Schütz :
> Hello,
>
> I use wicket 1.5.4 or 1.5.5 with Opera and Firefox. I checked with
> the following lines:
>
> Application:
> -
> protected
On Sat, Mar 31, 2012 at 10:05 PM, sudeivas wrote:
> This idea sounds good to me rather than just passing the whole JAVA object.
> But this raises an another question. Since I am just passing PageParameters
> to the page, in the beginning it will be a stateless page. But when I start
> using Ajax c
> final Layer layerOSMTilesAtHome = new OSM("Osmarender",
> OSMLayer.TilesAtHome);
The "Osmarender" renderer became unavailable recently (not sure why).
Comment out the lines that refer to it, and to "layerOSMTilesAtHome".
This has nothing to do with Wicket.
--
Michael Allan
Toronto, +1
Hello,
I use wicket 1.5.4 or 1.5.5 with Opera and Firefox. I checked with
the following lines:
Application:
-
protected void init() {
super.init();
getRequestCycleSettings().setGatherExtendedBrowserInfo(true);
...
}
MyWebPage:
-
WebSession session = WebSession.get();
This idea sounds good to me rather than just passing the whole JAVA object.
But this raises an another question. Since I am just passing PageParameters
to the page, in the beginning it will be a stateless page. But when I start
using Ajax components inside the page, then it becomes a stateful page
You need to mount PageB with mountPage("/pageb", PageB.class) and use
setResponsePage(PageB.class, parameters)
'parameters' should bring a key/value that will be used to create a
proper objectX, e.g. a key which will be used to load an entity from
DB.
And there is no need to use AjaxLink if you al
we run a few 1.5.x apps in aws on tomcat and have not experienced a
problem like this. its probably something weird in your environment.
-igor
On Sat, Mar 31, 2012 at 10:58 AM, roddo123 wrote:
> I haven't been able to have much success with visualvm in that environment.
> But a test I did do was
I haven't been able to have much success with visualvm in that environment.
But a test I did do was create a wicket quickstart program, add appropriate
jars, remove the wicket label and replace it with a wicket form.
I then created a war, and deployed it to a new elastic beanstalk
environment.
The problem in our application is there is no fixed path except for the home
page. From the home page the user will navigate to a different page after
clicking on a ajax link (we use setResponsePage(new PageB(Object x)).
In Page B we have lot of widgets getting populated dynamically based on
value
On Sat, Mar 31, 2012 at 6:22 PM, sudeivas wrote:
> I believe the best solution for me is to update my project to the latest
> version of wicket, but still I am worried about the following issue,
>
> https://issues.apache.org/jira/browse/WICKET-4454
>
> since lot of our code have nested components.
I believe the best solution for me is to update my project to the latest
version of wicket, but still I am worried about the following issue,
https://issues.apache.org/jira/browse/WICKET-4454
since lot of our code have nested components. Any idea when 1.5.6 will be
released? (so that I can wait f
oh sorry corrected a bit
On Sat, Mar 31, 2012 at 1:50 PM, vineet semwal
wrote:
> for creation ,is it done like this in wicket if(page is creatable){
> create}else{ /*throw pageexpiredexception*/ redirect to error page }
>
> else there can be a loop of pageexpiredexception just curious..
>
>
> On
for creation ,is it done like this in wicket if(page is creatable){
create}else{ throw pageexpiredexception}
else there can be a loop of pageexpiredexception just curious..
On Sat, Mar 31, 2012 at 12:53 PM, Martin Grigorov wrote:
> On Sat, Mar 31, 2012 at 12:29 AM, sudeivas wrote:
>> Thanks fo
Hi,
See javax.servlet.http.Cookie#setMaxAge().
Also see org.apache.wicket.util.cookies.CookieUtils
On Sat, Mar 31, 2012 at 8:25 AM, kshitiz wrote:
> Hi,
>
> Is there any way to set cookie expiration time in Wicket? I am not able to
> find any example related to that...like we can set session exp
On Sat, Mar 31, 2012 at 12:29 AM, sudeivas wrote:
> Thanks for the information. I am currently using wicket 1.5.3.
>
> I hope this applies to wicket-1.5.3 as well.
Yes
>
> But in my case, everything works fine. But when our session management
> fails, then we run into the following exceptions:
>
18 matches
Mail list logo
