Em Tue, 08 Dec 2009 22:33:40 -0200, Vangel V. Ajanovski
escreveu:
But, the bad thing is that here Thiago's solution does not help - with
it I get an Event.observe is not a function
And now it does not work even in IE.
This is a Prototype function, documented here:
http://www.prototypejs.o
I removed the submit button and it works indeed.
Thank you for the answer.
--
View this message in context:
http://old.nabble.com/Select-does-not-submit-form-on-change-tp26687467p26703632.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
On 09.12.2009 01:33, Vangel V. Ajanovski wrote:
>
> But, the bad thing is that here Thiago's solution does not help - with
> it I get an
> Event.observe is not a function
> And now it does not work even in IE.
>
>
Now I am replying to myself ;)
Of course it doesn't work - prototype is not au
Sorry, but there might be some problem with the mailing list, my message
was considered as a SPAM and first the text was removed from the
message, and the next time I got info that it was considered as SPAM.
I am sending the message again.
On 08.12.2009 02:47, Mite wrote:
> I have written this co
smime.p7s
Description: S/MIME Cryptographic Signature
Why don't you want to pass the page's context to the tab component? Isn't the
content of the tabs dependent on the value of the page's context?
On 09/12/2009, at 4:46 AM, kamiseq wrote:
> ok one more thing, my tabs are working great but let examine such a usecase
>
> 1)I have user page with a g
Yes, I agree with that Norman. That's sort of what I implied when I
said that I "always link to pages with initial context already set" -
i.e. the reverse works better - re-initialize the page if a specific
context is set. That's one way, what Howard suggests is another
(identify page internal link
I've put some comments into the issue itself.
On Tue, Dec 8, 2009 at 1:48 PM, Massimo Lusetti wrote:
> On Tue, Dec 8, 2009 at 4:03 PM, Howard Lewis Ship wrote:
>
>> Unfortunately, ThreadLocal.get()/remove() was buggy and not thread
>> safe in JDK 1.5.
>
> Do you actually mean 'is' not 'was' ?
>
On Tue, Dec 8, 2009 at 4:03 PM, Howard Lewis Ship wrote:
> Unfortunately, ThreadLocal.get()/remove() was buggy and not thread
> safe in JDK 1.5.
Do you actually mean 'is' not 'was' ?
Couldn't this be (re)written without using syncronized blocks?
--
Massimo
http://meridio.blogspot.com
On Mon, Dec 7, 2009 at 5:58 PM, Howard Lewis Ship wrote:
>
> I've been planning to add a simpler alternative to
> SessionStateObjects, an annotation that simply says "store this value
> in the session with this explicit key", to make coordinating a T5 app
> with a legacy app simpler.
>
It's alre
I implemented a somewhat similar approach for search using an even
more basic approach. Most of my search fields are @Persisted, but I
still needed a way to know when to reset the search dialog. I ended up
creating a new context parameter, consisting of the string "reset".
Every time I want
On Tue, Dec 8, 2009 at 10:59 AM, Howard Lewis Ship wrote:
> I've had to solve this problem for one of my clients as well and I
> think it's something that should go into the framework. The approach
> I took was to identify self-referential links (page render links that
> are to the same page they
I've had to solve this problem for one of my clients as well and I
think it's something that should go into the framework. The approach
I took was to identify self-referential links (page render links that
are to the same page they originate from) using an additional query
parameter. This allows T
Em Tue, 08 Dec 2009 16:23:37 -0200, ningdh escreveu:
Hi, Thiago
Hi!
What Kalle and I concern is the onActivate must come first before
onPassivate, so if page A links to page B, A must set the context of B
first, right?
In this case, onActivate() is not invoked, so A must invoke one or
Hi, Thiago
- Original Message -
From: "Thiago H. de Paula Figueiredo"
To: "Tapestry users"
Sent: Wednesday, December 09, 2009 2:09 AM
Subject: Re: Best practice for initializing page to default context
> Em Tue, 08 Dec 2009 15:49:15 -0200, Kalle Korhonen
> escreveu:
>
>> DH's app
On Tue, Dec 8, 2009 at 10:02 AM, ningdh wrote:
> I can't think of a better way not to involve the field name encoded.
Yes, I understand why you did it.
> And if you don't like the field name exposed, you can also customize the
> param name by setting the annotation value, such as
> @PageActivat
Em Tue, 08 Dec 2009 15:49:15 -0200, Kalle Korhonen
escreveu:
DH's approach looks interesting, but maybe a bit involving with field
names encoded to the url. Thiago, I know it's the recommended approach
but I'm just saying it doesn't strike me as the ideal approach.
The ideal solution always
I can't think of a better way not to involve the field name encoded.
And if you don't like the field name exposed, you can also customize the param
name by setting the annotation value, such as
@PageActivationUnit("cat")
private Category category;
Then the url is like /searchpage/cat-VALUE
I
On Tue, Dec 8, 2009 at 3:39 AM, Thiago H. de Paula Figueiredo
wrote:
> Em Tue, 08 Dec 2009 04:22:58 -0200, Kalle Korhonen
> escreveu:
>> and subsequently, if my page has multiple entry points, I typically
>> resort to implementing it in a single onActivate(EventContext
>> eventContext) operation
ok one more thing, my tabs are working great but let examine such a usecase
1)I have user page with a grid of a user list
2)when user is selected I rerender the page with context specified by grid
element
3)my url then is something like myapp/user/1 and the tab control is
displayed with 3 tabs (fo
At last. This way works.
This is the second time you get me out of the mud. :)
Thank you
--
View this message in context:
http://old.nabble.com/Select-does-not-submit-form-on-change-tp26687467p26697258.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
I will be more specific then.
What you need to do is:
- Use Firefox and Firebug (or some other request monitoring tool) to see
what happens when you select something in your select. Is any event trigered
in the browser. Is something sent to the server?
- Check on the server side if the page clas
On Tue, Dec 8, 2009 at 5:08 AM, Olle Hallin wrote:
> Hi!
>
> We are load testing our new high volume site before soft launch, and we have
> noticed that we have two sources of severe lock contention.
> Of 300 threads, in average 165 are waiting for one of these two locks.
>
> One is in ZipFile (ca
Of course, but since I am not very good at javassit, my implementation may be
ugly and a bit long. Anyone please consummate it.
Like PageActivationContext, I introduce an PageActivationUnitWorker.
The key part is to collect the param fields and add the param map to page class
in runtime. onActiva
JIRA https://issues.apache.org/jira/browse/TAP5-945 created
Olle Hallin
Senior Java Developer and Architect
olle.hal...@crisp.se
www.crisp.se
http://www.linkedin.com/in/ollehallin
2009/12/8 Thiago H. de Paula Figueiredo
> Em Tue, 08 Dec 2009 11:08:38 -0200, Olle Hallin
> escreveu:
>
> Hi!
>
Em Tue, 08 Dec 2009 11:08:38 -0200, Olle Hallin
escreveu:
Hi!
Hi!
Shall I file a JIRA issue, or have I missed something?
I'm no expert at concurrency, but please post it so the committers with
the required knowledge can take a look at it. ;)
--
Thiago H. de Paula Figueiredo
Independ
Hi!
We are load testing our new high volume site before soft launch, and we have
noticed that we have two sources of severe lock contention.
Of 300 threads, in average 165 are waiting for one of these two locks.
One is in ZipFile (caused by @IncudeJavaScriptLibrary("classpath:...")) and
the othe
yep
I am just after huge argument with my firend about tapestry and wishes vs
reality :)
now I understand and it makes some sense although I try to avoid @persist as
much as possible
and the main problem here is to define how user must use the page and
interact with it and what if session expires
Em Tue, 08 Dec 2009 08:40:34 -0200, Jan Jirout
escreveu:
Hi,
Hi!
I think that both problems are related to "name stripping", but I don't
know how to add new rules to this process. It seems to me, that "URL
rewriting" doesn't help at all.
URL rewriting is definitely the best solution
Em Tue, 08 Dec 2009 04:22:58 -0200, Kalle Korhonen
escreveu:
and subsequently, if my page has multiple entry points, I typically
resort to implementing it in a single onActivate(EventContext
eventContext) operation containing a big if-else clause.
That's the recommended way when you have a
Em Mon, 07 Dec 2009 21:38:17 -0200, kamiseq escreveu:
hi,
Hi!
I ve wrote simple component that renders link and handles event
triggered by
the link then it sets some value and should render that value.
the problem is that I get the value but then the value is lost as
tapestry redirects
Em Tue, 08 Dec 2009 09:18:59 -0200, Mite escreveu:
No, I just have the function:
void onSubmit() {
System.out.println("Value changed!");
}
Try using onSuccess() instead of onSubmit().
By the way, instead of relying on onchange="", use Prototype events:
Event.observe(
No, I just have the function:
void onSubmit() {
System.out.println("Value changed!");
}
which prints to console when a submit is made, but it does not print
anything when I change the value.
Are you using some debug tool to verify if a request is sent to the server?
Like firebug i
You're not giving us very much information to work with here...
Are you using some debug tool to verify if a request is sent to the server?
Like firebug in firefox? Are you getting a javascript error when you select
something?
On Tue, Dec 8, 2009 at 11:58 AM, Mite wrote:
>
> Thank you for the r
The only way I got this to work was via Javascript called from the
select to do the submit.
-Original Message-
From: Mite [mailto:mitemeis...@gmail.com]
Sent: 08 December 2009 10:58
To: users@tapestry.apache.org
Subject: Re: Select does not submit form on change
Thank you for the repl
Thank you for the reply.
It does not make any difference. Still the same result.
This is really bad. Trying to get to work an event on a select for a whole
day.
It is so much easier with .NET or only JavaScript and HTML.
Try
this.form.submit()
--
View this message in context:
http://old.n
Hi,
I have two probably related problems.
1) I have business object Article and User and also I have package
com.myapp.pages. Inside this package are placed pages Article and User.
Both of them works and contains with business object Article and User.
It lead to state when I have to fully spe
Hello *
I have a component DateSelector which must be in a form. DateSelector
contains 3 Select components.
My question is, how can I perform cross-field validation in DateSelector? As
far as I see, there is no event which the component gets which I can use to
perform this task. DateSelector get
Ok,
but how can I command the component to render actionLink as a link to the
page that contains the component or how could I redirect from component to
the page in generic way(Could I pass any reference of the page as
component's parameter? and then use public method on that page?)? any way to
int
Of course, but since I am not very good at javassit, my implementation may be
ugly and a bit long. Anyone please consummate it.
Like PageActivationContext, I introduce an PageActivationUnitWorker.
The key part is to collect the param fields and add the param map to page class
in runtime. onActiva
Would it be possible for you to share that code with us? I don't necessarily
want to use that approach, but it would be very helpful to see how you
implemented it.
Inge
On Tue, Dec 8, 2009 at 9:10 AM, DH wrote:
> Once I found it difficult too, and I never used EventContext because I
> think it
Once I found it difficult too, and I never used EventContext because I think
it is not better than multiple onActivate.
Finally I wrote my own PageActivationContext called PageActivationUnit, the
difference is that PageActivationContext only can occur once, but
PageActivationUnit can be used i
42 matches
Mail list logo
