I just tried this jdk:
http://www-128.ibm.com/developerworks/java/jdk/eclipse/
This is J9 from IBM which is java5 jdk as far as i can see.
And what that jdk can do is method additions!
In my first simple test i could rename a method in a class and re factor all
the calls to it. And the next
On Tue, 2006-11-21 at 15:10 -0800, Eelco Hillenius wrote:
On 11/21/06, Alexei Sokolov [EMAIL PROTECTED] wrote:
Actually,
There is a sysdeo tomcat plugin for eclipse which can be configured with a
special 'devloader' classloader. With this config you'll see changes right
after you saved
DevLoader doesn't do that work. DevLoader is there for you to be able to
have a Web application of your project that has libs and references to
other projects
and see those if they where in the WEB-INF/lib dir.. We replace the
classloader of tomcat to be able to load jars from other places.
also what does this feature have to do with URLS?
On 11/21/06, cowwoc [EMAIL PROTECTED] wrote:
Two questions about:
http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html
1) How did they get instantaneous page reloads working?
2) How did they get their URLs to remain
Nice URLS?
Well.. I don't know, to me it doesn't look that great. I mean it seem to
miss an information. What happens if you open the page in multiple
browser windows? If the URL is same, how
will tapestry reconstruct the data?
And also, does the Tapestry 5 finally supports dynamically
heh, if I had to choose between:
http://www.google.com/Start.html
and
http://www.google.com/Main/Start?wicket:interface=:0::
I'd choose the first time time and time again. There is the interface
part which I'd love to hide from users (they shouldn't ever be
explicitly
Don't underestimate the power of viral marketing for the Wicket
framework... having Wicket being part of every URL on the planet would
generate major mindshare.
Martijn
On 11/22/06, cowwoc [EMAIL PROTECTED] wrote:
heh, if I had to choose between:
http://www.google.com/Start.html
Especially if it was appended to www.google.com :P
Frank
On 11/22/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Don't underestimate the power of viral marketing for the Wicket
framework... having Wicket being part of every URL on the planet would
generate major mindshare.
Martijn
On
when do you choose an url?
urls only have to be nice when they are exported like links you click on
in external resources, mails for example
internally it doesn't matter to much for the webapplications you make with
wicket.
johan
On 11/22/06, cowwoc [EMAIL PROTECTED] wrote:
heh,
-
From: Martijn Dashorst [EMAIL PROTECTED]
Date: Wed, 22 Nov 2006 14:42:00
To:wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Tapestry 5 instantaneous reloads
Don't underestimate the power of viral marketing for the Wicket
framework... having Wicket being part of every URL
Frank Bille wrote:
Especially if it was appended to www.google.com http://www.google.com :P
Having just been to an 'open source jam' at Google's office last week
(where I met Al), they would barely state what languages they used, let
alone disclose what frameworks they use. So, in Google's
Make /wicket the default mapping, and most people will never change it :-)
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Upayavira [EMAIL PROTECTED]
Date: Wed, 22 Nov 2006 14:29:06
To:wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Tapestry 5
Again and again.
What would do if you open the start.html page in two browsers windows?
Or don't your users do that? The additional information in url is not
there for fun. There is a good reason for that.
And give us some time, after the refactor planed for 2.0 it should be
possible to get
Again and again.
What would do if you open the start.html page in two browsers windows?
thats the wrong question! - the question would be: what behaviour would the
enduser expect when he uses 2 browserwindows/tabs for 1 website?
I found out that most enduser just do this, to keep a site as a
you can already get rid of the wicket prefix if you want.
copy paste this class:
change the static final namespace variable.
johan
On 11/22/06, Matej Knopp [EMAIL PROTECTED] wrote:
Again and again.
What would do if you open the start.html page in two browsers windows?
Or don't your users do
hmmm forgot to copy paste myself :)
the class in question is WebRequestCodingStrategy
On 11/22/06, Johan Compagner [EMAIL PROTECTED] wrote:
you can already get rid of the wicket prefix if you want.
copy paste this class:
change the static final namespace variable.
johan
On 11/22/06,
I think you're missing a very important use-case. I created a Wicket
webapp at work, what happens on a weekly basis is that someone sees
something he wants to discuss so he copy/pastes the URL from his browser
into an email. Non-nice URLs shouldn't even be visible for people to
mistakenly
if you want to support that
always redirect to a Bookmarkable page class
setResponsePage(MyPage.class)
setRedirect(true)
johan
On 11/22/06, cowwoc [EMAIL PROTECTED] wrote:
I think you're missing a very important use-case. I created a
Wicket
webapp at work, what happens on a weekly
But this is something completely different. Cart is shared between
pages, usually stored in session. Cart is not specific for every pages.
But if you have a tabbed panel in a page, you want to have one tab
opened in one window and another tab opened in second window. That's
what users require.
If you can't copy/paste that additional information anyway (because
you'll get a Page Expired) then it shouldn't be visible at all so people
don't even make the mistake of including it.
I agree with you that Wicket somehow has to know that window1 has a
different state than
Are you even sure tapestry is doing that?
-Matej
cowwoc wrote:
If you can't copy/paste that additional information anyway (because
you'll get a Page Expired) then it shouldn't be visible at all so people
don't even make the mistake of including it.
I agree with you that Wicket
I was just thinking about that now...
And suddenly i have a question: Why do we have the new window/tab check
again in the page?
I couldn't care less anymore about a page being in 2 browsers (and in the
same pagemap)
Just be sure that versioning works so if the page is changed in one window
it
:[EMAIL PROTECTED] Im Auftrag
von Matej Knopp
Gesendet: Mittwoch, 22. November 2006 16:36
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] Tapestry 5 instantaneous reloads
But this is something completely different. Cart is shared
between pages, usually stored in session
I don't know about the check. IMHO it should be disabled by default. Now
that we have second level session store there's not need for that script
and multiple pagemap. No need at all.
-Matej
Johan Compagner wrote:
I was just thinking about that now...
And suddenly i have a question: Why
i could do that..
Just make a form post of every link
then store state in a special field (see 2.0 that has partial implementation
already)
If you refresh the browsers url then we have to have the static mounts (that
we talked about)
and the page for that class is found and rendered (or not
This is just ugly. And I'm not even sure it would work while preserving
current no-double-posts policy.
Imagine you're doing a form post now. After the post processed, wicket
makes redirects. But if you want to send the page id as post
information, you can't redirect! So you have two options.
yeah? and what happens when your component property is not a primitive?
are you then happy with
http://www.google.com/Start.html?param1=A98AS98AA8947A8947A8947A89478A97A94879A847A9879A8479A8479A847A9847A9487A4987A4987A498A749A8749A8479A84789A7498A7498A7498A47A9847A984789A7498A4
which would be
PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Igor
Vaynberg
Gesendet: Mittwoch, 22. November 2006 17:22
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] Tapestry 5 instantaneous reloads
i do it all the time. i am at some point in a webapp, i rightclick on a link
do open in a new
the classloader will still barf after certain situations i think.
when you add a new property for example and refresh a page, what happens?
a new instance of that component/page is created, but the property's value
is not in the url which might lead to some weird invalid state scenarios.
-igor
Really, what is the hangup on URLs anyway. Do you ever get stressed
out by seeing an URL like
http://www.amazon.com/s/ref=nb_ss_b/102-2078604-2484922?url=search-alias%3Dstripbooksfield-keywords=donkeyGo.x=0Go.y=0Go=Go
?
Eelco
On 11/22/06, cowwoc [EMAIL PROTECTED] wrote:
heh, if I had
I think you're missing a very important use-case. I created a Wicket
webapp at work, what happens on a weekly basis is that someone sees
something he wants to discuss so he copy/pastes the URL from his browser
into an email. Non-nice URLs shouldn't even be visible for people to
No. ONE part of the story is back button support. IN CASE you
are using the second level session store thing that is default for 1.3
and 2.0 now, we don't need that multi-window support. If you don't use
that, but e.g instead use the older page maps, you DO need it, as you
don't want one
Look, this discussion every time again is getting old. It has been
stated many times before: the difference between Wicket and many other
frameworks is that Wicket's URL are 'safe' *by default*; if you want
them to be public (bookmarkable), you have to be explicit about it.
With other frameworks,
Again, I refer you to Tapestry. Obviously I wouldn't want the kind of
URL you pasted but if you look at Tapestry's screencast they don't add
*anything* to the URL. Now, it could very well be that this is something
specific to small examples and does not work for bigger ones but it
could
you dont see the ugly because the screencast is a freaking helloworld app
and the properties used are primitives.
its so typical, someone puts out a screencast of helloworld with zero
complexity because it is a helloworld and everyone jumps up and down
screaming: oh how cool is that?
i want to
When Wicket 2.0 is released and I can use bookmarkable forms I will
quite gladly use it. I am simply pointing out the problems with the
current design. BTW, Wicket 2.0 does completely solve this, right?
Gili
Eelco Hillenius wrote:
I think you're missing a very important
if they dont add anything to the url then the url might look pretty but two
people coming to it will see different things because all the info is stored
in session.
so it makes what you want even worse. at least with wicket you get a page
expired page, with tapestry you get a page but you see
Eelco, one of the points I tried making (and seemed to have gotten lost
in the loop) is this:
1) User is viewing a non-bookmarkable page
http://www.google.com/Main/Start?wicket:interface=:0:: but wicket
displays http://www.google.com/Start in his URL bar instead (not sure if
this is
For example, if you go to Amazon, add some book to your cart do
checkout and copy/paste that the URL into someone else's browser it'll
recover gracefully by redirecting you to some page displaying something
related to cart (maybe it displays your cart as empty) or some page
displaying
Thank you :) So assuming bookmarkable forms are 100% solved in Wicket
2.0 I think this covers all bases.
Gili
Eelco Hillenius wrote:
For example, if you go to Amazon, add some book to your cart do
checkout and copy/paste that the URL into someone else's browser it'll
recover
Two questions about:
http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html
1) How did they get instantaneous page reloads working?
2) How did they get their URLs to remain nice even though the
underlying state is changing?
and what is the implications for Wicket?
On 11/21/06, Alexei Sokolov [EMAIL PROTECTED] wrote:
Actually,
There is a sysdeo tomcat plugin for eclipse which can be configured with a
special 'devloader' classloader. With this config you'll see changes right
after you saved your java source. But it won't help with nice urls ;)
That's
Actually,
There is a sysdeo tomcat plugin for eclipse which can be configured with a
special 'devloader' classloader. With this config you'll see changes right
after you saved your java source. But it won't help with nice urls ;)
Alex
On 11/21/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
@lists.sourceforge.net
Betreff: [Wicket-user] Tapestry 5 instantaneous reloads
Two questions about:
http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html
1) How did they get instantaneous page reloads working?
2) How did they get their URLs to remain nice even though
44 matches
Mail list logo
