from:"Sebastian"

I just realized that the current session is also bound to the thread 
context. Would it make sense to attach the Session to the background 
thread using the same way we do it for the Application?


E.g.

Session oldSession = Session.exists() ? Session.get() : null;
Session.set(_session);
try
{
... invoke...
}
finally
{
   if (oldSession == null) Session.unset();
   else Session.set(oldSession);
}

Without doing this, the exception IllegalSateException: You can only 
locate or create sessions in the context of a request cycle may be thrown.


Seb

On 01.10.2010 00:42, Rodolfo Hansen wrote:

On Thu, 2010-09-30 at 23:48 +0200, Sebastian wrote:


There was an issue in your patch where the application could be left

in the ThreadContext, which was fixed,

Hi Rodolfo,

I think you are referring to

try {
Application.set(_application);
methods[m].invoke(o, parameters);
} finally {
Application.set(originalApplication);
if (originalApplication != null) Application.set(originalApplication);
}

The problem is if this code is executed in a separate thread the
originalApplication will be null. If you just omit the null check in the
finally clause the setter will throw an IllegalArgumentException. So to
remove the app from the ThreadContext we would have to call
Application.unset() instead:

if (originalApplication == null) Application.unset();
else Application.set(originalApplication);



you are right, although i checked the source for set and didn't see the
throw...

amended in the 1.4 branches




Regards,
Seb



On 30.09.2010 23:08, Rodolfo Hansen wrote:

Hi Sebastian, your patch is in:

trunk (1.5)
1.4 branch (future 1.4.13 release)
and 1.4.12

There was an issue in your patch where the application could be left in
the ThreadContext, which was fixed,
as well as a simplification in the trigger function.

On Wed, 2010-09-29 at 21:39 +0200, Sebastian wrote:


Hi,

there is a problem in the Push TimerChannelService implementation:
Callbacks do not work reliable when they are invoked from non-Web
threads. The There is no application attached to current thread
WicketRuntimeException will occur in such a case. The attached patch
fixes this issue.

Regards,

Seb








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

Wicket Serialization


Hi,

is it possible to configure a wicket app in a way that definitely will 
use page serialization/deserializion on each request and will not hold 
any page/component instances between requests in memory? I'd like to use 
this during development time to test some aspects of my wicket components.


regards,
seb


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

Re: Wicket Serialization


hi,

on a local copy of Wicket I now temporarily modified the 
SecondLevelCacheSessionStore class and always have the 
SecondLevelCachePageMap.getLastPage() method return null. This enforces 
that a freshly deserialized page object instance is used on each request.


The reason why I am doing this is that e.g. the wicketstuff wicket-push 
projects keeps references to component instances in singleton services, 
e.g. the TimerPushService. Modifications on these components between 
requests only work as long wicket will reuse the same object instances 
on the next request. Since an HTTP session may be serialized by an app 
server between requests based an some 2nd level caching strategy it is 
important to simulate this to detect code that relies on specific object 
references and thus may break in such a case.


seb

On 01.10.2010 16:43, Igor Vaynberg wrote:

wicket already tests serialization for you in dev mode

-igor

On Fri, Oct 1, 2010 at 5:37 AM, Sebastiannospam...@gmx.net  wrote:

Hi,

is it possible to configure a wicket app in a way that definitely will use
page serialization/deserializion on each request and will not hold any
page/component instances between requests in memory? I'd like to use this
during development time to test some aspects of my wicket components.

regards,
seb


-
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: Wicket Serialization

the push service does not directly keep references, this happens because 
of the usage of anonymous classes created within the components, e.g. 
callbacks, eventlisteners, e.g.:


final Label label = new Label(label,);

final IPushTarget pushTarget = getTimerPushService().installPush(this);
backendService.doStuff(new ProgressListener() {
  public void onEventChange(final Event event) {
if (pushTarget.isConnected()) {
label.setDefaultModelObject(event.message);
pushTarget.addComponent(label);
pushTarget.trigger();
}
}

= this will work as long as the current page does not get deserialized 
between request. the backendService gets the listener object which in 
turn has a reference to the label. as long as one can not enforce during 
dev time that pages are really deserialized you have no really chance to 
encounter the problem and thus fix it.



On 02.10.2010 00:40, Igor Vaynberg wrote:

sounds wrong, no one should be keeping references to components

-igor

On Fri, Oct 1, 2010 at 3:32 PM, Sebastiannospam...@gmx.net  wrote:

hi,

on a local copy of Wicket I now temporarily modified the
SecondLevelCacheSessionStore class and always have the
SecondLevelCachePageMap.getLastPage() method return null. This enforces that
a freshly deserialized page object instance is used on each request.

The reason why I am doing this is that e.g. the wicketstuff wicket-push
projects keeps references to component instances in singleton services, e.g.
the TimerPushService. Modifications on these components between requests
only work as long wicket will reuse the same object instances on the next
request. Since an HTTP session may be serialized by an app server between
requests based an some 2nd level caching strategy it is important to
simulate this to detect code that relies on specific object references and
thus may break in such a case.

seb

On 01.10.2010 16:43, Igor Vaynberg wrote:


wicket already tests serialization for you in dev mode

-igor

On Fri, Oct 1, 2010 at 5:37 AM, Sebastiannospam...@gmx.netwrote:


Hi,

is it possible to configure a wicket app in a way that definitely will
use
page serialization/deserializion on each request and will not hold any
page/component instances between requests in memory? I'd like to use this
during development time to test some aspects of my wicket components.

regards,
seb






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

Re: How to use jWicket ResizableBehavior

2010-09-30 Thread Sebastian

Looks like there is a problem in the ResizableBehaviour class. It does 
not ensure that the necessary jQuery CSS is added to the markup. Since 
the method that could do this has protected visibility I need to 
subclass the ResizableBehaviour like this:


ResizableBehaviour resizer = new ResizableBehaviour(){{ 
addUserProvidedResourceReferences(AbstractJqueryUiEmbeddedBehaviour.jQueryUiBaseCss); 
}};

myComponent.add(resizer);

Seb

On 29.09.2010 19:08, Sebastian wrote:

Hi,

I'd like to make a DIV resizable. The JavaDoc of ResizableBehavior says
I just need to add a new behavior instance to a Wicket component (in my
case a WebMarkupContainer) to make it resizable. Doing so results in my
HTML output referencing the minified jquery libs and containing code
like jQuery('mydiv#2').resizable(...). However the DIV did not change
at all and it is not resizable. What do I miss?

Thanks,
Seb


-
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: Bug in Wicket Push TimerChannelService when used with background threads

2010-09-30 Thread Sebastian

 There was an issue in your patch where the application could be left 
in the ThreadContext, which was fixed,


Hi Rodolfo,

I think you are referring to

try {
  Application.set(_application);
  methods[m].invoke(o, parameters);
} finally {
  Application.set(originalApplication);
  if (originalApplication != null) Application.set(originalApplication);
}

The problem is if this code is executed in a separate thread the 
originalApplication will be null. If you just omit the null check in the 
finally clause the setter will throw an IllegalArgumentException. So to 
remove the app from the ThreadContext we would have to call 
Application.unset() instead:


if (originalApplication == null) Application.unset();
else Application.set(originalApplication);

Regards,
Seb



On 30.09.2010 23:08, Rodolfo Hansen wrote:

Hi Sebastian, your patch is in:

trunk (1.5)
1.4 branch (future 1.4.13 release)
and 1.4.12

There was an issue in your patch where the application could be left in
the ThreadContext, which was fixed,
as well as a simplification in the trigger function.

On Wed, 2010-09-29 at 21:39 +0200, Sebastian wrote:


Hi,

there is a problem in the Push TimerChannelService implementation:
Callbacks do not work reliable when they are invoked from non-Web
threads. The There is no application attached to current thread
WicketRuntimeException will occur in such a case. The attached patch
fixes this issue.

Regards,

Seb
-
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

How to use jWicket ResizableBehavior


Hi,

I'd like to make a DIV resizable. The JavaDoc of ResizableBehavior says 
I just need to add a new behavior instance to a Wicket component (in my 
case a WebMarkupContainer) to make it resizable. Doing so results in my 
HTML output referencing the minified jquery libs and containing code 
like jQuery('mydiv#2').resizable(...). However the DIV did not change 
at all and it is not resizable. What do I miss?


Thanks,
Seb


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

Wicket Push for Java 5?


Hi,

why is the wicket push module available in the Maven repo1 compiled with 
Java 6? I checked out the code and cannot find a single usage of any new 
Java 6 features (except the @Override annotation used on methods of 
implemented interfaces).


I'm currently working in an environment where only Java 5 is allowed. 
all other wicket components retrieved via Maven repo1 work fine here.


Regards,
Seb


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

Re: Wicket Push for Java 5?


Hi Mike,

thanks for your resoponse. Maybe you can just have the push-comet module 
being compiled with Java 6? I am using the push.timer implementation 
currently. I recompiled it using Java5 and it works fine.


Regards,

Seb

On 29.09.2010 19:55, Michael O'Cleirigh wrote:

Hi Sebastian,

Its related to the dependencies of the wicketstuff-push. When I switched
the wicketstuff build to use a real JDK 5 instead of JDK 6 in
compatibility mode errors like this were seen:

[INFO]

[INFO] Error for project: Wicketstuff Push (during deploy)
[INFO]

[INFO] Compilation failure
/home/wicket/.hudson/jobs/Wicket Stuff
Core/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdService.java:[11,-1]
cannot access org.cometd.bayeux.Channel
bad class file:
/home/wicket/.m2/repository/org/cometd/java/bayeux-api/2.0.0.RC2/bayeux-api-2.0.0.RC2.jar(org/cometd/bayeux/Channel.class)

class file has wrong version 50.0, should be 49.0
*
*This is why the project was moved to be built by java 6 instead of java 5.

Regards,

Mike
*
*

Hi,

why is the wicket push module available in the Maven repo1 compiled
with Java 6? I checked out the code and cannot find a single usage of
any new Java 6 features (except the @Override annotation used on
methods of implemented interfaces).

I'm currently working in an environment where only Java 5 is allowed.
all other wicket components retrieved via Maven repo1 work fine here.

Regards,
Seb


-
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

Reporting bugs for Wicketstuff components


Hi,

where can I report bugs for wicketstuff components?

Regards,

Seb


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

Bug in Wicket Push TimerChannelService when used with background threads


Hi,

there is a problem in the Push TimerChannelService implementation: 
Callbacks do not work reliable when they are invoked from non-Web 
threads. The There is no application attached to current thread 
WicketRuntimeException will occur in such a case. The attached patch 
fixes this issue.


Regards,

Seb
Index: push/src/main/java/org/wicketstuff/push/timer/TimerChannelBehavior.java
===
--- push/src/main/java/org/wicketstuff/push/timer/TimerChannelBehavior.java 
(revision 5552)
+++ push/src/main/java/org/wicketstuff/push/timer/TimerChannelBehavior.java 
(working copy)
@@ -50,6 +50,7 @@
  * appropriately the resources associated with the page.
  * 
  * @author Xavier Hanin
+ * @author Sebastian Thomschke fixed There is no application attached to 
current thread
  * 
  * @see IChannelService
  * @see TimerChannelService
@@ -157,12 +158,12 @@
 */
public void invoke(final Object o) throws 
IllegalArgumentException,
IllegalAccessException, 
InvocationTargetException {
-   final Application originalApplication = 
Application.get();
+   final Application originalApplication = 
Application.exists() ? Application.get() : null;
try {
Application.set(_application);
methods[m].invoke(o, parameters);
} finally {
-   Application.set(originalApplication);
+   if (originalApplication != null) 
Application.set(originalApplication);
}
}
}
@@ -175,8 +176,8 @@
/**
 * Construct.
 */
-   public DelayedMethodCallList() {
-   _application = Application.get();
+   public DelayedMethodCallList(final Application application) {
+   _application = application;
calls = new ArrayListDelayedMethodCall();
}
 
@@ -185,8 +186,8 @@
 * 
 * @param dmcl
 */
-   public DelayedMethodCallList(final DelayedMethodCallList dmcl) {
-   _application = Application.get();
+   public DelayedMethodCallList(final DelayedMethodCallList dmcl, 
final Application application) {
+   _application = application;
calls = new ArrayListDelayedMethodCall(dmcl.calls);
}
 
@@ -253,7 +254,7 @@
 * A trigger currently being constructed, waiting for a call to 
trigger
 * to go to the triggers list.
 */
-   private final DelayedMethodCallList currentTrigger = new 
DelayedMethodCallList();
+   private final DelayedMethodCallList currentTrigger;
/**
 * The Wicket Application in which this target is used
 */
@@ -275,6 +276,7 @@
this.application = application;
this.id = id;
this.timeout = timeout;
+   this.currentTrigger = new 
DelayedMethodCallList(application);
}
 
/**
@@ -337,7 +339,7 @@
if (currentTrigger.isEmpty()) {
return;
}
-   trigger = new 
DelayedMethodCallList(currentTrigger);
+   trigger = new 
DelayedMethodCallList(currentTrigger, application);
currentTrigger.clear();
}
final ListDelayedMethodCallList triggers = 
getTriggers();

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

Re: OT: Best practices regarding service layers DAOs

2010-08-30 Thread Sebastian


Alexander,

If I understand you correctly, you are saying: view-only operations (e.g.
listings, search forms) can access the DAOs directly, and all operations
that modify data should be routed through the service layer?
How do you deal with enforcing security constraints (e.g. user X with role Y
can only see records created by himself)? I'd like to keep such things out
of the view (wicket), so that when I also want to expose say a webservice or
REST interface I do not need to duplicate the constraints checks and
enforcement.

Brian,

I'm using warp-persist (which will be superseded by guice-persist shortly),
which provides transactional semantics comparable to Spring. This is also
one of the reasons I started building services: to have a clear boundary for
transactions.
-- 
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/OT-Best-practices-regarding-service-layers-DAOs-tp2400408p2400503.html
Sent from the Wicket - User 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

OT: Best practices regarding service layers DAOs

2010-08-30 Thread Sebastian

Hi all,

I've been struggling with some design questions in some wicket projects
lately, and hope to get some insights from fellow wicketeers.

Some years ago I started with Databinder as a DAO layer, without a service
layer. This led to UI code building queries or adding Restrictions to a jpa
(hibernate) query.
After working like that on some smaller projects, I came across warp-persist
and started using that (plus guice). Great! many new possibilities.
However, ever since I started using those tools, I have ended up with the
following:

- JPA Entities
- DAO interface per entity, with a (guice-bound) implementation
- UI either calls DAO methods directly for loading data, or specialized
IDataProvider implementation which takes a DAO and allows the UI to add
filters (e.g. a filter based on a search by name field).
- Service layer which is more or less based on the Transaction script
pattern (as described by Martin Fowler); this contains specific use cases,
such as cases where multiple objects need to be dealt with in a separate
transaction (@Transactional)

However, the above gets messy quickly. There are different ways to get to
the data: in some cases the UI calls DAOs directly, and sometimes a service
should be used since it does extra filtering etc.

So lately I started to wonder if I should make the UI only call the service
layer... Which would lead to a lot of extra classes and code which merely
forwards calls to the DAOs. Especially when combined with IDataProvider it
leads to a lot of UI-specific (findByXandY, findCountByXandY) methods in
both the DAO and service layer.

I decided to take a step back and re-evaluate. I only work on projects for
my own firm (so no external projects), and unfortunately do not have access
to people who have experience with these sorts of architectural design
issues. Well, of course there is the option of outsourcing, which I've tried
in a few projects; But let's just say that the resulting apps were by no
means well designed, even though the price was relatively high (small
project, 40.000 euro cost).

Recently I picked up Domain Driven Design by Eric Evans, and I like what I
am reading. Since most of my projects are small, I don't want to add many
layers to make things more complicated. However, I do want separation of
concerns (e.g. a clear boundary/layer for security, transactions). Injecting
services into my entities seems wrong to me, and I certainly don't want to
go the RoR ActiveRecord direction (all logic in entities, been there didn't
like it).

Since the projects are small, the effects of relatively unclean code are
negligible. On the other hand I am a purist (and a perfectionist), eager to
learn and improve; Also, some projects become more and more important (e.g.
handling millions of dollars worth of transactions), and keep on growing.

Due to lack of experience in bigger projects I feel like I keep on
struggling with this without having a clear focus. It would really help me
to hear from other how they layer their wicket apps and why.

Thanks in advance for reading, and for posting a reply!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/OT-Best-practices-regarding-service-layers-DAOs-tp2400408p2400408.html
Sent from the Wicket - User 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

Using up/down/remove links of ListView items clears text fields


Hi,

I am trying to use a list view component on a page where rows with text 
fields can be added, removed or moved around. I am using the removeLink, 
moveUpLink and moveDownLink methods of the listview to create the 
respective links for each list item.
The problem is that even when I enable the reuseListItems option, on 
using any of these links the text fields forget the recently entered 
data (raw input) and revert to the values of the backing model.


This issue does not occur when I am adding rows the list view.

Below is an example. I can add rows using the Add Row button. When I 
enter text into the text fields, when I use the links next to a row, the 
content of any text field is cleared.


Any suggestions?

Regards,

Seb

/ PAGE /
import java.util.*;
import org.apache.wicket.PageParameters;
import org.apache.wicket.markup.html.WebPage;
import org.apache.wicket.markup.html.basic.Label;
import org.apache.wicket.markup.html.form.*;
import org.apache.wicket.markup.html.list.*;
import org.apache.wicket.model.*;

public class ListViewPage extends WebPage {
  public static class Row {
public String key;
public String value;
  }

  private final ListRow rows = new ArrayListRow();

  public ListViewPage(final PageParameters parameters) {

add(new FormListRow(rowsForm).

  add(new Button(addRowButton) {
public void onSubmit() { rows.add(new Row()); }
  }.setDefaultFormProcessing(false)).

  add(new ListViewRow(rowsList, new 
PropertyModelListRow(this, rows)) {

protected void populateItem(final ListItemRow item) {
  final Row row = item.getModelObject();

  item.add(new Label(index, new 
AbstractReadOnlyModelInteger() {

   public Integer getObject() { return item.getIndex() + 1; }
  }));

  item.add(new RequiredTextFieldString(key, new 
PropertyModelString(row, key)));


  item.add(new TextFieldString(value, new 
PropertyModelString(row, value)));


  item.add(removeLink(removeRowLink, item));
  item.add(moveUpLink(moveUpLink, item));
  item.add(moveDownLink(moveDownLink, item));
}
  }.setReuseItems(true)));
  }
}

/ HTML /
html
headtitleListView Test/title/head
body
  form wicket:id=rowsForm
  button wicket:id=addRowButtonAdd Row/button
  tabletr wicket:id=rowsList
 tdnbsp;nbsp;nbsp;#span wicket:id=index1/span/td
 tdKey: input type=text wicket:id=key //td
 tdValue: input type=text wicket:id=value //td
 td
a href=# wicket:id=moveUpLink[uarr;]/a
a href=# wicket:id=moveDownLink[darr;]/a
a href=# wicket:id=removeRowLink[X]/a
 /td
  /tr/table
  input type=submit value=Submit /
/form
/body
/html


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

Re: Using up/down/remove links of ListView items clears text fields


Hi Martin,

thanks for pointing me to the reuse component concept. It solved my 
problem partially but not completely. The problem is, that the links 
provided by the listview result in HTTP GET request which means that any 
values recently entered will not be transferred back and get lost. I am 
now using my own link implementations based on the SubmitLink class. I 
am attaching all files of my working example as reference.


Generally I think it makes great sense to have this behaviour as part of 
the ListView. At least I expected it to work this way in the first place.


Regards,

Seb

On 14.08.2010 16:40, Martin Makundi wrote:

Hi!

You can solve this in a robust manner using reusemanager:

http://osdir.com/ml/users-wicket.apache.org/2010-08/msg00161.html

2010/8/14 Sebastiannospam...@gmx.net:

Hi,

I am trying to use a list view component on a page where rows with text
fields can be added, removed or moved around. I am using the removeLink,
moveUpLink and moveDownLink methods of the listview to create the respective
links for each list item.
The problem is that even when I enable the reuseListItems option, on using
any of these links the text fields forget the recently entered data (raw
input) and revert to the values of the backing model.

This issue does not occur when I am adding rows the list view.

Below is an example. I can add rows using the Add Row button. When I enter
text into the text fields, when I use the links next to a row, the content
of any text field is cleared.

Any suggestions?

Regards,

Seb

/ PAGE /
import java.util.*;
import org.apache.wicket.PageParameters;
import org.apache.wicket.markup.html.WebPage;
import org.apache.wicket.markup.html.basic.Label;
import org.apache.wicket.markup.html.form.*;
import org.apache.wicket.markup.html.list.*;
import org.apache.wicket.model.*;

public class ListViewPage extends WebPage {
  public static class Row {
public String key;
public String value;
  }

  private final ListRow  rows = new ArrayListRow();

  public ListViewPage(final PageParameters parameters) {

add(new FormListRow(rowsForm).

  add(new Button(addRowButton) {
public void onSubmit() { rows.add(new Row()); }
  }.setDefaultFormProcessing(false)).

  add(new ListViewRow(rowsList, new PropertyModelListRow(this,
rows)) {
protected void populateItem(final ListItemRow  item) {
  final Row row = item.getModelObject();

  item.add(new Label(index, new AbstractReadOnlyModelInteger() {
   public Integer getObject() { return item.getIndex() + 1; }
  }));

  item.add(new RequiredTextFieldString(key, new
PropertyModelString(row, key)));

  item.add(new TextFieldString(value, new
PropertyModelString(row, value)));

  item.add(removeLink(removeRowLink, item));
  item.add(moveUpLink(moveUpLink, item));
  item.add(moveDownLink(moveDownLink, item));
}
  }.setReuseItems(true)));
  }
}

/ HTML /
html
headtitleListView Test/title/head
body
  form wicket:id=rowsForm
  button wicket:id=addRowButtonAdd Row/button
  tabletr wicket:id=rowsList
 tdnbsp;nbsp;nbsp;#span wicket:id=index1/span/td
 tdKey:input type=text wicket:id=key //td
 tdValue:input type=text wicket:id=value //td
 td
a href=# wicket:id=moveUpLink[uarr;]/a
a href=# wicket:id=moveDownLink[darr;]/a
a href=# wicket:id=removeRowLink[X]/a
 /td
  /tr/table
  input type=submit value=Submit /
/form
/body
/html


-
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




package wickettest;

import java.io.Serializable;
import java.util.HashMap;
import java.util.Map;

import org.apache.wicket.markup.html.form.FormComponent;

public class FormComponentReuseManager implements Serializable
{
private static final long serialVersionUID = 1L;

private final MapObject, MapString, FormComponent ?  
componentsByRowId = new HashMapObject, MapString, FormComponent ? ();

public T FormComponentT rememberOrReuse(final Object rowId, final 
FormComponentT newComponent)
{
MapString, FormComponent ?  rowComponents = 
componentsByRowId.get(rowId);
if (rowComponents == null)
componentsByRowId.put(rowId, rowComponents = new 
HashMapString, FormComponent ? ());

@SuppressWarnings(unchecked)
final FormComponentT existingComponent = (FormComponentT) 
rowComponents.get(newComponent.getId());
if (existingComponent == null)
{

Re: Using up/down/remove links of ListView items clears text fields

Couldn't detect the listview if it is part of a form and decide for 
SubmitLink or Link?


On 14.08.2010 18:51, James Carman wrote:

But then all listviews that need up/down links have to be in a form.

On Aug 14, 2010 12:37 PM, Sebastiannospam...@gmx.net  wrote:

Hi Martin,

thanks for pointing me to the reuse component concept. It solved my
problem partially but not completely. The problem is, that the links
provided by the listview result in HTTP GET request which means that any
values recently entered will not be transferred back and get lost. I am
now using my own link implementations based on the SubmitLink class. I
am attaching all files of my working example as reference.

Generally I think it makes great sense to have this behaviour as part of
the ListView. At least I expected it to work this way in the first place.

Regards,

Seb

On 14.08.2010 16:40, Martin Makundi wrote:

Hi!

You can solve this in a robust manner using reusemanager:

http://osdir.com/ml/users-wicket.apache.org/2010-08/msg00161.html

2010/8/14 Sebastiannospam...@gmx.net:

Hi,

I am trying to use a list view component on a page where rows with text
fields can be added, removed or moved around. I am using the removeLink,
moveUpLink and moveDownLink methods of the listview to create the

respective

links for each list item.
The problem is that even when I enable the reuseListItems option, on

using

any of these links the text fields forget the recently entered data

(raw

input) and revert to the values of the backing model.

This issue does not occur when I am adding rows the list view.

Below is an example. I can add rows using the Add Row button. When I

enter

text into the text fields, when I use the links next to a row, the

content

of any text field is cleared.

Any suggestions?

Regards,

Seb

/ PAGE /
import java.util.*;
import org.apache.wicket.PageParameters;
import org.apache.wicket.markup.html.WebPage;
import org.apache.wicket.markup.html.basic.Label;
import org.apache.wicket.markup.html.form.*;
import org.apache.wicket.markup.html.list.*;
import org.apache.wicket.model.*;

public class ListViewPage extends WebPage {
public static class Row {
public String key;
public String value;
}

private final ListRow  rows = new ArrayListRow();

public ListViewPage(final PageParameters parameters) {

add(new FormListRow(rowsForm).

add(new Button(addRowButton) {
public void onSubmit() { rows.add(new Row()); }
}.setDefaultFormProcessing(false)).

add(new ListViewRow(rowsList, new PropertyModelListRow(this,
rows)) {
protected void populateItem(final ListItemRow  item) {
final Row row = item.getModelObject();

item.add(new Label(index, new AbstractReadOnlyModelInteger() {
public Integer getObject() { return item.getIndex() + 1; }
}));

item.add(new RequiredTextFieldString(key, new
PropertyModelString(row, key)));

item.add(new TextFieldString(value, new
PropertyModelString(row, value)));

item.add(removeLink(removeRowLink, item));
item.add(moveUpLink(moveUpLink, item));
item.add(moveDownLink(moveDownLink, item));
}
}.setReuseItems(true)));
}
}

/ HTML /
html
headtitleListView Test/title/head
body
form wicket:id=rowsForm
button wicket:id=addRowButtonAdd Row/button
tabletr wicket:id=rowsList
tdnbsp;nbsp;nbsp;#span wicket:id=index1/span/td
tdKey:input type=text wicket:id=key //td
tdValue:input type=text wicket:id=value //td
td
a href=# wicket:id=moveUpLink[uarr;]/a
a href=# wicket:id=moveDownLink[darr;]/a
a href=# wicket:id=removeRowLink[X]/a
/td
/tr/table
input type=submit value=Submit /
/form
/body
/html


-
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: Using up/down/remove links of ListView items clears text fields