Re: Image based on external url model object

[Maxim Solodovnik]

unfortunately I was unable to test it or participate in discussion :(
will try it in next available snapshot :)

On Tue, Dec 1, 2015 at 2:17 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

> Hi Martin :-D,
>
> and here it is:
>
> https://github.com/apache/wicket/pull/143
>
> kind regards
>
> Tobias
>
> Am 30.11.15 um 21:00 schrieb Martin Grigorov:
>
> Hi,
>>
>> On Nov 30, 2015 4:21 PM, "Sebastien"  wrote:
>>
>>> Hi Tobias,
>>>
>>> As I stated, I would prefer 2 different models so :
>>> - the main model is used for "src"
>>> - the model is not itself an array of models (I don't recall there is a
>>> such case elsewhere in Wicket)
>>> - it is easier to handle the CPM case
>>>
>>> As the other devs are now back from week-end, it would be nice to have
>>>
>> some
>>
>>> other opinions! :)
>>>
>> I usually wait for the PR to be able to comment on the changes.
>>
>>
>>>
>> https://github.com/klopfdreh/wicket-components-playground/blob/master/wicket-components-playground/src/main/java/org/apache/wicket/markup/html/image/ExternalImage.java
>>
>> There is no commenting functionality in such links.
>>
>> I could comment on the original commits but:
>> 1) I have to find them
>> 2) no one else (but Tobias) will see my comments
>>
>> Thanks & best regards,
>>> Sebastien.
>>>
>>>
>>> On Sat, Nov 28, 2015 at 8:10 AM, Tobias Soloschenko <
>>> tobiassolosche...@googlemail.com> wrote:
>>>
>>> Hi Sebastien,

 thanks for testing :-)

 I thought it would be nice to get all models by the default WebComponent
 method and that they are all stored as defaultmodelobject.

 WDTY?

 Anyway it would safe 2 methods.

 kind regards

 Tobias


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


-- 
WBR
Maxim aka solomax

jsession id in url

[Lois GreeneHernandez]

Hi All,

I was tasked with modifying a wicket6/glassfish4 application so that the 
session id changes as soon as a user logs in.  This is to avoid the problem of 
Session Fixation.  I used the replaceSession() method (from the wicket Session 
class), which does a destroy(); and a bind();.  replaceSession().  It seem to 
do the trick as the session id does indeed change.  The problem is that now we 
see a jsessionid in the url everytime we initially log on.  The id goes away 
after you log in and only appears on the initial launch.

My question is, is there a way to ensure that no jessionid appears in the url 
AND that the session id changes?  Any advice would be greatly appreciated.

Thanks

Lois

Re: jsession id in url

[Sven Meier]

Hi,

did you configure Tomcat to not use jsessionid?

http://stackoverflow.com/questions/962729/is-it-possible-to-disable-jsessionid-in-tomcat-servlet

Regards
Sven

On 04.12.2015 17:03, Lois GreeneHernandez wrote:

Hi All,

I was tasked with modifying a wicket6/glassfish4 application so that the 
session id changes as soon as a user logs in.  This is to avoid the problem of 
Session Fixation.  I used the replaceSession() method (from the wicket Session 
class), which does a destroy(); and a bind();.  replaceSession().  It seem to 
do the trick as the session id does indeed change.  The problem is that now we 
see a jsessionid in the url everytime we initially log on.  The id goes away 
after you log in and only appears on the initial launch.

My question is, is there a way to ensure that no jessionid appears in the url 
AND that the session id changes?  Any advice would be greatly appreciated.

Thanks

Lois




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

Re: AjaxIndicatingButton

[Mihir Chhaya]

Hi,

As you have mentioned target.addComponent(comp), it seems you are using
Wicket 1.4. Just so that it might be helpful to you; Wicket 1.4 is no
longer supported - does not mean that you won't get answers from forum but
there won't be any release for 1.4 version (I am writing this based upon
online Wicket version status - so please take it as suggestion).

If I am understanding it correctly, all you want is disable two other
buttons on submit of 'this' button. And as by design; Wicket needs the
component to be added for ajax change via target.addComponent. Which should
take effect immediately.

I might be wrong in my suggestion as your scenario needs more details for
better understanding.

-Mihir.

On Fri, Dec 4, 2015 at 3:28 PM, sorinev  wrote:

> I have a dialog with 3 AjaxIndicatingButtons on it. When I override
> onSubmit(), I can disable the 'this' component in real time
> (this.setEnabled(false)), but traditionally, any other component that gets
> modified has to do target.addComponent(comp) and then wait for the
> onSubmit() to return in order for it to take effect.
>
> However, I really need to have all three buttons be disabled immediately if
> *any* button is actively inside it's onSubmit() function (being re-enabled
> when the function returns is ok). Is this possible?
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874.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: jsession id in url

[Martin Grigorov]

web.xml
On Dec 4, 2015 8:20 PM, "Lois GreeneHernandez" 
wrote:

> Thanks Martin for your response,
>
> I have a question, does this code go into web.xml or sun-web.xml or is
> there another xml that I need to create.  I know that one can have a
> glassfish.*.xml but we don't have that in our set up.
>
> Please advise.
>
> Thanks in advance for all of your help.
>
> Lois
>
> -Original Message-
> From: Martin Grigorov [mailto:mgrigo...@apache.org]
> Sent: Friday, December 04, 2015 1:11 PM
> To: users@wicket.apache.org
> Subject: Re: jsession id in url
>
> Hi,
>
> See the Tomcat 7/8 hint at the bottom. GF4 should support that already.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Fri, Dec 4, 2015 at 8:02 PM, Lois GreeneHernandez <
> lgreenehernan...@knoa.com> wrote:
>
> > Actually we're using glassfish 4 and it's a good question, but I don't
> > know if we configured it to not use jsessionid?  I'll research that.
> >
> > Thanks for your input.
> >
> > Lois
> >
> > -Original Message-
> > From: Sven Meier [mailto:s...@meiers.net]
> > Sent: Friday, December 04, 2015 12:43 PM
> > To: users@wicket.apache.org
> > Subject: Re: jsession id in url
> >
> > Hi,
> >
> > did you configure Tomcat to not use jsessionid?
> >
> >
> > http://stackoverflow.com/questions/962729/is-it-possible-to-disable-js
> > essionid-in-tomcat-servlet
> >
> > Regards
> > Sven
> >
> > On 04.12.2015 17:03, Lois GreeneHernandez wrote:
> > > Hi All,
> > >
> > > I was tasked with modifying a wicket6/glassfish4 application so that
> > > the
> > session id changes as soon as a user logs in.  This is to avoid the
> > problem of Session Fixation.  I used the replaceSession() method (from
> > the wicket Session class), which does a destroy(); and a bind();.
> replaceSession().
> > It seem to do the trick as the session id does indeed change.  The
> > problem is that now we see a jsessionid in the url everytime we
> initially log on.
> > The id goes away after you log in and only appears on the initial launch.
> > >
> > > My question is, is there a way to ensure that no jessionid appears
> > > in
> > the url AND that the session id changes?  Any advice would be greatly
> > appreciated.
> > >
> > > Thanks
> > >
> > > Lois
> > >
> > >
> >
> > -
> > 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
> >
> >
>

AjaxIndicatingButton

[sorinev]

I have a dialog with 3 AjaxIndicatingButtons on it. When I override
onSubmit(), I can disable the 'this' component in real time
(this.setEnabled(false)), but traditionally, any other component that gets
modified has to do target.addComponent(comp) and then wait for the
onSubmit() to return in order for it to take effect.

However, I really need to have all three buttons be disabled immediately if
*any* button is actively inside it's onSubmit() function (being re-enabled
when the function returns is ok). Is this possible? 

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874.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: AjaxIndicatingButton

[sorinev]

Yes, it's Wicket 1.4.17. I've thought about migrating it to one of the more
recent versions. But with 41k lines of java across 225 files just in the
Wicket portion of our enterprise application, it'll be a major pain to
migrate considering there were several enormous changes to certain
components/functionality that we use a lot. Believe me, it does kill me that
we are on a version that is so old. 

As for the disabling thing, more specifically I wanted to be able to do
something like this:

protected void onSubmit(AjaxRequestTarget target, Form form){
this.setEnabled(false);
//disable button 2 here
//disable button 3 here

//do a bunch of stuff here

//enable button 3 here
//enable button 2 here
this.setEnabled(true);
}

Meaning, I'd like the effect to happen immediately, without having to do
target.addComponent() and without having to wait for onSubmit() to return
(since it would be pointless to disable and re-enable after I've already
finished the work). Basically, the user needs to not be able to use any
other buttons while some other button's code is busy in onSubmit().
mihir wrote
> Hi,
> 
> As you have mentioned target.addComponent(comp), it seems you are using
> Wicket 1.4. Just so that it might be helpful to you; Wicket 1.4 is no
> longer supported - does not mean that you won't get answers from forum but
> there won't be any release for 1.4 version (I am writing this based upon
> online Wicket version status - so please take it as suggestion).
> 
> If I am understanding it correctly, all you want is disable two other
> buttons on submit of 'this' button. And as by design; Wicket needs the
> component to be added for ajax change via target.addComponent. Which
> should
> take effect immediately.
> 
> I might be wrong in my suggestion as your scenario needs more details for
> better understanding.
> 
> -Mihir.
> 
> On Fri, Dec 4, 2015 at 3:28 PM, sorinev 

> sorinev@

>  wrote:
> 
>> I have a dialog with 3 AjaxIndicatingButtons on it. When I override
>> onSubmit(), I can disable the 'this' component in real time
>> (this.setEnabled(false)), but traditionally, any other component that
>> gets
>> modified has to do target.addComponent(comp) and then wait for the
>> onSubmit() to return in order for it to take effect.
>>
>> However, I really need to have all three buttons be disabled immediately
>> if
>> *any* button is actively inside it's onSubmit() function (being
>> re-enabled
>> when the function returns is ok). Is this possible?
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
>>



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874p4672877.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: behavior passing components during construction

[Sebastien]

Hi, see #bind()

Re: AjaxIndicatingButton

[Mihir Chhaya]

You could something like below:

   final AjaxButton testButton1 = new AjaxButton("test1"){

/**
*
*/
   private static final long serialVersionUID = 1L;

   @Override
protected void onSubmit(AjaxRequestTarget target, Form form)
{

 target.appendJavascript("document.getElementById('tb2').disabled=true;");

 target.appendJavascript("document.getElementById('tb3').disabled=true;");
}
};

testButton1.setMarkupId("tb1");
testButton1.setOutputMarkupId(true);

final Button testButton2 = new Button("test2");
testButton2.setMarkupId("tb2");
testButton2.setOutputMarkupId(true);

final Button testButton3 = new Button("test3");
testButton3.setMarkupId("tb3");
testButton3.setOutputMarkupId(true);

Thanks,
-Mihir.

On Fri, Dec 4, 2015 at 4:32 PM, sorinev  wrote:

> Yes, it's Wicket 1.4.17. I've thought about migrating it to one of the more
> recent versions. But with 41k lines of java across 225 files just in the
> Wicket portion of our enterprise application, it'll be a major pain to
> migrate considering there were several enormous changes to certain
> components/functionality that we use a lot. Believe me, it does kill me
> that
> we are on a version that is so old.
>
> As for the disabling thing, more specifically I wanted to be able to do
> something like this:
>
> protected void onSubmit(AjaxRequestTarget target, Form form){
> this.setEnabled(false);
> //disable button 2 here
> //disable button 3 here
>
> //do a bunch of stuff here
>
> //enable button 3 here
> //enable button 2 here
> this.setEnabled(true);
> }
>
> Meaning, I'd like the effect to happen immediately, without having to do
> target.addComponent() and without having to wait for onSubmit() to return
> (since it would be pointless to disable and re-enable after I've already
> finished the work). Basically, the user needs to not be able to use any
> other buttons while some other button's code is busy in onSubmit().
> mihir wrote
> > Hi,
> >
> > As you have mentioned target.addComponent(comp), it seems you are using
> > Wicket 1.4. Just so that it might be helpful to you; Wicket 1.4 is no
> > longer supported - does not mean that you won't get answers from forum
> but
> > there won't be any release for 1.4 version (I am writing this based upon
> > online Wicket version status - so please take it as suggestion).
> >
> > If I am understanding it correctly, all you want is disable two other
> > buttons on submit of 'this' button. And as by design; Wicket needs the
> > component to be added for ajax change via target.addComponent. Which
> > should
> > take effect immediately.
> >
> > I might be wrong in my suggestion as your scenario needs more details for
> > better understanding.
> >
> > -Mihir.
> >
> > On Fri, Dec 4, 2015 at 3:28 PM, sorinev 
>
> > sorinev@
>
> >  wrote:
> >
> >> I have a dialog with 3 AjaxIndicatingButtons on it. When I override
> >> onSubmit(), I can disable the 'this' component in real time
> >> (this.setEnabled(false)), but traditionally, any other component that
> >> gets
> >> modified has to do target.addComponent(comp) and then wait for the
> >> onSubmit() to return in order for it to take effect.
> >>
> >> However, I really need to have all three buttons be disabled immediately
> >> if
> >> *any* button is actively inside it's onSubmit() function (being
> >> re-enabled
> >> when the function returns is ok). Is this possible?
> >>
> >> --
> >> View this message in context:
> >>
> http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874.html
> >> Sent from the Users forum mailing list archive at Nabble.com.
> >>
> >> -
> >> To unsubscribe, e-mail:
>
> > users-unsubscribe@.apache
>
> >> For additional commands, e-mail:
>
> > users-help@.apache
>
> >>
> >>
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874p4672877.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: AjaxIndicatingButton

[sorinev]

I gave that a shot but it didn't seem to work. It still did the disabling
after onSubmit() returned. I'm not going to worry about it at this point, I
just thought it'd be better to do it. 

Thanks for your assistance mihir. 


mihir wrote
> You could something like below:
> 
>final AjaxButton testButton1 = new AjaxButton("test1"){
> 
> /**
> *
> */
>private static final long serialVersionUID = 1L;
> 
>@Override
> protected void onSubmit(AjaxRequestTarget target, Form
> form)
> {
> 
>  target.appendJavascript("document.getElementById('tb2').disabled=true;");
> 
>  target.appendJavascript("document.getElementById('tb3').disabled=true;");
> }
> };
> 
> testButton1.setMarkupId("tb1");
> testButton1.setOutputMarkupId(true);
> 
> final Button testButton2 = new Button("test2");
> testButton2.setMarkupId("tb2");
> testButton2.setOutputMarkupId(true);
> 
> final Button testButton3 = new Button("test3");
> testButton3.setMarkupId("tb3");
> testButton3.setOutputMarkupId(true);
> 
> Thanks,
> -Mihir.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874p4672879.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: AjaxIndicatingButton

[Martin Grigorov]

Hi,

You need to disable the button with JavaScript just before its Ajax call is
made and re-enable it in the success/failure JS callbacks.
I don't remember how to do the first... For the latter you have to override
some extra methods. Check the API.
On Dec 5, 2015 1:54 AM, "sorinev"  wrote:

> I gave that a shot but it didn't seem to work. It still did the disabling
> after onSubmit() returned. I'm not going to worry about it at this point, I
> just thought it'd be better to do it.
>
> Thanks for your assistance mihir.
>
>
> mihir wrote
> > You could something like below:
> >
> >final AjaxButton testButton1 = new AjaxButton("test1"){
> >
> > /**
> > *
> > */
> >private static final long serialVersionUID = 1L;
> >
> >@Override
> > protected void onSubmit(AjaxRequestTarget target, Form
> > form)
> > {
> >
> >
> target.appendJavascript("document.getElementById('tb2').disabled=true;");
> >
> >
> target.appendJavascript("document.getElementById('tb3').disabled=true;");
> > }
> > };
> >
> > testButton1.setMarkupId("tb1");
> > testButton1.setOutputMarkupId(true);
> >
> > final Button testButton2 = new Button("test2");
> > testButton2.setMarkupId("tb2");
> > testButton2.setOutputMarkupId(true);
> >
> > final Button testButton3 = new Button("test3");
> > testButton3.setMarkupId("tb3");
> > testButton3.setOutputMarkupId(true);
> >
> > Thanks,
> > -Mihir.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/AjaxIndicatingButton-tp4672874p4672879.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: jsession id in url

[Martin Grigorov]

Hi,

See the Tomcat 7/8 hint at the bottom. GF4 should support that already.

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

On Fri, Dec 4, 2015 at 8:02 PM, Lois GreeneHernandez <
lgreenehernan...@knoa.com> wrote:

> Actually we're using glassfish 4 and it's a good question, but I don't
> know if we configured it to not use jsessionid?  I'll research that.
>
> Thanks for your input.
>
> Lois
>
> -Original Message-
> From: Sven Meier [mailto:s...@meiers.net]
> Sent: Friday, December 04, 2015 12:43 PM
> To: users@wicket.apache.org
> Subject: Re: jsession id in url
>
> Hi,
>
> did you configure Tomcat to not use jsessionid?
>
>
> http://stackoverflow.com/questions/962729/is-it-possible-to-disable-jsessionid-in-tomcat-servlet
>
> Regards
> Sven
>
> On 04.12.2015 17:03, Lois GreeneHernandez wrote:
> > Hi All,
> >
> > I was tasked with modifying a wicket6/glassfish4 application so that the
> session id changes as soon as a user logs in.  This is to avoid the problem
> of Session Fixation.  I used the replaceSession() method (from the wicket
> Session class), which does a destroy(); and a bind();.  replaceSession().
> It seem to do the trick as the session id does indeed change.  The problem
> is that now we see a jsessionid in the url everytime we initially log on.
> The id goes away after you log in and only appears on the initial launch.
> >
> > My question is, is there a way to ensure that no jessionid appears in
> the url AND that the session id changes?  Any advice would be greatly
> appreciated.
> >
> > Thanks
> >
> > Lois
> >
> >
>
> -
> 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: jsession id in url

[Lois GreeneHernandez]

Thanks Martin for your response, 

I have a question, does this code go into web.xml or sun-web.xml or is there 
another xml that I need to create.  I know that one can have a glassfish.*.xml 
but we don't have that in our set up.  

Please advise. 

Thanks in advance for all of your help. 

Lois

-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org] 
Sent: Friday, December 04, 2015 1:11 PM
To: users@wicket.apache.org
Subject: Re: jsession id in url

Hi,

See the Tomcat 7/8 hint at the bottom. GF4 should support that already.

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

On Fri, Dec 4, 2015 at 8:02 PM, Lois GreeneHernandez < 
lgreenehernan...@knoa.com> wrote:

> Actually we're using glassfish 4 and it's a good question, but I don't 
> know if we configured it to not use jsessionid?  I'll research that.
>
> Thanks for your input.
>
> Lois
>
> -Original Message-
> From: Sven Meier [mailto:s...@meiers.net]
> Sent: Friday, December 04, 2015 12:43 PM
> To: users@wicket.apache.org
> Subject: Re: jsession id in url
>
> Hi,
>
> did you configure Tomcat to not use jsessionid?
>
>
> http://stackoverflow.com/questions/962729/is-it-possible-to-disable-js
> essionid-in-tomcat-servlet
>
> Regards
> Sven
>
> On 04.12.2015 17:03, Lois GreeneHernandez wrote:
> > Hi All,
> >
> > I was tasked with modifying a wicket6/glassfish4 application so that 
> > the
> session id changes as soon as a user logs in.  This is to avoid the 
> problem of Session Fixation.  I used the replaceSession() method (from 
> the wicket Session class), which does a destroy(); and a bind();.  
> replaceSession().
> It seem to do the trick as the session id does indeed change.  The 
> problem is that now we see a jsessionid in the url everytime we initially log 
> on.
> The id goes away after you log in and only appears on the initial launch.
> >
> > My question is, is there a way to ensure that no jessionid appears 
> > in
> the url AND that the session id changes?  Any advice would be greatly 
> appreciated.
> >
> > Thanks
> >
> > Lois
> >
> >
>
> -
> 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: jsession id in url

[Lois GreeneHernandez]

Actually we're using glassfish 4 and it's a good question, but I don't know if 
we configured it to not use jsessionid?  I'll research that. 

Thanks for your input. 

Lois

-Original Message-
From: Sven Meier [mailto:s...@meiers.net] 
Sent: Friday, December 04, 2015 12:43 PM
To: users@wicket.apache.org
Subject: Re: jsession id in url

Hi,

did you configure Tomcat to not use jsessionid?

http://stackoverflow.com/questions/962729/is-it-possible-to-disable-jsessionid-in-tomcat-servlet

Regards
Sven

On 04.12.2015 17:03, Lois GreeneHernandez wrote:
> Hi All,
>
> I was tasked with modifying a wicket6/glassfish4 application so that the 
> session id changes as soon as a user logs in.  This is to avoid the problem 
> of Session Fixation.  I used the replaceSession() method (from the wicket 
> Session class), which does a destroy(); and a bind();.  replaceSession().  It 
> seem to do the trick as the session id does indeed change.  The problem is 
> that now we see a jsessionid in the url everytime we initially log on.  The 
> id goes away after you log in and only appears on the initial launch.
>
> My question is, is there a way to ensure that no jessionid appears in the url 
> AND that the session id changes?  Any advice would be greatly appreciated.
>
> Thanks
>
> Lois
>
>

-
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: Image based on external url model object

[Tobias Soloschenko]

Hi Maxim,

it should be available within the next SNAPSHOT. I pushed the 
corresponding commits to master and to wicket-7.x, now.


ExternalImage and ExternalSource.

Here are some examples:

https://github.com/apache/wicket/blob/master/wicket-core/src/test/java/org/apache/wicket/markup/html/image/ExternalImageTestPage.java

kind regards

Tobias

Am 04.12.15 um 16:08 schrieb Maxim Solodovnik:

unfortunately I was unable to test it or participate in discussion :(
will try it in next available snapshot :)

On Tue, Dec 1, 2015 at 2:17 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:


Hi Martin :-D,

and here it is:

https://github.com/apache/wicket/pull/143

kind regards

Tobias

Am 30.11.15 um 21:00 schrieb Martin Grigorov:

Hi,

On Nov 30, 2015 4:21 PM, "Sebastien"  wrote:


Hi Tobias,

As I stated, I would prefer 2 different models so :
- the main model is used for "src"
- the model is not itself an array of models (I don't recall there is a
such case elsewhere in Wicket)
- it is easier to handle the CPM case

As the other devs are now back from week-end, it would be nice to have


some


other opinions! :)


I usually wait for the PR to be able to comment on the changes.


https://github.com/klopfdreh/wicket-components-playground/blob/master/wicket-components-playground/src/main/java/org/apache/wicket/markup/html/image/ExternalImage.java

There is no commenting functionality in such links.

I could comment on the original commits but:
1) I have to find them
2) no one else (but Tobias) will see my comments

Thanks & best regards,

Sebastien.


On Sat, Nov 28, 2015 at 8:10 AM, Tobias Soloschenko <
tobiassolosche...@googlemail.com> wrote:

Hi Sebastien,

thanks for testing :-)

I thought it would be nice to get all models by the default WebComponent
method and that they are all stored as defaultmodelobject.

WDTY?

Anyway it would safe 2 methods.

kind regards

Tobias



-
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

behavior passing components during construction

[Ronny Pscheidl]

hello,
i want to write an collapsebehavior based on bootstrap collapse (
http://getbootstrap.com/javascript/#collapse). so you have an icon or
button or waht else which will toggle a container. both components are
independent added to the page or panel.

example:

public class CollapseBehavior extends Behavior {
   private final IModel targetMarkupId;

   public CollapseBehavior(Component target) {
  target.setOutputMarkupId(true);
  target.add(new CssClassAppender("collapse"));
  targetMarkupId = target.getOutputMarkupId();
   }
}


public class HomePage extends WebPage {
   public HomePage() {
  Button collapse = new Button("button");
  WebMarkupContainer target = new WebMarkupContainer("body");
  collapse.add(new CollapseBehavior(target));
  add(collapse);
  add(target);
   }
}

wicket guide says do not pass components during construction. Is there a
better way?

regards

john.j.cool