Re: servlet api "BigBang"
Hi Jon, On Wed, Feb 2, 2022 at 10:10 PM Locke, Jonathan (Luo Shibo) < jonath...@telenav.com> wrote: > If the community likes the idea, it would be possible to migrate Wicket to > KivaKit logging (and status messaging). > Wicket uses just slf4j-api, the facade. The applications decide which implementation to use: Logback, Log4j 1/2, ... Moving from slf4j-api to Kivakit would break all applications. The better way would be Kivakit to provide implementation of SLF4J APIs. I am not sure whether this will somehow reduce Kivakit's logging capabilities though. > > https://state-of-the-art.org/2021/08/17/logging.html > > https://medium.com/@jonathanlocke/why-messaging-is-a-better-way-to-report-status-2badb679345e > > KivaKit is a very Wicket-like way to do microservices, but you can consume > just pieces of it easily. Everything you'd need to do messaging and logging > is in the module kivakit-kernel (although there are some additional > loggers like EmailLogger in kivakit-extensions). Let me know if people are > interested in trying this out on a branch and I'd be happy to help out. > > Best, > >Jon > > > From: Martin Grigorov > Sent: Wednesday, February 2, 2022 12:15 PM > To: users@wicket.apache.org > Subject: Re: servlet api "BigBang" > > Hi, > > On Wed, Feb 2, 2022 at 4:59 PM Tobias Haupt > wrote: > > > We are using wicket for several projects and are piece by piece > > migrating to wicket 9. > > In all of these projects we use logback as logging adapter. Since > > version 9.x wicket requires version 2.0.0.alpha[x] of slfj. > > Logback provides releases starting with version 1.3.0-alpha compatible > > with slfj 2.0.0.alpha. The Problem is that the new version is built > > against the "new" servlet-api 5.0 only. There all the javax. namespaces > > are renamed to jakarta. This makes logback unasable for a lot of > > applications that still run in older Containers (Tomcat 9 etc.). The > > people at logback are aware of that problem: see issue LOGBACK-1575. > > > > Question: is there a hard requirement to update the dependency of wicket > > to slfi to 2.0.0 especially as these releases are still tagged as alpha? > > Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as > > possible? > > > > Wicket moved to 2.0.0-alpha because SLF4J 2.x is module-rized (JPMS) and > Wicket too since 9.5.0. > You can tell Maven to use 1.7.x in your application. The APIs are the same > so it should work. > > > > > > > kind regards, > > Tobias > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > [EXTERNAL EMAIL] CAUTION: This email originated from outside of Telenav. > DO NOT CLICK links or attachments unless you recognize the sender and know > the content is safe. >
Re: servlet api "BigBang"
Hi Martin, Hi, On Wed, Feb 2, 2022 at 4:59 PM Tobias Haupt wrote: We are using wicket for several projects and are piece by piece migrating to wicket 9. In all of these projects we use logback as logging adapter. Since version 9.x wicket requires version 2.0.0.alpha[x] of slfj. Logback provides releases starting with version 1.3.0-alpha compatible with slfj 2.0.0.alpha. The Problem is that the new version is built against the "new" servlet-api 5.0 only. There all the javax. namespaces are renamed to jakarta. This makes logback unasable for a lot of applications that still run in older Containers (Tomcat 9 etc.). The people at logback are aware of that problem: see issue LOGBACK-1575. Question: is there a hard requirement to update the dependency of wicket to slfi to 2.0.0 especially as these releases are still tagged as alpha? Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as possible? Wicket moved to 2.0.0-alpha because SLF4J 2.x is module-rized (JPMS) and Wicket too since 9.5.0. You can tell Maven to use 1.7.x in your application. The APIs are the same so it should work. Good to know, that its compatible to 1.7.x and wicket is not using any new api features. We will downgrade for the time beeing. kind regards, Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Tobias Haupt Software Engineer Telefon +49 (351) 4108-142 Fax +49 (351) 4108-5142 tobias.ha...@exedio.com www.exedio.com exedio Gesellschaft für Softwareentwicklung mbH Buchenstraße 16 B 01097 Dresden Deutschland Handelsregister: HRB 22109, Amtsgericht Dresden Sitz der Gesellschaft: Dresden Geschäftsführer: Sven-Erik Bornscheuer, Lutz Kirchner, Falk Krause - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
[ANNOUNCE] Apache Wicket 8.14.0 released
The Apache Wicket PMC is proud to announce Apache Wicket 8.14.0! Apache Wicket is an open source Java component oriented web application framework that powers thousands of web applications and web sites for governments, stores, universities, cities, banks, email providers, and more. You can find more about Apache Wicket at https://wicket.apache.org This release marks another minor release of Wicket 8. We use semantic versioning for the development of Wicket, and as such no API breaks are present in this release compared to 8.0.0. Using this release -- With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): org.apache.wicket wicket-core 8.14.0 Or download and build the distribution yourself, or use our convenience binary package you can find here: * Download: http://wicket.apache.org/start/wicket-8.x.html#manually Upgrading from earlier versions --- If you upgrade from 8.y.z this release is a drop in replacement. If you come from a version prior to 8.0.0, please read our Wicket 8 migration guide found at * http://s.apache.org/wicket8migrate Have fun! — The Wicket team CHANGELOG for 8.14.0: ** Bug * [WICKET-6908] - Possible bug / edge case where page is not detached * [WICKET-6910] - StalePageException not thrown * [WICKET-6914] - Visibility change of "File Upload" via ajax causes "missing" form-data * [WICKET-6931] - User guide: 'determinate' is not a verb; should be changed into 'to determine' * [WICKET-6944] - Memory leak in WicketEndpoint * [WICKET-6945] - MultipartFormComponentListener modifies enctype on invisible forms, leading to javascript errors ** Task * [WICKET-6919] - Improve EnclosureContainer's javadoc to explain that it should not be used with * [WICKET-6937] - Update the keystore used by the quickstart application * [WICKET-6942] - Replace usage of log4j 1.x in tests and wicket-examples with slf4j-simple - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: servlet api "BigBang"
If the community likes the idea, it would be possible to migrate Wicket to KivaKit logging (and status messaging). https://state-of-the-art.org/2021/08/17/logging.html https://medium.com/@jonathanlocke/why-messaging-is-a-better-way-to-report-status-2badb679345e KivaKit is a very Wicket-like way to do microservices, but you can consume just pieces of it easily. Everything you'd need to do messaging and logging is in the module kivakit-kernel (although there are some additional loggers like EmailLogger in kivakit-extensions). Let me know if people are interested in trying this out on a branch and I'd be happy to help out. Best, Jon From: Martin Grigorov Sent: Wednesday, February 2, 2022 12:15 PM To: users@wicket.apache.org Subject: Re: servlet api "BigBang" Hi, On Wed, Feb 2, 2022 at 4:59 PM Tobias Haupt wrote: > We are using wicket for several projects and are piece by piece > migrating to wicket 9. > In all of these projects we use logback as logging adapter. Since > version 9.x wicket requires version 2.0.0.alpha[x] of slfj. > Logback provides releases starting with version 1.3.0-alpha compatible > with slfj 2.0.0.alpha. The Problem is that the new version is built > against the "new" servlet-api 5.0 only. There all the javax. namespaces > are renamed to jakarta. This makes logback unasable for a lot of > applications that still run in older Containers (Tomcat 9 etc.). The > people at logback are aware of that problem: see issue LOGBACK-1575. > > Question: is there a hard requirement to update the dependency of wicket > to slfi to 2.0.0 especially as these releases are still tagged as alpha? > Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as > possible? > Wicket moved to 2.0.0-alpha because SLF4J 2.x is module-rized (JPMS) and Wicket too since 9.5.0. You can tell Maven to use 1.7.x in your application. The APIs are the same so it should work. > > kind regards, > Tobias > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > [EXTERNAL EMAIL] CAUTION: This email originated from outside of Telenav. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe.
Re: servlet api "BigBang"
Hi, On Wed, Feb 2, 2022 at 4:59 PM Tobias Haupt wrote: > We are using wicket for several projects and are piece by piece > migrating to wicket 9. > In all of these projects we use logback as logging adapter. Since > version 9.x wicket requires version 2.0.0.alpha[x] of slfj. > Logback provides releases starting with version 1.3.0-alpha compatible > with slfj 2.0.0.alpha. The Problem is that the new version is built > against the "new" servlet-api 5.0 only. There all the javax. namespaces > are renamed to jakarta. This makes logback unasable for a lot of > applications that still run in older Containers (Tomcat 9 etc.). The > people at logback are aware of that problem: see issue LOGBACK-1575. > > Question: is there a hard requirement to update the dependency of wicket > to slfi to 2.0.0 especially as these releases are still tagged as alpha? > Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as > possible? > Wicket moved to 2.0.0-alpha because SLF4J 2.x is module-rized (JPMS) and Wicket too since 9.5.0. You can tell Maven to use 1.7.x in your application. The APIs are the same so it should work. > > kind regards, > Tobias > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: servlet api "BigBang"
Correction: since version 9.5.0, wicket requires version 2.0.0.alpha[x] of slf4j. Wicket 9.4.0 required 1.7.25. We are using wicket for several projects and are piece by piece migrating to wicket 9. In all of these projects we use logback as logging adapter. Since version 9.x wicket requires version 2.0.0.alpha[x] of slfj. Logback provides releases starting with version 1.3.0-alpha compatible with slfj 2.0.0.alpha. The Problem is that the new version is built against the "new" servlet-api 5.0 only. There all the javax. namespaces are renamed to jakarta. This makes logback unasable for a lot of applications that still run in older Containers (Tomcat 9 etc.). The people at logback are aware of that problem: see issue LOGBACK-1575. Question: is there a hard requirement to update the dependency of wicket to slfi to 2.0.0 especially as these releases are still tagged as alpha? Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as possible? kind regards, Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Tobias Haupt Software Engineer Telefon +49 (351) 4108-142 Fax +49 (351) 4108-5142 tobias.ha...@exedio.com www.exedio.com exedio Gesellschaft für Softwareentwicklung mbH Buchenstraße 16 B 01097 Dresden Deutschland Handelsregister: HRB 22109, Amtsgericht Dresden Sitz der Gesellschaft: Dresden Geschäftsführer: Sven-Erik Bornscheuer, Lutz Kirchner, Falk Krause - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
servlet api "BigBang"
We are using wicket for several projects and are piece by piece migrating to wicket 9. In all of these projects we use logback as logging adapter. Since version 9.x wicket requires version 2.0.0.alpha[x] of slfj. Logback provides releases starting with version 1.3.0-alpha compatible with slfj 2.0.0.alpha. The Problem is that the new version is built against the "new" servlet-api 5.0 only. There all the javax. namespaces are renamed to jakarta. This makes logback unasable for a lot of applications that still run in older Containers (Tomcat 9 etc.). The people at logback are aware of that problem: see issue LOGBACK-1575. Question: is there a hard requirement to update the dependency of wicket to slfi to 2.0.0 especially as these releases are still tagged as alpha? Wouldn't it be better for wicket to stay at 1.x (eg. 1.7.35) as long as possible? kind regards, Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to use the JavaScriptDeferHeaderResponse correctly?
Hi Sven,
Thank you for the workaround, I’ll try it out this week.
I have also created a jira issue for this:
https://issues.apache.org/jira/browse/WICKET-6953
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 1 februari 2022 bij 20:22:58, Sven Meier (s...@meiers.net) schreef:
As a workaround you could use this:
getHeaderResponseDecorators().add( (response) -> {
if (RequestCycle.get().find(AjaxRequestTarget.class) == null) {
response = new JavaScriptDeferHeaderResponse(response);
}
return response;
});
Regards
Sven
On 01.02.22 17:16, Sven Meier wrote:
> Hi Bas,
>
> that seems to be broken since
> https://issues.apache.org/jira/browse/WICKET-6703
>
> The JS is correctly collected by PartialPageUpdate, but then sent
> through the response decorators once again, thus being wrapped in a
> 'DOMContentLoaded' listener.
>
> Please open a Jira issue.
>
> Regards
> Sven
>
>
> On 01.02.22 16:28, Sven Meier wrote:
>> Hi Bas,
>>
>> your attachment didn't make it through the mailing list.
>>
>> Can you point me to where I can download it from?
>>
>> Thanks
>> Sven
>>
>>
>> On 31.01.22 14:51, Bas Gooren wrote:
>>> Hi,
>>>
>>> We are experimenting with the JavaScriptDeferHeaderResponse, but out
>>> of the box it doesn’t work correctly for us.
>>> We are on wicket 9.7.0.
>>>
>>> On an Ajax call (e.g. link click), the response includes a
>>> ‘DOMContentLoaded’ event listener (which is not needed there). Since
>>> that never fires, any javascript handlers that are in the Ajax
>>> response are not registered.
>>> Please have a look at the attached Quickstart, which demonstrates
>>> the issue.
>>>
>>> Once the AJAX link is clicked, this evaluate node is added to the
>>> Ajax response (relevant part shown):
>>>
>>> document.addEventListener('DOMContentLoaded', function() {
>>>
(function(){console.log('test');})();(function(){Wicket.Log.enabled=true;})();(function(){Wicket.Ajax.baseUrl="?0";})();(function(){Wicket.Ajax.ajax({"u":"./?0-1.0-ajax","c":"ajax1","e":"click","pd":true});})();(function(){console.log('click');})();;
>>> });
>>>
>>> The Ajax handler (Wicket.Ajax.ajax()) is inside the DOMContentLoaded
>>> event handler.
>>>
>>> I’m not sure if we should be using the JavaScriptDeferHeaderResponse
>>> differently. We tried registering it using the three different
>>> methods provided by the header response decorators collection (add,
>>> add pre, add post).
>>>
>>> Any help would be appreciated :-)
>>>
>>> Met vriendelijke groet,
>>> Kind regards,
>>>
>>> Bas Gooren
>>>
>>> -
>>> 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
