Requirements for a progress bar in a file upload form
Hi, I built a form in Wicket, in which a file can be uploaded to the server. Furthermore, to show the progress of uploading I also built in a progress bar. The problem now is that that progress bar does not work. I do not know what I forgot to implement and/or what I did. I think I forgot something. My question is: What are the requirements for the working of a progress bar in a form for uploading a file? Thanks for your help in advance! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Requirements-for-a-progress-bar-in-a-file-upload-form-tp4661935.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
CSS include order
Is there a quick/simple way to ensure that our site-wide CSS is included last (as included in our BasePage.html section), after all other Components have contributed their CSS files? N
Re: Jetty Gzip Compression
See https://issues.apache.org/jira/browse/WICKET-5392
On Fri, Nov 30, 2012 at 5:11 PM, Martin Grigorov wrote:
> Try with wget/curl client instead.
> I meant "text/javascript" ..
>
>
> On Fri, Nov 30, 2012 at 4:08 PM, Nick Pratt wrote:
>
>> Ive stepped through the GzipFilter, and things look to be processed
>> through
>> the Gzip compression, but only my welcome.html page is returned as gzipped
>> - all the .css and .js resources do not have a gzip Content-Encoding set
>> on
>> them.
>>
>> Just to clarify, did you really mean "text/application" instead of
>> "text/css" and "application/javascript" ?
>>
>> N
>>
>>
>> On Fri, Nov 30, 2012 at 3:45 AM, Martin Grigorov > >wrote:
>>
>> > Hi,
>> >
>> > The gzip filter should be before Wicket filter. This way it has the
>> chance
>> > to manipulate the response generated by Wicket.
>> > Wicket just calls httpServletResponse.setContentType("text/application")
>> > and httpServletResponse.write(someStringWithJS).
>> > GZipFilter's job is to change the content type and gzip the JS string.
>> > I recommend you to put a breakpoint in GZipFilter and see what happens.
>> >
>> >
>> > On Thu, Nov 29, 2012 at 8:30 PM, Nick Pratt wrote:
>> >
>> > > Ive enabled Gzip compression via the Jetty filter for my application
>> > (Jetty
>> > > v6 and v8).
>> > > Based on Chrome Dev Tools and Firebug in Firefox, my .js and .css
>> files
>> > are
>> > > not being compressed (browser states in the request that it will take
>> > gzip
>> > > response), although text/html is, and Im trying to understand why.
>> > >
>> > > Ive got the mimeTypes configured in the GzipFilter servlet,
>> minGzipSize
>> > > defaults to 0 bytes.
>> > >
>> > > In Wicket 6, is there anything going on with the resources that would
>> > > prevent Jetty's GzipFilter from working?
>> > >
>> > > Ive tried placing the filter both before and after the WicketFilter.
>> > >
>> > > Chrome's PageSpeed analyzer also thinks most of my larger JS files are
>> > not
>> > > compressed (Ive been looking at the Response headers)
>> > >
>> > > Any thoughts?
>> > >
>> > > N
>> > >
>> >
>> >
>> >
>> > --
>> > Martin Grigorov
>> > jWeekend
>> > Training, Consulting, Development
>> > http://jWeekend.com
Re: AW: set session-timeout
On Wed, Oct 23, 2013 at 12:35 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> AFAIK you can specify the session timeout in your web.xml or in your
> container. I don't see why Wicket should get involved in that, other
> than change the session timeout for logged in users (i.e. after they
> successfully authenticated with your application), or special users
> (administrators with limited session time, etc). In those cases you
> already have a bound session, and you can use the previous call. If
> you want to specify session timeout for all users, then do it in your
> deployment descriptor.
>
Christoph's first message says: Now I want to make the time until the
application expires *configurable*
>
> http://stackoverflow.com/questions/15382895/session-timeout-in-web-xml
>
> Martijn
>
> On Wed, Oct 23, 2013 at 7:23 AM, Martin Grigorov
> wrote:
> > On Wed, Oct 23, 2013 at 2:36 AM, Joachim Schrod wrote:
> >
> >> On 10/22/13 15:32, Martin Grigorov wrote:
> >> > On Tue, Oct 22, 2013 at 4:27 PM, Joachim Schrod
> wrote:
> >> >
> >> >> On 10/22/13 10:34, christoph.ma...@t-systems.com wrote:
> >> >> > If I do this in my WicketApplication class, in the init()
> >> >> > method I get java.lang.reflect.UndeclaredThrowableException.
> >> >> > But if I add this to my base page it works. Is there any
> >> >> > possibility to do this in the WicketApplication class?
> >> >>
> >> >> You have to redefine WebApplication#newSession().
> >> >>
> >> >> It can't be done in init(), as no session exists yet. And you must
> >> >> set the Session timeout for each new session anew.
> >> >>
> >> >> Without having tried it, code like
> >> >>
> >> >> @Override
> >> >> public Session newSession(Request request, Response response) {
> >> >> Session session = super.newSession(request, response);
> >> >>
> >> >>
> >> >>
> >>
> ((ServletWebRequest)request).getContainerRequest().getSession().setMaxInactiveInterval(TIMEOUT);
> >> >>
> >> >
> >> > ALARM!
> >> > getSession() is the same as getSession(true). I.e. it will create a
> new
> >> > http session for each and every http request, even for static
> resources.
> >> >
> >> > Wicket creates Wicket Session when Session.get() is used, but creates
> >> Http
> >> > Session only when wicketSession.bind() is called.
> >>
> >> Interesting to hear; I'd have thought that works. Tricky thing,
> >> that. As I wrote, I didn't try the code; I just copied the access
> >> to HttpSession from the posts below.
> >>
> >> But, since wicketSession.bind() is final, one cannot subclass
> >> Session and redefine it either, to set the timeout there. (Much too
> >> many methods of Wicket classes are final, without really good
> >> reason; I copy them to my applications making the methods non-final
> >> much too often. :-( )
> >>
> >
> > If you override bind() and do something wrong then the functionality will
> > break completely.
> >
> >
> >>
> >> Martin, what would you propose to be the hook that allows to
> >> establish a different session timeout application-wide within your
> >> Java application? I hadn't had yet that case, web.xml suffices by
> >> now, but it would be good to know for the future.
> >>
> >
> > It is much better from framework point of view to give you a hook:
> >
> >
> org.apache.wicket.session.ISessionStore#getBindListeners().add(myListener)
> >
> >
> >>
> >> Cheers,
> >> Joachim
> >>
> >> >> return session;
> >> >> }
> >> >>
> >> >> should work. Maybe check that request is really a
> >> >> ServletWebRequest. (This is also a good place to set the locale.)
> >> >>
> >> >> HTH,
> >> >> Joachim
> >> >>
> >> >> >
> >> >> > -Ursprüngliche Nachricht-
> >> >> > Von: francois meillet [mailto:francois.meil...@gmail.com]
> >> >> > Gesendet: Montag, 21. Oktober 2013 16:34
> >> >> > An: users@wicket.apache.org
> >> >> > Betreff: Re: set session-timeout
> >> >> >
> >> >> > HttpSession httpSession = ((ServletWebRequest)
> >> >> RequestCycle.get().getRequest()).getContainerRequest().getSession();
> >> >> > httpSession.setMaxInactiveInterval(timeOut);
> >> >> >
> >> >> > François
> >> >> >
> >> >> >
> >> >> > On Mon, Oct 21, 2013 at 4:12 PM, Martin Grigorov <
> >> mgrigo...@apache.org
> >> >> >wrote:
> >> >> >
> >> >> >>
> >> >> >>
> >> http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/a
> >> >> >> pi/javax/servlet/http/HttpSession.html#setMaxInactiveInterval(int)
> >> >> >>
> >> >> >>
> >> >> >> On Mon, Oct 21, 2013 at 4:44 PM,
> >> wrote:
> >> >> >>
> >> >> >> > Hello,
> >> >> >> >
> >> >> >> > in my application i have set the errorpage for expired pages
> like
> >> >> this:
> >> >> >> >
> >> >> >> > getApplicationSettings().setPageExpiredErrorPage(Timeout.class);
> >> >> >> >
> >> >> >> > Now I want to make the time until the application expires
> >> >> configurable.
> >> >> >> > How can I do this? Can I set this in the
> WicketApplication.init()?
> >> --
> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: AW: set session-timeout
AFAIK you can specify the session timeout in your web.xml or in your
container. I don't see why Wicket should get involved in that, other
than change the session timeout for logged in users (i.e. after they
successfully authenticated with your application), or special users
(administrators with limited session time, etc). In those cases you
already have a bound session, and you can use the previous call. If
you want to specify session timeout for all users, then do it in your
deployment descriptor.
http://stackoverflow.com/questions/15382895/session-timeout-in-web-xml
Martijn
On Wed, Oct 23, 2013 at 7:23 AM, Martin Grigorov wrote:
> On Wed, Oct 23, 2013 at 2:36 AM, Joachim Schrod wrote:
>
>> On 10/22/13 15:32, Martin Grigorov wrote:
>> > On Tue, Oct 22, 2013 at 4:27 PM, Joachim Schrod wrote:
>> >
>> >> On 10/22/13 10:34, christoph.ma...@t-systems.com wrote:
>> >> > If I do this in my WicketApplication class, in the init()
>> >> > method I get java.lang.reflect.UndeclaredThrowableException.
>> >> > But if I add this to my base page it works. Is there any
>> >> > possibility to do this in the WicketApplication class?
>> >>
>> >> You have to redefine WebApplication#newSession().
>> >>
>> >> It can't be done in init(), as no session exists yet. And you must
>> >> set the Session timeout for each new session anew.
>> >>
>> >> Without having tried it, code like
>> >>
>> >> @Override
>> >> public Session newSession(Request request, Response response) {
>> >> Session session = super.newSession(request, response);
>> >>
>> >>
>> >>
>> ((ServletWebRequest)request).getContainerRequest().getSession().setMaxInactiveInterval(TIMEOUT);
>> >>
>> >
>> > ALARM!
>> > getSession() is the same as getSession(true). I.e. it will create a new
>> > http session for each and every http request, even for static resources.
>> >
>> > Wicket creates Wicket Session when Session.get() is used, but creates
>> Http
>> > Session only when wicketSession.bind() is called.
>>
>> Interesting to hear; I'd have thought that works. Tricky thing,
>> that. As I wrote, I didn't try the code; I just copied the access
>> to HttpSession from the posts below.
>>
>> But, since wicketSession.bind() is final, one cannot subclass
>> Session and redefine it either, to set the timeout there. (Much too
>> many methods of Wicket classes are final, without really good
>> reason; I copy them to my applications making the methods non-final
>> much too often. :-( )
>>
>
> If you override bind() and do something wrong then the functionality will
> break completely.
>
>
>>
>> Martin, what would you propose to be the hook that allows to
>> establish a different session timeout application-wide within your
>> Java application? I hadn't had yet that case, web.xml suffices by
>> now, but it would be good to know for the future.
>>
>
> It is much better from framework point of view to give you a hook:
>
> org.apache.wicket.session.ISessionStore#getBindListeners().add(myListener)
>
>
>>
>> Cheers,
>> Joachim
>>
>> >> return session;
>> >> }
>> >>
>> >> should work. Maybe check that request is really a
>> >> ServletWebRequest. (This is also a good place to set the locale.)
>> >>
>> >> HTH,
>> >> Joachim
>> >>
>> >> >
>> >> > -Ursprüngliche Nachricht-
>> >> > Von: francois meillet [mailto:francois.meil...@gmail.com]
>> >> > Gesendet: Montag, 21. Oktober 2013 16:34
>> >> > An: users@wicket.apache.org
>> >> > Betreff: Re: set session-timeout
>> >> >
>> >> > HttpSession httpSession = ((ServletWebRequest)
>> >> RequestCycle.get().getRequest()).getContainerRequest().getSession();
>> >> > httpSession.setMaxInactiveInterval(timeOut);
>> >> >
>> >> > François
>> >> >
>> >> >
>> >> > On Mon, Oct 21, 2013 at 4:12 PM, Martin Grigorov <
>> mgrigo...@apache.org
>> >> >wrote:
>> >> >
>> >> >>
>> >> >>
>> http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/a
>> >> >> pi/javax/servlet/http/HttpSession.html#setMaxInactiveInterval(int)
>> >> >>
>> >> >>
>> >> >> On Mon, Oct 21, 2013 at 4:44 PM,
>> wrote:
>> >> >>
>> >> >> > Hello,
>> >> >> >
>> >> >> > in my application i have set the errorpage for expired pages like
>> >> this:
>> >> >> >
>> >> >> > getApplicationSettings().setPageExpiredErrorPage(Timeout.class);
>> >> >> >
>> >> >> > Now I want to make the time until the application expires
>> >> configurable.
>> >> >> > How can I do this? Can I set this in the WicketApplication.init()?
>> --
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> Joachim Schrod, Roedermark, Germany
>> Email: jsch...@acm.org
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
-
To unsubscribe, e-mail: users-unsubscr.
