please check this out: http://syca.4java.ca/gmap//iulianOn 9/7/06, Erik van Oosten <
[EMAIL PROTECTED]> wrote:Nice.Is there an example application running somewhere?
Erik.Frank Bille schreef:> There is something in Wicket-Stuff:>> http://svn.sourceforge.net/viewvc/wicket-stuff/trunk/wicket-con
That is a very very nice implementation.
Thanks Iulian,
Erik.
Iulian Costan schreef:
> please check this out: http://syca.4java.ca/gmap/
>
> /iulian
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
-
U
Should I provide some other forms of code in order to get help?
No developer using wicket faced similar problem? Maybe my approach is
not correct?
Regards,
shumbola
> All,
> I've got this simple use case:
> On compose e-mail page click on some button that shows list of users
> in modal window a
Thx,Currently we release the pages only at the end of the request anyway. So what we can dois just remove everything out of the used map for the current thread always after the requestand call notify all..
Then it should always be cleanup.johanOn 9/8/06, Eelco Hillenius <[EMAIL PROTECTED]
> wrote:I
Are there any method to degrade the all the wicket AJAX
component to a normal request? It may be useful for debugging.
I am using jetty http server 5.0, wicket 1.2.2 and jetty launcher
to develop and test my project, but after I changed my java
source code, the server cannot updated until I restar
What I do to hot deploy in Eclipse is setting configure to DEVELOPMENT in init:...class MyApplication extends WebApplication {... init() {... configure(DEVELOPMENT);... }
...}This gives you hot update of resources (HTML). For java code run the jetty launcher as debug. Debug gives you h
Frank frank!this is bad advice!don't call the configure method yourself. That shouldn't be done.Because configure m ethod is always already calledWhat you should do is set in through the web.xml in deployment mode (or developerment if you always want to be in development mode)
But if you have it in
On Sep 7, 2006, at 3:09 PM, Erik Brakkee wrote: Andrew Lombardi wrote: Erik, I had similar issues with the DatePicker for various reasons. After some help from Nick and Igor I built a 3 dropdown component for choosing date similar to what you describe below. Check out my blog entry for detai
I am using the DatePicker (wicket.extensions.markup.html.datepicker)
Panel on one of my forms. I want it to start out disabled so I called
setEnabled(false) on the object. However, I can still click on the
DatePicker icon.
Admittedly, I am still very new to this,
but after looking at the code
But if you have two threads working on that page, the first thread to
end would also remove the page reference for the second?
Eelco
On 9/8/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> Thx,
> Currently we release the pages only at the end of the request anyway. So
> what we can do
> is just
billen-IgorOn 9/8/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
Frank frank!this is bad advice!don't call the configure method yourself. That shouldn't be done.Because configure m ethod is always already calledWhat you should do is set in through the web.xml in deployment mode (or developerment if
On 9/8/06, Chan Man Kam <[EMAIL PROTECTED]> wrote:
Are there any method to degrade the all the wicket AJAXcomponent to a normal request? It may be useful for debugging.there is no way to "degrade" this off some switch. wicket provides what we call ajax "fallback" components, these components use aj
yes. datepicker doesnt support the disabled attribute yet. if you would like you can create a patch and send it in. the core team will be concentrating on replacing it because of license issues with what is now in wicket-contrib-datepicker (about 20% there). help is always welcome.
-IgorOn 9/8/06,
you cant have two threads working on a page - thats the whole point of syncing :)-IgorOn 9/8/06, Eelco Hillenius <
[EMAIL PROTECTED]> wrote:But if you have two threads working on that page, the first thread to
end would also remove the page reference for the second?EelcoOn 9/8/06, Johan Compagner <
> I'm having trouble with porting this code into wicket. For the first
> time when one clicks the "..." button, modal dialog comes up. For the
> following clicks, IE opens up both a new window and the modal dialog
> with the same contents.
> With FF it works as expected.
>
> I suspect, it has somet
Yes smartass, of course. That's why the wait (on session) is there.
However, if you look at this:
Thread t = (Thread)usedPages.get(id);
while (t != null && t != Thread.currentThread())
{
try
I didn't propose that completely i think about doing this Thread t = (Thread)usedSession.get(this); // See now 'this' instead of the page idwhile (t != null && t !=
Thread.currentThread()){try
17 matches
Mail list logo
