We have IExportableColumn
where T is the type of each row in the table.
where S is the type of the sort property of the table.
and the method
public void exportData(IDataProvider dataProvider,
List> columns, OutputStream outputStream)
try
List> columns = new
ArrayList>();
François Meillet
Hi,
I am trying to export data to csv in my wicket pages. I am using
CSVDataExporter for this purpose. Due to some constraints I am not using it
in conjunction to ExportToolbar. There is a link and on click of the link I
am trying to call exportData() on instance of CSVDataExporter.
I am using Ab
Thanks ! It is more clear now !
On Wed, Nov 5, 2014 at 3:44 PM, Wayne W wrote:
> Sorry Martin its not clear enough. This any better?
>
>
>1. Tomcat1 / Session A / Thread 1: User goes to : my.example.com/login
> (LoginPage.java)
>2. Tomcat1 / Session A / Thread 2: They log in
>3.
Sorry Martin its not clear enough. This any better?
1. Tomcat1 / Session A / Thread 1: User goes to : my.example.com/login
(LoginPage.java)
2. Tomcat1 / Session A / Thread 2: They log in
3. Tomcat 1 / Session A / Thread 2 : We invalidate the session and do a
redirect to : foo.exam
Then your first mail misleads.
Would you please explain again the steps with more details which step on
which node happens.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Nov 5, 2014 at 1:01 PM, Wayne W wrote:
> Hi Martin,
>
> I don't think this is anythin
Hi Martin,
I don't think this is anything to do with session replication, as we
invalidate the session at step 3 and its not about trying to pick the
session up on a different instance. Its about creating a new session from a
redirect where the issue seems. We do use sticky session load balancing
Hi,
As far as I know the session replication supporting code is the same since
Wicket 1.4.1 (or 1.4.2).
The Wicket Session object is saved as an attribute in the HttpSession. The
HttpSession is replicated by Tomcat itself. What is your Tomcat config
related to replication ?
Do you use sticky sess
Hi,
we recently migrated to 6.17 from 4.x. Something we are now experiencing is
an odd session problem in production.
We have 2 tomcats load balance running the front end wicket code. We have a
certain flow that goes like this:
1. User goes to : my.example.com/login (LoginPage.java)
2. Th
