Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Bram Pouwelse
Thanks 2012/10/23 Andreas Pieber : > well, then I start the release. at least all my tests doesnt show up > any problems... and this looks at least better than it was before... > I'll notify via this list once the release had been done > > kind regards, > Andreas > > On Tue, Oct 23, 2012 at 8:27 P

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Andreas Pieber
well, then I start the release. at least all my tests doesnt show up any problems... and this looks at least better than it was before... I'll notify via this list once the release had been done kind regards, Andreas On Tue, Oct 23, 2012 at 8:27 PM, Achim Nierbeck wrote: > Yep, that should do it

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Achim Nierbeck
Yep, that should do it, at least that's the part I tested a long running test in the coming week will show how good :-) regards, Achim 2012/10/23 Andreas Pieber : > OK, this [1] should do it. WDYT? Out with it? > > Kind regards, > Andreas > > [1] > https://github.com/ops4j/org.ops4j.pax.wicket/

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Andreas Pieber
OK, this [1] should do it. WDYT? Out with it? Kind regards, Andreas [1] https://github.com/ops4j/org.ops4j.pax.wicket/commit/a2a103355e6c480864dcf1bd748b197fe695b0db On Tue, Oct 23, 2012 at 7:16 PM, Bram Pouwelse wrote: > Hi Andreas, > > The fix seems to work, the only concern I have is that t

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Bram Pouwelse
Hi Andreas, The fix seems to work, the only concern I have is that this may cause exceptions in a case where a custom property is set on the application in the application factory. This property would not be set by Pax Wicket when the "enhanced" version of the application is created. But even wit

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Andreas Pieber
perfect! I just want to get a second feedback from Bram. If he also confirms the trick working I'll commit and release PaxWicket 1.1.1 tonight. Thank you very much for discovering and testing this one! Kind regards, Andreas On Tue, Oct 23, 2012 at 5:03 PM, Achim Nierbeck wrote: > Hi Guys, > > I

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Achim Nierbeck
Hi Guys, I changed it according to the idea of Bram, and tested it with my application that was consuming far to much memory (reproducable). It's now stable below 300 MB of Heap. @Bram thanks for pointing to this, this really safed my day :-D regards, Achim 2012/10/23 Achim Nierbeck : > Hi Andr

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Achim Nierbeck
Hi Andreas, I did change this locally and I'm testing it right now. Will give feedback later ... regards, Achim 2012/10/23 Andreas Pieber : > Well, I can commit your proposed changes, but you would still have to build > pax wicket locally and use the snapshots. When you confirm that the problem

Re: Pax Wicket PropertyResolver creating lots of DefaultClassCache instances

2012-10-23 Thread Andreas Pieber
Well, I can commit your proposed changes, but you would still have to build pax wicket locally and use the snapshots. When you confirm that the problem I really fixed I can push a release to Central within a Max of 8 hours... Let me know of I can help you in any way. Kind regards, Andreas On Oct

Re: Next releases of Pax CDI and Pax Web

2012-10-23 Thread Harald Wellmann
Hi Achim, that's fine with me. I'm looking forward to Pax Web 3.0.0.M1, and I'll release Pax CDI 0.3.0 soon after that. Regards, Harald Am 22.10.2012 09:00, schrieb Achim Nierbeck: Hi Harald, one more feedback on this thread :) I was successful on the weekend with testing Tomcat. So before