Re: About XML Injection
Yes, super thanks for detailed explanation On Sat, Apr 11, 2020 at 11:19 AM Martin Terra < martin.te...@koodaripalvelut.com> wrote: > la 11. huhtik. 2020 klo 5.58 Shengche Hsiao (shengchehs...@gmail.com) > kirjoitti: > > > Thanks Martin, I might misunderstand the report, and I'll validate the > > submitted values to prevent xml injection. > > > > You're welcome. To clarify: validation can prevent any malicious effects of > injected values, but it cannot prevent the injection itself. Therefore, > validation could cure the issue found in the report. This should > ofcourse be verified by reproducing the issue before fix and confirming > that applying the fix successfully mitigates the issue. > > ** > Martin > > > > On Thu, Apr 9, 2020 at 8:07 PM Martin Grigorov > > wrote: > > > > > I still do not understand what exactly is the issue here. > > > > > > The client/browser submits the values as key/value pairs > > > (application/x-www-form-urlencoded). > > > The server responds with XML that is processed by wicket-ajax.js. > > > How validation of the submit values could help with the XML injection > ?! > > > > > > > > > On Thu, Apr 9, 2020 at 2:52 PM Shengche Hsiao > > > > wrote: > > > > > > > Thank you, I'll do that and see if works > > > > > > > > On Thu, Apr 9, 2020 at 6:35 PM Martin Terra < > > > > martin.te...@koodaripalvelut.com> wrote: > > > > > > > > > Can you solve this by simple validation if submitted values are > > legal? > > > > This > > > > > way it does not matter if client tries to override the submit. > > > > > > > > > > ** > > > > > Martin > > > > > > > > > > to 9. huhtik. 2020 klo 12.22 Shengche Hsiao ( > shengchehs...@gmail.com > > ) > > > > > kirjoitti: > > > > > > > > > > > I got a report , it suggest our web site to deal with xml > injection > > > > > issue. > > > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke another > > > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the > > reporters > > > > > > used Burpsuite > > > > > > to inject xml on xmlpayload, such as inject > > > > > > > > > > > > > > > > > > image.png > > > > > > < > > > > > > > > > > > > > > > > > > > > > https://drive.google.com/file/d/1U9nls1Z7tfs_zqEvbLLYsef89BFMopeY/view?usp=drive_web > > > > > > > > > > > > > > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > > > > > > > image.png > > > > > > < > > > > > > > > > > > > > > > > > > > > > https://drive.google.com/file/d/1RcAegoREfmkdPNm1DCw9ouUyfI20lh7K/view?usp=drive_web > > > > > > > > > > > > > > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check the > > > entire > > > > > > payload or only check there value we need ? > > > > > > > > > > > > On Thu, Apr 9, 2020 at 4:57 PM Martin Grigorov < > > mgrigo...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > > > The images didn't make it to the mailing list. > > > > > > > Please use some online image paste bin. > > > > > > > > > > > > > > On Thu, Apr 9, 2020 at 11:33 AM Shengche Hsiao < > > > > > shengchehs...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > I got a report , it suggest our web site to deal with xml > > > injection > > > > > > > issue. > > > > > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke > > another > > > > > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the > > > > reporters > > > > > > > used > > > > > > > > Burpsuite to inject xml on xmlpayload, such as inject > > > > > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check > > the > > > > > entire > > > > > > > > payload or only check there value we need ? > > > > > > > > > > > > > > > > On Thu, Apr 9, 2020 at 4:11 PM Martin Grigorov < > > > > mgrigo...@apache.org > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > >> On Thu, Apr 9, 2020 at 11:09 AM Shengche Hsiao < > > > > > > shengchehs...@gmail.com > > > > > > > > > > > > > > > >> wrote: > > > > > > > >> > > > > > > > >> > Yes, I need to know overriding which methods > > > > > > > >> > > > > > > > > >> > > > > > > > >> I still do not understand what exactly you need to > accomplish. > > > > > > > >> Please be more specific! > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > > >> > On Thu, Apr 9, 2020 at 16:03 Martin Grigorov < > > > > > mgrigo...@apache.org> > > > > > > > >> wrote: > > > > > > > >> > > > > > > > > >> > > Hi, > > > > > > > >> > > > > > > > > > >> > > On Thu, Apr 9, 2020 at 10:27 AM ShengChe Hsiao < > > > > > > front...@gmail.com> > > > > > > > >> > wrote: > > > > > > > >> > > > > > > > > > >> > > > Dear all > > > > > > > >> > > > > > > > > > > >> > > > I use built-in ajax dropdownchoice component, it's > > default > > > > > > payload > > > > > > > >> is > > > > > > > >> > xml > > > > > > > >> > > >
Re: About XML Injection
la 11. huhtik. 2020 klo 5.58 Shengche Hsiao (shengchehs...@gmail.com) kirjoitti: > Thanks Martin, I might misunderstand the report, and I'll validate the > submitted values to prevent xml injection. > You're welcome. To clarify: validation can prevent any malicious effects of injected values, but it cannot prevent the injection itself. Therefore, validation could cure the issue found in the report. This should ofcourse be verified by reproducing the issue before fix and confirming that applying the fix successfully mitigates the issue. ** Martin > On Thu, Apr 9, 2020 at 8:07 PM Martin Grigorov > wrote: > > > I still do not understand what exactly is the issue here. > > > > The client/browser submits the values as key/value pairs > > (application/x-www-form-urlencoded). > > The server responds with XML that is processed by wicket-ajax.js. > > How validation of the submit values could help with the XML injection ?! > > > > > > On Thu, Apr 9, 2020 at 2:52 PM Shengche Hsiao > > wrote: > > > > > Thank you, I'll do that and see if works > > > > > > On Thu, Apr 9, 2020 at 6:35 PM Martin Terra < > > > martin.te...@koodaripalvelut.com> wrote: > > > > > > > Can you solve this by simple validation if submitted values are > legal? > > > This > > > > way it does not matter if client tries to override the submit. > > > > > > > > ** > > > > Martin > > > > > > > > to 9. huhtik. 2020 klo 12.22 Shengche Hsiao (shengchehs...@gmail.com > ) > > > > kirjoitti: > > > > > > > > > I got a report , it suggest our web site to deal with xml injection > > > > issue. > > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke another > > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the > reporters > > > > > used Burpsuite > > > > > to inject xml on xmlpayload, such as inject > > > > > > > > > > > > > > > image.png > > > > > < > > > > > > > > > > > > > > > https://drive.google.com/file/d/1U9nls1Z7tfs_zqEvbLLYsef89BFMopeY/view?usp=drive_web > > > > > > > > > > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > > > > image.png > > > > > < > > > > > > > > > > > > > > > https://drive.google.com/file/d/1RcAegoREfmkdPNm1DCw9ouUyfI20lh7K/view?usp=drive_web > > > > > > > > > > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check the > > entire > > > > > payload or only check there value we need ? > > > > > > > > > > On Thu, Apr 9, 2020 at 4:57 PM Martin Grigorov < > mgrigo...@apache.org > > > > > > > > wrote: > > > > > > > > > > > The images didn't make it to the mailing list. > > > > > > Please use some online image paste bin. > > > > > > > > > > > > On Thu, Apr 9, 2020 at 11:33 AM Shengche Hsiao < > > > > shengchehs...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > I got a report , it suggest our web site to deal with xml > > injection > > > > > > issue. > > > > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke > another > > > > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the > > > reporters > > > > > > used > > > > > > > Burpsuite to inject xml on xmlpayload, such as inject > > > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check > the > > > > entire > > > > > > > payload or only check there value we need ? > > > > > > > > > > > > > > On Thu, Apr 9, 2020 at 4:11 PM Martin Grigorov < > > > mgrigo...@apache.org > > > > > > > > > > > > wrote: > > > > > > > > > > > > > >> On Thu, Apr 9, 2020 at 11:09 AM Shengche Hsiao < > > > > > shengchehs...@gmail.com > > > > > > > > > > > > > >> wrote: > > > > > > >> > > > > > > >> > Yes, I need to know overriding which methods > > > > > > >> > > > > > > > >> > > > > > > >> I still do not understand what exactly you need to accomplish. > > > > > > >> Please be more specific! > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > > >> > On Thu, Apr 9, 2020 at 16:03 Martin Grigorov < > > > > mgrigo...@apache.org> > > > > > > >> wrote: > > > > > > >> > > > > > > > >> > > Hi, > > > > > > >> > > > > > > > > >> > > On Thu, Apr 9, 2020 at 10:27 AM ShengChe Hsiao < > > > > > front...@gmail.com> > > > > > > >> > wrote: > > > > > > >> > > > > > > > > >> > > > Dear all > > > > > > >> > > > > > > > > > >> > > > I use built-in ajax dropdownchoice component, it's > default > > > > > payload > > > > > > >> is > > > > > > >> > xml > > > > > > >> > > > entity, but if I need to prevent xml injection ,how can > i > > > do? > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > Could you please give some more information what exactly > you > > > > need? > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > --->
Re: About XML Injection
Thanks Martin, I might misunderstand the report, and I'll validate the submitted values to prevent xml injection. On Thu, Apr 9, 2020 at 8:07 PM Martin Grigorov wrote: > I still do not understand what exactly is the issue here. > > The client/browser submits the values as key/value pairs > (application/x-www-form-urlencoded). > The server responds with XML that is processed by wicket-ajax.js. > How validation of the submit values could help with the XML injection ?! > > > On Thu, Apr 9, 2020 at 2:52 PM Shengche Hsiao > wrote: > > > Thank you, I'll do that and see if works > > > > On Thu, Apr 9, 2020 at 6:35 PM Martin Terra < > > martin.te...@koodaripalvelut.com> wrote: > > > > > Can you solve this by simple validation if submitted values are legal? > > This > > > way it does not matter if client tries to override the submit. > > > > > > ** > > > Martin > > > > > > to 9. huhtik. 2020 klo 12.22 Shengche Hsiao (shengchehs...@gmail.com) > > > kirjoitti: > > > > > > > I got a report , it suggest our web site to deal with xml injection > > > issue. > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke another > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the reporters > > > > used Burpsuite > > > > to inject xml on xmlpayload, such as inject > > > > > > > > > > > > image.png > > > > < > > > > > > > > > > https://drive.google.com/file/d/1U9nls1Z7tfs_zqEvbLLYsef89BFMopeY/view?usp=drive_web > > > > > > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > image.png > > > > < > > > > > > > > > > https://drive.google.com/file/d/1RcAegoREfmkdPNm1DCw9ouUyfI20lh7K/view?usp=drive_web > > > > > > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check the > entire > > > > payload or only check there value we need ? > > > > > > > > On Thu, Apr 9, 2020 at 4:57 PM Martin Grigorov > > > > > wrote: > > > > > > > > > The images didn't make it to the mailing list. > > > > > Please use some online image paste bin. > > > > > > > > > > On Thu, Apr 9, 2020 at 11:33 AM Shengche Hsiao < > > > shengchehs...@gmail.com> > > > > > wrote: > > > > > > > > > > > I got a report , it suggest our web site to deal with xml > injection > > > > > issue. > > > > > > We use DropDownChoice with OnChangeAjaxBehavior to invoke another > > > > > > DropDownChoice via wicket-ajax buit-in xml payload, and the > > reporters > > > > > used > > > > > > Burpsuite to inject xml on xmlpayload, such as inject > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > and resulted in some abnormal response > > > > > > > > > > > > [image: image.png] > > > > > > > > > > > > As a result, I have to prevent the xml injection, do I check the > > > entire > > > > > > payload or only check there value we need ? > > > > > > > > > > > > On Thu, Apr 9, 2020 at 4:11 PM Martin Grigorov < > > mgrigo...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > >> On Thu, Apr 9, 2020 at 11:09 AM Shengche Hsiao < > > > > shengchehs...@gmail.com > > > > > > > > > > > >> wrote: > > > > > >> > > > > > >> > Yes, I need to know overriding which methods > > > > > >> > > > > > > >> > > > > > >> I still do not understand what exactly you need to accomplish. > > > > > >> Please be more specific! > > > > > >> > > > > > >> > > > > > >> > > > > > > >> > On Thu, Apr 9, 2020 at 16:03 Martin Grigorov < > > > mgrigo...@apache.org> > > > > > >> wrote: > > > > > >> > > > > > > >> > > Hi, > > > > > >> > > > > > > > >> > > On Thu, Apr 9, 2020 at 10:27 AM ShengChe Hsiao < > > > > front...@gmail.com> > > > > > >> > wrote: > > > > > >> > > > > > > > >> > > > Dear all > > > > > >> > > > > > > > > >> > > > I use built-in ajax dropdownchoice component, it's default > > > > payload > > > > > >> is > > > > > >> > xml > > > > > >> > > > entity, but if I need to prevent xml injection ,how can i > > do? > > > > > >> > > > > > > > > >> > > > > > > > >> > > Could you please give some more information what exactly you > > > need? > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > >> > > > ---> > > > > > >> > > > To boldly go where no man has gone before. > > > > > >> > > > > > > > > > > > > > > >> > > > ---> > > > > > >> > > > We do this not because it is easy. We do this because it > is > > > > hard. > > > > > >> > > > > > > > - > > > > > >> > > > --> > > > > > >> > > > If I have seen further it is by standing on the shoulders > of > > > > > giants. > > > > > >> > > > -- > > > > > >> > > > -> > > > > > >> > > > front...@gmail.com > > > > > >> > > > >
Re: Equivalent for PerSessionPageStore in Wicket 9
On Fri, Apr 10, 2020 at 4:01 PM Thomas Heigl wrote:
> FYI: I deployed Wicket 9.0.0-M5 to production an hour ago. 100k requests
> served and no issues so far.
>
Awesome!
Thank you for testing it!
>
> Great work!
>
> Thomas
>
> On Wed, Apr 8, 2020 at 3:13 PM Sven Meier wrote:
>
> > Many thanks Maxim!
> >
> > Sven
> >
> > On 08.04.20 14:29, Maxim Solodovnik wrote:
> > > Released :)
> > >
> > > On Wed, 8 Apr 2020 at 15:41, Maxim Solodovnik
> > wrote:
> > >> OK
> > >>
> > >> Will start new release process in couple of hours
> > >> Please stop me if you will find any blocker :)
> > >>
> > >> On Wed, 8 Apr 2020 at 14:36, Thomas Heigl
> wrote:
> > >>> Hi Maxim,
> > >>>
> > >>> It works for me now!
> > >>>
> > >>> Thomas
> > >>>
> > >>> On Wed, Apr 8, 2020 at 9:17 AM Maxim Solodovnik <
> solomax...@gmail.com>
> > >>> wrote:
> > >>>
> > Thanks a million!
> >
> > On Wed, 8 Apr 2020 at 14:10, Thomas Heigl
> > wrote:
> > > Hi Maxim,
> > >
> > > I'm testing against the snapshot now. Will get back to you shortly.
> > >
> > > Thomas
> > >
> > > On Wed, Apr 8, 2020 at 2:53 AM Maxim Solodovnik <
> > solomax...@gmail.com>
> > > wrote:
> > >
> > >> Hello All,
> > >>
> > >> M5 seems to be broken (deploy has failed more than 10 times during
> > my
> > >> build attempts)
> > >> I have to start another release
> > >> Could you please tell when can I start?
> > >>
> > >> On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik <
> solomax...@gmail.com
> > >
> > >> wrote:
> > >>> Hello Thomas,
> > >>>
> > >>> Please test M6-SNAPSHOT (so I don't have to release M5.2 :
> > >>>
> > >>> On Wed, 8 Apr 2020 at 02:39, Thomas Heigl
> > wrote:
> > Hi Maxim,
> >
> > That would be great. I want to do some more extensive testing
> and
> > then
> > deploy M5 into production. ;)
> >
> > Thomas
> >
> > On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik <
> > solomax...@gmail.com>
> > wrote:
> >
> > > I can pack another release
> > > later this week ...
> > >
> > > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl >
> > >> wrote:
> > >> Thanks Sven!
> > >>
> > >> Did your changes make it into the release? Or did they just
> > miss
> > >> it?
> > >> Thomas
> > >>
> > >> On Tue, Apr 7, 2020 at 7:43 PM Sven Meier
> > wrote:
> > >>> Hi Thomas,
> > >>>
> > >>> yes, you're right:
> > >>>
> > >>> wicketstuff data stores missed some adjustments to the latest
> > >> updates
> > > in
> > >>> wicket-core.
> > >>>
> > >>> And SessionQuotaManagingDataStore$DelegatedPage must be
> > >> serializable of
> > >>> course.
> > >>>
> > >>> I've pushed changes to wicketstuff master.
> > >>>
> > >>> Thanks
> > >>> Sven
> > >>>
> > >>>
> > >>> On 07.04.20 14:14, Thomas Heigl wrote:
> > And one more thing. There is now a warning logged just
> > before
> > >>> serialization:
> > WARN o.a.w.pageStore.AsynchronousPageStore: Delegated
> > page
> > >> store
> > > 'org.apache.wicket.pageStore.SerializingPageStore' can
> > not be
> > >>> asynchronous
> >
> > On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl <
> > >> tho...@umschalt.com>
> > > wrote:
> > > The cause is the following MetaData entry in the session:
> > >
> > > class
> >
> >
> org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > > On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl <
> > >> tho...@umschalt.com>
> > >>> wrote:
> > >> Hi Sven,
> > >>
> > >> I just found time to give this a try with Wicket
> > 9.0.0-M5.
> > >> There
> > > seem
> > >>> to
> > >> be issues with serialization now.
> > >>
> > >> My new config:
> > >>
> > >> protected IPageStore newCachingStore(IPageStore
> > pageStore) {
> > >>> return new CachingPageStore(pageStore, new
> > >>> InMemoryPageStore(getName(),
> > >>> MAX_PAGES_CACHED_PER_SESSION));
> > >>> }
> > >>> protected IPageStore newPersistentStore() {
> > >>> final RedissonRedisCache redisCache = new
> > >>> RedissonRedisCache(redissonClient);
> > >>> final RedisDataStore redisDataStore = new
> > > RedisDataStore(getName(),
> > >>> redisCache, new RedisSettings());
> > >>> return new
Re: Quick Start Error with 8.7.0 - The desired archetype does not exist
This worked after upgrade to latest version on Maven (3.6.30). Bruce Sent from my iPad > On Apr 10, 2020, at 8:36 AM, Martin Grigorov wrote: > > Hi, > > It works fine for me: > > mvn archetype:generate -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 > -DgroupId=4MyTestCompany -DartifactId=testWicket8 -DarchetypeRepository= > https://repository.apache.org/ -DinteractiveMode=false > [INFO] Scanning for projects... > [INFO] > [INFO] --< org.apache.maven:standalone-pom >> --- > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] [ pom > ]- > [INFO] > [INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > > generate-sources @ standalone-pom >>> > [INFO] > [INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < > generate-sources @ standalone-pom <<< > [INFO] > [INFO] > [INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ > standalone-pom --- > [INFO] Generating project in Batch mode > [INFO] Archetype repository not defined. Using the one from > [org.apache.wicket:wicket-archetype-quickstart:9.0.0-M4] found in catalog > remote > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > (2.7 kB at 21 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > (42 kB at 629 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > (30 kB at 475 kB/s) > [INFO] > > [INFO] Using following parameters for creating project from Archetype: > wicket-archetype-quickstart:8.7.0 > [INFO] > > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: packageInPathFormat, Value: 4MyTestCompany > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Project created from Archetype in dir: /tmp/testWicket8 > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 2.944 s > [INFO] Finished at: 2020-04-10T15:35:22+03:00 > [INFO] > > >> On Fri, Apr 10, 2020 at 3:28 PM Bruce Lombardi wrote: >> >> Hi, >> >> >> >> I tried to use the Quick Start to get wicket 8.7.0 . >> >> >> >> The command line generated on the Wicked site is as follows (except I added >> the -X switch and ran it again after getting the error to get more >> information). >> >> >> >> mvn -X archetype:generate -DarchetypeGroupId=org.apache.wicket >> -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 >> -DgroupId=4MyTestCompany -DartifactId=testWicket8 >> -DarchetypeRepository=https://repository.apache.org/ >> -DinteractiveMode=false >> >> >> >> >> >> The full trace is below, but the error seems to be: >> >> >> >> "The desired archetype does not exist >> (org.apache.wicket:wicket-archetype-quickstart:8.7.0)" >> >> >> >> Is this really missing or is there something wrong with my Maven set up? >> >> >> >> Bruce >> >> >> >> >> >> [DEBUG] Included: org.codehaus.groovy:groovy:jar:1.8.3 >> >> [DEBUG] Included: antlr:antlr:jar:2.7.7 >> >> [DEBUG] Included: asm:asm:jar:3.2 >> >> [DEBUG] Included: asm:asm-commons:jar:3.2 >> >> [DEBUG] Included: asm:asm-util:jar:3.2 >> >> [DEBUG] Included: asm:asm-analysis:jar:3.2 >> >> [DEBUG] Included: asm:asm-tree:jar:3.2 >> >> [DEBUG] Included: org.beanshell:bsh:jar:2.0b4 >> >> [DEBUG] Included: >> org.apache.maven.shared:maven-script-interpreter:jar:1.0 >> >> [DEBUG] Included: org.apache.ant:ant:jar:1.8.1 >> >> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.8 >> >> [DEBUG] Excluded:
Re: Quick Start Error with 8.7.0 - The desired archetype does not exist
Bruce Sent from my iPad > On Apr 10, 2020, at 8:36 AM, Martin Grigorov wrote: > > Hi, > > It works fine for me: > > mvn archetype:generate -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 > -DgroupId=4MyTestCompany -DartifactId=testWicket8 -DarchetypeRepository= > https://repository.apache.org/ -DinteractiveMode=false > [INFO] Scanning for projects... > [INFO] > [INFO] --< org.apache.maven:standalone-pom >> --- > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] [ pom > ]- > [INFO] > [INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > > generate-sources @ standalone-pom >>> > [INFO] > [INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < > generate-sources @ standalone-pom <<< > [INFO] > [INFO] > [INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ > standalone-pom --- > [INFO] Generating project in Batch mode > [INFO] Archetype repository not defined. Using the one from > [org.apache.wicket:wicket-archetype-quickstart:9.0.0-M4] found in catalog > remote > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > (2.7 kB at 21 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > (42 kB at 629 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > (30 kB at 475 kB/s) > [INFO] > > [INFO] Using following parameters for creating project from Archetype: > wicket-archetype-quickstart:8.7.0 > [INFO] > > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: packageInPathFormat, Value: 4MyTestCompany > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Project created from Archetype in dir: /tmp/testWicket8 > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 2.944 s > [INFO] Finished at: 2020-04-10T15:35:22+03:00 > [INFO] > > >> On Fri, Apr 10, 2020 at 3:28 PM Bruce Lombardi wrote: >> >> Hi, >> >> >> >> I tried to use the Quick Start to get wicket 8.7.0 . >> >> >> >> The command line generated on the Wicked site is as follows (except I added >> the -X switch and ran it again after getting the error to get more >> information). >> >> >> >> mvn -X archetype:generate -DarchetypeGroupId=org.apache.wicket >> -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 >> -DgroupId=4MyTestCompany -DartifactId=testWicket8 >> -DarchetypeRepository=https://repository.apache.org/ >> -DinteractiveMode=false >> >> >> >> >> >> The full trace is below, but the error seems to be: >> >> >> >> "The desired archetype does not exist >> (org.apache.wicket:wicket-archetype-quickstart:8.7.0)" >> >> >> >> Is this really missing or is there something wrong with my Maven set up? >> >> >> >> Bruce >> >> >> >> >> >> [DEBUG] Included: org.codehaus.groovy:groovy:jar:1.8.3 >> >> [DEBUG] Included: antlr:antlr:jar:2.7.7 >> >> [DEBUG] Included: asm:asm:jar:3.2 >> >> [DEBUG] Included: asm:asm-commons:jar:3.2 >> >> [DEBUG] Included: asm:asm-util:jar:3.2 >> >> [DEBUG] Included: asm:asm-analysis:jar:3.2 >> >> [DEBUG] Included: asm:asm-tree:jar:3.2 >> >> [DEBUG] Included: org.beanshell:bsh:jar:2.0b4 >> >> [DEBUG] Included: >> org.apache.maven.shared:maven-script-interpreter:jar:1.0 >> >> [DEBUG] Included: org.apache.ant:ant:jar:1.8.1 >> >> [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.8 >> >> [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.8 >> >> [DEBUG] Excluded:
Wicket 1.4 equivalent of FeedbackCollector
I have a little chunk of re-usable code I wrote in some of our more modern apps that I've been asked to add to a couple apps we have that are very old. they're still on wicket 1.4 and the boss doesn't want to invest in upgrading them wholesale, but just wants this one feature put in. It relies on FeedbackCollector. Is there a 1.4 equivalent for the FeedbackCollector? -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Quick Start Error with 8.7.0 - The desired archetype does not exist
Thanks Martin, I tried again and still no luck. I’ll have to look deeper into my maven configuration I guess. Any other ideas would be appreciated. Bruce Sent from my iPad > On Apr 10, 2020, at 8:36 AM, Martin Grigorov wrote: > > Hi, > > It works fine for me: > > mvn archetype:generate -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 > -DgroupId=4MyTestCompany -DartifactId=testWicket8 -DarchetypeRepository= > https://repository.apache.org/ -DinteractiveMode=false > [INFO] Scanning for projects... > [INFO] > [INFO] --< org.apache.maven:standalone-pom >> --- > [INFO] Building Maven Stub Project (No POM) 1 > [INFO] [ pom > ]- > [INFO] > [INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > > generate-sources @ standalone-pom >>> > [INFO] > [INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < > generate-sources @ standalone-pom <<< > [INFO] > [INFO] > [INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ > standalone-pom --- > [INFO] Generating project in Batch mode > [INFO] Archetype repository not defined. Using the one from > [org.apache.wicket:wicket-archetype-quickstart:9.0.0-M4] found in catalog > remote > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom > (2.7 kB at 21 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom > (42 kB at 629 kB/s) > [INFO] Downloading from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > [INFO] Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar > (30 kB at 475 kB/s) > [INFO] > > [INFO] Using following parameters for creating project from Archetype: > wicket-archetype-quickstart:8.7.0 > [INFO] > > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: packageInPathFormat, Value: 4MyTestCompany > [INFO] Parameter: package, Value: 4MyTestCompany > [INFO] Parameter: groupId, Value: 4MyTestCompany > [INFO] Parameter: artifactId, Value: testWicket8 > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Project created from Archetype in dir: /tmp/testWicket8 > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 2.944 s > [INFO] Finished at: 2020-04-10T15:35:22+03:00 > [INFO] > > >> On Fri, Apr 10, 2020 at 3:28 PM Bruce Lombardi wrote: >> >> Hi, >> >> >> >> I tried to use the Quick Start to get wicket 8.7.0 . >> >> >> >> The command line generated on the Wicked site is as follows (except I added >> the -X switch and ran it again after getting the error to get more >> information). >> >> >> >> mvn -X archetype:generate -DarchetypeGroupId=org.apache.wicket >> -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 >> -DgroupId=4MyTestCompany -DartifactId=testWicket8 >> -DarchetypeRepository=https://repository.apache.org/ >> -DinteractiveMode=false >> >> >> >> >> >> The full trace is below, but the error seems to be: >> >> >> >> "The desired archetype does not exist >> (org.apache.wicket:wicket-archetype-quickstart:8.7.0)" >> >> >> >> Is this really missing or is there something wrong with my Maven set up? >> >> >> >> Bruce >> >> >> >> >> >> [DEBUG] Included: org.codehaus.groovy:groovy:jar:1.8.3 >> >> [DEBUG] Included: antlr:antlr:jar:2.7.7 >> >> [DEBUG] Included: asm:asm:jar:3.2 >> >> [DEBUG] Included: asm:asm-commons:jar:3.2 >> >> [DEBUG] Included: asm:asm-util:jar:3.2 >> >> [DEBUG] Included: asm:asm-analysis:jar:3.2 >> >> [DEBUG] Included: asm:asm-tree:jar:3.2 >> >> [DEBUG] Included: org.beanshell:bsh:jar:2.0b4 >> >> [DEBUG] Included: >> org.apache.maven.shared:maven-script-interpreter:jar:1.0 >> >> [DEBUG] Included: org.apache.ant:ant:jar:1.8.1 >> >> [DEBUG] Excluded:
Re: Equivalent for PerSessionPageStore in Wicket 9
FYI: I deployed Wicket 9.0.0-M5 to production an hour ago. 100k requests
served and no issues so far.
Great work!
Thomas
On Wed, Apr 8, 2020 at 3:13 PM Sven Meier wrote:
> Many thanks Maxim!
>
> Sven
>
> On 08.04.20 14:29, Maxim Solodovnik wrote:
> > Released :)
> >
> > On Wed, 8 Apr 2020 at 15:41, Maxim Solodovnik
> wrote:
> >> OK
> >>
> >> Will start new release process in couple of hours
> >> Please stop me if you will find any blocker :)
> >>
> >> On Wed, 8 Apr 2020 at 14:36, Thomas Heigl wrote:
> >>> Hi Maxim,
> >>>
> >>> It works for me now!
> >>>
> >>> Thomas
> >>>
> >>> On Wed, Apr 8, 2020 at 9:17 AM Maxim Solodovnik
> >>> wrote:
> >>>
> Thanks a million!
>
> On Wed, 8 Apr 2020 at 14:10, Thomas Heigl
> wrote:
> > Hi Maxim,
> >
> > I'm testing against the snapshot now. Will get back to you shortly.
> >
> > Thomas
> >
> > On Wed, Apr 8, 2020 at 2:53 AM Maxim Solodovnik <
> solomax...@gmail.com>
> > wrote:
> >
> >> Hello All,
> >>
> >> M5 seems to be broken (deploy has failed more than 10 times during
> my
> >> build attempts)
> >> I have to start another release
> >> Could you please tell when can I start?
> >>
> >> On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik >
> >> wrote:
> >>> Hello Thomas,
> >>>
> >>> Please test M6-SNAPSHOT (so I don't have to release M5.2 :
> >>>
> >>> On Wed, 8 Apr 2020 at 02:39, Thomas Heigl
> wrote:
> Hi Maxim,
>
> That would be great. I want to do some more extensive testing and
> then
> deploy M5 into production. ;)
>
> Thomas
>
> On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik <
> solomax...@gmail.com>
> wrote:
>
> > I can pack another release
> > later this week ...
> >
> > On Wed, 8 Apr 2020 at 00:48, Thomas Heigl
> >> wrote:
> >> Thanks Sven!
> >>
> >> Did your changes make it into the release? Or did they just
> miss
> >> it?
> >> Thomas
> >>
> >> On Tue, Apr 7, 2020 at 7:43 PM Sven Meier
> wrote:
> >>> Hi Thomas,
> >>>
> >>> yes, you're right:
> >>>
> >>> wicketstuff data stores missed some adjustments to the latest
> >> updates
> > in
> >>> wicket-core.
> >>>
> >>> And SessionQuotaManagingDataStore$DelegatedPage must be
> >> serializable of
> >>> course.
> >>>
> >>> I've pushed changes to wicketstuff master.
> >>>
> >>> Thanks
> >>> Sven
> >>>
> >>>
> >>> On 07.04.20 14:14, Thomas Heigl wrote:
> And one more thing. There is now a warning logged just
> before
> >>> serialization:
> WARN o.a.w.pageStore.AsynchronousPageStore: Delegated
> page
> >> store
> > 'org.apache.wicket.pageStore.SerializingPageStore' can
> not be
> >>> asynchronous
>
> On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl <
> >> tho...@umschalt.com>
> > wrote:
> > The cause is the following MetaData entry in the session:
> >
> > class
>
> org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
> > On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl <
> >> tho...@umschalt.com>
> >>> wrote:
> >> Hi Sven,
> >>
> >> I just found time to give this a try with Wicket
> 9.0.0-M5.
> >> There
> > seem
> >>> to
> >> be issues with serialization now.
> >>
> >> My new config:
> >>
> >> protected IPageStore newCachingStore(IPageStore
> pageStore) {
> >>> return new CachingPageStore(pageStore, new
> >>> InMemoryPageStore(getName(),
> >>> MAX_PAGES_CACHED_PER_SESSION));
> >>> }
> >>> protected IPageStore newPersistentStore() {
> >>> final RedissonRedisCache redisCache = new
> >>> RedissonRedisCache(redissonClient);
> >>> final RedisDataStore redisDataStore = new
> > RedisDataStore(getName(),
> >>> redisCache, new RedisSettings());
> >>> return new SessionQuotaManagingDataStore(redisDataStore,
> >>> DATA_STORE_MAX_BYTES_PER_SESSION);
> >>> }
> >> This exception is logged after requests:
> >>
> >>
> >> org.springframework.data.redis.serializer.SerializationException:
> >>> Cannot
> >>> serialize; nested exception is
> >>>
>
> org.springframework.core.serializer.support.SerializationFailedException:
> >>> Failed to serialize
Re: Quick Start Error with 8.7.0 - The desired archetype does not exist
Hi, It works fine for me: mvn archetype:generate -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 -DgroupId=4MyTestCompany -DartifactId=testWicket8 -DarchetypeRepository= https://repository.apache.org/ -DinteractiveMode=false [INFO] Scanning for projects... [INFO] [INFO] --< org.apache.maven:standalone-pom >--- [INFO] Building Maven Stub Project (No POM) 1 [INFO] [ pom ]- [INFO] [INFO] >>> maven-archetype-plugin:3.0.1:generate (default-cli) > generate-sources @ standalone-pom >>> [INFO] [INFO] <<< maven-archetype-plugin:3.0.1:generate (default-cli) < generate-sources @ standalone-pom <<< [INFO] [INFO] [INFO] --- maven-archetype-plugin:3.0.1:generate (default-cli) @ standalone-pom --- [INFO] Generating project in Batch mode [INFO] Archetype repository not defined. Using the one from [org.apache.wicket:wicket-archetype-quickstart:9.0.0-M4] found in catalog remote [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.pom (2.7 kB at 21 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-parent/8.7.0/wicket-parent-8.7.0.pom (42 kB at 629 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/wicket/wicket-archetype-quickstart/8.7.0/wicket-archetype-quickstart-8.7.0.jar (30 kB at 475 kB/s) [INFO] [INFO] Using following parameters for creating project from Archetype: wicket-archetype-quickstart:8.7.0 [INFO] [INFO] Parameter: groupId, Value: 4MyTestCompany [INFO] Parameter: artifactId, Value: testWicket8 [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: package, Value: 4MyTestCompany [INFO] Parameter: packageInPathFormat, Value: 4MyTestCompany [INFO] Parameter: package, Value: 4MyTestCompany [INFO] Parameter: groupId, Value: 4MyTestCompany [INFO] Parameter: artifactId, Value: testWicket8 [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Project created from Archetype in dir: /tmp/testWicket8 [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 2.944 s [INFO] Finished at: 2020-04-10T15:35:22+03:00 [INFO] On Fri, Apr 10, 2020 at 3:28 PM Bruce Lombardi wrote: > Hi, > > > > I tried to use the Quick Start to get wicket 8.7.0 . > > > > The command line generated on the Wicked site is as follows (except I added > the -X switch and ran it again after getting the error to get more > information). > > > > mvn -X archetype:generate -DarchetypeGroupId=org.apache.wicket > -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 > -DgroupId=4MyTestCompany -DartifactId=testWicket8 > -DarchetypeRepository=https://repository.apache.org/ > -DinteractiveMode=false > > > > > > The full trace is below, but the error seems to be: > > > > "The desired archetype does not exist > (org.apache.wicket:wicket-archetype-quickstart:8.7.0)" > > > > Is this really missing or is there something wrong with my Maven set up? > > > > Bruce > > > > > > [DEBUG] Included: org.codehaus.groovy:groovy:jar:1.8.3 > > [DEBUG] Included: antlr:antlr:jar:2.7.7 > > [DEBUG] Included: asm:asm:jar:3.2 > > [DEBUG] Included: asm:asm-commons:jar:3.2 > > [DEBUG] Included: asm:asm-util:jar:3.2 > > [DEBUG] Included: asm:asm-analysis:jar:3.2 > > [DEBUG] Included: asm:asm-tree:jar:3.2 > > [DEBUG] Included: org.beanshell:bsh:jar:2.0b4 > > [DEBUG] Included: > org.apache.maven.shared:maven-script-interpreter:jar:1.0 > > [DEBUG] Included: org.apache.ant:ant:jar:1.8.1 > > [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.8 > > [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.8 > > [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.8 > > [DEBUG] Excluded: > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 > > [DEBUG] Excluded: junit:junit:jar:4.8.2 > > [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.8 > > [DEBUG] Excluded: org.apache.maven:maven-core:jar:2.0.8 > > [DEBUG] Excluded:
Quick Start Error with 8.7.0 - The desired archetype does not exist
Hi, I tried to use the Quick Start to get wicket 8.7.0 . The command line generated on the Wicked site is as follows (except I added the -X switch and ran it again after getting the error to get more information). mvn -X archetype:generate -DarchetypeGroupId=org.apache.wicket -DarchetypeArtifactId=wicket-archetype-quickstart -DarchetypeVersion=8.7.0 -DgroupId=4MyTestCompany -DartifactId=testWicket8 -DarchetypeRepository=https://repository.apache.org/ -DinteractiveMode=false The full trace is below, but the error seems to be: "The desired archetype does not exist (org.apache.wicket:wicket-archetype-quickstart:8.7.0)" Is this really missing or is there something wrong with my Maven set up? Bruce [DEBUG] Included: org.codehaus.groovy:groovy:jar:1.8.3 [DEBUG] Included: antlr:antlr:jar:2.7.7 [DEBUG] Included: asm:asm:jar:3.2 [DEBUG] Included: asm:asm-commons:jar:3.2 [DEBUG] Included: asm:asm-util:jar:3.2 [DEBUG] Included: asm:asm-analysis:jar:3.2 [DEBUG] Included: asm:asm-tree:jar:3.2 [DEBUG] Included: org.beanshell:bsh:jar:2.0b4 [DEBUG] Included: org.apache.maven.shared:maven-script-interpreter:jar:1.0 [DEBUG] Included: org.apache.ant:ant:jar:1.8.1 [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.8 [DEBUG] Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 [DEBUG] Excluded: junit:junit:jar:4.8.2 [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-core:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-error-diagnostics:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-plugin-descriptor:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.8 [DEBUG] Excluded: org.apache.maven:maven-monitor:jar:2.0.8 [DEBUG] Excluded: classworlds:classworlds:jar:1.1 [DEBUG] Configuring mojo org.apache.maven.plugins:maven-archetype-plugin:2.2:generate from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-archetype-plugin:2.2, parent: sun.misc.Launcher$AppClassLoader@4e25154f] [DEBUG] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [DEBUG] Setting property: site.resource.loader.class => 'org.codehaus.plexus.velocity.SiteResourceLoader'. [DEBUG] Setting property: velocimacro.messages.on => 'false'. [DEBUG] Setting property: resource.loader => 'classpath,site'. [DEBUG] Setting property: runtime.log.invalid.references => 'false'. [DEBUG] Setting property: resource.manager.logwhenfound => 'false'. [DEBUG] *** [DEBUG] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29) [DEBUG] RuntimeInstance initializing. [DEBUG] Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [DEBUG] LogSystem has been deprecated. Please use a LogChute implementation. [DEBUG] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader [DEBUG] ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) [DEBUG] Default ResourceManager initialization complete. [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Include [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [DEBUG] Created '20' parsers. [DEBUG] Velocimacro : initialization starting. [DEBUG] Velocimacro : allowInline = true : VMs can be defined inline in templates [DEBUG] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions [DEBUG] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [DEBUG] Velocimacro : autoload off : VM system will not automatically reload global library macros [DEBUG] Velocimacro : Velocimacro : initialization complete. [DEBUG] RuntimeInstance successfully initialized. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-archetype-plugin:2.2:generate' with basic configurator
Re: Upgrade to Wicket 9: troubles with WicketTester and MockPageStore
On 2020/04/10 08:13:40, Maxim Solodovnik wrote: > On Fri, 10 Apr 2020 at 15:06, Francesco Chicchiriccò > wrote: > > > On 2020/04/10 06:59:06, Sven Meier wrote: > > > Hi Francesco, > > > > > > there was a slight difference in the mock setup, which should now be as > > > in Wicket 8: > > > > > > https://issues.apache.org/jira/browse/WICKET-6766 > > > > > > Many thanks for testing with Wicket 9! > > > > Great spot Sven! > > > > Which is the SNAPSHOT version to try such a change? When the related > > artifact will be available? > > > > this is M6-SNAPSHOT > M5 was just released ... Thanks Maxim. By looking at Sven's commit I could simplify my workaround as https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L110-L120 Once 9.0.0-M6 will be out, I'll remove it. Thanks again! > > > On 09.04.20 16:42, Francesco Chicchiriccò wrote: > > > > On 2020/04/09 12:04:00, Sven Meier wrote: > > > >> Hi Francesco, > > > >> > > > >> I'll have to check what has changed here. > > > >> > > > >> I wouldn't expect any problems with MockPageStore, but perhaps it > > > >> changed slightly. > > > >> > > > >> Can you write a testcase that runs in Wicket 8 but fails in 9? > > > > Not sure if I am able, but I'll try. > > > > Meanwhile, should you get an enlightenment, please report. > > > > > > > > Regards. > > > > > > > >> On 09.04.20 12:20, Francesco Chicchiriccò wrote: > > > >>> Hi all, > > > >>> at Syncope we have been upgrading our Console and Enduser web > > applications from Wicket 8 to 9.0.0-M5, in our master branch. > > > >>> > > > >>> The process have been quite smooth effectively, with a single > > noticeable exception: in our tests we largely use WicketTester; we have > > verified, however, that Pages in the MockPageStore are incrementing their > > numericId during tests execution, even though they are still looked up by > > their initial numericId. > > > >>> > > > >>> We are using this workaround: > > > >>> > > > >>> > > https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L107-L125 > > > >>> > > > >>> which is serving its purpose for the moment; please note that this > > was not needed with Wicket 8. > > > >>> > > > >>> Are we missing something or the one above is effectively a bug? > > > >>> > > > >>> Thanks for your support. > > > >>> Regards. > > > >>> > > > >>> - > > > >>> 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 > > > > > > > > > > - > > > 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 > > > > > > -- > Best regards, > Maxim > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Upgrade to Wicket 9: troubles with WicketTester and MockPageStore
On Fri, 10 Apr 2020 at 15:06, Francesco Chicchiriccò wrote: > On 2020/04/10 06:59:06, Sven Meier wrote: > > Hi Francesco, > > > > there was a slight difference in the mock setup, which should now be as > > in Wicket 8: > > > > https://issues.apache.org/jira/browse/WICKET-6766 > > > > Many thanks for testing with Wicket 9! > > Great spot Sven! > > Which is the SNAPSHOT version to try such a change? When the related > artifact will be available? > this is M6-SNAPSHOT M5 was just released ... > > Regards. > > > On 09.04.20 16:42, Francesco Chicchiriccò wrote: > > > On 2020/04/09 12:04:00, Sven Meier wrote: > > >> Hi Francesco, > > >> > > >> I'll have to check what has changed here. > > >> > > >> I wouldn't expect any problems with MockPageStore, but perhaps it > > >> changed slightly. > > >> > > >> Can you write a testcase that runs in Wicket 8 but fails in 9? > > > Not sure if I am able, but I'll try. > > > Meanwhile, should you get an enlightenment, please report. > > > > > > Regards. > > > > > >> On 09.04.20 12:20, Francesco Chicchiriccò wrote: > > >>> Hi all, > > >>> at Syncope we have been upgrading our Console and Enduser web > applications from Wicket 8 to 9.0.0-M5, in our master branch. > > >>> > > >>> The process have been quite smooth effectively, with a single > noticeable exception: in our tests we largely use WicketTester; we have > verified, however, that Pages in the MockPageStore are incrementing their > numericId during tests execution, even though they are still looked up by > their initial numericId. > > >>> > > >>> We are using this workaround: > > >>> > > >>> > https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L107-L125 > > >>> > > >>> which is serving its purpose for the moment; please note that this > was not needed with Wicket 8. > > >>> > > >>> Are we missing something or the one above is effectively a bug? > > >>> > > >>> Thanks for your support. > > >>> Regards. > > >>> > > >>> - > > >>> 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 > > > > > > > - > > 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 > > -- Best regards, Maxim
Re: Upgrade to Wicket 9: troubles with WicketTester and MockPageStore
On 2020/04/10 06:59:06, Sven Meier wrote: > Hi Francesco, > > there was a slight difference in the mock setup, which should now be as > in Wicket 8: > > https://issues.apache.org/jira/browse/WICKET-6766 > > Many thanks for testing with Wicket 9! Great spot Sven! Which is the SNAPSHOT version to try such a change? When the related artifact will be available? Regards. > On 09.04.20 16:42, Francesco Chicchiriccò wrote: > > On 2020/04/09 12:04:00, Sven Meier wrote: > >> Hi Francesco, > >> > >> I'll have to check what has changed here. > >> > >> I wouldn't expect any problems with MockPageStore, but perhaps it > >> changed slightly. > >> > >> Can you write a testcase that runs in Wicket 8 but fails in 9? > > Not sure if I am able, but I'll try. > > Meanwhile, should you get an enlightenment, please report. > > > > Regards. > > > >> On 09.04.20 12:20, Francesco Chicchiriccò wrote: > >>> Hi all, > >>> at Syncope we have been upgrading our Console and Enduser web > >>> applications from Wicket 8 to 9.0.0-M5, in our master branch. > >>> > >>> The process have been quite smooth effectively, with a single noticeable > >>> exception: in our tests we largely use WicketTester; we have verified, > >>> however, that Pages in the MockPageStore are incrementing their numericId > >>> during tests execution, even though they are still looked up by their > >>> initial numericId. > >>> > >>> We are using this workaround: > >>> > >>> https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L107-L125 > >>> > >>> which is serving its purpose for the moment; please note that this was > >>> not needed with Wicket 8. > >>> > >>> Are we missing something or the one above is effectively a bug? > >>> > >>> Thanks for your support. > >>> Regards. > >>> > >>> - > >>> 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 > > > > - > 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: Upgrade to Wicket 9: troubles with WicketTester and MockPageStore
Hi Francesco, there was a slight difference in the mock setup, which should now be as in Wicket 8: https://issues.apache.org/jira/browse/WICKET-6766 Many thanks for testing with Wicket 9! Sven On 09.04.20 16:42, Francesco Chicchiriccò wrote: On 2020/04/09 12:04:00, Sven Meier wrote: Hi Francesco, I'll have to check what has changed here. I wouldn't expect any problems with MockPageStore, but perhaps it changed slightly. Can you write a testcase that runs in Wicket 8 but fails in 9? Not sure if I am able, but I'll try. Meanwhile, should you get an enlightenment, please report. Regards. On 09.04.20 12:20, Francesco Chicchiriccò wrote: Hi all, at Syncope we have been upgrading our Console and Enduser web applications from Wicket 8 to 9.0.0-M5, in our master branch. The process have been quite smooth effectively, with a single noticeable exception: in our tests we largely use WicketTester; we have verified, however, that Pages in the MockPageStore are incrementing their numericId during tests execution, even though they are still looked up by their initial numericId. We are using this workaround: https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/AbstractConsoleITCase.java#L107-L125 which is serving its purpose for the moment; please note that this was not needed with Wicket 8. Are we missing something or the one above is effectively a bug? Thanks for your support. Regards. - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
