/not-addding-componet-in-case-of-error-tp26754430p26779962.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
--
regards,
Vineet Semwal
--
View this message in context:
http://old.nabble.com/not-addding-componet-in-case-of-error-tp26754430p26779967.html
Sent from the Wicket - User mailing list archive at Nabble.com
Or just set visibility based on error
On Saturday, December 12, 2009, vineet semwal
vineetsemwal1...@gmail.com wrote:
add empty webmarkupcontainers as your components,if no error,replace the
containers with your components
else
you don't need to replace.
On Sat, Dec 12, 2009 at 8:02 AM,
toggling visibility will always do,
my idea was creating the actual component only if data is available .
On Mon, Dec 14, 2009 at 2:05 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
Or just set visibility based on error
On Saturday, December 12, 2009, vineet semwal
I have a case where I check some error condition at the beginning of the code.
If there is error I just want to display error message so
basically it is
if (error == true){
display message
} else {
//render regular page
add(component1)
add(compnent2)
}
if there is error I don't have any data to
add empty webmarkupcontainers as your components,if no error,replace the
containers with your components
else
you don't need to replace.
On Sat, Dec 12, 2009 at 8:02 AM, Swarnim Ranjitkar swarn...@hotmail.comwrote:
I have a case where I check some error condition at the beginning of the
