Re: [ANNOUNCE] WicketStuff 7.3.0 Released

[Martin Grigorov]

On Tue, May 10, 2016 at 9:27 PM, Gabriel Landon  wrote:

> A big thank you to kkaravitis for his work on the portlet bridge.
>

Yes!
Thank you, Kostas!


> I will definitely use it within the year to upgrade to wicket 7 and liferay
> 6.2.
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/ANNOUNCE-WicketStuff-7-3-0-Released-tp4674633p4674636.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: [ANNOUNCE] WicketStuff 7.3.0 Released

[Gabriel Landon]

A big thank you to kkaravitis for his work on the portlet bridge.
I will definitely use it within the year to upgrade to wicket 7 and liferay
6.2.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/ANNOUNCE-WicketStuff-7-3-0-Released-tp4674633p4674636.html
Sent from the Users forum mailing list archive at Nabble.com.

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

Re: [ANNOUNCE] WicketStuff 7.3.0 Released

[Ernesto Reinaldo Barreiro]

Thanks!

On Tue, May 10, 2016 at 9:26 PM, Martin Grigorov 
wrote:

> WicketStuff core 7.3.0 based on Apache Wicket 7.3.0 is released and
> available
> at Maven Central.
>
> The changelog since 7.2.0 is:
>
> kkaravitis (33):
>   Override the System Mapper functionality for portlet specific
> purposes
>   added support for wicket ajax requets. The
> BookmarkableListenerInterfaceRequestHandler is associated with wicket
> ajax requests.
>   Every wicket portlet should render page and write response if the
> current portlet request is a render request.
>   Added the following functionality
>   PortletSystemMapper refactoring after
> https://issues.apache.org/jira/browse/WICKET-6130 fix
>   - Added the pageClass in page expiration exception message - the
> value of Application.get() is cached into a local variable to avoid
> making two ThreadLocal lookups.
>   .
>   added comments
>   Merge branch 'master' of https://github.com/wicketstuff/core
>   added comments, removed unnecessary imports and code formatted
> according to wicket code template
>   fix for https://github.com/wicketstuff/core/issues/478 issue
>   fix for https://github.com/wicketstuff/core/issues/478 issue
>   create wicket-portlet-examples module
>   .
>   liferay 6.2 wicket portlet examples
>   Merge branch 'master' of https://github.com/wicketstuff/core
>   liferay 6.2 wicket portlet examples
>   correct illegal request uris
>   fix for #482 issue: WicketPortlet does not portletify the redirect
> url correctly
>   remove temporarily the wicket portlet examples
>   liferay 6.2 wicket portlet examples
>   liferay 6.2 wicket portlet examples
>   added role mappers
>   liferay deployment fixes
>   liferay deployment
>   liferay deployment
>   liferay deployment
>   change plugin version to 7.3.0
>   wiki images
>   plugin version is 7.3.0
>   remove unused imports
>   fix for #487 issue
>   fix for #487, #488 issues
>
> Andrea Del Bene (21):
>   Update README.md
>   Update README.md
>   Merge pull request #461 from diegofalcinelli/patch-1
>   Fix for #462
>   Attempt to solve compiling problem with nashorn module
>   Upgrade jdk to > 1.8.40
>   Added missing bumped pom
>   Added further missing bumped poms
>   Trying increasing the delay for Nashorn unit test
>   Merge pull request #455 from samogot/master
>   Attempt to solve problems with Maven options see
> http://stackoverflow.com/questions/29201549/travis-ci-ignoring-maven-opts
>   Attempt to solve problems with Maven options take 2
>  Attempt to solve problems with Maven options take 3
>   Introduced a countdown latch to avoid concurrent failure in
> ProgressButtonTest
>   Removed typo
>   Fixed  #475
>   Issue #477
>   Merge pull request #480 from mitring/master
>   Issue #490
>   re-trigger CI
>   removed unused variable.
>
> Konstantinos Karavitis (12):
>   Merge pull request #479 from kkaravitis/master
>   Update liferay-plugin-package.xml
>   Update portlet.xml
>   Create readme.md
>   Update readme.md
>   Update readme.md
>   Update readme.md
>   Create readme.md
>   Update readme.md
>   Update readme.md
>   Delete 5.png
>   Merge pull request #489 from kkaravitis/master
>
> Martin Tzvetanov Grigorov (10):
>   Bump version to 7.3.0-SNAPSHOT
>   Fixes #450 - Remove dependencies to Log4j
>   WicketWICKET-6105 Decommission wicket-datetime
>   [datetime-yui] Move the examples page from wicket-examples to
> wicketstuff-datetime-yui-examples
>   [datetime-yui] The examples run fine
>   [datetime] Remove obsolete Maven Site artefacts
>   Update Scala to 2.11.8
>   [portlets] Improve pom.xml to inherit the version of Wicket from the
> parent pom and to use ${project.version} instead of ${wicket.version}
>   [offline-mode] Minor improvements
>   Release 7.3.0
>
> Maxim Solodovnik (5):
>   whitespace fix
>   Merge pull request #460 from reiern70/master
>   Merge pull request #468 from simokivimaki/master
>   Whitespaces are fixed
>   Whitespaces are fixed
>
> Simo Kivimäki (4):
>   Using 7.3.0-SNAPSHOT parent.
>   Updated TinyMCE to version 4.3.4. Issue #465. - TinyMCE
> development package excluding: classes, jquery things, compat3x plugin,
> *dev.js. - All languages except ru@petr1708 which failed to download.
>   A fix for: Updated TinyMCE to version 4.3.4. Issue #465. -
> Restored imageupload plugin - Added compat3x plugin
>   Select2 Settings add 'createTag' setting #463
>
> Tobias Soloschenko (4):
>   Added wicketstuff-nashorn-parent as submodule
>   Fixed wicketstuff-nashorn-parent as submodule (folder)
>   Wicket Offline Mode
>   Fix TLD validation issue
>
> Alexey Prudnikov (2):
>   

[ANNOUNCE] WicketStuff 7.3.0 Released

[Martin Grigorov]

WicketStuff core 7.3.0 based on Apache Wicket 7.3.0 is released and available
at Maven Central.

The changelog since 7.2.0 is:

kkaravitis (33):
  Override the System Mapper functionality for portlet specific purposes
  added support for wicket ajax requets. The
BookmarkableListenerInterfaceRequestHandler is associated with wicket
ajax requests.
  Every wicket portlet should render page and write response if the
current portlet request is a render request.
  Added the following functionality
  PortletSystemMapper refactoring after
https://issues.apache.org/jira/browse/WICKET-6130 fix
  - Added the pageClass in page expiration exception message - the
value of Application.get() is cached into a local variable to avoid
making two ThreadLocal lookups.
  .
  added comments
  Merge branch 'master' of https://github.com/wicketstuff/core
  added comments, removed unnecessary imports and code formatted
according to wicket code template
  fix for https://github.com/wicketstuff/core/issues/478 issue
  fix for https://github.com/wicketstuff/core/issues/478 issue
  create wicket-portlet-examples module
  .
  liferay 6.2 wicket portlet examples
  Merge branch 'master' of https://github.com/wicketstuff/core
  liferay 6.2 wicket portlet examples
  correct illegal request uris
  fix for #482 issue: WicketPortlet does not portletify the redirect
url correctly
  remove temporarily the wicket portlet examples
  liferay 6.2 wicket portlet examples
  liferay 6.2 wicket portlet examples
  added role mappers
  liferay deployment fixes
  liferay deployment
  liferay deployment
  liferay deployment
  change plugin version to 7.3.0
  wiki images
  plugin version is 7.3.0
  remove unused imports
  fix for #487 issue
  fix for #487, #488 issues

Andrea Del Bene (21):
  Update README.md
  Update README.md
  Merge pull request #461 from diegofalcinelli/patch-1
  Fix for #462
  Attempt to solve compiling problem with nashorn module
  Upgrade jdk to > 1.8.40
  Added missing bumped pom
  Added further missing bumped poms
  Trying increasing the delay for Nashorn unit test
  Merge pull request #455 from samogot/master
  Attempt to solve problems with Maven options see
http://stackoverflow.com/questions/29201549/travis-ci-ignoring-maven-opts
  Attempt to solve problems with Maven options take 2
 Attempt to solve problems with Maven options take 3
  Introduced a countdown latch to avoid concurrent failure in
ProgressButtonTest
  Removed typo
  Fixed  #475
  Issue #477
  Merge pull request #480 from mitring/master
  Issue #490
  re-trigger CI
  removed unused variable.

Konstantinos Karavitis (12):
  Merge pull request #479 from kkaravitis/master
  Update liferay-plugin-package.xml
  Update portlet.xml
  Create readme.md
  Update readme.md
  Update readme.md
  Update readme.md
  Create readme.md
  Update readme.md
  Update readme.md
  Delete 5.png
  Merge pull request #489 from kkaravitis/master

Martin Tzvetanov Grigorov (10):
  Bump version to 7.3.0-SNAPSHOT
  Fixes #450 - Remove dependencies to Log4j
  WicketWICKET-6105 Decommission wicket-datetime
  [datetime-yui] Move the examples page from wicket-examples to
wicketstuff-datetime-yui-examples
  [datetime-yui] The examples run fine
  [datetime] Remove obsolete Maven Site artefacts
  Update Scala to 2.11.8
  [portlets] Improve pom.xml to inherit the version of Wicket from the
parent pom and to use ${project.version} instead of ${wicket.version}
  [offline-mode] Minor improvements
  Release 7.3.0

Maxim Solodovnik (5):
  whitespace fix
  Merge pull request #460 from reiern70/master
  Merge pull request #468 from simokivimaki/master
  Whitespaces are fixed
  Whitespaces are fixed

Simo Kivimäki (4):
  Using 7.3.0-SNAPSHOT parent.
  Updated TinyMCE to version 4.3.4. Issue #465. - TinyMCE
development package excluding: classes, jquery things, compat3x plugin,
*dev.js. - All languages except ru@petr1708 which failed to download.
  A fix for: Updated TinyMCE to version 4.3.4. Issue #465. -
Restored imageupload plugin - Added compat3x plugin
  Select2 Settings add 'createTag' setting #463

Tobias Soloschenko (4):
  Added wicketstuff-nashorn-parent as submodule
  Fixed wicketstuff-nashorn-parent as submodule (folder)
  Wicket Offline Mode
  Fix TLD validation issue

Alexey Prudnikov (2):
  [datastores] Add IDataStore implementation that saves serialized
pages in Apache Ignite
  [datastores] Fix comments and code style

Hendy Irawan (1):
  since we use SLF4J, replace commons-logging and log4j are only used
for test

diegofalcinelli (1):
  Update README.md

reiern70 (1):
  [select2] make theme 

[ANNOUNCE] WicketStuff 6.23.0 is released

[Martin Grigorov]

Hi,

WicketStuff core 6.23.0 based on Apache Wicket 6.23.0 is released and
available at Maven Central.

The changelog since 6.22.0 is:

Andrea Del Bene (2):
  [restannotations] Issue #477
  [restannotations] Issue #490

Martin Tzvetanov Grigorov (2):
  [native-web-socket-javax] WICKET-6103 Synchronization on JSR 356
connection
  Release 6.23.0

kkaravitis (2):
  [portlet] wicketstuff portlet fixies
  [portlet] added wicket 6 portlet examples for liferay 6.2

Konstantinos Karavitis (1):
  [portlet] Merge pull request #484 from kkaravitis/wicket-6.x

Tobias Soloschenko (1):
  [javaee] Readded tag descriptors



The WicketStuff team!

Re: Which model to use for forwarding form processing results?

[Bas Gooren]

Thorsten,

Yes, that is normal behavior I think - for invisible components we either wrap 
it in a container which receives the event, or let the page be the coordinator.

Invisible components also don’t receive clicks on links etc, so I think this 
was done to be consistent.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 10 mei 2016 bij 19:48:48, Thorsten Schöning (tschoen...@am-soft.de) schreef:

Guten Tag Bas Gooren,  
am Dienstag, 10. Mai 2016 um 13:43 schrieben Sie:  

> This sounds like a good use-case for an event.  

Thanks for this hint, I totally forgot about it and decided to give it  
a try. There was a pitfall in my case, though: 
Component.canCallListenerInterface  
is asked before an event is dispatched and I'm starting with an  
invisible panel, so the method returns false, waiting for data to  
become visible, which is never dispatched... Doesn't seem to be  
mentioned in the docs or I must have missed it.  

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: Which model to use for forwarding form processing results?

[Thorsten Schöning]

Guten Tag Bas Gooren,
am Dienstag, 10. Mai 2016 um 13:43 schrieben Sie:

> This sounds like a good use-case for an event.

Thanks for this hint, I totally forgot about it and decided to give it
a try. There was a pitfall in my case, though: 
Component.canCallListenerInterface
is asked before an event is dispatched and I'm starting with an
invisible panel, so the method returns false, waiting for data to
become visible, which is never dispatched... Doesn't seem to be
mentioned in the docs or I must have missed it.

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: [wicketstuff-restannotations] AbstractRestResource.toObject makes it impossible for mapped methods to know a parameter conversion went wrong.

[Fabio Fioretti]

I confirm version 6.23.0 fixed the problem.

Thank you for the great support!

Kind regards,
Fabio

On Thu, Apr 28, 2016 at 12:02 PM, Fabio Fioretti <
windom.macroso...@gmail.com> wrote:

> Thanks Andrea, that would be excellent!
>
> Keep up the great work,
> Fabio
>
> On Thu, Apr 28, 2016 at 11:52 AM, Andrea Del Bene 
> wrote:
>
>> Thank you for the issue! I think we can make it for next release 6.23.0
>> which should come quite soon (at the moment we are voting to release Wicket
>> 6.23.0).
>>
>> Andrea.
>>
>>
>> On 28/04/2016 11:34, Fabio Fioretti wrote:
>>
>>> Done: https://github.com/wicketstuff/core/issues/490
>>>
>>> Many thanks,
>>> Fabio
>>>
>>> On Thu, Apr 28, 2016 at 11:03 AM, Martin Grigorov <
>>> martin.grigo...@gmail.com
>>>
 wrote:
 Please file an issue at Wicketstuff GibHub.
 On Apr 28, 2016 10:31 AM, "Fabio Fioretti" 
 wrote:

 Hi Martin,
>
> Thanks, I agree - findOffices() shouldn't be executed at all. In fact,
> handleMethodExecution() returns before invoking application code in all
> other cases (step 1 for unauthorized access, step 3 for validation
>
 errors).

> Any chance to have it fixed relatively soon? (maybe Andrea can answer
>
 this)

> Kind regards,
> Fabio
>
> On Thu, Apr 28, 2016 at 6:44 AM, Martin Grigorov  >
> wrote:
>
> Hi,
>>
>>
>> On Wed, Apr 27, 2016 at 12:07 PM, Fabio Fioretti <
>> windom.macroso...@gmail.com> wrote:
>>
>> Hi all,
>>>
>>> Please consider the following simple implementation of
>>>
>> AbstractRestResource
>>
>>> (6.22.0):
>>>
>>> @ResourcePath("/rest/api")
>>> public class MyRestResource extends
>>> AbstractRestResource
>>> {
>>>
>>>   public MyRestResource ()
>>>   {
>>>super(new JsonWebSerialDeserial(new GsonObjectSerialDeserial()));
>>>   }
>>>
>>>   @MethodMapping(value = "/offices")
>>>   public List findOffices(
>>> @RequestParam(value = "region", required = false) Integer
>>>
>> regionId)

>   {
>>>return findOfficesByRegion(regionId);
>>>   }
>>> }
>>>
>>> My question relates to the findOffices method and its filtering
>>>
>> regionId
>
>> parameter when the value is not a valid integer. For example,
>>>
>> consider

> the
>>
>>> request 'GET /rest/api/offices?region=AA'.
>>>
>>> At the second step of AbstractRestResource.handleMethodExecution,
>>> extractMethodParameters is invoked, which in turn triggers the
>>>
>> conversion
>
>> of all parameters through the static method toObject.
>>>
>>> When the conversion goes wrong and ConversionException is thrown,
>>>
>> toObject
>>
>>> catches it, sets the response status to 400 and returns null!
>>>
>>> Now, when my findOffices is finally executed, I get a null regionId
>>>
>> but I
>
>> don't know whether it was not valid or the parameter was not present
>>>
>> at

> all. Checking the response status downstream is also particularly
>>>
>> hard

> because I have no getStatus (Tomcat 6 here, ouch!).
>>>
>>> To my mind, findOffices should return null instead of the unfiltered
>>>
>> list
>
>> of offices if the conversion went wrong, even because the response
>>> status is 400 (as set by toObject). However, how can I know it?
>>>
>>> Any suggestions?
>>>
>>> IMO this is a bug in the library.
>> #findOffices() should not be executed at all.
>> A response with status code 400 should be returned immediately after
>>
> the

> unsuccessful convention without giving a chance to the application code
>>
> to
>
>> be executed.
>>
>> Many thanks,
>>> Fabio
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>

Re: Which model to use for forwarding form processing results?

[Bas Gooren]

Hi Thorsten,

This sounds like a good use-case for an event.

You can have the form broadcast an event to the page, and let any component 
that needs to redraw based on the data handle that event. This provides a nice 
decoupling between the form result and 0…n other components in your page that 
need the data.

The components handling the event then also don’t need to know where the event 
originated.

For more info, see the wicket guide; the info is under chapter 17.2, scroll 
down to “Wicket events infrastructure”.
https://ci.apache.org/projects/wicket/guide/6.x/guide/advanced.html#advanced_2

And a bonus tip: you can use the wicketstuff-annotationeventdispatcher jar to 
make your life even easier. Just include it in your project (it will 
automatically register itself in wicket), and then you can annotate any public 
component method in your page with @OnEvent, for example:

@OnEvent
public void onFormDataSubmittedEvent(FormDateSubmittedEvent event) {
… impl
}

It’s actually a great way to handle data-passing in pages.

Met vriendelijke groet,
Kind regards,

Bas Gooren

Op 10 mei 2016 bij 08:54:14, Thorsten Schöning (tschoen...@am-soft.de) schreef:

Hi all,  

I have one and the same form on different pages used to provide some  
input data which is afterwards used by the form's onSubmit handler to  
request some complex data structure from a 3rd party service. This  
result needs to be forwarded to the caller/owner of the form, mainly  
pages, so those can provide the data to different views focussing on  
different aspects of the data. Most of those views are panels using  
different DataViews to provide data in HTML tables in the end.  

The important thing is that the form shouldn't render the results  
itself, only return some raw data structure, and the panels shouldn't  
need to know about the form as well.  

What is the best way to send those resulting data around?  

From my understanding it's not the default model of the form with all  
the convert input stuff, those input comes from the user, but it may  
be that of the page containing form and panels, so both could access  
the page and its default model. Else I could simply create a model  
instance and forward it using the CTORs of the form and panels,  
without (misusing?) the page's default model.  

Does it even matter at all?  

Thanks!  

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: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

[Martin Grigorov]

Hi Ernesto,

We are fully aware of this!
That's why the migration guide is split into "API breaks" and "Behavior
changes".
API breaks usually are easy to fix because the compiler complains about
them.
Behavior changes are not problem for Semantic Versioning but we postpone
them to major versions because of what you have said below - they are
silent and more hard to be debugged.
For all of them there is a respective discussion thread at dev@ - whether,
when and how to do them.
I know that most people are busy with their own business and family (me
included!) and don't have time to participate in discussions,
brainstorming, testing but this process is the best we can do at the
moment.
Any ideas for improving the process are always welcome!

I hope that we will release 8.0.0-M1 soon so more people like you can give
it a try and report issues and ideas for improvements before we freeze the
code for API breaks.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Tue, May 10, 2016 at 9:32 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Tobias,
>
>
> > I think as long as the third party library is not Wicket 7.0 proofed you
> > should use it careful. Because of this the migration guide is very
> useful -
> > each framework should be checked when upgrade a major version.
> >
>
>
> Mind that I'm fully aware of the personal sacrifices some people make to
> deliver new versions and improve the framework. So, what I tell bellow is
> with full respect to that.
>
> I'm NOT really "complaining" let's say I'm just voicing some concerns from
> users. This is the second Wicket application I migrate to Wicket 7.0 in
> last two of months. First application was for a customer and we encountered
> a few little "surprises", e.g.
>
>
> https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.markup.html.panel.FeedbackPanelDonotsetCSSclassontheli
> >spanelementforafeedbackmessageWICKET-4831
>
> IMHO changes like this bring no real value and just make migrations less
> "stable". Not to mention things like this
>
>
> https://ci.apache.org/projects/wicket/guide/7.x/guide/componentQueueing.html
>
>  which might have made framework slower (according to certain post on
> list). I know that without changes there is no evolution. I'm just telling
> that maybe there is a need to make changes more gradually (e.g. deprecate
> things) and try to introduce features (if possible) in a way that they can
> be "switched off".
>
> Even on OS level there is a requirement note and sometimes API changes have
> > impact on applications and their complete compatibility.
> >
>
> IMHO users just expect things to work out of the box. More if they are just
> very satisfied with the version of the product they are using and the only
> reason they are actually migrating is just to not "fall behind". There was
> already something called Wicket 2.0 which was abandoned after a few months
> of development because, if I remember correctly, it broke too much previous
> version code base. As a user I would like not to experience something
> similar anymore.  I haven't tried yet Wicket 8.x but I'm a bit afraid it
> might be a bit disruptive for some users/applications. I will want to try
> it ASAP and give my modest feedback.
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: are there any changes to radioGroup and AjaxFormChoiceComponentUpdatingBehavior on wickte 7?

[Ernesto Reinaldo Barreiro]

Tobias,


> I think as long as the third party library is not Wicket 7.0 proofed you
> should use it careful. Because of this the migration guide is very useful -
> each framework should be checked when upgrade a major version.
>


Mind that I'm fully aware of the personal sacrifices some people make to
deliver new versions and improve the framework. So, what I tell bellow is
with full respect to that.

I'm NOT really "complaining" let's say I'm just voicing some concerns from
users. This is the second Wicket application I migrate to Wicket 7.0 in
last two of months. First application was for a customer and we encountered
a few little "surprises", e.g.

https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+7.0#MigrationtoWicket7.0-org.apache.wicket.markup.html.panel.FeedbackPanelDonotsetCSSclassontheli
>spanelementforafeedbackmessageWICKET-4831

IMHO changes like this bring no real value and just make migrations less
"stable". Not to mention things like this

https://ci.apache.org/projects/wicket/guide/7.x/guide/componentQueueing.html

 which might have made framework slower (according to certain post on
list). I know that without changes there is no evolution. I'm just telling
that maybe there is a need to make changes more gradually (e.g. deprecate
things) and try to introduce features (if possible) in a way that they can
be "switched off".

Even on OS level there is a requirement note and sometimes API changes have
> impact on applications and their complete compatibility.
>

IMHO users just expect things to work out of the box. More if they are just
very satisfied with the version of the product they are using and the only
reason they are actually migrating is just to not "fall behind". There was
already something called Wicket 2.0 which was abandoned after a few months
of development because, if I remember correctly, it broke too much previous
version code base. As a user I would like not to experience something
similar anymore.  I haven't tried yet Wicket 8.x but I'm a bit afraid it
might be a bit disruptive for some users/applications. I will want to try
it ASAP and give my modest feedback.


-- 
Regards - Ernesto Reinaldo Barreiro

Which model to use for forwarding form processing results?

[Thorsten Schöning]

Hi all,

I have one and the same form on different pages used to provide some
input data which is afterwards used by the form's onSubmit handler to
request some complex data structure from a 3rd party service. This
result needs to be forwarded to the caller/owner of the form, mainly
pages, so those can provide the data to different views focussing on
different aspects of the data. Most of those views are panels using
different DataViews to provide data in HTML tables in the end.

The important thing is that the form shouldn't render the results
itself, only return some raw data structure, and the panels shouldn't
need to know about the form as well.

What is the best way to send those resulting data around?

From my understanding it's not the default model of the form with all
the convert input stuff, those input comes from the user, but it may
be that of the page containing form and panels, so both could access
the page and its default model. Else I could simply create a model
instance and forward it using the CTORs of the form and panels,
without (misusing?) the page's default model.

Does it even matter at all?

Thanks!

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