Re: 5.4 Upload / Long Response Issue?

More information: When running from Terminal with "mvn jetty:run" or from within Eclipse using the M2E plugin (Run or Debug mode), it will create extra threads. When running from within Eclipse using RunJettyRun (Run or Debug mode), no extra threads are created and it works perfectly. Could be t

Re: 5.4 Upload / Long Response Issue?

I can try Tomcat, but i'll be a day or two or so before I can get to that. mrg On Thu, Aug 28, 2014 at 3:35 PM, Lance Java wrote: > Totally weird, can you try deploying to tomcat? It's worth a try to see if > an issue with jetty. > On 28 Aug 2014 19:36, "Michael Gentry" wrote: > > > Hi agai

Re: Unit test component with request parameter

Looks like you've put a lot of thought into your urls. > It would end up looking something like this. domain.com /category/make/$N/$N/$N/$N/$N/$N/$N/$N/$N/$N/brown

Re: Unit test component with request parameter

On Thu, 28 Aug 2014 16:27:20 -0300, George Christman wrote: Your absolutely correct, context URLs are much better for SEO than request parameters. I tend to use both at the same time, example domain/category?make=ford, category being the context. I think what you've done is a cool idea, h

Re: 5.4 Upload / Long Response Issue?

Totally weird, can you try deploying to tomcat? It's worth a try to see if an issue with jetty. On 28 Aug 2014 19:36, "Michael Gentry" wrote: > Hi again Lance, > > 1) No proxy. Directly connecting to Jetty @ http://localhost:6789/ > > 2) No other filters. I'm using Tapestry's IOC for servi

Re: Unit test component with request parameter

Your absolutely correct, context URLs are much better for SEO than request parameters. I tend to use both at the same time, example domain/category?make=ford, category being the context. I think what you've done is a cool idea, however with the amount of filters that we will end up having, it would

Re: 5.4 Upload / Long Response Issue?

Hi again Lance, 1) No proxy. Directly connecting to Jetty @ http://localhost:6789/ 2) No other filters. I'm using Tapestry's IOC for services and trying to keep things lean. FWIW, when I dropped the file in as a unit test, it would import just fine using the T5 service without spawning ext

Re: 5.4 Upload / Long Response Issue?

While not the same problem, I’ve had issues uploading even small files to Tapestry on Tomcat when behind a load balancer. Eliminating the load balancer solved the problem. Not really a Tapestry problem, I’d suspect, but possibly related. Norman Franke Answering Service for Directors, Inc. www.m

Re: Unit test component with request parameter

> I believe you were the one who use push me away from @Persist Lol... sounds like me :) I'm no SEO guru but I think keywords in the URL score better than request parameters. You might be interested in this recent feature I added to @PageActivationContext https://issues.apache.org/jira/browse/TAP

Re: 5.4 Upload / Long Response Issue?

1.Is your app sitting behind a proxy? (eg apache?). 2. Are there any other servlet filters we should know about? (eg spring?)

Re: 5.4 Upload / Long Response Issue?

Hi Lance, All 3 browsers issue a single request. The second thread and onValidate/onSuccess occur 30 seconds after the original upload using all 3 browsers (and repost/redeliver the original payload it seems, since the complete XML file is available to the new thread(s)). Thanks, mrg On Thu,

Re: Unit test component with request parameter

Yup you got it :) I believe you were the one who use push me away from @Persist and build stateless apps lol. On Thu, Aug 28, 2014 at 12:24 PM, Lance Java wrote: > I've been making assumptions without viewing code :) Up until now I've been > thinking it was an AJAX update. > > I'm now thinking

Re: Unit test component with request parameter

I've been making assumptions without viewing code :) Up until now I've been thinking it was an AJAX update. I'm now thinking you're doing a redirect after post and you're using request parameters to pass the values (avoiding @Persist and having bookmarkable urls). Sounds fine to me. The other opt

Re: Unit test component with request parameter

Wouldn't you still need to set the parameters to build the URL though? We just need to be sure the filters remain in the URL so that the searches can be book marked and indexed by search engines. On Thu, Aug 28, 2014 at 10:46 AM, Lance Java wrote: > > Im not sure I understand the differences be

Re: 5.4 Upload / Long Response Issue?

Strange? Can you open up the network traffic in your browser's dev tools and see the httptraffic? If there's 2 requests, can you copy / paste the request headers?

Re: Unit test component with request parameter

> Im not sure I understand the differences between field values and event parameters field values - What I meant here was using a and binding properties to TextField and Select etc. event parameters - eg: onMyEvent(String param1, String param2, ...) Have you seen the filter demo of the observe pl

5.4 Upload / Long Response Issue?

Hi everyone, I'm currently using 5.4B6 and we are doing uploads of XML data (using the standard Tapestry Upload/UploadFile mechanism -- no multi-file AJAX/etc extensions). When we upload a small file, it processes just fine, but on a larger file (which takes several minutes to process), multiple

Re: Lots of issues being closed

On Wed, 27 Aug 2014 22:10:42 -0300, Howard Lewis Ship wrote: I'm very interested in getting 5.4 out the door; So am I. there's still a number of serious issues barring the way, and the backlog of bugs is proving to be a real impediment. We could tag in JIRA this bugs so committers and

Re: Unit test component with request parameter

Ah okay, so I guess what you are suggesting is similar to what I originally had. I'm not sure I understand the differences between field values and event parameters. I just need to be able to read parameters from the URL. On Thu, Aug 28, 2014 at 9:08 AM, Lance Java wrote: > I'd do something lik

Re: Unit test component with request parameter

I'd do something like this to separate web from service and keep it testable. @Inject private MyService myService; public void doSearch(@RequestParam String filter1, @RequestParam Integer filter2) { SearchFilter filter = new SearchFilter(); filter.setFilter1(filter1); filter.setFilter2(f

Re: Unit test component with request parameter

@RequestParameter will only work for page and component events. A robust service layer should never reference the Request or any other web objects so you should really pass them through to the service. Perhaps you want to encapsulate multiple values in a bean which can grow over time without chang

Re: Unit test component with request parameter

Hi lance, I've been working on simplifying the design, so with that said the service and page design is a little different from what I have checked in. My goal is to remove all the request parameters from the page and put them directly into the service so that I'm not having to pass them all over t

Re: Unit test component with request parameter

An even simpler approach is to grab the request parameter in the page / component and pass through to a service. Then forget about testing the page / component and focus on the service. This is what I usually do. A couple of lines of code go untested but my api is better and tests are much easier

Re: Unit test component with request parameter

Hi George, you're lucky I know your architecture :) You should include a snippet of the test module for completeness. You'll notice the request is actually a mockito proxy setup in the @Before of the test (in the test module). Can you use @RequestParameter in the event (instead of request.getPara