Re: In Wicket 1.5, How to get a modified value from a Panel to Page?

[Martin Grigorov]

Honestly, I have no idea what you are talking about.
Sorry but I cannot help you.

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

On Mon, Feb 15, 2016 at 10:13 PM, durairaj t  wrote:

> Hi Martin -
>
>
>  In the below code snippet; (Line # 6) textFieldID.isModified()from the
> TestPanel object is always returning default value as "false" at run time
> in the TestWebPage, but I'm modifying the boolean value as "true" at
> runtime in the TestPanel. It should return the modified value in the
> TestWebPage.
>
> it is working in 1.4, but not in 1.5.
>
>
>
> *TestWebPage.java:*
>
> 1. TestWebPage extends WebPage{
>
> 2. TestPanel textFieldID = *new* TestPanel(“textFieldID
> ”,modelObject,arrayList1,arrayList2,0,100,this);
>
> 3.   moduleForm.addComponent(textFieldID,FlagsEnum.*enCoutiesId*, w
> ebMarkupContainer);
>
> 4. // some other code here
>
> 5. //following code returns default value always at run time.
>
> 6. textFieldID.isModified(); //
>
> 7. }
>
>
>
>
> * TestPanel.java:*
>
>
>
> 1.  TestPanel extends Panel{
>
> 2.
>
> 3.  //some other instance variables
>
> 4.
>
> 5.  private boolean isModified=false;
>
> 6.
>
> 7.  //some other code here
>
> 8.
>
> 9.  *public* *boolean* isModified() {
>
> 10. *return* modified;
>
> 11. }
>
> 12.
>
> 13. }// closing class
>
>
> Following workarounds are working only in Pages and Inner classes,
>
> 1. TestPanel.this
> 2. getPageReference()
>
>
>
>
> Thanks.
>
> On Mon, Feb 15, 2016 at 3:19 PM, Martin Grigorov 
> wrote:
>
> > Hi,
> >
> > It is not very clear what you are trying to achieve.
> > Please re-phrase.
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Mon, Feb 15, 2016 at 8:54 PM, durairaj t 
> > wrote:
> >
> > >  I'm trying to get a modified Panel object in a Page,
> > >
> > >  I tried with "TestPage.this.getPageReference().getPage();" and
> > > "TestPanel.this" both are not working.
> > >
> > > I can use Session but have to get more than a modified values.
> > >
> > > Any help?
> > >
> > > Thanks.
> > >
> >
>

Re: In Wicket 1.5, How to get a modified value from a Panel to Page?

[durairaj t]

Hi Martin -


 In the below code snippet; (Line # 6) textFieldID.isModified()from the
TestPanel object is always returning default value as "false" at run time
in the TestWebPage, but I'm modifying the boolean value as "true" at
runtime in the TestPanel. It should return the modified value in the
TestWebPage.

it is working in 1.4, but not in 1.5.



*TestWebPage.java:*

1. TestWebPage extends WebPage{

2. TestPanel textFieldID = *new* TestPanel(“textFieldID
”,modelObject,arrayList1,arrayList2,0,100,this);

3.   moduleForm.addComponent(textFieldID,FlagsEnum.*enCoutiesId*, w
ebMarkupContainer);

4. // some other code here

5. //following code returns default value always at run time.

6. textFieldID.isModified(); //

7. }




* TestPanel.java:*



1.  TestPanel extends Panel{

2.

3.  //some other instance variables

4.

5.  private boolean isModified=false;

6.

7.  //some other code here

8.

9.  *public* *boolean* isModified() {

10. *return* modified;

11. }

12.

13. }// closing class


Following workarounds are working only in Pages and Inner classes,

1. TestPanel.this
2. getPageReference()




Thanks.

On Mon, Feb 15, 2016 at 3:19 PM, Martin Grigorov 
wrote:

> Hi,
>
> It is not very clear what you are trying to achieve.
> Please re-phrase.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Feb 15, 2016 at 8:54 PM, durairaj t 
> wrote:
>
> >  I'm trying to get a modified Panel object in a Page,
> >
> >  I tried with "TestPage.this.getPageReference().getPage();" and
> > "TestPanel.this" both are not working.
> >
> > I can use Session but have to get more than a modified values.
> >
> > Any help?
> >
> > Thanks.
> >
>

Re: In Wicket 1.5, How to get a modified value from a Panel to Page?

[Martin Grigorov]

Hi,

It is not very clear what you are trying to achieve.
Please re-phrase.

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

On Mon, Feb 15, 2016 at 8:54 PM, durairaj t  wrote:

>  I'm trying to get a modified Panel object in a Page,
>
>  I tried with "TestPage.this.getPageReference().getPage();" and
> "TestPanel.this" both are not working.
>
> I can use Session but have to get more than a modified values.
>
> Any help?
>
> Thanks.
>

In Wicket 1.5, How to get a modified value from a Panel to Page?

[durairaj t]

 I'm trying to get a modified Panel object in a Page,

 I tried with "TestPage.this.getPageReference().getPage();" and
"TestPanel.this" both are not working.

I can use Session but have to get more than a modified values.

Any help?

Thanks.

Re: why DCEVM is not supporting in JBOSS 6.1 configured in eclipse kepler

[Martin Grigorov]

Hi,

There is no single occurrence of "Wicket" in your email.
You should ask this question in JBoss forums.

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

On Mon, Feb 15, 2016 at 2:31 PM, suryapriya  wrote:

> I installed DCEVM-light-7u79-installer in my JDK1.7.0_45 then after we have
> made some configurations like -XXaltjvm=dcevm
> -javaagent:path\hotswap-agent.jar=autoHotswap=true in eclipse Run
> configurations -> VM Arguments path, standalone.bat,standalone.conf.bat
> file
> under bin in Jboss -server-6.2 version.
>
> I have configured my jboss in my eclipse under server JBoss EAP 6.1+
> Runtime
> Server configuration. I am facing the issue is if i start my server through
> command prompt it is hitting local properly, but when I start server
> through
> eclipse the DCEVM installation changes is not working properly and local
> url
> throwing JBWEB65: HTTP Status 500 - java.lang.NumberFormatException:
> null.
>
>
> Please suggest me any solutions for this
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/why-DCEVM-is-not-supporting-in-JBOSS-6-1-configured-in-eclipse-kepler-tp4673597.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: Question / Modular FormComponents / FormComponentPanels / AbstractFormValidator and problems with model updates

[Sven Meier]

Hi Patrick,

sorry for the confusion.

>Does this objection have any consequences for my implementation?

Wicket validates all values *before* they are written into the models.
So validators always validate the converted input only.

You have the following options:
- IValidator, validates the converted input of a single field
- IFormValidator, validates the converted input of multiple fields (but 
has to be attached to the form)
- FormComponentPanel, same as IFormValidator - pro: does not need to be 
added to form, cons: have to override convertInput() and/or updateModel()
- validate your domain objects after the models have been updated, e.g. 
from onClick().


Perhaps you create a quickstart, so we can make sure that we're talking 
about the same option.


Regards
Sven


On 15.02.2016 12:35, Patrick Davids wrote:

Hi Sven,

> Yes, the converted values haven't been written yet.

Does this objection have any consequences for my implementation?
For me, it semms it is working now... so I think, there is no need to 
me to additionally override


>  @Override
>  public void validate() {
>// validate nested convertedInput which is *not* yet written
>
>if (nestedFormComponent.getConvertedInput() ...) {
>  error(...);
>}
>  }

Should I pay any special attention for an unusual behavior?
Should I test a special case?
Whats the risk, leaving my impl. as it is?
Or am I quite save?

kind regards
Patrick

Am 12.02.2016 um 18:29 schrieb Sven Meier:

Hi again,

now I see what you meant:

Yes, the converted values haven't been written yet.
I was writing my example off the top of my head :). Validators won't
help here, you'll have to do validation by hand instead:

   PersonPanel extends FormComponentPanel {
 @Override
 protected void convertInput() {
   // converted input is just the current model object
   setConvertedInput(getModelObject();
 }

 @Override
 public void validate() {
   // validate nested convertedInput which is *not* yet written

   if (nestedFormComponent.getConvertedInput() ...) {
 error(...);
   }
 }

Regards
Sven


On 12.02.2016 18:17, Sven Meier wrote:

Hi Martin,

>The modelObject should be the one before the form submit,

it should be the same one which all nested formComponents are
changing. I can't think of a case where this shouldn't hold.

>Because Form#updateModels() is called after the conversion and
validations.
>By calling the line above you basically ignore the submitted 
parameters.


The containing 'normal' formComponents have written the parameters
into their models, which are changing properties of the 'main'
modelObject.

For the FormComponentPanel the following is a noop:
setConvertedInput(getModelObject());
...
updateModel();

I'm doing it this way, because the formComponentPanel hasn't anything
to convert actually, its model object stays the same.

Regards
Sven


On 12.02.2016 17:44, Martin Grigorov wrote:

Hi Sven,


On Fri, Feb 12, 2016 at 12:08 PM, Sven Meier  wrote:


Hi,


Is it a good idea to implement such a case extending
FormComponentPanel,

or is FormComponentPanel for other purposes?

usuallly a FormComponentPanel is used when you want to combine the
input
of several formComponents into a single model object, e.g.
MultiFileUploadField and DateTimeField.

But you can also use it for validation of whole model objects:

PersonPanel extends FormComponentPanel {
   protected void convertInput() {
 // converter input is just the current model object
 setConvertedInput(getModelObject();


The modelObject should be the one before the form submit, no? Because
Form#updateModels() is called after the conversion and validations.
By calling the line above you basically ignore the submitted 
parameters.

I am missing something in your idea. What is it?



   }
}

Form f = new Form(...);
PersonPanel personPanel = new PersonPanel(...)
personPanel.add(new XYValidator()); // <-- a validator that
validates the
'converted' person
f.add(personPanel);

Have fun
Sven




On 12.02.2016 11:17, Patrick Davids wrote:


Hi all,
I would like to implement some kind of modular form components.

So, a developer is able stick together a form to save e.g. person 
data
and adress data with different panels containing the particular 
needed

input fields (textfield, selectboxes etc).

Form f = new Form(...);
f.add(new PersonFormComponentPanel(...));
f.add(new AddressFormComponentPanel(...));

Both, PersonFormComponentPanel and AddressFormComponentPanel are
simple
panels, now, and it is working so far.

Now, I have a special use-case, which needs to add an
AbstractFormValidator to the form.

Not to bypass the inner required textfields validations of
PersonFormComponentPanel, I can implement
FormComponent[] getDependentFormComponents(){...}
of the AbstractFormValidator.

BUT, it requieres to return FormComponents, not simple panels.
So, my idea was, just changing the 

why DCEVM is not supporting in JBOSS 6.1 configured in eclipse kepler

[suryapriya]

I installed DCEVM-light-7u79-installer in my JDK1.7.0_45 then after we have
made some configurations like -XXaltjvm=dcevm
-javaagent:path\hotswap-agent.jar=autoHotswap=true in eclipse Run
configurations -> VM Arguments path, standalone.bat,standalone.conf.bat file
under bin in Jboss -server-6.2 version.

I have configured my jboss in my eclipse under server JBoss EAP 6.1+ Runtime
Server configuration. I am facing the issue is if i start my server through
command prompt it is hitting local properly, but when I start server through
eclipse the DCEVM installation changes is not working properly and local url
throwing JBWEB65: HTTP Status 500 - java.lang.NumberFormatException:
null. 


Please suggest me any solutions for this

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/why-DCEVM-is-not-supporting-in-JBOSS-6-1-configured-in-eclipse-kepler-tp4673597.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: Question / Modular FormComponents / FormComponentPanels / AbstractFormValidator and problems with model updates

[Patrick Davids]

Hi Sven,

> Yes, the converted values haven't been written yet.

Does this objection have any consequences for my implementation?
For me, it semms it is working now... so I think, there is no need to me 
to additionally override


>  @Override
>  public void validate() {
>// validate nested convertedInput which is *not* yet written
>
>if (nestedFormComponent.getConvertedInput() ...) {
>  error(...);
>}
>  }

Should I pay any special attention for an unusual behavior?
Should I test a special case?
Whats the risk, leaving my impl. as it is?
Or am I quite save?

kind regards
Patrick

Am 12.02.2016 um 18:29 schrieb Sven Meier:

Hi again,

now I see what you meant:

Yes, the converted values haven't been written yet.
I was writing my example off the top of my head :). Validators won't
help here, you'll have to do validation by hand instead:

   PersonPanel extends FormComponentPanel {
 @Override
 protected void convertInput() {
   // converted input is just the current model object
   setConvertedInput(getModelObject();
 }

 @Override
 public void validate() {
   // validate nested convertedInput which is *not* yet written

   if (nestedFormComponent.getConvertedInput() ...) {
 error(...);
   }
 }

Regards
Sven


On 12.02.2016 18:17, Sven Meier wrote:

Hi Martin,

>The modelObject should be the one before the form submit,

it should be the same one which all nested formComponents are
changing. I can't think of a case where this shouldn't hold.

>Because Form#updateModels() is called after the conversion and
validations.
>By calling the line above you basically ignore the submitted parameters.

The containing 'normal' formComponents have written the parameters
into their models, which are changing properties of the 'main'
modelObject.

For the FormComponentPanel the following is a noop:
setConvertedInput(getModelObject());
...
updateModel();

I'm doing it this way, because the formComponentPanel hasn't anything
to convert actually, its model object stays the same.

Regards
Sven


On 12.02.2016 17:44, Martin Grigorov wrote:

Hi Sven,


On Fri, Feb 12, 2016 at 12:08 PM, Sven Meier  wrote:


Hi,


Is it a good idea to implement such a case extending
FormComponentPanel,

or is FormComponentPanel for other purposes?

usuallly a FormComponentPanel is used when you want to combine the
input
of several formComponents into a single model object, e.g.
MultiFileUploadField and DateTimeField.

But you can also use it for validation of whole model objects:

PersonPanel extends FormComponentPanel {
   protected void convertInput() {
 // converter input is just the current model object
 setConvertedInput(getModelObject();


The modelObject should be the one before the form submit, no? Because
Form#updateModels() is called after the conversion and validations.
By calling the line above you basically ignore the submitted parameters.
I am missing something in your idea. What is it?



   }
}

Form f = new Form(...);
PersonPanel personPanel = new PersonPanel(...)
personPanel.add(new XYValidator()); // <-- a validator that
validates the
'converted' person
f.add(personPanel);

Have fun
Sven




On 12.02.2016 11:17, Patrick Davids wrote:


Hi all,
I would like to implement some kind of modular form components.

So, a developer is able stick together a form to save e.g. person data
and adress data with different panels containing the particular needed
input fields (textfield, selectboxes etc).

Form f = new Form(...);
f.add(new PersonFormComponentPanel(...));
f.add(new AddressFormComponentPanel(...));

Both, PersonFormComponentPanel and AddressFormComponentPanel are
simple
panels, now, and it is working so far.

Now, I have a special use-case, which needs to add an
AbstractFormValidator to the form.

Not to bypass the inner required textfields validations of
PersonFormComponentPanel, I can implement
FormComponent[] getDependentFormComponents(){...}
of the AbstractFormValidator.

BUT, it requieres to return FormComponents, not simple panels.
So, my idea was, just changing the implementation of
PersonFormComponentPanel extends Panel to PersonFormComponentPanel
extends
FormComponentPanel, so the entire PersonFormComponentPanel acts as
FormComponent to be able to fullfill the FormComponent[]
getDependentFormComponents(){...} return value.

Unfortunately this is not working, and I dont know why...
My getInnerMostModel() of the PropertyResolver is always null and the
formcomponents model-update does not succeed / WicketRuntimeException.

Maybe it has something todo with the need to implement
setConvertedInput() / getConvertedInput() which is mentioned in the
javadoc
of FormComponentPanel?

I'm not sure about that... maybe someone can help here?

So... these are my questions:
Is it a good idea to implement such a case extending
FormComponentPanel,
or is FormComponentPanel for other purposes?

How can I 

Re: AjaxEvent click and onclick

[Martin Grigorov]

Hi,

"click" should be used for Ajax behaviors because Wicket 6.0+ uses
JavaScript event listeners.
AttributeModifier modifies HTML attributes and they have to be prefixed
with "on".

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

On Mon, Feb 15, 2016 at 9:50 AM, Kevin  wrote:

> When i use a link (wicket 6.21.0 or 7.1.0) the java code below doesn't
> change
> my element.
> String js = "this.style.display = 'none';";
> js += "document.getElementById('" + showLinkId + "').style.display = '';";
> this.add(AttributeModifier.replace("click", js));
>
> When is use the same code but use "onclick" instead of "click", everything
> works fine.
> I have been told that we should us "click" instead of "onclick".
> What am I doing wrong?
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/AjaxEvent-click-and-onclick-tp4673590.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
>
>

AjaxEvent click and onclick

[Kevin]

When i use a link (wicket 6.21.0 or 7.1.0) the java code below doesn't change
my element.
String js = "this.style.display = 'none';";
js += "document.getElementById('" + showLinkId + "').style.display = '';";
this.add(AttributeModifier.replace("click", js));

When is use the same code but use "onclick" instead of "click", everything
works fine.
I have been told that we should us "click" instead of "onclick". 
What am I doing wrong?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/AjaxEvent-click-and-onclick-tp4673590.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