[jira] [Resolved] (WICKET-7090) Files in release jars do not have a modification timestamp set

[ https://issues.apache.org/jira/browse/WICKET-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-7090. - Fix Version/s: 10.0.0-M3 Resolution: Fixed > Files in release jars do not have a

[jira] [Closed] (WICKET-7090) Files in release jars do not have a modification timestamp set

[ https://issues.apache.org/jira/browse/WICKET-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-7090. --- > Files in release jars do not have a modification timestamp set >

[jira] [Commented] (WICKET-7092) Content Security Policy 'Nonces should only use the base64 charset'

[ https://issues.apache.org/jira/browse/WICKET-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803055#comment-17803055 ] Emond Papegaaij commented on WICKET-7092: - Base64 has 2 commonly used alphabets, normal and URL.

[jira] [Closed] (WICKET-7092) Content Security Policy 'Nonces should only use the base64 charset'

[ https://issues.apache.org/jira/browse/WICKET-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-7092. --- Resolution: Won't Fix The characters used in the nonce are valid according to the CSP

[jira] [Assigned] (WICKET-7090) Files in release jars do not have a modification timestamp set

[ https://issues.apache.org/jira/browse/WICKET-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-7090: --- Assignee: Emond Papegaaij > Files in release jars do not have a modification

[jira] [Commented] (WICKET-7092) Content Security Policy 'Nonces should only use the base64 charset'

[ https://issues.apache.org/jira/browse/WICKET-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802878#comment-17802878 ] Emond Papegaaij commented on WICKET-7092: - This seems like a bug in the tool used to check the

[jira] [Created] (WICKET-7090) Files in release jars do not have a modification timestamp set

Emond Papegaaij created WICKET-7090: --- Summary: Files in release jars do not have a modification timestamp set Key: WICKET-7090 URL: https://issues.apache.org/jira/browse/WICKET-7090 Project: Wicket

[jira] [Commented] (WICKET-7043) Bug report - enter button doesn't submit form on Safari

[ https://issues.apache.org/jira/browse/WICKET-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713956#comment-17713956 ] Emond Papegaaij commented on WICKET-7043: - This is a known bug in safari, which probably cannot

[jira] [Updated] (WICKET-7016) Support GCM-SIV for page store encryption

[ https://issues.apache.org/jira/browse/WICKET-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-7016: Description: The current ICrypter implementation uses AES-256 with CBC. Although this is

[jira] [Resolved] (WICKET-7016) Support GCM-SIV for page store encryption

[ https://issues.apache.org/jira/browse/WICKET-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-7016. - Fix Version/s: 10.0.0 9.13.0 Resolution: Fixed > Support

[jira] [Assigned] (WICKET-7016) Support GCM-SIV for page store encryption

[ https://issues.apache.org/jira/browse/WICKET-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-7016: --- Assignee: Emond Papegaaij > Support GCM-SIV for page store encryption >

[jira] [Created] (WICKET-7016) Support GCM-SIV for page store encryption

Emond Papegaaij created WICKET-7016: --- Summary: Support GCM-SIV for page store encryption Key: WICKET-7016 URL: https://issues.apache.org/jira/browse/WICKET-7016 Project: Wicket Issue Type:

[jira] [Closed] (WICKET-7014) Use new API for forward compatibility with CDI 4

[ https://issues.apache.org/jira/browse/WICKET-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-7014. --- > Use new API for forward compatibility with CDI 4 >

[jira] [Resolved] (WICKET-7014) Use new API for forward compatibility with CDI 4

[ https://issues.apache.org/jira/browse/WICKET-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-7014. - Fix Version/s: 9.13.0 10.0.0 Resolution: Fixed > Use new API

[jira] [Created] (WICKET-7014) Use new API for forward compatibility with CDI 4

Emond Papegaaij created WICKET-7014: --- Summary: Use new API for forward compatibility with CDI 4 Key: WICKET-7014 URL: https://issues.apache.org/jira/browse/WICKET-7014 Project: Wicket

[jira] [Assigned] (WICKET-7014) Use new API for forward compatibility with CDI 4

[ https://issues.apache.org/jira/browse/WICKET-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-7014: --- Assignee: Emond Papegaaij > Use new API for forward compatibility with CDI 4 >

[jira] [Commented] (WICKET-7002) Application metadata access should not require synchronization

[ https://issues.apache.org/jira/browse/WICKET-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601334#comment-17601334 ] Emond Papegaaij commented on WICKET-7002: - It is likely that the call stack is either collapsed

[jira] [Resolved] (WICKET-6970) Unnecessary string building in AssociatedMarkupSourcingStrategy

[ https://issues.apache.org/jira/browse/WICKET-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6970. - Fix Version/s: 10.0.0 9.10.0 Resolution: Fixed > Unnecessary

[jira] [Assigned] (WICKET-6970) Unnecessary string building in AssociatedMarkupSourcingStrategy

[ https://issues.apache.org/jira/browse/WICKET-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-6970: --- Assignee: Emond Papegaaij > Unnecessary string building in

[jira] [Created] (WICKET-6970) Unnecessary string building in AssociatedMarkupSourcingStrategy

Emond Papegaaij created WICKET-6970: --- Summary: Unnecessary string building in AssociatedMarkupSourcingStrategy Key: WICKET-6970 URL: https://issues.apache.org/jira/browse/WICKET-6970 Project:

[jira] [Commented] (WICKET-6959) Form#setDefaultButton does not work under Safari

[ https://issues.apache.org/jira/browse/WICKET-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500740#comment-17500740 ] Emond Papegaaij commented on WICKET-6959: - Actually, I think Safari has it wrong. This is from

[jira] [Commented] (WICKET-6938) wicket-autocomplete.js not CSP compliant

[ https://issues.apache.org/jira/browse/WICKET-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452554#comment-17452554 ] Emond Papegaaij commented on WICKET-6938: - [~alfortin] This will need to be addressed in the

[jira] [Commented] (WICKET-6938) wicket-autocomplete.js not CSP compliant

[ https://issues.apache.org/jira/browse/WICKET-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452500#comment-17452500 ] Emond Papegaaij commented on WICKET-6938: - [~alfortin] You cannot use eval in any way without

[jira] [Commented] (WICKET-6913) Java 17 compatibility

[ https://issues.apache.org/jira/browse/WICKET-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400259#comment-17400259 ] Emond Papegaaij commented on WICKET-6913: - That's unfortunate, as these modules are obviously

[jira] [Commented] (WICKET-6913) Java 17 compatibility

[ https://issues.apache.org/jira/browse/WICKET-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400173#comment-17400173 ] Emond Papegaaij commented on WICKET-6913: - A dependency upgrade normally is fine, but we

[jira] [Commented] (WICKET-6913) Java 17 compatibility

[ https://issues.apache.org/jira/browse/WICKET-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399989#comment-17399989 ] Emond Papegaaij commented on WICKET-6913: - Or we could copy the new module from master to 9.x

[jira] [Closed] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-6861. --- Resolution: Won't Fix Closing this issue. I've tried several solutions and came to the

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17270139#comment-17270139 ] Emond Papegaaij commented on WICKET-6861: - Ah, you mean {{_isPresent}} in

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17270056#comment-17270056 ] Emond Papegaaij commented on WICKET-6861: - That won't work either. In fact, when the server

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17270011#comment-17270011 ] Emond Papegaaij commented on WICKET-6861: - No, that won't help. The trigger function clears the

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17269967#comment-17269967 ] Emond Papegaaij commented on WICKET-6861: - We've hit the same error again, with our patched

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267723#comment-17267723 ] Emond Papegaaij commented on WICKET-6861: - We are now running our tests with a patched version

[jira] [Commented] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

[ https://issues.apache.org/jira/browse/WICKET-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266176#comment-17266176 ] Emond Papegaaij commented on WICKET-6861: - I've read the same in the spec and it indeed states

[jira] [Created] (WICKET-6861) Possible race condition in clearing and triggering of Wicket timers

Emond Papegaaij created WICKET-6861: --- Summary: Possible race condition in clearing and triggering of Wicket timers Key: WICKET-6861 URL: https://issues.apache.org/jira/browse/WICKET-6861 Project:

[jira] [Commented] (WICKET-6855) Request: Provide separate wicket-api.jar for interfaces

[ https://issues.apache.org/jira/browse/WICKET-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242714#comment-17242714 ] Emond Papegaaij commented on WICKET-6855: - The example projects you mentioned use the

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232163#comment-17232163 ] Emond Papegaaij commented on WICKET-6847: - Yes, this also affects 8.x. > async page storing

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230140#comment-17230140 ] Emond Papegaaij commented on WICKET-6847: - Yes, please retest, this piece of code is quite

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229901#comment-17229901 ] Emond Papegaaij commented on WICKET-6848: - Ok, I've found the cause. [~svenmeier] on your

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229895#comment-17229895 ] Emond Papegaaij commented on WICKET-6848: - Sorry for being a bit late to reply. I've got a very

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227385#comment-17227385 ] Emond Papegaaij commented on WICKET-6847: - Yes, but in this case it simply calls

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227336#comment-17227336 ] Emond Papegaaij commented on WICKET-6847: - I'm looking at the change by [~mgrigorov] once more

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227324#comment-17227324 ] Emond Papegaaij commented on WICKET-6847: - I think I know the cause of the problem. The check

[jira] [Updated] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6848: Affects Version/s: 8.10.0 > Session invalidation fails because response is already

[jira] [Resolved] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6848. - Fix Version/s: 8.11.0 9.2.0 Assignee: Emond Papegaaij

[jira] [Commented] (WICKET-6847) async page storing fails with flush before detach without session

[ https://issues.apache.org/jira/browse/WICKET-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224632#comment-17224632 ] Emond Papegaaij commented on WICKET-6847: - [~reiern70] in WICKET-6848 you said you are still

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224630#comment-17224630 ] Emond Papegaaij commented on WICKET-6848: - I've committed my patch as it does fix this

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224529#comment-17224529 ] Emond Papegaaij commented on WICKET-6848: - It is important for the cookie to be cleared. For

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223680#comment-17223680 ] Emond Papegaaij commented on WICKET-6848: - [~reiern70] That's a different bug: WICKET-6847. This

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223618#comment-17223618 ] Emond Papegaaij commented on WICKET-6848: - No, that does not work. At that point the

[jira] [Resolved] (WICKET-6849) quickstart styling is broken due to CSP

[ https://issues.apache.org/jira/browse/WICKET-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6849. - Fix Version/s: 9.2.0 Assignee: Emond Papegaaij Resolution: Fixed >

[jira] [Created] (WICKET-6849) quickstart styling is broken due to CSP

Emond Papegaaij created WICKET-6849: --- Summary: quickstart styling is broken due to CSP Key: WICKET-6849 URL: https://issues.apache.org/jira/browse/WICKET-6849 Project: Wicket Issue Type:

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223545#comment-17223545 ] Emond Papegaaij commented on WICKET-6848: - The attached patch fixes the issue by not flushing

[jira] [Updated] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6848: Attachment: WICKET-6848.diff > Session invalidation fails because response is already

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223529#comment-17223529 ] Emond Papegaaij commented on WICKET-6848: - I've done some more debugging and the current

[jira] [Commented] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223506#comment-17223506 ] Emond Papegaaij commented on WICKET-6848: - I've managed to produce a quickstart for this

[jira] [Updated] (WICKET-6848) Session invalidation fails because response is already committed

[ https://issues.apache.org/jira/browse/WICKET-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6848: Attachment: wicket6848.zip > Session invalidation fails because response is already

[jira] [Created] (WICKET-6848) Session invalidation fails because response is already committed

Emond Papegaaij created WICKET-6848: --- Summary: Session invalidation fails because response is already committed Key: WICKET-6848 URL: https://issues.apache.org/jira/browse/WICKET-6848 Project:

[jira] [Commented] (WICKET-6832) CSP support in Java 8

[ https://issues.apache.org/jira/browse/WICKET-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17216697#comment-17216697 ] Emond Papegaaij commented on WICKET-6832: - I totally agree with Martin, Sven and Andrea here.

[jira] [Resolved] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6702. - Resolution: Fixed > AsynchronousPageStore with NotDetachedModelChecker - "Not detached

[jira] [Resolved] (WICKET-6831) Try to flush the response before detach

[ https://issues.apache.org/jira/browse/WICKET-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6831. - Fix Version/s: 8.10.0 9.1.0 Assignee: Emond Papegaaij

[jira] [Commented] (WICKET-6831) Try to flush the response before detach

[ https://issues.apache.org/jira/browse/WICKET-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205471#comment-17205471 ] Emond Papegaaij commented on WICKET-6831: - I've cherry picked the 3 commits on a branch for

[jira] [Commented] (WICKET-6831) Try to flush the response before detach

[ https://issues.apache.org/jira/browse/WICKET-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17204742#comment-17204742 ] Emond Papegaaij commented on WICKET-6831: - I ran the tests on our application and did not see

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197514#comment-17197514 ] Emond Papegaaij commented on WICKET-6702: - In that case, we should do what you suggested. I'm

[jira] [Comment Edited] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197208#comment-17197208 ] Emond Papegaaij edited comment on WICKET-6702 at 9/16/20, 7:52 PM: ---

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197208#comment-17197208 ] Emond Papegaaij commented on WICKET-6702: - But that will remove the functionality of the async

[jira] [Commented] (WICKET-6831) Try to flush the response before detach

[ https://issues.apache.org/jira/browse/WICKET-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197207#comment-17197207 ] Emond Papegaaij commented on WICKET-6831: - No, throwing an exception after flushing will not

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17197018#comment-17197018 ] Emond Papegaaij commented on WICKET-6702: - I couldn't resist the temptation and tried flushing

[jira] [Created] (WICKET-6831) Try to flush the response before detach

Emond Papegaaij created WICKET-6831: --- Summary: Try to flush the response before detach Key: WICKET-6831 URL: https://issues.apache.org/jira/browse/WICKET-6831 Project: Wicket Issue Type:

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196993#comment-17196993 ] Emond Papegaaij commented on WICKET-6702: - [~svenmeier] as you can see, I've pushed a change to

[jira] [Updated] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6702: Fix Version/s: 9.1.0 > AsynchronousPageStore with NotDetachedModelChecker - "Not detached

[jira] [Comment Edited] (WICKET-6723) Move to Jakarta APIs and Servlet 4.0

[ https://issues.apache.org/jira/browse/WICKET-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196858#comment-17196858 ] Emond Papegaaij edited comment on WICKET-6723 at 9/16/20, 10:28 AM:

[jira] [Commented] (WICKET-6723) Move to Jakarta APIs and Servlet 4.0

[ https://issues.apache.org/jira/browse/WICKET-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196858#comment-17196858 ] Emond Papegaaij commented on WICKET-6723: - The migration to servlet 4 was discussed on the dev

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196141#comment-17196141 ] Emond Papegaaij commented on WICKET-6702: - [~tobiashaupt] I agree with you that it might be a

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195357#comment-17195357 ] Emond Papegaaij commented on WICKET-6702: - I've just tested the second solution, and for me it

[jira] [Commented] (WICKET-6702) AsynchronousPageStore with NotDetachedModelChecker - "Not detached model found" exception on several fast sequential Ajax calls

[ https://issues.apache.org/jira/browse/WICKET-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195353#comment-17195353 ] Emond Papegaaij commented on WICKET-6702: - This issue is still valid in 9.1.0-SNAPSHOT. I'm

[jira] [Commented] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

[ https://issues.apache.org/jira/browse/WICKET-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176217#comment-17176217 ] Emond Papegaaij commented on WICKET-6786: - [~svenmeier] I agree about the name.

[jira] [Resolved] (WICKET-6813) Setting child-src does not update frame-src after initial assignment

[ https://issues.apache.org/jira/browse/WICKET-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6813. - Resolution: Fixed > Setting child-src does not update frame-src after initial

[jira] [Closed] (WICKET-6812) CSPHeaderConfiguration only copies first value from child-src to frame-src

[ https://issues.apache.org/jira/browse/WICKET-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-6812. --- Resolution: Duplicate > CSPHeaderConfiguration only copies first value from child-src to

[jira] [Updated] (WICKET-6813) Setting child-src does not update frame-src after initial assignment

[ https://issues.apache.org/jira/browse/WICKET-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6813: Fix Version/s: 9.1.0 > Setting child-src does not update frame-src after initial

[jira] [Reopened] (WICKET-6813) Setting child-src does not update frame-src after initial assignment

[ https://issues.apache.org/jira/browse/WICKET-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reopened WICKET-6813: - Assignee: Emond Papegaaij > Setting child-src does not update frame-src after initial

[jira] [Closed] (WICKET-6813) Setting child-src does not update frame-src after initial assignment

[ https://issues.apache.org/jira/browse/WICKET-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij closed WICKET-6813. --- Resolution: Duplicate > Setting child-src does not update frame-src after initial

[jira] [Assigned] (WICKET-6812) CSPHeaderConfiguration only copies first value from child-src to frame-src

[ https://issues.apache.org/jira/browse/WICKET-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij reassigned WICKET-6812: --- Assignee: Emond Papegaaij > CSPHeaderConfiguration only copies first value from

[jira] [Created] (WICKET-6812) CSPHeaderConfiguration only copies first value from child-src to frame-src

Emond Papegaaij created WICKET-6812: --- Summary: CSPHeaderConfiguration only copies first value from child-src to frame-src Key: WICKET-6812 URL: https://issues.apache.org/jira/browse/WICKET-6812

[jira] [Resolved] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

[ https://issues.apache.org/jira/browse/WICKET-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij resolved WICKET-6786. - Fix Version/s: 9.1.0 Assignee: Emond Papegaaij Resolution: Fixed >

[jira] [Commented] (WICKET-6809) wicket-core-8.9.0.jar not closed when Application is undeployed from an application server

[ https://issues.apache.org/jira/browse/WICKET-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170022#comment-17170022 ] Emond Papegaaij commented on WICKET-6809: - [~bht] you keep on making assumptions which are not

[jira] [Commented] (WICKET-6809) wicket-core-8.9.0.jar not closed when Application is undeployed from an application server

[ https://issues.apache.org/jira/browse/WICKET-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169941#comment-17169941 ] Emond Papegaaij commented on WICKET-6809: - [~bht] I understand that issues like these can be

[jira] [Issue Comment Deleted] (WICKET-6809) wicket-core-8.9.0.jar not closed when Application is undeployed from an application server

[ https://issues.apache.org/jira/browse/WICKET-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6809: Comment: was deleted (was: [~bht] I agree with Sven that we should not add workarounds

[jira] [Commented] (WICKET-6809) wicket-core-8.9.0.jar not closed when Application is undeployed from an application server

[ https://issues.apache.org/jira/browse/WICKET-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17169893#comment-17169893 ] Emond Papegaaij commented on WICKET-6809: - [~bht] I agree with Sven that we should not add

[jira] [Commented] (WICKET-6808) Cannot add page to AjaxRequestTarget

[ https://issues.apache.org/jira/browse/WICKET-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168839#comment-17168839 ] Emond Papegaaij commented on WICKET-6808: - It's not that common to add the page to the

[jira] [Created] (WICKET-6808) Cannot add page to AjaxRequestTarget

Emond Papegaaij created WICKET-6808: --- Summary: Cannot add page to AjaxRequestTarget Key: WICKET-6808 URL: https://issues.apache.org/jira/browse/WICKET-6808 Project: Wicket Issue Type: Bug

[jira] [Commented] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

[ https://issues.apache.org/jira/browse/WICKET-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149689#comment-17149689 ] Emond Papegaaij commented on WICKET-6786: - Yes, that's what I meant. I hope the new

[jira] [Commented] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

[ https://issues.apache.org/jira/browse/WICKET-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149633#comment-17149633 ] Emond Papegaaij commented on WICKET-6786: - Hi Santiago, I do not agree with you on this

[jira] [Commented] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117795#comment-17117795 ] Emond Papegaaij commented on WICKET-6774: - [~mgrigorov] Good questions, we did not yet get any

[jira] [Commented] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117578#comment-17117578 ] Emond Papegaaij commented on WICKET-6774: - [~thomas.heigl] thanks for your input. You are right

[jira] [Commented] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116216#comment-17116216 ] Emond Papegaaij commented on WICKET-6774: - [~thomas.heigl] I've continued my quest to rewrite

[jira] [Updated] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6774: Attachment: ComponentBenchmarks.java > Separate model, behaviors and metadata into

[jira] [Updated] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emond Papegaaij updated WICKET-6774: Priority: Minor (was: Major) > Separate model, behaviors and metadata into separate

[jira] [Commented] (WICKET-6790) CLONE - Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116162#comment-17116162 ] Emond Papegaaij commented on WICKET-6790: - Hi [~o888ca], why did you clone WICKET-6774 into this

[jira] [Created] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

Emond Papegaaij created WICKET-6786: --- Summary: CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers Key: WICKET-6786 URL: https://issues.apache.org/jira/browse/WICKET-6786

[jira] [Commented] (WICKET-6774) Separate model, behaviors and metadata into separate fields

[ https://issues.apache.org/jira/browse/WICKET-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100195#comment-17100195 ] Emond Papegaaij commented on WICKET-6774: - I've done some measurements in our application and

  1   2   3   4   5   6   >