Re: Apache + GitHub step 1

2014-02-12 Thread Jeremy Thomerson
Yes!


On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 Hi,

 Just noticed

 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

 We want all of it, right ?!

 Martin Grigorov
 Wicket Training and Consulting




-- 
Jeremy Thomerson
http://wickettraining.com


Re: Apache + GitHub step 1

2014-02-12 Thread Santo Raso
Finally


2014-02-12 9:00 GMT+01:00 Jeremy Thomerson jer...@wickettraining.com:

 Yes!


 On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov mgrigo...@apache.org
 wrote:

  Hi,
 
  Just noticed
 
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
 
  We want all of it, right ?!
 
  Martin Grigorov
  Wicket Training and Consulting
 



 --
 Jeremy Thomerson
 http://wickettraining.com



[VOTE] Release wicket 6.14.0

2014-02-12 Thread Martijn Dashorst
This is a vote to release Apache Wicket 6.14.0

Please download the source distributions found in our staging area
linked below.

I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.

[ ] Yes, release Apache Wicket 6.14.0
[ ] No, don't release Apache Wicket 6.14.0, because ...

Distributions, changelog, keys and signatures can be found at:

https://dist.apache.org/repos/dist/dev/wicket/6.14.0

Staging repository:

https://repository.apache.org/content/repositories/orgapachewicket-1004/

The binaries are available in the above link, as are a staging
repository for Maven. Typically the vote is on the source, but should
you find a problem with one of the binaries, please let me know, I can
re-roll them some way or the other.



The signatures for the source release artefacts:

apache-wicket-6.14.0.zip.asc

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
=4QkG
-END PGP SIGNATURE-

apache-wicket-6.14.0.tar.gz.asc

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
=3DVp
-END PGP SIGNATURE-



Release Notes - Wicket - Version 6.14.0

** Bug

* [WICKET-4697] - Autolinking not working as soon as component gets
  a wicket:id

* [WICKET-5043] - Page not mounted with WebApplication#mountPackage

* [WICKET-5449] - Missing chapter 2 is causing off-by-one page names
  in the guides URL links

* [WICKET-5460] - onBeforeRender called too early on stateless page

* [WICKET-5462] - Ajax form-component-label repainting fails when
  setResponsePage() is used to navigate away from
  the page that has previously failed form
  validaiton

* [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
  combination with Wizards

* [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
  ComponentNotFoundException as a side-effect

* [WICKET-5467] - NumberTextField should support any as valid step
  attribute value

* [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
  / after query parameters

* [WICKET-5469] - ModalWindow unload warning always displayed (even
  if window is closed)

* [WICKET-5472] - PackageResource#internalGetResourceStream() should
  return ProcessingResourceStream only when the
  resource is existing

* [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
  correctly

* [WICKET-5477] - CSS class is not applied to TD for data filter

* [WICKET-5478] - Wrong JavaDoc for WicketTester

* [WICKET-5480] - AutoLabelResolver creates null pointer exception
  in 6.13

* [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
  annotations

* [WICKET-5484] - WebPageRenderer must not render full page in Ajax
  requests

* [WICKET-5486] - WebPageRenderer should honor
  RedirectPolicy.ALWAYS_REDIRECT more consistently

* [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
  undefined on IE8, positions calendar out of
viewport

* [WICKET-5492] - WebApplication ignores a SecurityException when
  reading the configuration type

* [WICKET-5496] - Wrong translation of RangeValidator.minimum and
  RangeValidator.maximum

* [WICKET-5497] - NPE in JsonUtils when the value is null

* [WICKET-5499] - Page is not touched during initialization

* [WICKET-5500] - Ignore the path parameters when reading the page
  class

* [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050

** Improvement

* [WICKET-5288] - Allow script-Tags act as WebMarkUpContainer to
  add Child-Components

* [WICKET-5439] - Allow restarting AbstractAjaxTimerBehavior without
  updating its hosting component

* [WICKET-5463] - RequestUtil.getCharset(HttpServletRequest request)
  Resilience against unsupported Charsets in Request

* [WICKET-5470] - Remove 'final' from org.apache.wicket.markup.html.
  form.EnumChoiceRenderer#getDisplayValue

* [WICKET-5471] - Store the page if it is known that it will be used
  in a following request

* [WICKET-5493] - Disable jar indexing

** New Feature

* [WICKET-3491] - Introduce IComponentOnConfigureListener

** Task

* [WICKET-5488] - 

Re: Apache + GitHub step 1

2014-02-12 Thread Martin Grigorov
Don't get too excited :)
It is just about mail notifications and comments in JIRA/GitHub.
Pull Requests are still not supported.

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 9:48 AM, Santo Raso omgan...@gmail.com wrote:

 Finally


 2014-02-12 9:00 GMT+01:00 Jeremy Thomerson jer...@wickettraining.com:

  Yes!
 
 
  On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov mgrigo...@apache.org
  wrote:
 
   Hi,
  
   Just noticed
  
  
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
  
   We want all of it, right ?!
  
   Martin Grigorov
   Wicket Training and Consulting
  
 
 
 
  --
  Jeremy Thomerson
  http://wickettraining.com
 



Re: Apache + GitHub step 1

2014-02-12 Thread Martijn Dashorst
+1

What do we want? github integration! How much do we want it? All of it!
When do we want it? now!


On Wed, Feb 12, 2014 at 8:18 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 Hi,

 Just noticed

 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

 We want all of it, right ?!

 Martin Grigorov
 Wicket Training and Consulting




-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com


Re: Apache + GitHub step 1

2014-02-12 Thread Martin Grigorov
https://issues.apache.org/jira/browse/INFRA-7304

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 9:52 AM, Martijn Dashorst 
martijn.dasho...@gmail.com wrote:

 +1

 What do we want? github integration! How much do we want it? All of it!
 When do we want it? now!


 On Wed, Feb 12, 2014 at 8:18 AM, Martin Grigorov mgrigo...@apache.org
 wrote:

  Hi,
 
  Just noticed
 
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
 
  We want all of it, right ?!
 
  Martin Grigorov
  Wicket Training and Consulting
 



 --
 Become a Wicket expert, learn from the best: http://wicketinaction.com



[GitHub] wicket pull request: Wicket 4586: add getter for renderer in autoc...

2014-02-12 Thread tgoetz
Github user tgoetz closed the pull request at:

https://github.com/apache/wicket/pull/14



Re: [VOTE] Release wicket 6.14.0

2014-02-12 Thread Jonas
[X] Yes, release Apache Wicket 6.14.0
(non binding)

Tested our main webapp, plus verified the jira tracks I've filed
(WICKET-5469, WICKET-5493)

cheers,
Jonas


On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst 
martijn.dasho...@gmail.com wrote:

 This is a vote to release Apache Wicket 6.14.0

 Please download the source distributions found in our staging area
 linked below.

 I have included the signatures for both the source archives. This vote
 lasts for 72 hours minimum.

 [ ] Yes, release Apache Wicket 6.14.0
 [ ] No, don't release Apache Wicket 6.14.0, because ...

 Distributions, changelog, keys and signatures can be found at:

 https://dist.apache.org/repos/dist/dev/wicket/6.14.0

 Staging repository:


 https://repository.apache.org/content/repositories/orgapachewicket-1004/

 The binaries are available in the above link, as are a staging
 repository for Maven. Typically the vote is on the source, but should
 you find a problem with one of the binaries, please let me know, I can
 re-roll them some way or the other.

 

 The signatures for the source release artefacts:

 apache-wicket-6.14.0.zip.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
 zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
 =4QkG
 -END PGP SIGNATURE-

 apache-wicket-6.14.0.tar.gz.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
 KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
 =3DVp
 -END PGP SIGNATURE-

 

 Release Notes - Wicket - Version 6.14.0

 ** Bug

 * [WICKET-4697] - Autolinking not working as soon as component gets
   a wicket:id

 * [WICKET-5043] - Page not mounted with WebApplication#mountPackage

 * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names
   in the guides URL links

 * [WICKET-5460] - onBeforeRender called too early on stateless page

 * [WICKET-5462] - Ajax form-component-label repainting fails when
   setResponsePage() is used to navigate away from
   the page that has previously failed form
   validaiton

 * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
   combination with Wizards

 * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
   ComponentNotFoundException as a side-effect

 * [WICKET-5467] - NumberTextField should support any as valid step
   attribute value

 * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
   / after query parameters

 * [WICKET-5469] - ModalWindow unload warning always displayed (even
   if window is closed)

 * [WICKET-5472] - PackageResource#internalGetResourceStream() should
   return ProcessingResourceStream only when the
   resource is existing

 * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
   correctly

 * [WICKET-5477] - CSS class is not applied to TD for data filter

 * [WICKET-5478] - Wrong JavaDoc for WicketTester

 * [WICKET-5480] - AutoLabelResolver creates null pointer exception
   in 6.13

 * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
   annotations

 * [WICKET-5484] - WebPageRenderer must not render full page in Ajax
   requests

 * [WICKET-5486] - WebPageRenderer should honor
   RedirectPolicy.ALWAYS_REDIRECT more consistently

 * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
   undefined on IE8, positions calendar out of
 viewport

 * [WICKET-5492] - WebApplication ignores a SecurityException when
   reading the configuration type

 * [WICKET-5496] - Wrong translation of RangeValidator.minimum and
   RangeValidator.maximum

 * [WICKET-5497] - NPE in JsonUtils when the value is null

 * [WICKET-5499] - Page is not touched during initialization

 * [WICKET-5500] - Ignore the path parameters when reading the page
   class

 * [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050

 ** Improvement

 * [WICKET-5288] - Allow script-Tags act as WebMarkUpContainer to
   add Child-Components

 * [WICKET-5439] - Allow restarting AbstractAjaxTimerBehavior without
   updating its hosting component

 * [WICKET-5463] - RequestUtil.getCharset(HttpServletRequest request)
   Resilience against unsupported Charsets in Request

 * [WICKET-5470] - Remove 'final' from 

[GitHub] wicket pull request: WICKET-4592: WicketAjaxDebug.logError call re...

2014-02-12 Thread tgoetz
Github user tgoetz closed the pull request at:

https://github.com/apache/wicket/pull/15



[GitHub] wicket pull request: Implementation for WICKET-4861.

2014-02-12 Thread costescuandrei
Github user costescuandrei closed the pull request at:

https://github.com/apache/wicket/pull/20



Re: Apache + GitHub step 1

2014-02-12 Thread Martijn Dashorst
Appears to work already!

Martijn


On Wed, Feb 12, 2014 at 10:02 AM, Martin Grigorov mgrigo...@apache.orgwrote:

 https://issues.apache.org/jira/browse/INFRA-7304

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Feb 12, 2014 at 9:52 AM, Martijn Dashorst 
 martijn.dasho...@gmail.com wrote:

  +1
 
  What do we want? github integration! How much do we want it? All of it!
  When do we want it? now!
 
 
  On Wed, Feb 12, 2014 at 8:18 AM, Martin Grigorov mgrigo...@apache.org
  wrote:
 
   Hi,
  
   Just noticed
  
  
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
  
   We want all of it, right ?!
  
   Martin Grigorov
   Wicket Training and Consulting
  
 
 
 
  --
  Become a Wicket expert, learn from the best: http://wicketinaction.com
 




-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com


Re: Is EnclosureTest#testRender10 correct ?

2014-02-12 Thread Martin Grigorov
For completeness this issue has been fixed with
https://issues.apache.org/jira/browse/WICKET-5499

Martin Grigorov
Wicket Training and Consulting


On Tue, Feb 11, 2014 at 2:42 PM, Sven Meier s...@meiers.net wrote:

 Hi Martin,

 EnclosurePage_10 is stateless, so a redirect is issued to a new page
 instance. Therefore #setVisible() on the checkbox has no effect.


  or the test got broken at some point after running
 with -Dwicket.replace.expected.results=true ?


 Probably.

 Sven


 On 02/11/2014 02:07 PM, Martin Grigorov wrote:

 Hi,

 While debugging https://issues.apache.org/jira/browse/WICKET-5499 I
 stumbled upon
   org.apache.wicket.markup.html.internal.EnclosureTest#testRender10

 Maybe I miss something but this confuses me with its behavior.
 There is a page with the following markup:

 html xmlns:wicket
 body
wicket:enclosure child=input
  input wicket:id=input type=checkbox value=salami/
  span wicket:id=labellabel/span
/wicket:enclosure
 /body
 /html


 and Java code:

 public EnclosurePage_10()
 {
   add(new CheckBox(input));
 add(new Label(label));
 }

 The test changes the visibility of the CheckBox and/or the Label and
 verifies the response markup.
 No matter what combination of visibility these components have the final
 result is always the same - the enclosure and its children are always
 rendered.

 Am I missing something or the test got broken at some point after running
 with -Dwicket.replace.expected.results=true ?


 Martin Grigorov
 Wicket Training and Consulting





Problems with Weld in wicket-exaamples

2014-02-12 Thread Martin Grigorov
Hi,

While testing 6.14.0 I've hit this error when trying to run the examples
with 'mvn jetty:run':

ERROR - JettyContainer - Unable to create JettyWeldInjector.
CDI injection will not be available in Servlets, Filters or Listeners
java.lang.IllegalArgumentException: Cannot load class for
org.jboss.weld.environment.jetty.WeldDecorator
at
org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflections.java:62)
 at
org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.java:68)
at
org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:150)
 at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:733)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:233)
 at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1222)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:676)
 at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
at
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:256)
 at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
 at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
 at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
 at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90)
at org.eclipse.jetty.server.Server.doStart(Server.java:260)
 at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
 at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:511)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:364)
 at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:516)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
 at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.NoClassDefFoundError:
org/eclipse/jetty/servlet/ServletContextHandler$Decorator
at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
 at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
 at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
 at
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:415)
at
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:377)
 at
org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflections.java:55)
... 42 more
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jetty.servlet.ServletContextHandler$Decorator
 at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at 

Re: [VOTE] Release wicket 6.14.0

2014-02-12 Thread Martin Grigorov
[ X ] No, don't release Apache Wicket 6.14.0, because submitting stateless
form binds a session

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst 
martijn.dasho...@gmail.com wrote:

 This is a vote to release Apache Wicket 6.14.0

 Please download the source distributions found in our staging area
 linked below.

 I have included the signatures for both the source archives. This vote
 lasts for 72 hours minimum.

 [ ] Yes, release Apache Wicket 6.14.0
 [ ] No, don't release Apache Wicket 6.14.0, because ...

 Distributions, changelog, keys and signatures can be found at:

 https://dist.apache.org/repos/dist/dev/wicket/6.14.0

 Staging repository:


 https://repository.apache.org/content/repositories/orgapachewicket-1004/

 The binaries are available in the above link, as are a staging
 repository for Maven. Typically the vote is on the source, but should
 you find a problem with one of the binaries, please let me know, I can
 re-roll them some way or the other.

 

 The signatures for the source release artefacts:

 apache-wicket-6.14.0.zip.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
 zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
 =4QkG
 -END PGP SIGNATURE-

 apache-wicket-6.14.0.tar.gz.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
 KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
 =3DVp
 -END PGP SIGNATURE-

 

 Release Notes - Wicket - Version 6.14.0

 ** Bug

 * [WICKET-4697] - Autolinking not working as soon as component gets
   a wicket:id

 * [WICKET-5043] - Page not mounted with WebApplication#mountPackage

 * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names
   in the guides URL links

 * [WICKET-5460] - onBeforeRender called too early on stateless page

 * [WICKET-5462] - Ajax form-component-label repainting fails when
   setResponsePage() is used to navigate away from
   the page that has previously failed form
   validaiton

 * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
   combination with Wizards

 * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
   ComponentNotFoundException as a side-effect

 * [WICKET-5467] - NumberTextField should support any as valid step
   attribute value

 * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
   / after query parameters

 * [WICKET-5469] - ModalWindow unload warning always displayed (even
   if window is closed)

 * [WICKET-5472] - PackageResource#internalGetResourceStream() should
   return ProcessingResourceStream only when the
   resource is existing

 * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
   correctly

 * [WICKET-5477] - CSS class is not applied to TD for data filter

 * [WICKET-5478] - Wrong JavaDoc for WicketTester

 * [WICKET-5480] - AutoLabelResolver creates null pointer exception
   in 6.13

 * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
   annotations

 * [WICKET-5484] - WebPageRenderer must not render full page in Ajax
   requests

 * [WICKET-5486] - WebPageRenderer should honor
   RedirectPolicy.ALWAYS_REDIRECT more consistently

 * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
   undefined on IE8, positions calendar out of
 viewport

 * [WICKET-5492] - WebApplication ignores a SecurityException when
   reading the configuration type

 * [WICKET-5496] - Wrong translation of RangeValidator.minimum and
   RangeValidator.maximum

 * [WICKET-5497] - NPE in JsonUtils when the value is null

 * [WICKET-5499] - Page is not touched during initialization

 * [WICKET-5500] - Ignore the path parameters when reading the page
   class

 * [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050

 ** Improvement

 * [WICKET-5288] - Allow script-Tags act as WebMarkUpContainer to
   add Child-Components

 * [WICKET-5439] - Allow restarting AbstractAjaxTimerBehavior without
   updating its hosting component

 * [WICKET-5463] - RequestUtil.getCharset(HttpServletRequest request)
   Resilience against unsupported Charsets in Request

 * [WICKET-5470] - Remove 'final' from org.apache.wicket.markup.html.
 

Re: [VOTE] Release wicket 6.14.0

2014-02-12 Thread Sven Meier

Damn, not every page passed to PageProvider is stateless:

+   if (pageProvider.hasPageInstance())
+   {
+   IRequestablePage page = 
pageProvider.getPageInstance();

+   if (page instanceof Page)
+   {
+   ((Page) page).setStatelessHint(false);

:(

Sven

On 02/12/2014 02:10 PM, Martin Grigorov wrote:

[ X ] No, don't release Apache Wicket 6.14.0, because submitting stateless
form binds a session

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst 
martijn.dasho...@gmail.com wrote:


This is a vote to release Apache Wicket 6.14.0

Please download the source distributions found in our staging area
linked below.

I have included the signatures for both the source archives. This vote
lasts for 72 hours minimum.

[ ] Yes, release Apache Wicket 6.14.0
[ ] No, don't release Apache Wicket 6.14.0, because ...

Distributions, changelog, keys and signatures can be found at:

 https://dist.apache.org/repos/dist/dev/wicket/6.14.0

Staging repository:


https://repository.apache.org/content/repositories/orgapachewicket-1004/

The binaries are available in the above link, as are a staging
repository for Maven. Typically the vote is on the source, but should
you find a problem with one of the binaries, please let me know, I can
re-roll them some way or the other.



The signatures for the source release artefacts:

apache-wicket-6.14.0.zip.asc

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
=4QkG
-END PGP SIGNATURE-

apache-wicket-6.14.0.tar.gz.asc

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
=3DVp
-END PGP SIGNATURE-



Release Notes - Wicket - Version 6.14.0

** Bug

 * [WICKET-4697] - Autolinking not working as soon as component gets
   a wicket:id

 * [WICKET-5043] - Page not mounted with WebApplication#mountPackage

 * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names
   in the guides URL links

 * [WICKET-5460] - onBeforeRender called too early on stateless page

 * [WICKET-5462] - Ajax form-component-label repainting fails when
   setResponsePage() is used to navigate away from
   the page that has previously failed form
   validaiton

 * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
   combination with Wizards

 * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
   ComponentNotFoundException as a side-effect

 * [WICKET-5467] - NumberTextField should support any as valid step
   attribute value

 * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
   / after query parameters

 * [WICKET-5469] - ModalWindow unload warning always displayed (even
   if window is closed)

 * [WICKET-5472] - PackageResource#internalGetResourceStream() should
   return ProcessingResourceStream only when the
   resource is existing

 * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
   correctly

 * [WICKET-5477] - CSS class is not applied to TD for data filter

 * [WICKET-5478] - Wrong JavaDoc for WicketTester

 * [WICKET-5480] - AutoLabelResolver creates null pointer exception
   in 6.13

 * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
   annotations

 * [WICKET-5484] - WebPageRenderer must not render full page in Ajax
   requests

 * [WICKET-5486] - WebPageRenderer should honor
   RedirectPolicy.ALWAYS_REDIRECT more consistently

 * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
   undefined on IE8, positions calendar out of
 viewport

 * [WICKET-5492] - WebApplication ignores a SecurityException when
   reading the configuration type

 * [WICKET-5496] - Wrong translation of RangeValidator.minimum and
   RangeValidator.maximum

 * [WICKET-5497] - NPE in JsonUtils when the value is null

 * [WICKET-5499] - Page is not touched during initialization

 * [WICKET-5500] - Ignore the path parameters when reading the page
   class

 * [WICKET-5502] - Patch FileUploadBase to fix CVE-2014-0050

** Improvement

 * [WICKET-5288] - Allow script-Tags act as WebMarkUpContainer to
   

Re: Problems with Weld in wicket-exaamples

2014-02-12 Thread Emond Papegaaij
6.13.0 has the same error in the log, but cdi works fine. I think it's only 
trying to tell that injection of the servlet components is not available, 
something we don't need for the examples.

On Wednesday 12 February 2014 14:00:13 Martin Grigorov wrote:
 Hi,
 
 While testing 6.14.0 I've hit this error when trying to run the examples
 with 'mvn jetty:run':
 
 ERROR - JettyContainer - Unable to create JettyWeldInjector.
 CDI injection will not be available in Servlets, Filters or Listeners
 java.lang.IllegalArgumentException: Cannot load class for
 org.jboss.weld.environment.jetty.WeldDecorator
 at
 
org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflection
s
 .java:62) at
 org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.ja
 va:68) at
 
org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java
 :150) at
 
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandle
r.
 java:733) at
 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContext
H
 andler.java:233) at
 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
1222)
 at
 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java
:
 676) at
 
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455) 
at
 
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.ja
va:
 256) at
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
 ava:59) at
 
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection
 .java:224) at
 
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextH
an
 dlerCollection.java:167) at
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
 ava:59) at
 
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection
 .java:224) at
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
 ava:59) at
 
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.ja
va:
 90) at org.eclipse.jetty.server.Server.doStart(Server.java:260)
  at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
 at
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
 ava:59) at
 
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java
 :511) at
 
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:3
6
 4) at 
org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:516)
 at
 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultB
uildPl
 uginManager.java:106) at
 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
va:2
 08) at
 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
va:1
 53) at
 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
va:1
 45) at
 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
 cycleModuleBuilder.java:84) at
 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
 cycleModuleBuilder.java:59) at
 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Lif
 ecycleStarter.java:183) at
 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarte
 r.java:161) at
 org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
va:57
 ) at
 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl
 .java:43) at java.lang.reflect.Method.invoke(Method.java:606)
  at
 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.ja
 va:289) at
 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
229)
  at
 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
ncher.

Re: Problems with Weld in wicket-exaamples

2014-02-12 Thread Martin Grigorov
On Wed, Feb 12, 2014 at 2:23 PM, Emond Papegaaij emond.papega...@topicus.nl
 wrote:

 6.13.0 has the same error in the log, but cdi works fine. I think it's only
 trying to tell that injection of the servlet components is not available,
 something we don't need for the examples.


The only minor problem is that the examples don't start at all :-)
I.e. mvn command fails.



 On Wednesday 12 February 2014 14:00:13 Martin Grigorov wrote:
  Hi,
 
  While testing 6.14.0 I've hit this error when trying to run the examples
  with 'mvn jetty:run':
 
  ERROR - JettyContainer - Unable to create JettyWeldInjector.
  CDI injection will not be available in Servlets, Filters or Listeners
  java.lang.IllegalArgumentException: Cannot load class for
  org.jboss.weld.environment.jetty.WeldDecorator
  at
 
 org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflection
 s
  .java:62) at
 
 org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.ja
  va:68) at
 

 org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java
  :150) at
 
 org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandle
 r.
  java:733) at
 
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContext
 H
  andler.java:233) at
 
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
 1222)
  at
 
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java
 :
  676) at
 
 org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
 at
 
 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.ja
 va:
  256) at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
  ava:59) at
 

 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection
  .java:224) at
 
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextH
 an
  dlerCollection.java:167) at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
  ava:59) at
 

 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection
  .java:224) at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
  ava:59) at
 
 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.ja
 va:
  90) at org.eclipse.jetty.server.Server.doStart(Server.java:260)
   at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
  at
 
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.j
  ava:59) at
 

 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java
  :511) at
 
 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:3
 6
  4) at
 org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:516)
  at
 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultB
 uildPl
  uginManager.java:106) at
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
 va:2
  08) at
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
 va:1
  53) at
 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
 va:1
  45) at
 

 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
  cycleModuleBuilder.java:84) at
 

 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
  cycleModuleBuilder.java:59) at
 

 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Lif
  ecycleStarter.java:183) at
 

 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarte
  r.java:161) at
  org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
 va:57
  ) at
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl
  .java:43) at java.lang.reflect.Method.invoke(Method.java:606)
   at
 
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
 cher.ja
  va:289) at
 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
 229)
   at
 
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
 ncher.



Re: [VOTE] Release wicket 6.14.0

2014-02-12 Thread Martin Grigorov
I'll move setStatelessHint(false) back to RequestCycle.setResponsePage()

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 2:22 PM, Sven Meier s...@meiers.net wrote:

 Damn, not every page passed to PageProvider is stateless:

 +   if (pageProvider.hasPageInstance())
 +   {
 +   IRequestablePage page =
 pageProvider.getPageInstance();
 +   if (page instanceof Page)
 +   {
 +   ((Page) page).setStatelessHint(false);

 :(

 Sven


 On 02/12/2014 02:10 PM, Martin Grigorov wrote:

 [ X ] No, don't release Apache Wicket 6.14.0, because submitting stateless
 form binds a session

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst 
 martijn.dasho...@gmail.com wrote:

  This is a vote to release Apache Wicket 6.14.0

 Please download the source distributions found in our staging area
 linked below.

 I have included the signatures for both the source archives. This vote
 lasts for 72 hours minimum.

 [ ] Yes, release Apache Wicket 6.14.0
 [ ] No, don't release Apache Wicket 6.14.0, because ...

 Distributions, changelog, keys and signatures can be found at:

  https://dist.apache.org/repos/dist/dev/wicket/6.14.0

 Staging repository:


 https://repository.apache.org/content/repositories/orgapachewicket-1004/

 The binaries are available in the above link, as are a staging
 repository for Maven. Typically the vote is on the source, but should
 you find a problem with one of the binaries, please let me know, I can
 re-roll them some way or the other.

 

 The signatures for the source release artefacts:

 apache-wicket-6.14.0.zip.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
 zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
 =4QkG
 -END PGP SIGNATURE-

 apache-wicket-6.14.0.tar.gz.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
 KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
 =3DVp
 -END PGP SIGNATURE-

 

 Release Notes - Wicket - Version 6.14.0

 ** Bug

  * [WICKET-4697] - Autolinking not working as soon as component gets
a wicket:id

  * [WICKET-5043] - Page not mounted with WebApplication#mountPackage

  * [WICKET-5449] - Missing chapter 2 is causing off-by-one page names
in the guides URL links

  * [WICKET-5460] - onBeforeRender called too early on stateless page

  * [WICKET-5462] - Ajax form-component-label repainting fails when
setResponsePage() is used to navigate away from
the page that has previously failed form
validaiton

  * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
combination with Wizards

  * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
ComponentNotFoundException as a side-effect

  * [WICKET-5467] - NumberTextField should support any as valid step
attribute value

  * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
/ after query parameters

  * [WICKET-5469] - ModalWindow unload warning always displayed (even
if window is closed)

  * [WICKET-5472] - PackageResource#internalGetResourceStream()
 should
return ProcessingResourceStream only when the
resource is existing

  * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
correctly

  * [WICKET-5477] - CSS class is not applied to TD for data filter

  * [WICKET-5478] - Wrong JavaDoc for WicketTester

  * [WICKET-5480] - AutoLabelResolver creates null pointer exception
in 6.13

  * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
annotations

  * [WICKET-5484] - WebPageRenderer must not render full page in Ajax
requests

  * [WICKET-5486] - WebPageRenderer should honor
RedirectPolicy.ALWAYS_REDIRECT more consistently

  * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
undefined on IE8, positions calendar out of
  viewport

  * [WICKET-5492] - WebApplication ignores a SecurityException when
reading the configuration type

  * [WICKET-5496] - Wrong translation of RangeValidator.minimum and
RangeValidator.maximum

  * [WICKET-5497] - NPE in JsonUtils when the value is null

  * [WICKET-5499] - Page is not 

Re: [VOTE] Release wicket 6.14.0

2014-02-12 Thread Martin Grigorov
This is fixed.
I still have to check our main application with 6.14.0

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 2:47 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 I'll move setStatelessHint(false) back to RequestCycle.setResponsePage()

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Feb 12, 2014 at 2:22 PM, Sven Meier s...@meiers.net wrote:

 Damn, not every page passed to PageProvider is stateless:

 +   if (pageProvider.hasPageInstance())
 +   {
 +   IRequestablePage page =
 pageProvider.getPageInstance();
 +   if (page instanceof Page)
 +   {
 +   ((Page) page).setStatelessHint(false);

 :(

 Sven


 On 02/12/2014 02:10 PM, Martin Grigorov wrote:

 [ X ] No, don't release Apache Wicket 6.14.0, because submitting
 stateless
 form binds a session

 Martin Grigorov
 Wicket Training and Consulting


 On Wed, Feb 12, 2014 at 9:51 AM, Martijn Dashorst 
 martijn.dasho...@gmail.com wrote:

  This is a vote to release Apache Wicket 6.14.0

 Please download the source distributions found in our staging area
 linked below.

 I have included the signatures for both the source archives. This vote
 lasts for 72 hours minimum.

 [ ] Yes, release Apache Wicket 6.14.0
 [ ] No, don't release Apache Wicket 6.14.0, because ...

 Distributions, changelog, keys and signatures can be found at:

  https://dist.apache.org/repos/dist/dev/wicket/6.14.0

 Staging repository:


 https://repository.apache.org/content/repositories/
 orgapachewicket-1004/

 The binaries are available in the above link, as are a staging
 repository for Maven. Typically the vote is on the source, but should
 you find a problem with one of the binaries, please let me know, I can
 re-roll them some way or the other.

 
 

 The signatures for the source release artefacts:

 apache-wicket-6.14.0.zip.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVtWgCfU65+p9WqfeRJSvCGHNZRrCX8
 zx0An3SsVk+/mxKCLYQYgbq23RRZMpFE
 =4QkG
 -END PGP SIGNATURE-

 apache-wicket-6.14.0.tar.gz.asc

 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
 Comment: GPGTools - https://gpgtools.org

 iEYEABECAAYFAlL6qx8ACgkQJBX8W/xy/UVnPQCggvOBE7HT/YeryU+6V/PgwmEM
 KCkAoIBVa6vkeRtz9ZsesunI6+eHgiYc
 =3DVp
 -END PGP SIGNATURE-

 
 

 Release Notes - Wicket - Version 6.14.0

 ** Bug

  * [WICKET-4697] - Autolinking not working as soon as component gets
a wicket:id

  * [WICKET-5043] - Page not mounted with WebApplication#mountPackage

  * [WICKET-5449] - Missing chapter 2 is causing off-by-one page
 names
in the guides URL links

  * [WICKET-5460] - onBeforeRender called too early on stateless page

  * [WICKET-5462] - Ajax form-component-label repainting fails when
setResponsePage() is used to navigate away from
the page that has previously failed form
validaiton

  * [WICKET-5464] - AbstractAjaxTimerBehavior does not work in
combination with Wizards

  * [WICKET-5466] - ListenerInterfaceRequestHandler#respond throws
ComponentNotFoundException as a side-effect

  * [WICKET-5467] - NumberTextField should support any as valid
 step
attribute value

  * [WICKET-5468] - UrlRenderer#renderRelativeUrl potentially appends
/ after query parameters

  * [WICKET-5469] - ModalWindow unload warning always displayed (even
if window is closed)

  * [WICKET-5472] - PackageResource#internalGetResourceStream()
 should
return ProcessingResourceStream only when the
resource is existing

  * [WICKET-5473] - Wicket does not handle non in-memory Httpsessions
correctly

  * [WICKET-5477] - CSS class is not applied to TD for data filter

  * [WICKET-5478] - Wrong JavaDoc for WicketTester

  * [WICKET-5480] - AutoLabelResolver creates null pointer exception
in 6.13

  * [WICKET-5482] - Wicket-guice doesn't support @javax.inject.Named
annotations

  * [WICKET-5484] - WebPageRenderer must not render full page in Ajax
requests

  * [WICKET-5486] - WebPageRenderer should honor
RedirectPolicy.ALWAYS_REDIRECT more consistently

  * [WICKET-5491] - Wicket.DateTime.getViewportHeight() returning
undefined on IE8, positions calendar out of
  viewport

  * [WICKET-5492] - WebApplication ignores a SecurityException when
reading the configuration type

  * 

Re: Problems with Weld in wicket-exaamples

2014-02-12 Thread Emond Papegaaij
On Wednesday 12 February 2014 14:28:06 Martin Grigorov wrote:
 On Wed, Feb 12, 2014 at 2:23 PM, Emond Papegaaij 
emond.papega...@topicus.nl
  wrote:
  
  6.13.0 has the same error in the log, but cdi works fine. I think it's
  only
  trying to tell that injection of the servlet components is not available,
  something we don't need for the examples.
 
 The only minor problem is that the examples don't start at all :-)
 I.e. mvn command fails.

That's weird, because it does work on wicket-6.13.0. Did anything else 
change? 6.13 already uses wicket-cdi-1.1 in the examples, so that can't be 
the problem.

  On Wednesday 12 February 2014 14:00:13 Martin Grigorov wrote:
   Hi,
   
   While testing 6.14.0 I've hit this error when trying to run the 
examples
   with 'mvn jetty:run':
   
   ERROR - JettyContainer - Unable to create JettyWeldInjector.
   CDI injection will not be available in Servlets, Filters or Listeners
   java.lang.IllegalArgumentException: Cannot load class for
   org.jboss.weld.environment.jetty.WeldDecorator
   at
  
  
org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflectio
  n
  s
  
   .java:62) at
  
  org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.
  ja 
   va:68) at
  
  
org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.ja
  va 
   :150) at
  
  
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandle
  r.
  
   java:733) at
  
  
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContex
  t
  H
  
   andler.java:233) at
  
  
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
  1222)
  
   at
  
  
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.jav
  a
  
   676) at
  
  
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
  at
  
  
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.ja
  
  va:
   256) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
  on 
   .java:224) at
  
  
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextH
  an
  
   dlerCollection.java:167) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
  on 
   .java:224) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.ja
  
  va:
   90) at org.eclipse.jetty.server.Server.doStart(Server.java:260)
   
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
   
   at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.ja
  va 
   :511) at
  
  
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:

Re: Problems with Weld in wicket-exaamples

2014-02-12 Thread Martin Grigorov
commit 632e4a37c8bacc6756a98c916abbdff37f4e7220
Author: Martin Tzvetanov Grigorov mgrigo...@apache.org
Date:   Wed Feb 5 09:48:18 2014 +0100

Upgrade Weld to 2.1.2 to suppress some warnings

diff --git a/wicket-examples/pom.xml b/wicket-examples/pom.xml
index 162536f..1cb3313 100644
--- a/wicket-examples/pom.xml
+++ b/wicket-examples/pom.xml
@@ -124,12 +124,12 @@
dependency
groupIdorg.jboss.weld/groupId
artifactIdweld-core/artifactId
-   version2.1.0.Final/version
+   version2.1.2.Final/version
/dependency
dependency
groupIdorg.jboss.weld.servlet/groupId
artifactIdweld-servlet-core/artifactId
-   version2.1.0.Final/version
+   version2.1.2.Final/version
/dependency


Minor version update to avoid the WARNings about InjectionTarget.

Deploying the .war in Tomcat works fine, so it seems it is the integration
with Jetty 7.x

Martin Grigorov
Wicket Training and Consulting


On Wed, Feb 12, 2014 at 3:35 PM, Emond Papegaaij emond.papega...@topicus.nl
 wrote:

 On Wednesday 12 February 2014 14:28:06 Martin Grigorov wrote:
  On Wed, Feb 12, 2014 at 2:23 PM, Emond Papegaaij
 emond.papega...@topicus.nl
   wrote:
  
   6.13.0 has the same error in the log, but cdi works fine. I think it's
   only
   trying to tell that injection of the servlet components is not
 available,
   something we don't need for the examples.
 
  The only minor problem is that the examples don't start at all :-)
  I.e. mvn command fails.

 That's weird, because it does work on wicket-6.13.0. Did anything else
 change? 6.13 already uses wicket-cdi-1.1 in the examples, so that can't be
 the problem.

   On Wednesday 12 February 2014 14:00:13 Martin Grigorov wrote:
Hi,
   
While testing 6.14.0 I've hit this error when trying to run the
 examples
with 'mvn jetty:run':
   
ERROR - JettyContainer - Unable to create
 JettyWeldInjector.
CDI injection will not be available in Servlets, Filters or Listeners
java.lang.IllegalArgumentException: Cannot load class for
org.jboss.weld.environment.jetty.WeldDecorator
at
  
  
 org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflectio
   n
   s
  
.java:62) at
  
  
 org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.
   ja
va:68) at
  
  
 org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.ja
   va
:150) at
  
  
 org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandle
   r.
  
java:733) at
  
  
 org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContex
   t
   H
  
andler.java:233) at
  
  
 org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
   1222)
  
at
  
  
 org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.jav
   a
  
676) at
  
  
 org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
   at
  
  
 org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.ja
  
   va:
256) at
  
  
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
   .j
ava:59) at
  
  
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
   on
.java:224) at
  
  
 org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextH
   an
  
dlerCollection.java:167) at
  
  
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
   .j
ava:59) at
  
  
 org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
   on
.java:224) at
  
  
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
   .j
ava:59) at
  
  
 org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.ja
  
   va:
90) at org.eclipse.jetty.server.Server.doStart(Server.java:260)
   
 at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
   
at
  
  
 org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
   .j
ava:59) at
  
  
 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.ja
   va
:511) at
  
  
 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:



Re: Problems with Weld in wicket-exaamples

2014-02-12 Thread Emond Papegaaij
On Wednesday 12 February 2014 14:28:06 Martin Grigorov wrote:
 On Wed, Feb 12, 2014 at 2:23 PM, Emond Papegaaij 
emond.papega...@topicus.nl
  wrote:
  
  6.13.0 has the same error in the log, but cdi works fine. I think it's
  only
  trying to tell that injection of the servlet components is not available,
  something we don't need for the examples.
 
 The only minor problem is that the examples don't start at all :-)
 I.e. mvn command fails.

I've just tested with wicket-6.x and the examples start just fine with 
jetty:run here.

 
  On Wednesday 12 February 2014 14:00:13 Martin Grigorov wrote:
   Hi,
   
   While testing 6.14.0 I've hit this error when trying to run the 
examples
   with 'mvn jetty:run':
   
   ERROR - JettyContainer - Unable to create JettyWeldInjector.
   CDI injection will not be available in Servlets, Filters or Listeners
   java.lang.IllegalArgumentException: Cannot load class for
   org.jboss.weld.environment.jetty.WeldDecorator
   at
  
  
org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflectio
  n
  s
  
   .java:62) at
  
  org.jboss.weld.environment.jetty.JettyContainer.initialize(JettyContainer.
  ja 
   va:68) at
  
  
org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.ja
  va 
   :150) at
  
  
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandle
  r.
  
   java:733) at
  
  
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContex
  t
  H
  
   andler.java:233) at
  
  
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
  1222)
  
   at
  
  
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.jav
  a
  
   676) at
  
  
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:455)
  at
  
  
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.ja
  
  va:
   256) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
  on 
   .java:224) at
  
  
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextH
  an
  
   dlerCollection.java:167) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollecti
  on 
   .java:224) at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.ja
  
  va:
   90) at org.eclipse.jetty.server.Server.doStart(Server.java:260)
   
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65)
   
   at
  
  
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle
  .j 
   ava:59) at
  
  
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.ja
  va 
   :511) at
  
  
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:

Re: Apache + GitHub step 1

2014-02-12 Thread Martin Funk
 Pull Requests are still not supported.
But they could be pulled to local and then pushed to the apache repo by core 
commiters, right?

mf

Am 12.02.2014 um 09:52 schrieb Martin Grigorov mgrigo...@apache.org:

 Don't get too excited :)
 It is just about mail notifications and comments in JIRA/GitHub.
 Pull Requests are still not supported.
 
 Martin Grigorov
 Wicket Training and Consulting
 
 
 On Wed, Feb 12, 2014 at 9:48 AM, Santo Raso omgan...@gmail.com wrote:
 
 Finally
 
 
 2014-02-12 9:00 GMT+01:00 Jeremy Thomerson jer...@wickettraining.com:
 
 Yes!
 
 
 On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov mgrigo...@apache.org
 wrote:
 
 Hi,
 
 Just noticed
 
 
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
 
 We want all of it, right ?!
 
 Martin Grigorov
 Wicket Training and Consulting
 
 
 
 
 --
 Jeremy Thomerson
 http://wickettraining.com
 
 



Re: Apache + GitHub step 1

2014-02-12 Thread Martin Grigorov
On Wed, Feb 12, 2014 at 7:12 PM, Martin Funk mafulaf...@gmail.com wrote:

  Pull Requests are still not supported.
 But they could be pulled to local and then pushed to the apache repo by
 core commiters, right?


Right, but it involves manual work in several steps.
For me the easiest way is to add '.patch' to the PR url, download it and
'git am' it. This losses the author info though...



 mf

 Am 12.02.2014 um 09:52 schrieb Martin Grigorov mgrigo...@apache.org:

  Don't get too excited :)
  It is just about mail notifications and comments in JIRA/GitHub.
  Pull Requests are still not supported.
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
  On Wed, Feb 12, 2014 at 9:48 AM, Santo Raso omgan...@gmail.com wrote:
 
  Finally
 
 
  2014-02-12 9:00 GMT+01:00 Jeremy Thomerson jer...@wickettraining.com:
 
  Yes!
 
 
  On Wed, Feb 12, 2014 at 2:18 AM, Martin Grigorov mgrigo...@apache.org
  wrote:
 
  Hi,
 
  Just noticed
 
 
 
 
 https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
 
  We want all of it, right ?!
 
  Martin Grigorov
  Wicket Training and Consulting
 
 
 
 
  --
  Jeremy Thomerson
  http://wickettraining.com