date:20140809

Re: java.lang.IllegalArgumentException: Argument 'name' may not be null or empty.

2014-08-09 Thread Martin Grigorov

Hi,

This kind of error may happen with request like
http://localhost:8080/wicket/bookmarkable/, assuming the app home page is
at http://localhost:8080/
I'll add a ticket to improve the default mappers for this case.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov


On Fri, Aug 8, 2014 at 1:26 PM, Karl-Heinz Golz karl-heinz.g...@t-online.de
 wrote:

 Hello,

 sometimes following exception is thrown (wicket 6.5.0):

 org.apache.wicket.DefaultExceptionMapper: Unexpected error occurred
 java.lang.IllegalArgumentException: Argument 'name' may not be null or
 empty.
 at org.apache.wicket.util.lang.Args.notEmpty(Args.java:64)
 at

 org.apache.wicket.core.request.mapper.AbstractComponentMapper.getPageClass(AbstractComponentMapper.java:137)
 at

 org.apache.wicket.core.request.mapper.BookmarkableMapper.parseRequest(BookmarkableMapper.java:110)
 at

 org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper.mapRequest(AbstractBookmarkableMapper.java:282)
 at

 org.apache.wicket.request.mapper.CompoundRequestMapper.mapRequest(CompoundRequestMapper.java:152)
 at

 org.apache.wicket.protocol.https.HttpsMapper.mapRequest(HttpsMapper.java:92)
 at

 org.apache.wicket.request.cycle.RequestCycle.resolveRequestHandler(RequestCycle.java:183)
 at

 org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:208)
 at

 org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:282)
 at

 org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:244)
 at

 org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
 at

 org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:267)
 at

 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at

 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203)
 at
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181)
 at

 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at

 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at

 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at

 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at

 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at

 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at

 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
 at

 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
 at
 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
 at java.lang.Thread.run(Thread.java:701)


 That occured approximately once per month and I ignored it but today it
 happened already about 10 times.
 Therefore I would like to find out what the reason is.

 Could someone give me a hint.

 Thanks in advance
 Karl-Heinz

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

2014-08-09 Thread Behrooz Nobakht

Thanks for the reply.

Could you possibly provide an insight on the solution below?
http://stackoverflow.com/a/8667136/248082

Actually, my problem is the same. As also a comment mentioned there, after
6.13, the custom mount mapper does not work properly any more.

Thanks,
Behrooz



On Thu, Jul 31, 2014 at 5:03 PM, Martin Grigorov mgrigo...@apache.org
wrote:

 On Jul 31, 2014 12:30 AM, Behrooz Nobakht nob...@gmail.com wrote:
 
  Thanks for the hint.
 
  It seems that we had a custom MountedMapper with the following specifics:
 
  @Override
  protected void encodePageComponentInfo(Url url,
  PageComponentInfo info) {
  // do nothing so that component info does not get
  // rendered in url
  }
 
  @Override
  public Url mapHandler(IRequestHandler requestHandler) {
  if (requestHandler instanceof
 ListenerInterfaceRequestHandler) {

 You need to check for BookmarkableListenerInterfaceRequestHandler too

  return null;
  } else {
  return super.mapHandler(requestHandler);
  }
  }
 
  I could not figure why this corrupted the callback URLs in the end but
 when
  I replaced them with the default one, the issue was resolved.
 
  Any idea to understand this better?
 
  Thanks,
  Behrooz
  
 
 
  On Wed, Jul 30, 2014 at 10:28 PM, Sven Meier s...@meiers.net wrote:
 
   Hi,
  
   u:./controllers
  
   that cannot be a valid url for an ajaxBehavior.
  
   You'll have to put a breakpoint in
 AbstractAjaxBehavior#getCallbackUrl()
   and see where the url is coming from.
  
   Regards
   Sven
  
  
  
   On 07/30/2014 10:04 PM, Behrooz Nobakht wrote:
  
   I tracked down the difference.
  
   When using 6.12.0, the HTML source of the page shows:
  
   Wicket.Ajax.ajax({u:./wicket/page?3-1.IBehaviorListener.1-table-
   form-url,e:change,c:url49,ad:true,m:POST});
  
  
   for the URL textfield that I use the AjaxFormCompnentUpdatingBehavior.
   However, from 6.13.0, instead the following is generated:
  
   Wicket.Ajax.ajax({u:./controllers,e:change,c:
   url42,ad:true,m:POST});
  
  
   which is different from above. Note that my page is a mounted page at
 path
   /controllers. The “u” field is the callback URL generated by the
 behavior.
  
   How should I fix this?
  
   Thanks,
   Behrooz
   
  
  
   On Wed, Jul 30, 2014 at 7:59 PM, Sven Meier s...@meiers.net wrote:
  
Hi,
  
   it works fine here with a small example.
  
   Please create a quickstart and attach it to a jira issue.
  
   Thanks
   Sven
  
  
   On 07/30/2014 07:42 PM, Behrooz Nobakht wrote:
  
Yes, I've tried all from 6.13.0 to 6.16.0 and the issue is the same.
  
   Thanks,
   Behrooz
  
  
  
   On Wed, Jul 30, 2014 at 7:32 PM, Sven Meier s...@meiers.net
 wrote:
  
 Have you tried 6.16.0?
  
   Regards
   Sven
  
  
  
   On 07/30/2014 07:11 PM, Behrooz Nobakht wrote:
  
 Hi,
  
   I just upgraded an Apache Wicket application from 6.12.0 to 6.13.0
   with
   a
   page including form with the following component:
  
   ```
   textfield.add(new AjaxFormComponentUpdatingBehavior(onchange) {
   private static final long serialVersionUID = 1L;
   @Override
   protected void onUpdate(AjaxRequestTarget target) {
   target.add(button);
   String validationMessage = validateModel(model);
   if (validationMessage != null) {
   addErrorMessage(target, feedback, validationMessage);
   button.setEnabled(false);
   return;
   }
  
   button.setEnabled(true);
   }
   });
   ```
  
   With 6.13.0, when I write something in the textfield and then
 press a
   tab
   (go to next field), the page automatically gets reloaded. Is this
 a
   known
   issue? What am I missing?
  
   Thanks in advance,
   Behrooz
  
  
  
  
 
   -
  
   To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
   For additional commands, e-mail: users-h...@wicket.apache.org
  
  
  
  
  -
   To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
   For additional commands, e-mail: users-h...@wicket.apache.org
  
  
  
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
   For additional commands, e-mail: users-h...@wicket.apache.org
  
  
 
 
  --
  -- Behrooz Nobakht




-- 
-- Behrooz Nobakht

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

2014-08-09 Thread Martin Grigorov

Sorry.I didn't get what I'm supposed to do.

Did you apply my suggestion ?
I see the code at http://stackoverflow.com/a/8667136/248082 is OK.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov


On Sat, Aug 9, 2014 at 6:15 PM, Behrooz Nobakht nob...@gmail.com wrote:

 Thanks for the reply.

 Could you possibly provide an insight on the solution below?
 http://stackoverflow.com/a/8667136/248082

 Actually, my problem is the same. As also a comment mentioned there, after
 6.13, the custom mount mapper does not work properly any more.

 Thanks,
 Behrooz



 On Thu, Jul 31, 2014 at 5:03 PM, Martin Grigorov mgrigo...@apache.org
 wrote:

  On Jul 31, 2014 12:30 AM, Behrooz Nobakht nob...@gmail.com wrote:
  
   Thanks for the hint.
  
   It seems that we had a custom MountedMapper with the following
 specifics:
  
   @Override
   protected void encodePageComponentInfo(Url url,
   PageComponentInfo info) {
   // do nothing so that component info does not get
   // rendered in url
   }
  
   @Override
   public Url mapHandler(IRequestHandler requestHandler) {
   if (requestHandler instanceof
  ListenerInterfaceRequestHandler) {
 
  You need to check for BookmarkableListenerInterfaceRequestHandler too
 
   return null;
   } else {
   return super.mapHandler(requestHandler);
   }
   }
  
   I could not figure why this corrupted the callback URLs in the end but
  when
   I replaced them with the default one, the issue was resolved.
  
   Any idea to understand this better?
  
   Thanks,
   Behrooz
   
  
  
   On Wed, Jul 30, 2014 at 10:28 PM, Sven Meier s...@meiers.net wrote:
  
Hi,
   
u:./controllers
   
that cannot be a valid url for an ajaxBehavior.
   
You'll have to put a breakpoint in
  AbstractAjaxBehavior#getCallbackUrl()
and see where the url is coming from.
   
Regards
Sven
   
   
   
On 07/30/2014 10:04 PM, Behrooz Nobakht wrote:
   
I tracked down the difference.
   
When using 6.12.0, the HTML source of the page shows:
   
Wicket.Ajax.ajax({u:./wicket/page?3-1.IBehaviorListener.1-table-
form-url,e:change,c:url49,ad:true,m:POST});
   
   
for the URL textfield that I use the
 AjaxFormCompnentUpdatingBehavior.
However, from 6.13.0, instead the following is generated:
   
Wicket.Ajax.ajax({u:./controllers,e:change,c:
url42,ad:true,m:POST});
   
   
which is different from above. Note that my page is a mounted page
 at
  path
/controllers. The “u” field is the callback URL generated by the
  behavior.
   
How should I fix this?
   
Thanks,
Behrooz

   
   
On Wed, Jul 30, 2014 at 7:59 PM, Sven Meier s...@meiers.net
 wrote:
   
 Hi,
   
it works fine here with a small example.
   
Please create a quickstart and attach it to a jira issue.
   
Thanks
Sven
   
   
On 07/30/2014 07:42 PM, Behrooz Nobakht wrote:
   
 Yes, I've tried all from 6.13.0 to 6.16.0 and the issue is the
 same.
   
Thanks,
Behrooz
   
   
   
On Wed, Jul 30, 2014 at 7:32 PM, Sven Meier s...@meiers.net
  wrote:
   
  Have you tried 6.16.0?
   
Regards
Sven
   
   
   
On 07/30/2014 07:11 PM, Behrooz Nobakht wrote:
   
  Hi,
   
I just upgraded an Apache Wicket application from 6.12.0 to
 6.13.0
with
a
page including form with the following component:
   
```
textfield.add(new AjaxFormComponentUpdatingBehavior(onchange)
 {
private static final long serialVersionUID = 1L;
@Override
protected void onUpdate(AjaxRequestTarget target) {
target.add(button);
String validationMessage = validateModel(model);
if (validationMessage != null) {
addErrorMessage(target, feedback, validationMessage);
button.setEnabled(false);
return;
}
   
button.setEnabled(true);
}
});
```
   
With 6.13.0, when I write something in the textfield and then
  press a
tab
(go to next field), the page automatically gets reloaded. Is
 this
  a
known
issue? What am I missing?
   
Thanks in advance,
Behrooz
   
   
   
   
  
-
   
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
   
   
   
   
   -
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
   
   
   
   
   
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
   
   
  
  
   --
   -- Behrooz Nobakht
 



 --
 -- Behrooz

Re: Foundation integrated in wicket

2014-08-09 Thread Paul Bors

Right, that’s all custom to your web app.

Suppose I want to take your SASS and apply it to my form field, more precisely 
a Wicket class.
Suppose I want to be able to “theme” the entire look-n-feel of the web app and 
only have to customize the theme and not the entire product.

That’s what I mean.

On Aug 7, 2014, at 10:15 AM, vp143 vishal.po...@cipriati.co.uk wrote:

 I am not sure I understand what you are after... I do not have anything on
 GitHub.
 
 I used SASS to install and compile my sass files and put my js files in my
 webapp directory.
 
 Let me know if you have any specific questions.
 
 Regards
 Vishal
 
 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/Foundation-integrated-in-wicket-tp4666792p4666936.html
 Sent from the Users forum mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

2014-08-09 Thread Behrooz Nobakht

Apologies from me if the question was not clear. Let me recap in a couple
of items:

   - From 6.12 to 6.13, something changed. This change requires to also
   check for BookmarkableListenerInterfaceRequestHandler in the custom
   MountedMapper. Is this change having other side effects? Is it
   documented to study more in depth?
   - From a higher level, what is the best practice to remove “version”
   from page URLs?

Thanks,
Behrooz



On Sat, Aug 9, 2014 at 6:40 PM, Martin Grigorov mgrigo...@apache.org
wrote:

 Sorry.I didn't get what I'm supposed to do.

 Did you apply my suggestion ?
 I see the code at http://stackoverflow.com/a/8667136/248082 is OK.

 Martin Grigorov
 Wicket Training and Consulting
 https://twitter.com/mtgrigorov


 On Sat, Aug 9, 2014 at 6:15 PM, Behrooz Nobakht nob...@gmail.com wrote:

  Thanks for the reply.
 
  Could you possibly provide an insight on the solution below?
  http://stackoverflow.com/a/8667136/248082
 
  Actually, my problem is the same. As also a comment mentioned there,
 after
  6.13, the custom mount mapper does not work properly any more.
 
  Thanks,
  Behrooz
 
 
 
  On Thu, Jul 31, 2014 at 5:03 PM, Martin Grigorov mgrigo...@apache.org
  wrote:
 
   On Jul 31, 2014 12:30 AM, Behrooz Nobakht nob...@gmail.com wrote:
   
Thanks for the hint.
   
It seems that we had a custom MountedMapper with the following
  specifics:
   
@Override
protected void encodePageComponentInfo(Url url,
PageComponentInfo info) {
// do nothing so that component info does not get
// rendered in url
}
   
@Override
public Url mapHandler(IRequestHandler requestHandler) {
if (requestHandler instanceof
   ListenerInterfaceRequestHandler) {
  
   You need to check for BookmarkableListenerInterfaceRequestHandler too
  
return null;
} else {
return super.mapHandler(requestHandler);
}
}
   
I could not figure why this corrupted the callback URLs in the end
 but
   when
I replaced them with the default one, the issue was resolved.
   
Any idea to understand this better?
   
Thanks,
Behrooz

   
   
On Wed, Jul 30, 2014 at 10:28 PM, Sven Meier s...@meiers.net
 wrote:
   
 Hi,

 u:./controllers

 that cannot be a valid url for an ajaxBehavior.

 You'll have to put a breakpoint in
   AbstractAjaxBehavior#getCallbackUrl()
 and see where the url is coming from.

 Regards
 Sven



 On 07/30/2014 10:04 PM, Behrooz Nobakht wrote:

 I tracked down the difference.

 When using 6.12.0, the HTML source of the page shows:


 Wicket.Ajax.ajax({u:./wicket/page?3-1.IBehaviorListener.1-table-
 form-url,e:change,c:url49,ad:true,m:POST});


 for the URL textfield that I use the
  AjaxFormCompnentUpdatingBehavior.
 However, from 6.13.0, instead the following is generated:

 Wicket.Ajax.ajax({u:./controllers,e:change,c:
 url42,ad:true,m:POST});


 which is different from above. Note that my page is a mounted page
  at
   path
 /controllers. The “u” field is the callback URL generated by the
   behavior.

 How should I fix this?

 Thanks,
 Behrooz
 


 On Wed, Jul 30, 2014 at 7:59 PM, Sven Meier s...@meiers.net
  wrote:

  Hi,

 it works fine here with a small example.

 Please create a quickstart and attach it to a jira issue.

 Thanks
 Sven


 On 07/30/2014 07:42 PM, Behrooz Nobakht wrote:

  Yes, I've tried all from 6.13.0 to 6.16.0 and the issue is the
  same.

 Thanks,
 Behrooz



 On Wed, Jul 30, 2014 at 7:32 PM, Sven Meier s...@meiers.net
   wrote:

   Have you tried 6.16.0?

 Regards
 Sven



 On 07/30/2014 07:11 PM, Behrooz Nobakht wrote:

   Hi,

 I just upgraded an Apache Wicket application from 6.12.0 to
  6.13.0
 with
 a
 page including form with the following component:

 ```
 textfield.add(new
 AjaxFormComponentUpdatingBehavior(onchange)
  {
 private static final long serialVersionUID = 1L;
 @Override
 protected void onUpdate(AjaxRequestTarget target) {
 target.add(button);
 String validationMessage = validateModel(model);
 if (validationMessage != null) {
 addErrorMessage(target, feedback, validationMessage);
 button.setEnabled(false);
 return;
 }

 button.setEnabled(true);
 }
 });
 ```

 With 6.13.0, when I write something in the textfield and then
   press a
 tab
 (go to next field), the page automatically gets reloaded. Is
  this
   a
 known
 issue? What am I missing?

 Thanks in advance,
 Behrooz

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

2014-08-09 Thread Martin Grigorov

Hi,

On Sat, Aug 9, 2014 at 8:15 PM, Behrooz Nobakht nob...@gmail.com wrote:

 Apologies from me if the question was not clear. Let me recap in a couple
 of items:

- From 6.12 to 6.13, something changed. This change requires to also


https://issues.apache.org/jira/browse/WICKET-4997


check for BookmarkableListenerInterfaceRequestHandler in the custom
MountedMapper. Is this change having other side effects? Is it


So far no one has found other side effects.


documented to study more in depth?


Check the ticket and the change in the code if necessary.


- From a higher level, what is the best practice to remove “version”
from page URLs?


Use stateless pages.



 Thanks,
 Behrooz
 


 On Sat, Aug 9, 2014 at 6:40 PM, Martin Grigorov mgrigo...@apache.org
 wrote:

  Sorry.I didn't get what I'm supposed to do.
 
  Did you apply my suggestion ?
  I see the code at http://stackoverflow.com/a/8667136/248082 is OK.
 
  Martin Grigorov
  Wicket Training and Consulting
  https://twitter.com/mtgrigorov
 
 
  On Sat, Aug 9, 2014 at 6:15 PM, Behrooz Nobakht nob...@gmail.com
 wrote:
 
   Thanks for the reply.
  
   Could you possibly provide an insight on the solution below?
   http://stackoverflow.com/a/8667136/248082
  
   Actually, my problem is the same. As also a comment mentioned there,
  after
   6.13, the custom mount mapper does not work properly any more.
  
   Thanks,
   Behrooz
  
  
  
   On Thu, Jul 31, 2014 at 5:03 PM, Martin Grigorov mgrigo...@apache.org
 
   wrote:
  
On Jul 31, 2014 12:30 AM, Behrooz Nobakht nob...@gmail.com
 wrote:

 Thanks for the hint.

 It seems that we had a custom MountedMapper with the following
   specifics:

 @Override
 protected void encodePageComponentInfo(Url url,
 PageComponentInfo info) {
 // do nothing so that component info does not get
 // rendered in url
 }

 @Override
 public Url mapHandler(IRequestHandler requestHandler) {
 if (requestHandler instanceof
ListenerInterfaceRequestHandler) {
   
You need to check for BookmarkableListenerInterfaceRequestHandler too
   
 return null;
 } else {
 return super.mapHandler(requestHandler);
 }
 }

 I could not figure why this corrupted the callback URLs in the end
  but
when
 I replaced them with the default one, the issue was resolved.

 Any idea to understand this better?

 Thanks,
 Behrooz
 


 On Wed, Jul 30, 2014 at 10:28 PM, Sven Meier s...@meiers.net
  wrote:

  Hi,
 
  u:./controllers
 
  that cannot be a valid url for an ajaxBehavior.
 
  You'll have to put a breakpoint in
AbstractAjaxBehavior#getCallbackUrl()
  and see where the url is coming from.
 
  Regards
  Sven
 
 
 
  On 07/30/2014 10:04 PM, Behrooz Nobakht wrote:
 
  I tracked down the difference.
 
  When using 6.12.0, the HTML source of the page shows:
 
 
  Wicket.Ajax.ajax({u:./wicket/page?3-1.IBehaviorListener.1-table-
  form-url,e:change,c:url49,ad:true,m:POST});
 
 
  for the URL textfield that I use the
   AjaxFormCompnentUpdatingBehavior.
  However, from 6.13.0, instead the following is generated:
 
  Wicket.Ajax.ajax({u:./controllers,e:change,c:
  url42,ad:true,m:POST});
 
 
  which is different from above. Note that my page is a mounted
 page
   at
path
  /controllers. The “u” field is the callback URL generated by the
behavior.
 
  How should I fix this?
 
  Thanks,
  Behrooz
  
 
 
  On Wed, Jul 30, 2014 at 7:59 PM, Sven Meier s...@meiers.net
   wrote:
 
   Hi,
 
  it works fine here with a small example.
 
  Please create a quickstart and attach it to a jira issue.
 
  Thanks
  Sven
 
 
  On 07/30/2014 07:42 PM, Behrooz Nobakht wrote:
 
   Yes, I've tried all from 6.13.0 to 6.16.0 and the issue is the
   same.
 
  Thanks,
  Behrooz
 
 
 
  On Wed, Jul 30, 2014 at 7:32 PM, Sven Meier s...@meiers.net
wrote:
 
Have you tried 6.16.0?
 
  Regards
  Sven
 
 
 
  On 07/30/2014 07:11 PM, Behrooz Nobakht wrote:
 
Hi,
 
  I just upgraded an Apache Wicket application from 6.12.0 to
   6.13.0
  with
  a
  page including form with the following component:
 
  ```
  textfield.add(new
  AjaxFormComponentUpdatingBehavior(onchange)
   {
  private static final long serialVersionUID = 1L;
  @Override
  protected void onUpdate(AjaxRequestTarget target) {
  target.add(button);
  String validationMessage = validateModel(model);
  if (validationMessage != null) {

Re: Foundation integrated in wicket

2014-08-09 Thread Paul Bors

I guess this doesn’t matter as long as one uses a theme outside of wicket.

n/m

On Aug 9, 2014, at 2:13 PM, Paul Bors p...@bors.ws wrote:

 Right, that’s all custom to your web app.
 
 Suppose I want to take your SASS and apply it to my form field, more 
 precisely a Wicket class.
 Suppose I want to be able to “theme” the entire look-n-feel of the web app 
 and only have to customize the theme and not the entire product.
 
 That’s what I mean.
 
 On Aug 7, 2014, at 10:15 AM, vp143 vishal.po...@cipriati.co.uk wrote:
 
 I am not sure I understand what you are after... I do not have anything on
 GitHub.
 
 I used SASS to install and compile my sass files and put my js files in my
 webapp directory.
 
 Let me know if you have any specific questions.
 
 Regards
 Vishal
 
 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/Foundation-integrated-in-wicket-tp4666792p4666936.html
 Sent from the Users forum mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Migration to wicket 7

2014-08-09 Thread Maxim Solodovnik

Thanks a lot


On 8 August 2014 15:28, Martin Grigorov mgrigo...@apache.org wrote:

 Here it is:

 https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-Usei18npropertyfilesforCSSclassnamesWICKET-5257

 Thanks for testing Wicket 7 and reporting such documentation issues!

 Martin Grigorov
 Wicket Training and Consulting
 https://twitter.com/mtgrigorov


 On Thu, Aug 7, 2014 at 7:38 PM, Martin Grigorov mgrigo...@apache.org
 wrote:

  this is the change:
  https://git-wip-us.apache.org/repos/asf?p=wicket.git;a=commit;h=2f87d0b
  it seems we forgot to add a migration entry about it. I'll update it soon
  the idea is to use i18n. now Wicket uses #getString() to find the value.
  check the latest master for the keys
 
  Martin Grigorov
  Wicket Training and Consulting
  https://twitter.com/mtgrigorov
 
 
  On Thu, Aug 7, 2014 at 7:31 PM, Maxim Solodovnik solomax...@gmail.com
  wrote:
 
  OK, I was searching the page for the name, and was unable to find it :(
 
  Any example on how to customize AjaxFallbackOrderByBorder without
  CssProvider
  ?
 
 
  On 8 August 2014 00:27, Martin Grigorov mgrigo...@apache.org wrote:
 
  
  
 
 https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-AllIXyzSettingsareremovedWICKET-5410
  
   Martin Grigorov
   Wicket Training and Consulting
   https://twitter.com/mtgrigorov
  
  
   On Thu, Aug 7, 2014 at 7:21 PM, Maxim Solodovnik 
 solomax...@gmail.com
   wrote:
  
and IPageSettings
   
sorry for multiple emails :(
   
   
On 8 August 2014 00:19, Maxim Solodovnik solomax...@gmail.com
  wrote:
   
 The guide also missing to
 mention org.apache.wicket.protocol.ws.IWebSocketSettings


 On 8 August 2014 00:18, Maxim Solodovnik solomax...@gmail.com
  wrote:

 Hello All,

 I'm currently trying to migrate to wicket 7.0.0 and currently
  stuck on
 replacing


   
  
 
 org.apache.wicket.extensions.markup.html.repeater.data.sort.OrderByLink.CssProvider
 it seems to be removed and Migration guide [1] contains no
  replacement
:(

 I'm trying to use it in custom class extending
   AjaxFallbackOrderByBorder

 Thanks in advance

 [1]

   
  
 
 https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0

 --
 WBR
 Maxim aka solomax




 --
 WBR
 Maxim aka solomax

   
   
   
--
WBR
Maxim aka solomax
   
  
 
 
 
  --
  WBR
  Maxim aka solomax
 
 
 




-- 
WBR
Maxim aka solomax

Re: java.lang.IllegalArgumentException: Argument 'name' may not be null or empty.

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

Re: Foundation integrated in wicket

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

Re: Upgrade to 6.12.0+ with AjaxFormComponentUpdatingBehavior reloads the page

Re: Foundation integrated in wicket

Re: Migration to wicket 7

8 matches

Site Navigation

Mail list logo

Footer information