On Fri, Oct 5, 2012 at 6:28 PM, Howard Lewis Ship wrote:
Sounds nice; that's how I've always assumed CDNs worked (lazily)
> though I'm told other require an explicit load of assets into the CDN,
> which is tricky in the Tapestry world where many of those assets are
> dynamically generated (or com
On Fri, Oct 5, 2012 at 6:28 PM, Howard Lewis Ship wrote:
> Sounds nice; that's how I've always assumed CDNs worked (lazily)
> though I'm told other require an explicit load of assets into the CDN,
> which is tricky in the Tapestry world where many of those assets are
> dynamically generated (or c
I wrote a CloudFront CDN while ago and also ran into a few problems. Is
loading content other than from S3 a new feature? I wrote a CDNManger
service that Lazily loaded the assets onto S3. The problem I ran into is
Tapestry uses the same URL to deliver compressed and uncompressed content
depending
Sounds nice; that's how I've always assumed CDNs worked (lazily)
though I'm told other require an explicit load of assets into the CDN,
which is tricky in the Tapestry world where many of those assets are
dynamically generated (or compiled, or aggregated).
On Thu, Oct 4, 2012 at 11:37 PM, Bård Mag
Sounds like this should be fixed. I voted for this bug to be fixed. You
should too.
On Oct 5, 2012, at 5:20 AM, Ivan Khalopik wrote:
> Use EventConstants.FAILURE event handler to return updated zone. There is
> also a bug in T5 with form validation inside zone:
> https://issues.apache.org/jira
Hi Howard,
Couldn't the Tapestry-generated URLs include both the Tapestry version
number + your application version number as part of the asset URL?
This way if all you do is upgrade Tapestry (5.3.4 -> 5.3.5), then
it'll automatically request new URLs that weren't cached. Of course,
I'm probably
Torrents of posts - apologies. That worked a treat; running with a temporary
mix-in with your fix for now - fantastic! Thanks a lot, if I could beam you
some beer I would. :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/RenderInformals-RenderInformalParameters-Ignored-
Excuse my haste! I just noticed that you'd posted a possible fix in the JIRA.
Will plug away on that. Thanks again Lance. :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/RenderInformals-RenderInformalParameters-Ignored-tp5716673p5716680.html
Sent from the Tapestry - Us
Hi Lance,
Thanks for your input! Perhaps related though in a slightly twisted way!
After searching through the rendered mark-up to double check there is no
trace of the informal parameters I'm expecting, anywhere! Specifically I'm
setting class="llamas", Ctrl+F-ing through the rendered source in t
I think you might be hitting this:
https://issues.apache.org/jira/browse/TAP5-1918. I'm guessing that your
informal parameters have been added to the parent element in the dom.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/RenderInformals-RenderInformalParameters-Ignore
Me too... Eclipse Indigo, CTRL+R works fine, content assist doesn't.
On Fri, Oct 5, 2012 at 6:10 AM, llama-king wrote:
> Hello!
>
> I can also chime in that the content assist doesn't appear to be working in
> general! The CTRL+R seems to be working though. I'm under Eclipse Indigo
> running 1.0.
Hello all,
I've read through all relevant topics and have yet to come up with why this
might not be working so many thanks in advance if anyone has any notions!
Take a small component class;
@SupportsInformalParameters
class Foo {
void beginRender(MarkupWriter writer) {
resources_.renderIn
Use EventConstants.FAILURE event handler to return updated zone. There is
also a bug in T5 with form validation inside zone:
https://issues.apache.org/jira/browse/TAP5-1512
You can try a workaround for this:
http://mutabra.blogspot.com/2012/09/tapestry-fixed-control-name-fixin.html
On Fri, Oct
Please read http://tapestry.apache.org/forms-and-validation.html
You can use onFailure for handling any form submission failures. If you want to
perform a common operation on success and failure you can use onSubmit()
regards
Taha
On Oct 5, 2012, at 2:40 PM, Ditso wrote:
> Hi all,
>
> I am c
Hi all,
I am currently having the following problem:
I have a form inside a zone which is linked to the form. When I trigger a
submit and the onvalidate does not succeed and I recorded errors to the
form. The onsucces is not excuted, obviously, but the zone is not updated
either which now should
It seems that you have error in setSubmittingElement js function. This
function is responsible of functionality you need. It sets the id and name
of submit button the form was submitted from.
Hmm - I did not see this. This may be the source of my problems?
Yes, exactly. You have error in setSubm
> Just tried your code and everething works as expected. Have you any client
> side errors reported by your browser?
Feil: TypeError: this.submitHidden is undefined
Kildefil:
http://localhost:8080/adapt-it/assets/796296867807588e/core/tapestry.js
Linje: 1512
Hmm - I did not see this. This may b
Just tried your code and everething works as expected. Have you any client
side errors reported by your browser?
On Fri, Oct 5, 2012 at 8:41 AM, Henrik von Schlanbusch wrote:
> Hi. I have problems understanding multiple submits. I am running T5.3.5.
>
> I have the following tml:
>
> id="singleUs
18 matches
Mail list logo
