Re: Markupstream.hasMore vs. MarkupStream.next

[Thorsten Schöning]

Guten Tag Thorsten Schöning,
am Freitag, 13. Mai 2016 um 20:14 schrieben Sie:

> Is this a bug or is using hasMore the wrong idiom in this case?

https://issues.apache.org/jira/browse/WICKET-6165

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: Generating table header ids for multiple tables pe rpage

[Thorsten Schöning]

Guten Tag Thorsten Schöning,
am Sonntag, 15. Mai 2016 um 11:14 schrieben Sie:

> So next I will have a look at extending
> AbstractTransformerBehavior with its "tranform" method.

Hi,

this was far easier to use, beautiful Wicket... Sadly I saw it too
late and wasted quite some hours on the former approach. :-)

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: wicket 6.x / java.text.ParseException on multiple div's

[Korbinian Bachl]

@Martin Spielmann, @Per Negro

thank you for your help. In fact I found out that there was a glitch in the 
HTML, however, not with the div's! - It seems as the parser has some problems 
when there is an error in the markup with quotations; In my case I had a 
innocent looking 



on the page hirarchy at the divs; (content a much lower level)

If you look at it you see 2 quotations at 340 and this seems to break the 
parser. He gives out the error, but the error is not where he reported it. 
Since my HTML got over 1000 lines i had quite a time to find this little bugger.

Anyway thanks for your help!

Best,

Korbinian

- Ursprüngliche Mail -
> Von: "Martin Spielmann" 
> An: users@wicket.apache.org
> Gesendet: Sonntag, 15. Mai 2016 11:47:07
> Betreff: Re: wicket 6.x / java.text.ParseException on multiple div's

> Hello Korbinian,
> 
> the error message tells you about a duplicated attribute. Please check if 
> there
> is a tag looking like this in your code:
> 
> 
> 
> 
> 
> E.g. smth like this:
> 
> Happened some times to me...
> 
> Best regards,
> Martin
> 
> 
> 
> Am 15. Mai 2016 11:39:30 MESZ, schrieb Korbinian Bachl
> :
>>Hello,
>>
>>I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now
>>got a problem I dont know how to solve. A page throws following error:
>>
>>java.text.ParseException: Same attribute found twice: div (line 163,
>>column 52)
>>at
>>org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
>>at
>>org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)
>>
>>
>>so far I would expect this to happen on wrong/ malformed HTML - but my
>>HTML is fine is indeed needed this way!
>>
>>complained HTML:
>>
>>
>>
>>      
>>           content
>>        
>>        
>>        
>>              content
>>        
>>
>>
>>So what is going on here? Why does wicket complain about those poor
>>div's? Is there any way I can disable this check for div's??? For me
>>this behaviour seems as a bug as div following a div is perfectly fine
>>HTML code?
>>
>>Best,
>>
>>Korbinian
>>
>>-
>>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>For additional commands, e-mail: users-h...@wicket.apache.org
> 
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: wicket 6.x / java.text.ParseException on multiple div's

[Korbinian Bachl]

Hello Per,

yes, when I remove just 1 of the 2 div's it works instantly; I can tigger this 
by putting in:

A
B


and he complains

Best,

Korbinian

- Ursprüngliche Mail -
> Von: "Per Newgro" 
> An: users@wicket.apache.org
> Gesendet: Sonntag, 15. Mai 2016 11:54:30
> Betreff: Re: wicket 6.x / java.text.ParseException on multiple div's

> Did you try to remove the questionable markup to see what is happening?
> 
> Am 15.05.2016 um 11:39 schrieb Korbinian Bachl:
>> Hello,
>>
>> I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now got a
>> problem I dont know how to solve. A page throws following error:
>>
>> java.text.ParseException: Same attribute found twice: div (line 163, column 
>> 52)
>> at
>> org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
>>  at 
>> org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)
>> 
>>
>> so far I would expect this to happen on wrong/ malformed HTML - but my HTML 
>> is
>> fine is indeed needed this way!
>>
>> complained HTML:
>>
>> 
>>
>>
>> content
>>  
>>  
>>  
>>content
>>  
>> 
>>
>> So what is going on here? Why does wicket complain about those poor div's? Is
>> there any way I can disable this check for div's??? For me this behaviour 
>> seems
>> as a bug as div following a div is perfectly fine HTML code?
>>
>> Best,
>>
>> Korbinian
>>
>> -
>> 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

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

Re: wicket 6.x / java.text.ParseException on multiple div's

[Korbinian Bachl]

Hello Martin,

I tried to look for this but I isn't that easy. He really complains about fine 
closed div's if I remove the mentioned div's it renders fine;

I can trigger the error when I just enter this into my page HTML:


A
B


and thats a perfectly fine HTML

Best,
Korbinian 


- Ursprüngliche Mail -
> Von: "Martin Spielmann" 
> An: users@wicket.apache.org
> Gesendet: Sonntag, 15. Mai 2016 11:47:07
> Betreff: Re: wicket 6.x / java.text.ParseException on multiple div's

> Hello Korbinian,
> 
> the error message tells you about a duplicated attribute. Please check if 
> there
> is a tag looking like this in your code:
> 
> 
> 
> 
> 
> E.g. smth like this:
> 
> Happened some times to me...
> 
> Best regards,
> Martin
> 
> 
> 
> Am 15. Mai 2016 11:39:30 MESZ, schrieb Korbinian Bachl
> :
>>Hello,
>>
>>I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now
>>got a problem I dont know how to solve. A page throws following error:
>>
>>java.text.ParseException: Same attribute found twice: div (line 163,
>>column 52)
>>at
>>org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
>>at
>>org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)
>>
>>
>>so far I would expect this to happen on wrong/ malformed HTML - but my
>>HTML is fine is indeed needed this way!
>>
>>complained HTML:
>>
>>
>>
>>      
>>           content
>>        
>>        
>>        
>>              content
>>        
>>
>>
>>So what is going on here? Why does wicket complain about those poor
>>div's? Is there any way I can disable this check for div's??? For me
>>this behaviour seems as a bug as div following a div is perfectly fine
>>HTML code?
>>
>>Best,
>>
>>Korbinian
>>
>>-
>>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>For additional commands, e-mail: users-h...@wicket.apache.org
> 
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: wicket 6.x / java.text.ParseException on multiple div's

[Per Newgro]

Did you try to remove the questionable markup to see what is happening?

Am 15.05.2016 um 11:39 schrieb Korbinian Bachl:

Hello,

I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now got a 
problem I dont know how to solve. A page throws following error:

java.text.ParseException: Same attribute found twice: div (line 163, column 52)
at 
org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
 at 
org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)


so far I would expect this to happen on wrong/ malformed HTML - but my HTML is 
fine is indeed needed this way!

complained HTML:



   
content
 
 
 

   content
 


So what is going on here? Why does wicket complain about those poor div's? Is 
there any way I can disable this check for div's??? For me this behaviour seems 
as a bug as div following a div is perfectly fine HTML code?

Best,

Korbinian

-
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

Re: wicket 6.x / java.text.ParseException on multiple div's

[Martin Spielmann]

Hello Korbinian,

the error message tells you about a duplicated attribute. Please check if there 
is a tag looking like this in your code:





E.g. smth like this:

Happened some times to me...

Best regards,
Martin



Am 15. Mai 2016 11:39:30 MESZ, schrieb Korbinian Bachl 
:
>Hello,
>
>I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now
>got a problem I dont know how to solve. A page throws following error:
>
>java.text.ParseException: Same attribute found twice: div (line 163,
>column 52)
>at
>org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
>at
>org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)
>
>
>so far I would expect this to happen on wrong/ malformed HTML - but my
>HTML is fine is indeed needed this way!
>
>complained HTML:
>
>
>
>      
>           content
>               
>        
>        
>              content
>        
>
>
>So what is going on here? Why does wicket complain about those poor
>div's? Is there any way I can disable this check for div's??? For me
>this behaviour seems as a bug as div following a div is perfectly fine
>HTML code?
>
>Best,
>
>Korbinian
>
>-
>To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>For additional commands, e-mail: users-h...@wicket.apache.org

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

wicket 6.x / java.text.ParseException on multiple div's

[Korbinian Bachl]

Hello,

I'm still on migrating a big wicket 1.4 app to wicket 6.23, and I now got a 
problem I dont know how to solve. A page throws following error:

java.text.ParseException: Same attribute found twice: div (line 163, column 52)
at 
org.apache.wicket.markup.parser.XmlPullParser.parseTagText(XmlPullParser.java:698)
at 
org.apache.wicket.markup.parser.XmlPullParser.next(XmlPullParser.java:311)


so far I would expect this to happen on wrong/ malformed HTML - but my HTML is 
fine is indeed needed this way!

complained HTML:



      
           content
               
        
        
              content
        


So what is going on here? Why does wicket complain about those poor div's? Is 
there any way I can disable this check for div's??? For me this behaviour seems 
as a bug as div following a div is perfectly fine HTML code?

Best,

Korbinian

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

Re: Generating table header ids for multiple tables pe rpage

[Thorsten Schöning]

Guten Tag Thorsten Schöning,
am Samstag, 14. Mai 2016 um 19:26 schrieben Sie:

> [...]instead I would like to have one
> place, e.g. "resultsContainer" itself, to process the markup in such a
> way that this parent container of all markup generates unique ids,
> changes the "headers" references to those ids and afterwards Wicket
> proceeds with markup processing fully transparent.

Hi,

I seem to have a working PoC overriding Component.getMarkup, by
converting the given markup of the super class to a string, replacing
some parts of it and creating a new IMarkupFragment instance. The most
tricky part of this is that one really needs to create a
MarkupFragment instance, not Markup, even though both implement the
same interface:

> Markup  newMarkup   = Markup.of(stringifiedNew);
> IMarkupFragment retVal  = new MarkupFragment(newMarkup, 0);

While this seems to work, it's not as elegant as I hoped because one
needs to override getMarkup. So next I will have a look at extending
AbstractTransformerBehavior with its "tranform" method. It reads as
well like what I would like to have, only after all processing by
Wicket has happends. Shouldn't make any difference for me, though.

https://ci.apache.org/projects/wicket/apidocs/7.x/org/apache/wicket/markup/transformer/AbstractTransformerBehavior.html#transform(org.apache.wicket.Component,%20java.lang.CharSequence)

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

WG: best way to set up tests with WicketTester Spring and Hibernate

[hansheinrichbraun]

solved with normal spring measures as well as with Mockito it was only the 
problem to find the right description


Von meinem Samsung Galaxy Smartphone gesendet.
 Ursprüngliche Nachricht Von: hansheinrichbraun 
 Datum: 13.05.16  14:07  (GMT+01:00) An: 
users@wicket.apache.org Betreff: best way to set up tests with WicketTester 
Spring and Hibernate 
i try to build my tests for my wicket applications with wicket 6.19.0 spring 
3.2.2.RELEASE and hibernate 4.1.8.Final
the tests run fine only when OpenSessionInViewFilter is used I get the Error 
could not initialize proxy - no sessionwhat is the best way to deal with 
problem.
I read a remark only to do the tests with Mockito


Von meinem Samsung Galaxy Smartphone gesendet.