So I can try and cling on to some credibility at work wasn't
ajaxfallbackbutton only added in 1.3-beta3? I think we started working with
1.3-beta2. We only switched because my Swing/AWT version needed a method not
to be final which changed in beta3...
Even worse is that my tech lead/client/boss
On 9/1/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 9/1/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
i have just about zero swing experience :)
I think I have even less swing experience, I doubt my playground
experience from 25 years ago counts...
Martijn
I can testify that Wicket
For certain browsers (even IE6) the GZIP compression doesn't work. And if
you have a lot of javascripts (YUI, dojo, ...) it can make a difference.
-Matej
On 9/2/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
ermwhat exactly is the point of minifing AND gziping javascript or
anything else? if
please what is the recommended means to pass objects across two wicket
applications deployed in different WARs
i am thinking..
in Application A
ServletContext aContext = getWicketServlet().getServletContext();
aContext.setAttribute( object.forb, object);
in Application B
ServletContext
gzip and minifing *do* go together.
Here's a really great site that compares the different approaches.
http://compressorrater.thruhere.net/
minifing before gziping shows a considerable reduction in content size
(usually between 5-10 percent).
On 9/2/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
Dean Edwards also had a recent blog posting on this topic. His
recommendation is to compress and gzip content whenever possible.
http://dean.edwards.name/weblog/2007/08/js-compression/
On 9/2/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
gzip and minifing *do* go together.
Here's a really great
Your approach will not work, because the applications are in two different
contexts. So each one has separate servlet context.
Quite some time ago I had to deal with problem like this, I remember using
simple hessian based spring remoting which did it's job perfectly and was
quite easy to set up.
Hi all,
I'm using a tad of loadtime weaving in a very selective way: just a number
of classes in the service layer are being woven. For doing this, aspectj
weaver is installed as a java agent and configured to monitor no more than
the classes to advice. At the same time, some patterns are
are you deploying on tomcat? i think tomcat monitors the dir and if it sees
a change it reloads the webapp. you can canfig it not to do that.
-igor
On 9/2/07, Carlos Pita [EMAIL PROTECTED] wrote:
Hi all,
I'm using a tad of loadtime weaving in a very selective way: just a number
of classes
On a 1.2.6 app, I have a form at the bottom of a page. The page is
basically a forum thread page, with a long list of replies, etc, and you
reply at the bottom. I have a SubmitLink that allows you to add files, and
then it returns you to the form. Of course, it redirects back to a page
like
It will not help you append the hash to submitlink, as wicket redirect
afterwards. So the hash would be discarded anyway. Unfortunately we can't
just preserve it during request, as the hash doesn't leave the browser, so
it's not possible to get the actual value before issuing a redirect.
One
That is the customary message the reloading servlet shows after reloading
any changes. What is new is the output from the weaver above it. I guess the
reloading classloader has to reinstantiate itself in order to load new
versions of the same old classes, and this is notified to the weaver java
Recently I had to go back to doing a couple of Swing screens and all
those inner classes and model objects were a breeze...
+1
I have done a lot of swing coding before and for the past 6 months in
wicket. I can definitely say this-
Although wicket has a lot of swing like programming style in
Been trying to update to 1.3 and encountered some problems with
SubmitLink.
Before, SubmitLink extended Button, so there were no problems with
forms. SubmitLinks could be used interchangeably with Buttons, and life
was good.
Now, SubmitLink implements IFormSubmittingComponent, so it's breaking
Instead of using wantOnSelectionChangedNotifications you could add an
AjaxEventBehavior or AjaxFormSubmitBehavior on onchange, depending on
whether you want the form to be processed or not.
wantOnSelectionChangedNotifications is a bit strange in that it uses
normal javascript to submit the form
15 matches
Mail list logo
