http://mail-archives.apache.org/mod_mbox/maven-users/200702.mbox/[EMAIL
PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions
As a long-time Tapestry user (but very new Wicket user), I have a few
thoughts about in-line component declaration.
1.) Even in a framework like Tapestry where the idiom is fully
supported, it can lead to complex and difficult to maintain
templates. In fact, it's generally discouraged in
On 2/14/07, Ryan Holmes [EMAIL PROTECTED] wrote:
As a long-time Tapestry user (but very new Wicket user), I have a few
thoughts about in-line component declaration.
1.) Even in a framework like Tapestry where the idiom is fully
supported, it can lead to complex and difficult to maintain
Hi
Im trying to test an application with jmeter , I keep getting page expired when
testing. I have a cookie manager and save jsessionid, are there any thing else
I should be aware of in that direction?
The application are rather simple although there are some ajax calls. The test
fails
It sounds like Scott just wants to allow the user to cancel the
slow-loading page by navigating to another page. If his database
request happened in a LoadableDetachableModel rather than a page
constructor, would that allow a new page to be rendered while the old
one is still trying to
Hmm, adding a link parser seemed to solve the problem.. But any how, if anyone
has some tips I'd like to hear them::-)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nino Wael
Sent: 14. februar 2007 10:19
To: wicket-user@lists.sourceforge.net
On 2/14/07, Ryan Holmes [EMAIL PROTECTED] wrote:
It sounds like Scott just wants to allow the user to cancel the
slow-loading page by navigating to another page.
Or at least don't show a blank page that'll provoke the user to hit
refresh ten times in a row.
If his database
request happened
Ahh, I think we discussed this earlier. The best solution are to utilize a
worker thread (I think) and make the client reload until the thread are done..
I think it's essential for wicket in order to handle session state to use a
singleton pattern for request cycles.
EG if page A have long
On 2/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
For some cases it is easier, more efficient or - as with behaviors -
simply the only way to write markup 'around' (before and after) the
actual tag that a component is coupled to. This is where
response.write can be used.
Is this also the
EG if page A have long loading time page b,c,d will just have to wait. So if
you utilize a worker thread then you will be able to cancel the thread and go
to the other page if you want to.
Not all requests are synced on the session though. Notably requests to
shared resources aren't, while
On 2/14/07, Robert . [EMAIL PROTECTED] wrote:
On 2/13/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
For some cases it is easier, more efficient or - as with behaviors -
simply the only way to write markup 'around' (before and after) the
actual tag that a component is coupled to. This is
Im not on the dev list, I guess I can look it up on nabble?
Yep: http://www.nabble.com/stateless-behaviors-tf3226344.html
Or subscribe to it! See http://incubator.apache.org/wicket/incubator.html
Eelco
-
Take Surveys.
Thanks, that really clears it up.
At first glance, synchronizing pages on the session seems a little
overly restrictive (Scott's issue being a case in point), but of
course *not* synchronizing on the session is an infamous source of
frustrating bugs, even in frameworks with much simpler
On 2/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 2/14/07, Ryan Holmes [EMAIL PROTECTED] wrote:
As a long-time Tapestry user (but very new Wicket user), I have a few
thoughts about in-line component declaration.
1.) Even in a framework like Tapestry where the idiom is fully
When doing an ajax update on a MarkupContainer containing a listview.. I
am replacing the listview model before the update:
java.lang.NullPointerException
at wicket.Page.componentStateChanging(Page.java:327)
at wicket.Component.addStateChange(Component.java:2551)
at
Hi,
Johan Compagner wrote:
So if you show A the second time then yes B is dropped. But if you then do
setResponsePage(B) B is again pushed to the stack and should be able to
render fine.
I found out why this questions sounded so stupid to you: I used ajax to show
the cached page in a
I apologize if this gets sent twice.. my ISP smtp server is acting up.
When doing an ajax update on a MarkupContainer containing a listview.. I
am replacing the listview model before the update:
java.lang.NullPointerException
at wicket.Page.componentStateChanging(Page.java:327)
On Wed, 14 Feb 2007, Aaron HIniker wrote:
When doing an ajax update on a MarkupContainer containing a listview.. I
am replacing the listview model before the update:
To update a ListView with ajax, I just manipulate its list
instead of replacing the whole model. To make removals work,
I
I looked at pages second level cache implementation in 1.3 and wonder
why not to use ehcache instead? It's much more intelligent, configurable
and performant. For example, it can have part of cache in memory while
swapping less frequently used pages on the disk.
--
Andrew Klochkov
Would a WebResource not lock the rest of the application? Ajax is not a
possibility due to security requirements. This page is already inside its
own frame, I pretty much need a unsynchronized page. Can you provide an
example of how to use a webResource to display a table
Scott
Didn't know about it before, so can't see a possible use case where it is
necessary
+1 remove.
On 2/14/07, Frank Bille [EMAIL PROTECTED] wrote:
On 2/14/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 2/14/07, Ryan Holmes [EMAIL PROTECTED] wrote:
As a long-time Tapestry user (but very
Sorry, I should have given the link. It is http://r8fe.net/webby/ as you
already mentioned. I found it through the Wicket links section btw.
- nilo
Jean-Baptiste Quenot-3 wrote:
* nilo de roock:
Today I looked at WebbyDB, it's a 'PHP-type-of-dump-classes-on-webpage'
app,
hibernate
Hello,
I know that there must be an easy way to do this, but I have not been able
to figured it out os far, and there are no examples that I could find.
I would like to know how you can update the AjaxFallbackDefaultDataTable in
2.0, when the underlying data has changed, such as in a delete or
Stability and consistency is paramount in a good framework - delete.
Jonathan Locke wrote:
Our Wiki describes the wicket:component tag as follows:
wicket:component - Creates a Wicket component on the fly. Needs a class
attribute. Though this has been in wicket for a long time, it is
yep. yep. yep. could not have said it better. it takes real effort
to restrain a maturing project from collapsing under its own weight.
*less is more*
Ryan Holmes wrote:
As a long-time Tapestry user (but very new Wicket user), I have a few
thoughts about in-line component
[X] Delete this unimportant and generally unsupported feature
On 2/13/07, Jonathan Locke [EMAIL PROTECTED] wrote:
Our Wiki describes the wicket:component tag as follows:
wicket:component - Creates a Wicket component on the fly. Needs a class
attribute. Though this has been in wicket for a
I am experiencing a very similar issue (using 1.2.x branch, aka 1.2.5)
however the reproduction scenario I am seeing is a submit after a ajax
link. I am available if anyone wants to help me track the cause down.
I am hoping to get some time tonight or tomorrow to put together a
simple application
it would be helpful to know the version
-igor
On 2/14/07, Aaron HIniker [EMAIL PROTECTED] wrote:
When doing an ajax update on a MarkupContainer containing a listview.. I
am replacing the listview model before the update:
java.lang.NullPointerException
at
you have to update the whole table. there is nothing draconian about it
because any other row may or may not be there after the update - other users
might be adding/removing things to the table as well.
-igor
On 2/14/07, De Soca [EMAIL PROTECTED] wrote:
Hello,
I know that there must be an
On 2/14/07, Andrew Klochkov [EMAIL PROTECTED] wrote:
I looked at pages second level cache implementation in 1.3 and wonder
why not to use ehcache instead?
Exactly what I have advocated, and which is why it is had the name
'second level cache'. However, I don't think it should be the default,
Hi all,
In my Databinder-using application I have the requirement to
create/edit entities both within a standard request cycle, and via
AJAX inside a Modal Window. In the interests of not duplicating code,
I would like to drive both these processes from the same Form object,
passing a boolean
I've tried writing a IPageStore using ehcache today, the performance
wasn't better than what we already have.
And Wicket second level session store is not really a cache, it's works
differently.
-Matej
Eelco Hillenius wrote:
On 2/14/07, Andrew Klochkov [EMAIL PROTECTED] wrote:
I looked at
ChuckDeal wrote:
How do the Wicket developers have their Eclipse environment setup?
I have a SNAPSHOT project that I created from the svn tree (wicket 1.3).
Each of the subprojects are below that project but the .classpath and
.project are not setup to allow building of the whole project.
On 2/14/07, Matej Knopp [EMAIL PROTECTED] wrote:
I've tried writing a IPageStore using ehcache today
Cool. Maybe you could paste the code into a blog or WIKI page?
Eelco
-
Take Surveys. Earn Cash. Influence the Future of
i thought you wanted to handle it the same way so why do you need to know if
the processing is ajax or regular request?
-igor
On 2/14/07, Charlie Dobbie [EMAIL PROTECTED] wrote:
Hi all,
In my Databinder-using application I have the requirement to
create/edit entities both within a standard
does wget keep the cookie for session tracking?
Yes, it does. I'm doing a
wget -erobots=off --post-data=username=(user)password=(pass)
--keep-session-cookies --save-cookies=cookies.txt
http://test.com/catalog/app/SignIn
I get SignIn + the cookie
(Cookie file:
test.com FALSE /catalog
i dont know if anyone has done any offline generation, but this seems like a
reasonable way to do it
not sure why its not working, dont know that much about wget either :)
do you have it set to follow redirects? because after a form submit there is
a redirect
-igor
On 2/14/07, Francisco
Hi,
I vote either:
[X] Keep wicket:component, but define its limits, document it on the wiki
as fully supported and commit to supporting it in the future
or
[X] Delete this unimportant and generally unsupported feature
with the amendment that the case below is supported in some other way
Also, you might want to change the redirect strategy to ONE_PASS_RENDER
Martijn
On 2/14/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
i dont know if anyone has done any offline generation, but this seems like a
reasonable way to do it
not sure why its not working, dont know that much about wget
On 2/13/07, Iulian Costan [EMAIL PROTECTED] wrote:
hey Filippo,
yes, i've been thinking for a while to release 1.0 version but couldnt make
it till now. yes, please do it, if you are kind enough to help me, that will
be great. as well pom files need little clean up as well, but that's another
Hi
I just wanted to share a little trick with you guys who might also be
struggling with this.
I have deployed an application on my linux box. Danish characters (æøå)
works fine, no problem.
Then we add AutoCompleteTextField to make search more nice on one page. And
here comes the problem.
Jonathan Locke schrieb:
[X] Delete this unimportant and generally unsupported feature
[ ] Keep wicket:component, but define its limits, document it on the wiki
as fully supported and commit to supporting it in the future
and a +1 for wicket:pseudo / wicket:container as well ;)
Greetings,
Wicket 1.3 (revision 507527)
I have been experiencing variations on the following stacktrace since I
updated to the latest snapshot. I say variations because sometimes the full
stack trace is many causes deep, but the only interesting cause is the NPE
at the bottom.
Its EXACTLY a cache
What isn't a cache is ehcache
At least not in my point of view
A cache is something you cache something as good as you can but it can be
gone at anytime.
ehcache is not a cache. Its a in memory predefined size list. where some can
drop of and others not
thats not caching.
yes the error reporting must be done better.
But your catch that it doesn't release the lock is a good one will check
that out.
But yes you have a problem because what it tries to serialize is not
supposed to be serialized.
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision
But cache is for caching things that are expensive to get, but when they
are evicted from cache, they can be restored. When you remove wicket
page (or better said page version) for wicket 2nd level store, it can
not be restored.
As for performance, the gain could be in finer grained
Well, I was using a release from the previous days and that is why it wasn't
swallowing the Exception (I have since verified that I am using the latest
SNAPSHOT from source, not wicketstuff repo). But I still experience HUGE
delays when it goes wrong (I just can't see why now, which is actually
Everything can be restored. Because everything is on disk.
yes but synching should be looked at. i think i go with jonathans idea that
i already was thinking of.
use a concurrent hashmap and then one entry is a list for one session.
then concurrency should be almost gone between sessions.
johan
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision 507527)
We're at 507700 now. Could you please update and see how that works?
Wicket defaults on normal serialization again and has improved
diagnostics for serialization problems.
If you want to help us make custom
Johan Compagner wrote:
But yes you have a problem because what it tries to serialize is not
supposed to be serialized.
Well, if it makes a difference, I do have a Hibernate session stored on the
Page object (trying to use DataBinder Converstational session support). So,
I could see why it
Eelco Hillenius wrote:
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision 507527)
We're at 507700 now. Could you please update and see how that works?
Wicket defaults on normal serialization again and has improved
diagnostics for serialization problems.
If I make
But that is wrong. Use the detach() methods to clean up that.
You shouldn't keep any database related things in the session if possible.
johan
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Johan Compagner wrote:
But yes you have a problem because what it tries to serialize is not
What kinds of things do you want to know about and how should I tell you?
Just post the problem as I did here or is there a specific thread you want
it posted to?
post the problems here, i will try to fix them asap.
johan
he is using long conversations, so he keeps the hib session and then
reconnects it on the next request. at least thats what it sounds like
-igor
On 2/14/07, Johan Compagner [EMAIL PROTECTED] wrote:
But that is wrong. Use the detach() methods to clean up that.
You shouldn't keep any database
Johan Compagner wrote:
But yes you have a problem because what it tries to serialize is not
supposed to be serialized.
Well, if it makes a difference, I do have a Hibernate session stored on the
Page object (trying to use DataBinder Converstational session support). So,
I could see
i wonder if it wouldn't pay to stop and refactor this a little.
besides repackaging, it seems like there is really a sessionstore
which stores sessions and a pagestore which stores pages for
a given session (that independently synchronized sublist).
i'm not sure that's the best thing, but i am
no there is not a page store per session
There is only one sessionstore and one pagestore per application.
what should be refactored a bit is the actual saving
Previously it was really a simple thing that serialized the page and saved
to disk
Now those 2 operations are really divided and a
On 2/14/07, Johan Compagner [EMAIL PROTECTED] wrote:
Its EXACTLY a cache
What isn't a cache is ehcache
At least not in my point of view
A cache is something you cache something as good as you can but it can be
gone at anytime.
ehcache is not a cache. Its a in memory predefined size list.
right. i wasn't talking about instances. only interfaces and method
calls. conceptually, if you have a session that is a store of pages
(the page map). you can ask the session for an interface that gives
you pages. how that's implemented is probably as you suggest.
although decoupling these
On 2/14/07, Johan Compagner [EMAIL PROTECTED] wrote:
no there is not a page store per session
There is only one sessionstore and one pagestore per application.
Yeah. My first implementation was actually per session, so that's
where we came from. That didn't work at it wasn't possible to support
right. i wasn't talking about instances. only interfaces and method
calls. conceptually, if you have a session that is a store of pages
(the page map). you can ask the session for an interface that gives
you pages.
But then you need to have a session first, and where to get that from
is
Hi,
I have to show a table where the number of columns and their titles are
not known at design time. They're calculated at runtime.
Are there any hints how I can approach this problem?
Thanks,
Ingo.
-
Take Surveys. Earn
http://wicketstuff.org/wicket13/repeater/?wicket:bookmarkablePage=Awicket.examples.repeater.DataTablePage
-igor
On 2/14/07, Ingo Adler [EMAIL PROTECTED] wrote:
Hi,
I have to show a table where the number of columns and their titles are
not known at design time. They're calculated at
ok. if you say so. i don't know the details here.
Eelco Hillenius wrote:
right. i wasn't talking about instances. only interfaces and method
calls. conceptually, if you have a session that is a store of pages
(the page map). you can ask the session for an interface that gives
you
I also experience the same problem after upgrade 1.2.3 - 1.2.5
wicket-ajax.js is missing after several ajax actions.
Still investigating what's going on...
On 2/12/07, Niels Bo [EMAIL PROTECTED] wrote:
After switching from 1.2.4 to 1.2.5, I am seeing a lot of JavaScript
errors
Object expected
there is a vote on dev to commit a patch that is supposed to fix this. give
it a try and let me know if it worked for you.
-igor
On 2/14/07, Ingram Chen [EMAIL PROTECTED] wrote:
I also experience the same problem after upgrade 1.2.3 - 1.2.5
wicket-ajax.js is missing after several ajax
66 matches
Mail list logo
