With my maven pom.xml settings setup like This...
version${jetty-maven-plugin-version}/version
dependencies
dependency
groupId${mysql.groupId}/groupId
artifactId${mysql.artifactId}/artifactId
Have you configured a non-standard XMLReader?
Take a look at the docs here
http://www.saxproject.org/apidoc/org/xml/sax/helpers/XMLReaderFactory.html#createXMLReader()
Tapestry's template parsing is done by SaxTemplateParser / XMLtokenStream
which ultimately delegates to an XMLReader created via
I only have 7 onchange listeners
I assume that you have 7 clientside listeners in total? (ie you are not
adding one of these 7 in a t:loop?)
I actually asked her for you, she is quite happy
I knew as soon as I typed 'him' it would be a her. That'll teach me to save
keystrokes on my phone! I
Actually there is a way to make it fast.
Things may become faster if you reduce number of HTML inputs from HTML
DOM.
Just remove them from HTML and rewrite submit logic to your own.
You may replace checkboxes with images. Replace those images with real
checkboxes when user hovers this image or
I forgot to mention, but I have tried the
same, and the result was the same, failure with an error Parameter(s)
'hideable, visible' are required for
fr.exanpe.t5.lib.components.HideablePanel, but have not been bound.
Date: Mon, 6 May 2013 19:10:24 -0700
From:
Please go through http://tapestry.apache.org/url-rewriting.html.
Also http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ is a
must read for url rewriting.
regards
Taha
On May 10, 2013, at 4:48 PM, Nomer Nominus wrote:
I have FullArticle tml page, and all articles get url
Remember to include
xmlns:p='tapestry:parameter' in the root tag.
not
xmlns:p='tapestry-parameter'
regards
Taha
On May 10, 2013, at 4:35 PM, Nomer Nominus wrote:
I forgot to mention, but I have tried the
same, and the result was the same, failure with an error Parameter(s)
'hideable,
Hi,
is it possible to force tapestry5 application to startup in eager mode?
I'm ready to trade off this to longer start up time.
Otherwise now after each redeployment in production a user may hit some
page or action for the first time and it will take long time.
I think its because of lazy
You can annotate individual service builder methods in AppModule with
@EagerLoad. There's also ServiceBindingOptions.eagerLoad() available for
bind().
Not sure if there's a global option.
On Thu, 09 May 2013 23:09:16 -0300, nhhockeyplayer nashua
nhhockeypla...@hotmail.com wrote:
Hi Thiago...
Hi!
sorry about half answers... just trying to do things concurrently.
No problem. :) I couldn't find anything wrong or that could cause this
weird issue you're having and I'm
When I read the original post, I thought all he needed was a proper pair
of onActivate/onPassivate methods. To get the first form of the url anyway.
On Fri, May 10, 2013 at 7:51 AM, Taha Siddiqi tawus.tapes...@gmail.comwrote:
Please go through http://tapestry.apache.org/url-rewriting.html.
On Fri, 10 May 2013 08:51:24 -0300, Taha Siddiqi
tawus.tapes...@gmail.com wrote:
Please go through http://tapestry.apache.org/url-rewriting.html.
Actually, read this: http://tapestry.apache.org/page-navigation.html,
specially the Page Activation section. No URL rewriting needed. Just use
EagerLoad is a pain when developing. I my opinion you should kill two birds
with one stone. Setup a monitor page that includes the services you want to
eager load and point a website monitor at it. Then it takes the startup hit
instead of your users and you also know when the site is broken.
On
Well thanks guys... I appreciate the attention.
I will see what the weekend gives.
Thanks Taha, this worked like a charm! :)
Date: Fri, 10 May 2013 04:47:27 -0700
From: ml-node+s1045711n5721355...@n5.nabble.com
To: tapestr...@outlook.com
Subject: Re: Tapestry5.3 misconfiguration with exanpe component HideablePanel
Remember to include
xmlns:p='tapestry:parameter' in
Hi! Thanks, @PageActivationContext annotation worked like a charm for this
issue. However, one more thing concerns me about this. Since I have @Persist
and @PageActivationContext over some property, does this require more round
times for connection and with it is slower than without using it?
Hi
@PageActivitationContext and @Persist are two ways to persist data across
requests. So they are mutually exclusive.
@PageActiviationContext adds the data as a context to the url while @Persist
saves it in session(or cookie). You should always prefer the former and avoid
the latter.
I need to check wheter File can be readable or not, however I don't know how to
implement it in Tapestry app. If I put inside my method
public String getPath() {
File file = new File(article);
if (article.canRead() || article.isFile()){
return something
}
Hi
On 11-May-2013, at 5:45 AM, Nomer Nominus tapestr...@outlook.com wrote:
I need to check wheter File can be readable or not, however I don't know how
to implement it in Tapestry app.
Just as you would implement it in plain java.
If I put inside my method
public String getPath() {
19 matches
Mail list logo
