Hi guys,
you are absolutely right. There wasn't a bug... I just overseen that there
were some changes. Other developers introduced another component with
appropriate html tag in the super class so I didn't see that.
Regards,
Dmitriy
2013/2/1 Martin Grigorov mgrigo...@apache.org
Hi,
I think
Understood. I am still unclear why wicket would behave differently in
deployment and development configuration with respect to missing components
in the markup. Is there any actual use case for this? If not, I believe it
would be better to have a consistent behavior.
Of course, changing the way
On Tue, Feb 5, 2013 at 10:05 AM, Marios Skounakis msc...@gmail.com wrote:
Understood. I am still unclear why wicket would behave differently in
deployment and development configuration with respect to missing components
in the markup. Is there any actual use case for this? If not, I believe it
If your web.xml specifies configuration=deployment and you want to report
the runtime error on a custom page then in your Application class:
protected void init() {
...
getApplicationSettings().setInternalErrorPage(MyInternalErrorPage.class);
...
}
class MyInternalErrorPage extend WebPage
Hi Folks,
I have another problem during Wicket 6 migration. This time it is a problem
with markup inheritance.
I have an old wicket panel and appropriate markup file:
MyOldGoodWicketPanel MyOldGoodWicketPanel.html
Markup file looks like this:
wicket:panel
... stuff ...
/wicket:panel
Some
Hi,
I think there are no changes in this area.
Do you extend/inherit the markup or completely override it ?
I expect to see wicket:extend instead of wicket:panel in
MyNewPanel.html.
Create a quickstart and attach it to a ticket in Jira please.
On Fri, Feb 1, 2013 at 2:12 PM, Dmitriy Neretin
