Re: 6.0.x Docs Down?

[Martin Grigorov]

The javadocs [1] and guide [2] are available again!

As I said we use JDK 7.x for the build as a workaround.

1. http://ci.apache.org/projects/wicket/apidocs/6.x/
2. http://ci.apache.org/projects/wicket/guide/6.x/

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Wed, Jul 8, 2015 at 9:34 AM, Martin Grigorov 
wrote:

> The problem is in OpenSSL. The Nexus server has been updated with a better
> SSL certificate and now JDK 1.6 cannot connect to it:
> https://issues.apache.org/jira/browse/BUILDS-85
>
> As a temporary workaround I'll switch our Wicket 6.x build to use JDK 7.x.
> There is a suggestion to use Maven toolchains, so Maven is run with JDK 7,
> but the compilation is done with JDK 1.6.
> I'll do it as soon as I have the time.
>
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Jul 8, 2015 at 4:39 AM, gump lee  wrote:
>
>> The link for 6.0 api still down.
>>
>> http://ci.apache.org/projects/wicket/apidocs/6.x/
>>
>> Where would I found the API document?
>>
>>
>> Thanks and best regards,
>> Gump
>>
>>
>> On Tue, Jun 30, 2015 at 1:54 PM, Martin Grigorov 
>> wrote:
>>
>> > https://blogs.apache.org/infra/entry/buildbot_master_currently_off_line
>> > On Jun 30, 2015 6:00 AM, "kyabe_JP"  wrote:
>> >
>> > > I have failed to access to any apidocs page, e.g
>> > > http://ci.apache.org/projects/wicket/apidocs/6.x/
>> > >   .
>> > >
>> > > According to the past conversation, the BuildBot servers had been
>> back.
>> > >
>> > > Am I looking wrong address or if it down again ?
>> > >
>> > >
>> > > --
>> > > View this message in context:
>> > >
>> >
>> http://apache-wicket.1842946.n4.nabble.com/6-0-x-Docs-Down-tp4665501p4671417.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: 6.0.x Docs Down?

[Rob Audenaerde]

Thanks Martin!

On Wed, Jul 8, 2015 at 9:08 AM, Martin Grigorov 
wrote:

> The javadocs [1] and guide [2] are available again!
>
> As I said we use JDK 7.x for the build as a workaround.
>
> 1. http://ci.apache.org/projects/wicket/apidocs/6.x/
> 2. http://ci.apache.org/projects/wicket/guide/6.x/
>
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Jul 8, 2015 at 9:34 AM, Martin Grigorov 
> wrote:
>
> > The problem is in OpenSSL. The Nexus server has been updated with a
> better
> > SSL certificate and now JDK 1.6 cannot connect to it:
> > https://issues.apache.org/jira/browse/BUILDS-85
> >
> > As a temporary workaround I'll switch our Wicket 6.x build to use JDK
> 7.x.
> > There is a suggestion to use Maven toolchains, so Maven is run with JDK
> 7,
> > but the compilation is done with JDK 1.6.
> > I'll do it as soon as I have the time.
> >
> > Martin Grigorov
> > Freelancer. Available for hire!
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Wed, Jul 8, 2015 at 4:39 AM, gump lee  wrote:
> >
> >> The link for 6.0 api still down.
> >>
> >> http://ci.apache.org/projects/wicket/apidocs/6.x/
> >>
> >> Where would I found the API document?
> >>
> >>
> >> Thanks and best regards,
> >> Gump
> >>
> >>
> >> On Tue, Jun 30, 2015 at 1:54 PM, Martin Grigorov 
> >> wrote:
> >>
> >> >
> https://blogs.apache.org/infra/entry/buildbot_master_currently_off_line
> >> > On Jun 30, 2015 6:00 AM, "kyabe_JP"  wrote:
> >> >
> >> > > I have failed to access to any apidocs page, e.g
> >> > > http://ci.apache.org/projects/wicket/apidocs/6.x/
> >> > >   .
> >> > >
> >> > > According to the past conversation, the BuildBot servers had been
> >> back.
> >> > >
> >> > > Am I looking wrong address or if it down again ?
> >> > >
> >> > >
> >> > > --
> >> > > View this message in context:
> >> > >
> >> >
> >>
> http://apache-wicket.1842946.n4.nabble.com/6-0-x-Docs-Down-tp4665501p4671417.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: 6.0.x Docs Down?

[Tobias Soloschenko]

Thank you very much for the investigations Martin! 

kind regards

Tobias

> Am 08.07.2015 um 09:08 schrieb Martin Grigorov :
> 
> The javadocs [1] and guide [2] are available again!
> 
> As I said we use JDK 7.x for the build as a workaround.
> 
> 1. http://ci.apache.org/projects/wicket/apidocs/6.x/
> 2. http://ci.apache.org/projects/wicket/guide/6.x/
> 
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
> 
> On Wed, Jul 8, 2015 at 9:34 AM, Martin Grigorov 
> wrote:
> 
>> The problem is in OpenSSL. The Nexus server has been updated with a better
>> SSL certificate and now JDK 1.6 cannot connect to it:
>> https://issues.apache.org/jira/browse/BUILDS-85
>> 
>> As a temporary workaround I'll switch our Wicket 6.x build to use JDK 7.x.
>> There is a suggestion to use Maven toolchains, so Maven is run with JDK 7,
>> but the compilation is done with JDK 1.6.
>> I'll do it as soon as I have the time.
>> 
>> Martin Grigorov
>> Freelancer. Available for hire!
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>> 
>>> On Wed, Jul 8, 2015 at 4:39 AM, gump lee  wrote:
>>> 
>>> The link for 6.0 api still down.
>>> 
>>> http://ci.apache.org/projects/wicket/apidocs/6.x/
>>> 
>>> Where would I found the API document?
>>> 
>>> 
>>> Thanks and best regards,
>>> Gump
>>> 
>>> 
>>> On Tue, Jun 30, 2015 at 1:54 PM, Martin Grigorov 
>>> wrote:
>>> 
 https://blogs.apache.org/infra/entry/buildbot_master_currently_off_line
> On Jun 30, 2015 6:00 AM, "kyabe_JP"  wrote:
> 
> I have failed to access to any apidocs page, e.g
> http://ci.apache.org/projects/wicket/apidocs/6.x/
>   .
> 
> According to the past conversation, the BuildBot servers had been
>>> back.
> 
> Am I looking wrong address or if it down again ?
> 
> 
> --
> View this message in context:
>>> http://apache-wicket.1842946.n4.nabble.com/6-0-x-Docs-Down-tp4665501p4671417.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
>> 
>> 

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

I'm back from the wilderness!!!

[shetc]

About to start working on a new project using Wicket 6.20 . After being taken
over by another company, I have been doing integration work and supporting
legacy Wicket-based apps (4.0 or less). Also new C# projects. We are finally
back on track so this is a welcome return to Wicket sensibility.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/I-m-back-from-the-wilderness-tp4671545.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: Wicket7: MediaComponent and Source classes

[Sebastien]

Hi,

Sorry, little bit late on the topic...

On Fri, Jul 3, 2015 at 7:38 AM, Martin Grigorov 
wrote:

> HI Maxim,
>
> This will lead to a big API break.
> If we change this signature then we will have to change many more to keep
> it consistent, and this will lead to a lot of work for the application
> developers to change AjaxRequestTarget with IPartialPageRequestHandler.
>

That's exactly the point I am worrying about... All signatures have to be
checked to see whether or not it's an AjaxRequestTarget usage only or a
method that can works with websockets too (and then change the signature to
IPartialPageRequestHandler)... With the same idea,
IListener/AbstractListener are part of ART. But #add(Component...) is part
of IPartialPageRequestHandler, so adding a component via websocket will not
trigger IListener#onBeforeRespond (1) ? This would probably lead to some
unexpected behaviors, like for instance in Wicket jQuery UI where there is
a "DestroyListener" (which handles the jquery #destroy of the widget)...

Am I accurate on the analysis or did I missed a point?

Thanks & best regards,
Sebastien.

(1) actually I never double checked this is the case, but on the
principle/theoretically I guess it should be...



>
> We may need to make this change for Wicket 8.x if there are many users
> wanting this change, but for now I'd suggest you to create an adapter.
>
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik 
> wrote:
>
>> Hello Martin,
>>
>> I guess following method need to be additionally updated:
>>
>> org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer
>>
>> On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov 
>> wrote:
>>
>> > The change is rather big:
>> >
>> >
>> https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af
>> > I guess many other methods will need to be changed too if one needs to
>> use
>> > them with WebSocket.
>> > The improvement in the Wicket API looked so innocent ...
>> >
>> > Martin Grigorov
>> > Freelancer. Available for hire!
>> > Wicket Training and Consulting
>> > https://twitter.com/mtgrigorov
>> >
>>
>

Re: Wicket7: MediaComponent and Source classes

[Sven Meier]

Hi,

that change seems to have a hight impact - sorry, I didn't think of 
these implications.


> But #add(Component...) is part of IPartialPageRequestHandler
> so adding a component via websocket will not trigger 
IListener#onBeforeRespond


WebSockerRequestHandler#addListener() was a noop previously, so we don't 
lose anything here


>I guess following method need to be additionally updated:
>org.apache.wicket.ajax.AbstractAjaxTimerBehavior#onTimer

Why, an Ajax timer is triggered by Ajax calls only, isn't it?

AbstractAjaxTimerBehavior#restart() and #stop() could be invoked from a 
WebSocket request though.


>All signatures have to be checked ... AjaxRequestTarget or ... 
IPartialPageRequestHandler


I checked Wicket's code for methods that take ART as argument and having 
a name which doesn't start with an 'on'-prefix:
There are the two methods above and ModalWindow#show() and #close() that 
should be changed to IPartialPageRequestHandler. These are backwards 
compatible changes actually.


There are half a dozen calls to #find(AjaxRequestTarget.class) in Wicket 
classes which should switch from ART to IPartialPageRequestHandler, to 
restore cooperation with WebSockets.


But it seems in wicket-jquery-ui there are more methods of this kind?

Regards
Sven


On 08.07.2015 21:30, Sebastien wrote:

Hi,

Sorry, little bit late on the topic...

On Fri, Jul 3, 2015 at 7:38 AM, Martin Grigorov 
wrote:


HI Maxim,

This will lead to a big API break.
If we change this signature then we will have to change many more to keep
it consistent, and this will lead to a lot of work for the application
developers to change AjaxRequestTarget with IPartialPageRequestHandler.


That's exactly the point I am worrying about... All signatures have to be
checked to see whether or not it's an AjaxRequestTarget usage only or a
method that can works with websockets too (and then change the signature to
IPartialPageRequestHandler)... With the same idea,
IListener/AbstractListener are part of ART. But #add(Component...) is part
of IPartialPageRequestHandler, so adding a component via websocket will not
trigger IListener#onBeforeRespond (1) ? This would probably lead to some
unexpected behaviors, like for instance in Wicket jQuery UI where there is
a "DestroyListener" (which handles the jquery #destroy of the widget)...

Am I accurate on the analysis or did I missed a point?

Thanks & best regards,
Sebastien.

(1) actually I never double checked this is the case, but on the
principle/theoretically I guess it should be...




We may need to make this change for Wicket 8.x if there are many users
wanting this change, but for now I'd suggest you to create an adapter.

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Fri, Jul 3, 2015 at 7:46 AM, Maxim Solodovnik 
wrote:


Hello Martin,

I guess following method need to be additionally updated:

org.apache.wicket.ajax.AbstractAjaxTimerBehavior.onTimer

On Thu, Jul 2, 2015 at 6:11 PM, Martin Grigorov 
wrote:


The change is rather big:



https://github.com/sebfz1/wicket-jquery-ui/commit/e94f89d8f07f2b1af2b327a4aaec5ddd4b1400af

I guess many other methods will need to be changed too if one needs to

use

them with WebSocket.
The improvement in the Wicket API looked so innocent ...

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov




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

Re: I'm back from the wilderness!!!

[Martijn Dashorst]

And soon you can start your migration to Wicket 7! Party hats on!

Martijn

On Wed, Jul 8, 2015 at 5:25 PM, shetc  wrote:
> About to start working on a new project using Wicket 6.20 . After being taken
> over by another company, I have been doing integration work and supporting
> legacy Wicket-based apps (4.0 or less). Also new C# projects. We are finally
> back on track so this is a welcome return to Wicket sensibility.
>
> --
> View this message in context: 
> http://apache-wicket.1842946.n4.nabble.com/I-m-back-from-the-wilderness-tp4671545.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
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: Wicket7: MediaComponent and Source classes

[Sebastien]

Hi Sven,


> But it seems in wicket-jquery-ui there are more methods of this kind?
>
>
True, about 85 methods (taking an ART without starting with "on"-prefix).
In these, I should identify the ones that should be changed (like #open,
#close, #show, #hide, #refresh, etc), the others, plus 2 calls to
#find(ART.class) to be taken into account...
This is a new change since -M6 and we are very (very) close to release
7.0.0, that's why I am a little bit concerned (did I wrote "worried"
previously? ;)). I hope I/we do not miss/forget something here...

Thanks & best regards,
Sebastien.

How to stop event propagation?

[gump lee]

Hello All,

I am using Wicket 6.19. I added a AjaxFormComponentUpdatingBehavior("keypress")
to a textfield so that when press any key will trigger my application to
update something. I want this only happen when user press 'Enter' key. so
that I override the method updateAjaxAttributes in the
AjaxFormComponentUpdatingBehavior

@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
super.updateAjaxAttributes(attributes);
AjaxCallListener myAjaxCallListener = new AjaxCallListener() {
@Override
public CharSequence getPrecondition(Component component) {
String script = "var keycode = Wicket.Event.keyCode(attrs.event);"
+ "if (keycode == 13) {"
+ "return true;"
+ "} else {" + "return false;}";

return script;
}
};
attributes.getAjaxCallListeners().add(myAjaxCallListener);
attributes.setEventPropagation(EventPropagation.STOP);
}

However, after the ajax call, the form submit also triggered. Does anyone
know the correct way to stop this form submit?


Thanks and best regards,
Gump

Re: How to stop event propagation?

[Martin Grigorov]

Hi,

You need to register the AjaxCallListener:
attributes.getAjaxCallListeners().add(myAjaxCallListener)

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Jul 9, 2015 at 5:11 AM, gump lee  wrote:

> Hello All,
>
> I am using Wicket 6.19. I added a
> AjaxFormComponentUpdatingBehavior("keypress")
> to a textfield so that when press any key will trigger my application to
> update something. I want this only happen when user press 'Enter' key. so
> that I override the method updateAjaxAttributes in the
> AjaxFormComponentUpdatingBehavior
>
> @Override
> protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
> super.updateAjaxAttributes(attributes);
> AjaxCallListener myAjaxCallListener = new AjaxCallListener() {
> @Override
> public CharSequence getPrecondition(Component component) {
> String script = "var keycode = Wicket.Event.keyCode(attrs.event);"
> + "if (keycode == 13) {"
> + "return true;"
> + "} else {" + "return false;}";
>
> return script;
> }
> };
> attributes.getAjaxCallListeners().add(myAjaxCallListener);
> attributes.setEventPropagation(EventPropagation.STOP);
> }
>
> However, after the ajax call, the form submit also triggered. Does anyone
> know the correct way to stop this form submit?
>
>
> Thanks and best regards,
> Gump
>

Re: How to stop event propagation?

[gump lee]

Thanks,

Actually I did it. refer to my attached code, I register my
AjaxcallListener. Did I register the AjaxCallListener correctly?

On Thu, Jul 9, 2015 at 2:23 PM, Martin Grigorov 
wrote:

> Hi,
>
> You need to register the AjaxCallListener:
> attributes.getAjaxCallListeners().add(myAjaxCallListener)
>
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Jul 9, 2015 at 5:11 AM, gump lee  wrote:
>
> > Hello All,
> >
> > I am using Wicket 6.19. I added a
> > AjaxFormComponentUpdatingBehavior("keypress")
> > to a textfield so that when press any key will trigger my application to
> > update something. I want this only happen when user press 'Enter' key. so
> > that I override the method updateAjaxAttributes in the
> > AjaxFormComponentUpdatingBehavior
> >
> > @Override
> > protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
> > super.updateAjaxAttributes(attributes);
> > AjaxCallListener myAjaxCallListener = new AjaxCallListener() {
> > @Override
> > public CharSequence getPrecondition(Component component) {
> > String script = "var keycode = Wicket.Event.keyCode(attrs.event);"
> > + "if (keycode == 13) {"
> > + "return true;"
> > + "} else {" + "return false;}";
> >
> > return script;
> > }
> > };
> > attributes.getAjaxCallListeners().add(myAjaxCallListener);
> > attributes.setEventPropagation(EventPropagation.STOP);
> > }
> >
> > However, after the ajax call, the form submit also triggered. Does anyone
> > know the correct way to stop this form submit?
> >
> >
> > Thanks and best regards,
> > Gump
> >
>

Re: How to stop event propagation?

[Martin Grigorov]

There is no attachment in both of your mails.
I don't see this line in your first message.

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Jul 9, 2015 at 9:42 AM, gump lee  wrote:

> Thanks,
>
> Actually I did it. refer to my attached code, I register my
> AjaxcallListener. Did I register the AjaxCallListener correctly?
>
> On Thu, Jul 9, 2015 at 2:23 PM, Martin Grigorov 
> wrote:
>
> > Hi,
> >
> > You need to register the AjaxCallListener:
> > attributes.getAjaxCallListeners().add(myAjaxCallListener)
> >
> > Martin Grigorov
> > Freelancer. Available for hire!
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Thu, Jul 9, 2015 at 5:11 AM, gump lee  wrote:
> >
> > > Hello All,
> > >
> > > I am using Wicket 6.19. I added a
> > > AjaxFormComponentUpdatingBehavior("keypress")
> > > to a textfield so that when press any key will trigger my application
> to
> > > update something. I want this only happen when user press 'Enter' key.
> so
> > > that I override the method updateAjaxAttributes in the
> > > AjaxFormComponentUpdatingBehavior
> > >
> > > @Override
> > > protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
> > > super.updateAjaxAttributes(attributes);
> > > AjaxCallListener myAjaxCallListener = new AjaxCallListener() {
> > > @Override
> > > public CharSequence getPrecondition(Component component) {
> > > String script = "var keycode = Wicket.Event.keyCode(attrs.event);"
> > > + "if (keycode == 13) {"
> > > + "return true;"
> > > + "} else {" + "return false;}";
> > >
> > > return script;
> > > }
> > > };
> > > attributes.getAjaxCallListeners().add(myAjaxCallListener);
> > > attributes.setEventPropagation(EventPropagation.STOP);
> > > }
> > >
> > > However, after the ajax call, the form submit also triggered. Does
> anyone
> > > know the correct way to stop this form submit?
> > >
> > >
> > > Thanks and best regards,
> > > Gump
> > >
> >
>