Separate issues.
For this I'm using the SImple Stupid JQuery Accordion and it's working
well.
The issue that I've run into in the past is that there are cases where
generating Blocks in the page based upon page data and accessing them
(e.g. to pass into a zone) would be useful.
I understa
>> The use model for this would be to allow Blocks to be dynamically created
>> in the template then retrieved using ComponentResources.findtBlock().
>From my understanding, adding something like this would be a serious
departure from how tapestry works.
First, in order to create the dynamic bloc
This is a tricky error to fix. At issue is the fact that the page
activation context can, theoretically, look like anything: strings,
numbers, path-like-stuff, whatever. The layers of conversion from the
path in the URL to, ultimately, numbers or entity objects happens
very, very late. In theory,
If you are using a recent release or snapshot of Tapestry 5.2, you'll
find the page pool is gone. Tapestry now instruments your pages and
components so that they can be shared across any number of threads
(mutable fields now result in writing to or reading from a per-thread
HashMap). You will now
Clarification: programatically created with ids specified from the
page or component class, then retrieved using findBlock() or something
similar.
On 10/15/2010 2:54 PM, Chuck Kring wrote:
Understood.
The use model for this would be to allow Blocks to be dynamically
created in the template
Understood.
The use model for this would be to allow Blocks to be dynamically
created in the template then retrieved using
ComponentResources.findtBlock(). I think findBlock() works off of the
Tapestry id which can't be set.
Chuck
On 10/15/2010 11:45 AM, Howard Lewis Ship wrote:
On Fri,
Hello,
We ran into a problem in our production environment where the tapestry page
pool was maxed out and new requests for a page were denied. We had set the
tapestry.page-pool.hard-limit value to 300, and the worker thread pool for
jboss was set to 160. We ended up changing the
tapestry.page-p
On Fri, Oct 15, 2010 at 5:52 AM, Moritz Gmelin wrote:
> Hi,
>
> Howard was right. It was a race condition.
> Maybe for other to prevent similar problems:
>
> We have an AccessControlDispatcher in our application that was inserted
> before:ComponentEvent in our application. This AccessControlDispa
On Fri, Oct 15, 2010 at 11:41 AM, Chuck Kring wrote:
> Whoa. Everything is easy in Tapestry. The hard part is figuring out the
> easy way to do it.
>
> Howard, if you happen to read this, one thing that would be generally
> useful would be to allow t:id to be set using a variable. Something
I'm going to give it a try. It looks very usable.
Thanks for the lead.
Chuck
On 10/14/2010 5:51 PM, ael wrote:
JQuery on the Go...
http://www.stemkoski.com/stupid-simple-jquery-accordion-menu/
Simple Stupid JQuery Accordion :)
-
On Fri, Oct 15, 2010 at 10:29 AM, Michael Gentry wrote:
> I'm not sure this always makes sense to do. One of our applications
> has a couple wizard-like interfaces where you answer a few items and
> move through until the end. Each page had a tiny little bit of
> page-specific JavaScript to be d
Whoa. Everything is easy in Tapestry. The hard part is figuring out
the easy way to do it.
Howard, if you happen to read this, one thing that would be generally
useful would be to allow t:id to be set using a variable. Something
like this:
Right now you can set the HTML id but not
Hey all, I know this is off-topic but considering I'm offering you a job I
thought it'd be okay.
There are 3 positions open (see below for more details): Lead Engineer, QA
Engineer, Software Engineer.
These are on-site positions. If you would like to be a remote contractor I'd be
happy to sp
I'm not sure this always makes sense to do. One of our applications
has a couple wizard-like interfaces where you answer a few items and
move through until the end. Each page had a tiny little bit of
page-specific JavaScript to be delivered in addition to the common
JavaScript (Prototype, Tapestr
On Fri, Oct 15, 2010 at 9:59 AM, Howard Lewis Ship wrote:
> On Fri, Oct 15, 2010 at 9:51 AM, Kalle Korhonen
> wrote:
>> On Fri, Oct 15, 2010 at 9:19 AM, Howard Lewis Ship wrote:
>>> On Fri, Oct 15, 2010 at 1:34 AM, stephanos wrote:
http://encosia.com/2008/12/10/3-reasons-why-you-should-let
On Fri, Oct 15, 2010 at 9:51 AM, Kalle Korhonen
wrote:
> On Fri, Oct 15, 2010 at 9:19 AM, Howard Lewis Ship wrote:
>> On Fri, Oct 15, 2010 at 1:34 AM, stephanos wrote:
>>> http://encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/
>>> advantages obviously are reduced
On Fri, 15 Oct 2010 13:31:07 -0300, Blower, Andy
wrote:
From one of my developers:
When using the VALIDATE event to validate form details, the validation
method is called several times.
@OnEvent(EventConstants.VALIDATE)
void validateChooseFolderForm() {
..
On Fri, Oct 15, 2010 at 9:19 AM, Howard Lewis Ship wrote:
> On Fri, Oct 15, 2010 at 1:34 AM, stephanos wrote:
>> http://encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/
>> advantages obviously are reduced traffic+CPU for the server, decreased
>> latency, increased
Components fire validate events as well as the form, so modify your
@OnEvent to identify the form as the origin of the event.
On Fri, Oct 15, 2010 at 9:31 AM, Blower, Andy
wrote:
> From one of my developers:
>
> When using the VALIDATE event to validate form details, the validation method
> is c
>From one of my developers:
When using the VALIDATE event to validate form details, the validation method
is called several times.
Eg.
@OnEvent(EventConstants.VALIDATE)
void validateChooseFolderForm() {
...
}
Is called at least three times, executing di
Done and rolled out this morning. That's what I meant - I guess my Java is
better than my English, eh?
;-)
> -Original Message-
> From: Howard Lewis Ship [mailto:hls...@gmail.com]
> Sent: 15 October 2010 17:20
> To: Tapestry users
> Subject: Re: [T5.2.1] TAP5-1177 In a partial page updat
You should be able to monkey-patch just this function, rather than all
of tapestry.js.
On Fri, Oct 15, 2010 at 1:59 AM, Blower, Andy
wrote:
> Raised TAP5-1309. I will override & patch tapestry.js to T5.2.0 version of
> this line of code.
>
>> -Original Message-
>> From: Howard Lewis Ship
On Fri, Oct 15, 2010 at 1:34 AM, stephanos wrote:
>
>> Why do you want this?
>
> Well the
> http://encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/
> advantages obviously are reduced traffic+CPU for the server, decreased
> latency, increased parallelism and better c
Hi,
Howard was right. It was a race condition.
Maybe for other to prevent similar problems:
We have an AccessControlDispatcher in our application that was inserted
before:ComponentEvent in our application. This AccessControlDispatcher uses the
SessionStateObject to check access permissions.
N
On Fri, Oct 15, 2010 at 12:39 PM, wrote:
> Hi Massimo,
>
> That won't resolve it see:
> http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-1-upgrade-woes-td2849844.html
>
> You have transitive dependencies, so you will need to fix your projects POM,
> publish to the repo and update the site acc
http://jira.codehaus.org/browse/CHEN-38
On 10/15/2010 12:33 PM, Massimo Lusetti wrote:
>
> Submit a patch within a Jira issue (at
> http://jira.codehaus.org/browse/CHEN) and I'll see what I can do...
> thanks.
>
> Cheers
smime.p7s
Description: S/MIME Cryptographic Signature
Hi Massimo,
That won't resolve it see:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-1-upgrade-woes-td2849844.html
You have transitive dependencies, so you will need to fix your projects POM,
publish to the repo and update the site accordingly.
Cheers,
Peter
- Original Message -
On Fri, Oct 15, 2010 at 12:28 PM, Vangel V. Ajanovski wrote:
> ChenilleKit is not working under Tapestry 5.2.1 because it uses the
> internal class internal.services.RequestPathOptimizer which does not
> exist any more.
>
> I have tried to download latest snapshot but it is few months old and it
ChenilleKit is not working under Tapestry 5.2.1 because it uses the
internal class internal.services.RequestPathOptimizer which does not
exist any more.
I have tried to download latest snapshot but it is few months old and it
still uses the same class.
I have tried to build Chenillekit from sour
Ahh yes, thanks! I see it was fixed over a year ago, but wasn't 5.1.0.6 and
5.1.0.7 voted down?
- Original Message -
From: "Stephan Windmüller"
To: users@tapestry.apache.org
Sent: Friday, 15 October, 2010 12:13:23 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Looks like a
On 15.10.2010 09:24, p.stavrini...@albourne.com wrote:
> When using an image submit button it appears that the onSelected event never
> fires:
Yes, and it is a known one:
https://issues.apache.org/jira/browse/TAP5-711
Regards
Stephan
--
Raised TAP5-1309. I will override & patch tapestry.js to T5.2.0 version of this
line of code.
> -Original Message-
> From: Howard Lewis Ship [mailto:hls...@gmail.com]
> Sent: 14 October 2010 22:39
> To: Tapestry users
> Subject: Re: [T5.2.1] TAP5-1177 In a partial page update request, if
> Why do you want this?
Well the
http://encosia.com/2008/12/10/3-reasons-why-you-should-let-google-host-jquery-for-you/
advantages obviously are reduced traffic+CPU for the server, decreased
latency, increased parallelism and better caching. How big an advantage it
really is probably depends o
Hi,
we've been running into this also.
Fixed this by creating a custom 404 page and setting this as the default start
page.
FourOhFour.tml
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
Page not found
And FourOhFour.java
import org.apache.tapestry5.Link;
import org.apa
> As the JIRA ticket says, this is expected behavior. In your case, /blabla
> is considered a request to / (Index) with one activation context parameter
> 'blabla' as there's no page named 'blabla'.
I was just wondering why the ticket is still 'Open' and has a patch that
apparently was never
Hmm... that's true, the Start page is "broken" as well in 5.2 - you
can't get it to return 404s anymore using Start page the same way as
in 5.1. That's a showstopper for upgrading one of my apps to 5.2. I
bet there's a way to restore the old behavior, anyone solved this
already?
Kalle
On Fri, Oc
On Thu, Oct 14, 2010 at 11:16 PM, Thiago H. de Paula Figueiredo
wrote:
> As the JIRA ticket says, this is expected behavior. In your case, /blabla is
> considered a request to / (Index) with one activation context parameter
> 'blabla' as there's no page named 'blabla'.
Correct and acknowledged b
Hi,
When using an image submit button it appears that the onSelected event never
fires: I.e:
This works:
//Java
void onSelectedFromNotesSearch(){
// is invoked
}
But this doesn't:
//Java
void onSelectedFromNotesSearch(){
// is not invoked
38 matches
Mail list logo
