Re: AbstractTransformerBehavior prevents further rendering.

2020-08-18 Thread Sven Meier

Hi,

sorry I missed that: on first sight it seems to work with a single 
transformer only.


Better you combined both your behaviors into one.

Have fun
Sven


On 18.08.20 08:11, Thorsten Schöning wrote:

Guten Tag Sven Meier,
am Montag, 17. August 2020 um 20:34 schrieben Sie:


please create a quickstart, without debugging I cannot pinpoint the problem.

Will try to have a look at this later. In general, should multiple of
my behaviours on the same component work? Do you know of any tests in
place already making sure this works?

Because in my setup the problem happens when executed using
WicketTester, which might make a difference to normal rendering as
well.

Mit freundlichen Grüßen,

Thorsten Schöning



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



Sub: HSTS filter

2020-08-18 Thread sundar saba
Hi all,

  I deploy wicket quick start application in tomcat and run in
https. I enabled HSTS headers in tomcat. I access the application  in
browser and various tools(Postman) HSTS filters are only displayed for pure
HTML pages in response header and wherever I use wicket component in HTML
pages HSTS filters are not displayed in response headers  for those pages.
Can you all please give your suggestion or feedbacks to move forward in
this issue.


Re: Sub: HSTS filter

2020-08-18 Thread Sven Meier

Hi,

are these headers preserved on other dynamic content, e.g. a servlet or jsp?

Or are they missing from Wicket generated content only?

Have fun
Sven


On 18.08.20 08:27, sundar saba wrote:

Hi all,

   I deploy wicket quick start application in tomcat and run in
https. I enabled HSTS headers in tomcat. I access the application  in
browser and various tools(Postman) HSTS filters are only displayed for pure
HTML pages in response header and wherever I use wicket component in HTML
pages HSTS filters are not displayed in response headers  for those pages.
Can you all please give your suggestion or feedbacks to move forward in
this issue.



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



Re: AbstractTransformerBehavior prevents further rendering.

2020-08-18 Thread Thorsten Schöning
Guten Tag Sven Meier,
am Dienstag, 18. August 2020 um 08:50 schrieben Sie:

> sorry I missed that: on first sight it seems to work with a single
> transformer only.

Is that a special restriction for transformers only? Because
behaviours in general seem to be looped through when rendering
components.

Doesn't it make more sense to support multiple transformers as well?
Need to decide if I try to fix the underlying root cause or implement
a workaround. Combing my transformers isn't that easy, they are
totally unrelated in theory and are used individually already.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow


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



Re: AbstractTransformerBehavior prevents further rendering.

2020-08-18 Thread Sven Meier

Hi Thorsten,

>Is that a special restriction for transformers only?

transformers do something very special, they temporarily replace the 
response:


https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/markup/transformer/AbstractTransformerBehavior.java

I haven't tried it, but using two of these seems not to work. I never 
seen the need for this though.


Have fun
Sven


On 18.08.20 14:38, Thorsten Schöning wrote:

Guten Tag Sven Meier,
am Dienstag, 18. August 2020 um 08:50 schrieben Sie:


sorry I missed that: on first sight it seems to work with a single
transformer only.

Is that a special restriction for transformers only? Because
behaviours in general seem to be looped through when rendering
components.

Doesn't it make more sense to support multiple transformers as well?
Need to decide if I try to fix the underlying root cause or implement
a workaround. Combing my transformers isn't that easy, they are
totally unrelated in theory and are used individually already.

Mit freundlichen Grüßen,

Thorsten Schöning



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