Re: problem with component

2010-02-04 Thread Thiago H. de Paula Figueiredo
On Thu, 04 Feb 2010 11:37:05 -0200, Jan Jirout wrote: Hi, Hi! I'll try change implementation of ComponentEventLinkEncoderMethodAdvice, it seems to me that it could help. I don't fully understand T5 so I don't know if it's bug or not. What do you think? This is a bug. Please file a JIRA

Re: problem with component

2010-02-04 Thread Jan Jirout
Hi, thanks for looking at this, it really helps me. I think that I found place where is forForm changed to wrong value, let me describe it: It seems that LinkImpl is correctly created in ComponentEventLinkEncoderImpl at 194 with forForm=true. Next is ComponentEventLinkEncoderMethodAdvice#adv

Re: problem with component

2010-02-02 Thread Thiago H. de Paula Figueiredo
On Tue, 02 Feb 2010 03:22:38 -0200, Josh Canfield wrote: I should add that SimpleRequestWrapper fakeRequest = new SimpleRequestWrapper(request, link.toAbsoluteURI()); comes from ComponentEventLinkEncoderMethodAdvice#rewriteIfNeeded I can't recall is there's a JIRA for that. If not, plea

Re: problem with component

2010-02-01 Thread Josh Canfield
I should add that > SimpleRequestWrapper fakeRequest = new SimpleRequestWrapper(request, > link.toAbsoluteURI()); comes from ComponentEventLinkEncoderMethodAdvice#rewriteIfNeeded On Mon, Feb 1, 2010 at 9:20 PM, Josh Canfield wrote: > Ok, I found the problem. > The form action is created like so

Re: problem with component

2010-02-01 Thread Josh Canfield
Ok, I found the problem. The form action is created like so: void beginRender(MarkupWriter writer) { Link link = resources.createFormEventLink(EventConstants.ACTION, context); It then pulls the query parameters from the link and sticks them into hidden fields. The problem is that when

Re: problem with component

2010-02-01 Thread Kristian Marinkovic
if you rewrite the URL you have to take care of the context yourself. you could use the PageRenderLinkSource service to create a Link with the desired context and return the generated url : Link link = pageLinkSource.createPageRenderLinkWithContext( DocumentExportPage.class, "my","cont

Re: problem with component

2010-01-30 Thread Josh Canfield
> I tried to use following code: > >public Request process(Request request, URLRewriteContext context) { >return new SimpleRequestWrapper(request, request.getPath()); >} > > When I use this code then context of component event is even lost. I didn't > find way how to create Simp

Re: problem with component

2010-01-30 Thread Jan Jirout
Hi, thanks for answer. In my real application I change just pieces of path but it didn't work. I tried to use following code: public Request process(Request request, URLRewriteContext context) { return new SimpleRequestWrapper(request, request.getPath()); } When I use this

Re: problem with component

2010-01-30 Thread Thiago H. de Paula Figueiredo
On Sat, 30 Jan 2010 19:58:34 -0200, Jan Jirout wrote: Hi All, Hi! I have strange problem with URL rewriting. I'm changing path name in URLRewriterRule. In following way: public Request process(Request request, URLRewriteContext context) { return new SimpleRequestWr

Re: Problem with component Dialog with Internet Explorer and Tapestry 4.1.2

2007-04-02 Thread Jesse Kuhnert
You can try applying some of the style definitions from http://tapestry.apache.org/tapestry4.1/usersguide/clientside-validation.html It's all controllable via css so there has to be some combination that works. On 3/30/07, Lionel Touati <[EMAIL PROTECTED]> wrote: Hi All, The Dialog compone