Re: [Wicket-user] Palette problem with latest snapshot
Ok, here are new details for this.
I was using following form:
from wicket:id=roleForm
input wicket:id=roleName
palette
/form
and java source
EditRoleForm(String str, Role role) {
super(str, new CompoundPropertyMode(role)); ***
add(new RequiredTextField(roleName);
add(new Palette(...);
}
and
class Role {
private int roleId;
private String roleName;
}
Found out that, if I use in line *** instead new PropertyModel(role,
roleName) it works as before.
What I was doing wrong? And why old snapshot accepted my error?
I'm sorry, I did not get to debugging yet, as soon as I'll have some extra
time, I'll do so.
Of course, until someone says, hey it is not worth it ;)
Timo Rantalaiho wrote:
On Fri, 15 Jun 2007, shumbola wrote:
A few days ago I've upgraded my project to the 1.3 snapshot from June 12.
Before I was using a one from May 10. Today I noticed that my page which
uses the Palette component stopped working. Anytime I launch that page it
It's easier to diagnose your problem if you provide the
complete source code and markup. But could it be that there
has been a change in the component hierarchy of Palette, and
your own markup is now incompatible with it?
We always use a snapshot of the current day and have
extensive JUnit tests (covering about 90% of the lines).
This makes it a lot easier to notice and fix this kind of
problems, as we can easily see from commits / dev / user
mailing lists what is going on, and just diff the whole
wicket source code when needed. A couple of days of diff is
perfectly readable, but one month not.
- Timo
--
Timo Rantalaiho
Reaktor Innovations OyURL: http://www.ri.fi/
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
View this message in context:
http://www.nabble.com/Palette-problem-with-latest-snapshot-tf3927222.html#a11161103
Sent from the Wicket - User mailing list archive at Nabble.com.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Palette problem with latest snapshot
Ok, here are new details for this.
I was using following form:
from wicket:id=roleForm
input wicket:id=roleName
span wicket:id=palettepalette/span
/form
and java source
EditRoleForm(String str, Role role) {
super(str, new CompoundPropertyMode(role)); ***
add(new RequiredTextField(roleName);
add(new Palette(...);
}
and
class Role {
private int roleId;
private String roleName;
}
Found out that, if I use in line *** instead new PropertyModel(role,
roleName) it works as before.
What I was doing wrong? And why old snapshot accepted my error?
I'm sorry, I did not get to debugging yet, as soon as I'll have some extra
time, I'll do so.
Of course, until someone says, hey it is not worth it ;)
Вы писали Saturday, June 16, 2007, 1:23:04 PM:
On Fri, 15 Jun 2007, shumbola wrote:
A few days ago I've upgraded my project to the 1.3 snapshot from June 12.
Before I was using a one from May 10. Today I noticed that my page which
uses the Palette component stopped working. Anytime I launch that page it
It's easier to diagnose your problem if you provide the
complete source code and markup. But could it be that there
has been a change in the component hierarchy of Palette, and
your own markup is now incompatible with it?
We always use a snapshot of the current day and have
extensive JUnit tests (covering about 90% of the lines).
This makes it a lot easier to notice and fix this kind of
problems, as we can easily see from commits / dev / user
mailing lists what is going on, and just diff the whole
wicket source code when needed. A couple of days of diff is
perfectly readable, but one month not.
- Timo
--
shumbola mailto:[EMAIL PROTECTED]
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Palette problem with latest snapshot
On Fri, 15 Jun 2007, shumbola wrote: A few days ago I've upgraded my project to the 1.3 snapshot from June 12. Before I was using a one from May 10. Today I noticed that my page which uses the Palette component stopped working. Anytime I launch that page it It's easier to diagnose your problem if you provide the complete source code and markup. But could it be that there has been a change in the component hierarchy of Palette, and your own markup is now incompatible with it? We always use a snapshot of the current day and have extensive JUnit tests (covering about 90% of the lines). This makes it a lot easier to notice and fix this kind of problems, as we can easily see from commits / dev / user mailing lists what is going on, and just diff the whole wicket source code when needed. A couple of days of diff is perfectly readable, but one month not. - Timo -- Timo Rantalaiho Reaktor Innovations OyURL: http://www.ri.fi/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Palette problem with latest snapshot
Hello, A few days ago I've upgraded my project to the 1.3 snapshot from June 12. Before I was using a one from May 10. Today I noticed that my page which uses the Palette component stopped working. Anytime I launch that page it gives me the following error: WicketMessage: No get method defined for class: class my.beans.Role expression: recorder Root cause: org.apache.wicket.WicketRuntimeException: No get method defined for class: class my.beans.Role expression: recorder at org.apache.wicket.util.lang.PropertyResolver.getGetAndSetter(PropertyResolver.java:391) at org.apache.wicket.util.lang.PropertyResolver.getObjectAndGetSetter(PropertyResolver.java:267) at org.apache.wicket.util.lang.PropertyResolver.getPropertyClass(PropertyResolver.java:145) at org.apache.wicket.model.AbstractPropertyModel.getObjectClass(AbstractPropertyModel.java:199) at org.apache.wicket.markup.html.form.AbstractTextComponent.getModelType(AbstractTextComponent.java:119) at org.apache.wicket.markup.html.form.AbstractTextComponent.onBeforeRender(AbstractTextComponent.java:107) at org.apache.wicket.extensions.markup.html.form.palette.component.Recorder.onBeforeRender(Recorder.java:76) at org.apache.wicket.Component.beforeRender(Component.java:847) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1449) at org.apache.wicket.Component.beforeRender(Component.java:857) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1449) at org.apache.wicket.Component.beforeRender(Component.java:857) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1449) at org.apache.wicket.Component.beforeRender(Component.java:857) at org.apache.wicket.Page.renderPage(Page.java:885) at org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:165) at org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:59) at org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:103) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1037) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1107) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1176) at org.apache.wicket.RequestCycle.request(RequestCycle.java:499) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:255) at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:126) ... So, I thought I've to upgrade to the latest and greatest, and did so. Downloaded a snapshot from June 15. It still does not work, the same exception :( I've tried to left the latest wicket*.jar but downgrade the wicket-extensions, it does not work. If I downgrade the wicket, then it works as before. What could be the problem here? Thanks, shumbola -- View this message in context: http://www.nabble.com/Palette-problem-with-latest-snapshot-tf3927222.html#a11137476 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
