Re: New sit for user guide examples.

[Štefan Šimík]

Thank you, looks really great.
I would also vote to display related source code for best experience.

On Sun, Apr 3, 2016 at 3:00 PM, Andrea Del Bene 
wrote:

> Hi,
>
> I've finally found the time to work on a site with live examples from the
> user guide. You can see the result here :
> http://examples-wickettutorial.rhcloud.com/
> It's an early version so any feedback is welcome!
>
> Have fun.
>
> Andrea.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: New documentation on Wicket internals

[Štefan Šimík]

Thankx, very useful,
I like these clear explanations about wicket internals. It is not always
easy to understand them from code.

On Fri, Mar 25, 2016 at 6:05 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Thanks!
>
> On Fri, Mar 25, 2016 at 4:34 PM, andrea del bene 
> wrote:
>
> > Hi,
> >
> > I've added a couple of notes to the userguide about markup parsing and
> > autocomponents:
> >
> >
> >
> https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents
> >
> > Have fun!
> >
> > Andrea.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: WicketStuff status and future; awesome-wicket project

[Štefan Šimík]

I find the list excellent. I had no idea, about so many useful things out
there!
Thank you for your effort!

It definitely goes to one of primary wicket related links ;)

On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный  wrote:

> Guys,
>
> Please help me understand what's status of wicketstuff project and
> what's a roadmap for the future?
>
> I'm asking, because from community stand point I don't see so much pros.
>
> Pros:
>
> 1) It's easy to have all wicket related projects in place and observe at
> once.
>
> But this pros can be easily done by creating a library of links to all
> wicket related project. What else do you have in mind?
>
> List of cons is longer:
>
> 1) It's hard to manage issues baceuse there are multiple projects and
> multiple authors.
> 2) It's expected that versions of wicketstuff projects are in sync
> with wicket version. But in reality, as I can see, significant part of
> projects update just pom.xml to a newer version. So: it brings
> redundant versions for those projects
> 3) Hard to search. Yes - google can find everything, but on github
> it's much more reasonable to have separate repository per project.
> 4) When project jumps to wicketstuff: all dependencies should be
> updated. And sometimes it's not easy: for example if you include
> ProjectA which includes ProjectB and projectB jump to wicketstuff.
> 5) And finally: most of projects are already outdated and not
> supported by authors
>
> For my own purposes I started to collect wicket related projects here:
> https://github.com/PhantomYdn/awesome-wicket
> Collection of links might be move beneficial for the community rather
> that moving everything under single project (WicketStuff), I think.
>
> Thanks,
>
> Ilya
>
> -
> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Input Stream DownloadLink

[Štefan Šimík]

Hi Martin,
I found it very useful and really appreciate you contribution.
I think it is definitely worth of effort, if something very similar does
not already exist in wicket distribution.
In that case, it would be great source of inspiration for new pull-request
into wicket.

Simple, short and clean description. I like that :)
Good work Martin

On Wed, Jan 6, 2016 at 12:16 AM, Martin Spielmann <
martin.spielm...@pingunaut.com> wrote:

> Hello all,
>
> I just published a small version of a download link which enables you to
> serve
> any data coming from an InputStream for download.
>
> https://github.com/pingunaut/wicket-stream-download-example
>
> I used that one in multiple projects now, so I thought it could be
> interesting
> for other people too.
> Just wanted to hear, if there any need for this one out there before
> spending
> more effort for docs and error handling.
>
> Happy new year!
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: contributing to wicketstuff-core, how to format file in IntelliJ IDEA?

[Štefan Šimík]

I am not sure, if I answer your question, but here is what came to my mind:

Shortcut for formatting code:
*Ctrl + Alt + L*

Formatting settings:
*Settings / Code Style / Java*

*More info:*
https://www.jetbrains.com/idea/help/reformatting-source-code.html

On Tue, Dec 29, 2015 at 12:34 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Hi,
>
> I want to add some features to wicket-select2 and I was wondering how to
> auto-format files in IntelliJ IDEA? I see there are some eclipse setting...
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: Properties file for *.jar full of custom validators

[Štefan Šimík]

Thank you Tobias - you spotted the right problem and it works now.

Problem was, really default behavior in copying resources by maven.
After fixing that, everything works now as expected.

Thank you guys - Martin, Tobias for your precious time and help!


To help others with same problem:
There is one cause why my validation messages did not work: *.properties
files were missing in final *.jar artifact
And there are 2 possible solutions how to fix that:

   1. Put *.utf8.properties file for wicket into
   src/main/resources/yourpackage/YourValidator.utf8.properties
   2. or put the same properties file directly near your validator *.java
   file, but then you need to instruct Maven to copy these resources into
   final artifact, because by default it skips them.
   - Put the XML below into your pom.xml.






src/main/resources
false


src/main/java
false

**


**/*.java








src/test/resources
false


src/test/java
false

**


**/*.java






On Mon, Dec 28, 2015 at 5:40 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

> Hi,
>
> did you put the properties in src/main/java or src/main/resources?
>
> You have to but it into resources if no additional maven settings are
> applied.
>
> So create a package with the same name in resources and name the
> properties file the same as the class
>
> src/main/java/my/package/MyValidator.java
> src/main/resources/my/package/MyValidator.properties
>
> kind regards
>
> Tobias
>
> > Am 27.12.2015 um 21:24 schrieb Štefan Šimík <stefan.si...@gmail.com>:
> >
> > Thank you for tip Martin ...
> > I tried both YourValidator.properties or YourValidator.utf8.propertiesit
> > right now, but the feedback message was empty string ("") in both cases.
> >
> > I found one working solution:
> > Call setMessage(...) on validator, which provides validation message, if
> no
> > key is found in properties files.
> >
> > But solution with using standard *.properties file would be still nicer
> for
> > me, if possible.
> >
> > On Sun, Dec 27, 2015 at 8:25 PM, Martin Grigorov <
> martin.grigo...@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I don't have my IDE with me now, so I can't verify but
> >> YourValidator.properties staying next to YourValidator.class should
> work.
> >>> On Dec 27, 2015 8:28 PM, "Štefan Šimík" <stefan.si...@gmail.com>
> wrote:
> >>>
> >>> I have separate *.jar containing custom form-component validators.
> >>> (in the *.jar file, there are only validators - no other Components, no
> >>> WebPage(s),
> >>> no WebApplication)
> >>>
> >>> MY QUESTION:
> >>> Which *.properties file should I create for these validators, so the
> >>> validator classes
> >>> and their default messages can be contained together in one *.jar?
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Properties file for *.jar full of custom validators

[Štefan Šimík]

Thank you for tip Martin ...
I tried both YourValidator.properties or YourValidator.utf8.propertiesit
right now, but the feedback message was empty string ("") in both cases.

I found one working solution:
Call setMessage(...) on validator, which provides validation message, if no
key is found in properties files.

But solution with using standard *.properties file would be still nicer for
me, if possible.

On Sun, Dec 27, 2015 at 8:25 PM, Martin Grigorov <martin.grigo...@gmail.com>
wrote:

> Hi,
>
> I don't have my IDE with me now, so I can't verify but
> YourValidator.properties staying next to YourValidator.class should work.
> On Dec 27, 2015 8:28 PM, "Štefan Šimík" <stefan.si...@gmail.com> wrote:
>
> > I have separate *.jar containing custom form-component validators.
> > (in the *.jar file, there are only validators - no other Components, no
> > WebPage(s),
> > no WebApplication)
> >
> > MY QUESTION:
> > Which *.properties file should I create for these validators, so the
> > validator classes
> > and their default messages can be contained together in one *.jar?
> >
>

Properties file for *.jar full of custom validators

[Štefan Šimík]

I have separate *.jar containing custom form-component validators.
(in the *.jar file, there are only validators - no other Components, no
WebPage(s),
no WebApplication)

MY QUESTION:
Which *.properties file should I create for these validators, so the
validator classes
and their default messages can be contained together in one *.jar?

Re: WicketFilter without web.xml

[Štefan Šimík]

I can send you my configuration, that works in my project with Wicket 7.1

It really is empty - because all configuration information is contained in
annotations above.


import org.apache.wicket.protocol.http.WicketFilter;

import javax.servlet.annotation.WebFilter;
import javax.servlet.annotation.WebInitParam;

@WebFilter(
filterName = "AppWicketFilter",
urlPatterns = {"/*"},
initParams = {
@WebInitParam(name = "applicationClassName", value =
"algoritmix.website.client.application.WicketApplication"),
@WebInitParam(name="configuration", value="development"),
@WebInitParam(name="filterMappingUrlPattern", value="/*"),
}
)
public class AppWicketFilter extends WicketFilter {
}

On Tue, Dec 8, 2015 at 8:07 PM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

> Hi guys,
>
> I just wanted to ask if this approach is the one to go with if I don't use
> the web.xml (false):
>
> @WebFilter(displayName = "App", filterName = "app", urlPatterns = "/*",
> initParams = {
>
> @WebInitParam(name = "applicationClassName", value =
> "com.app.web.WebApplication") })
>
> public class WicketInitFilter extends WicketFilter
>
> {
>
> }
>
>
> looks a bit empty. :-)
>
> kind regards
>
> Tobias
>

Passing ListItemModel to another model

[Štefan Šimík]

PROBLEM:
When ListItemModel is wrapped into CompoundPropertyModel (that is used as
default model of Form),
then Form model-object is never updated -> so old data are saved, without
any changes.


EXAMPLE OF PROBLEM:
Example of problem: (data in form object are NOT updated after from
submission)

ListItemModel listItemModel = ...coming from ListView
CompoundPropertyModel compoundModel = new
CompoundPropertyModel(listItemModel);


HOW PROBLEM WAS FIXED:
Fix was to extract model-object from ListItemModel and rewrap it into
CompoundPropertyModel.

ListItemModel listItemModel = ...coming from ListView
CompoundPropertyModel compoundModel = new
CompoundPropertyModel(listItemModel.getObject());


QUESTION
I suppose, that core of the problem is, that ListItemModel does not
implement IChainingModel, so it cannot be passed to another model... but I
am not sure, if I understand that correctly and identified the real core
problem.

Could you please confirm this, or provide some alternative explanation, why
I cannot ListItemModel to the CompoundPropertyModel (into its constructor) ?


Thank you for your help and explanation.

Re: Passing ListItemModel to another model

[Štefan Šimík]

Thank you Sven for help.

I created quickstart and found out a problem.
What you said is true - the problem is really not in CompoundPropertyModel
or in nesting of ListItemModel.

REAL PROBLEM WAS:
I was mistakenly passing Hibernate entities directly between pages -
without proper encapsulating them into LoadableDetachableModel.

As I was using hibernate merge() function to both save/update server data
-> that caused, that old data was merged and my form magically worked.
when de/serialized hibernate-entities already had assigned database ID.
That completely distracted me from looking for problem on server-side
and I mistakenly looked it on client side instead.

Doing isolated quickstart for myself will be the 1st thing I try next time
;)
Anyway, thank you, for pointing me to the right direction!

On Sat, Nov 28, 2015 at 9:47 PM, Sven Meier <s...@meiers.net> wrote:

> Hi,
>
> > I suppose, that core of the problem is, that ListItemModel does not
> > implement IChainingModel, so it cannot be passed to another model...
>
> CompoundPropertyModel does not care of the actual model implementation, it
> should work fine with any target model.
>
> Actually Wicket provides PropertyListView, which exactly wraps a
> ListItemModel in a CompoundPropertyModel.
>
> Please create a quickstart so we can see the cause of your problem.
>
> Have fun
> Sven
>
>
>
>
> On 28.11.2015 21:10, Štefan Šimík wrote:
>
>> PROBLEM:
>> When ListItemModel is wrapped into CompoundPropertyModel (that is used as
>> default model of Form),
>> then Form model-object is never updated -> so old data are saved, without
>> any changes.
>>
>>
>> EXAMPLE OF PROBLEM:
>> Example of problem: (data in form object are NOT updated after from
>> submission)
>>
>>  ListItemModel listItemModel = ...coming from ListView
>>  CompoundPropertyModel compoundModel = new
>> CompoundPropertyModel(listItemModel);
>>
>>
>> HOW PROBLEM WAS FIXED:
>> Fix was to extract model-object from ListItemModel and rewrap it into
>> CompoundPropertyModel.
>>
>>  ListItemModel listItemModel = ...coming from ListView
>>  CompoundPropertyModel compoundModel = new
>> CompoundPropertyModel(listItemModel.getObject());
>>
>>
>> QUESTION
>> I suppose, that core of the problem is, that ListItemModel does not
>> implement IChainingModel, so it cannot be passed to another model... but I
>> am not sure, if I understand that correctly and identified the real core
>> problem.
>>
>> Could you please confirm this, or provide some alternative explanation,
>> why
>> I cannot ListItemModel to the CompoundPropertyModel (into its
>> constructor) ?
>>
>>
>> Thank you for your help and explanation.
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Contribution to Wicket WIKI

[Štefan Šimík]

I would like to ask, how is possible to update WIKI.

I found som info at:
https://cwiki.apache.org/confluence/display/WICKET/How+to+contribute+documentation+to+the+Wiki

but I cannot find any link for editing of the page (I am logged in, as
common user).

Stefan