I just tried out the new T5.1 property expressions for the first time and got
an error. I’m trying to replace this:
${linkTitle}
public String getLinkTitle() {
return getTitle(false);
}
With this:
${getTitle(false)}
Which I should be able to do according to the Grammar as far
Rather than explain (probably badly) exactly what the problem is, I'll
provide a small example page called BasicAJAX. This page demonstrates that
if an actionlink that causes a zone refresh via AJAX is part of the
refreshed zone itself, it only works on alternate clicks in IE. Each time
it's rende
I just ran into this issue myself, and switching to a 1.5 jre fixed it.
(although now I get a "Java compiler level does not match the version of the
installed Java project facet." error reported by Eclipse... which means
nothing to me)
I thought that reporting what was causing the problem may hel
Thank you for this post, although I just spent 2 hours scratching my head on
this because I was having the error:
ERROR (RequestExceptionHandler:45 ) - Processing of request failed with
uncaught exception: Namespace prefix for URI 'http://www.w3.org/1999/xhtml'
is not defined.
java.lang.RuntimeE
I have encountered a similar issue, and the use of onPrepare() doesn't make
sense to me. Surely there's no point persisting any fields and then
resetting in onPrepare() is there? May as well just remove the @Persist.
There must be something I'm missing here.. can anyone fill me in?
Howard Lewis
;ve missed?
Andy Blower wrote:
>
> Filip - that looks really good work.
>
> I didn't realise new bindings can be created. I'm surprised that you're
> using %d, %s etc rather than the standard {0} {1} ResourceBundle
> parameters. To me it would be nicer express
I thought the properties file needs to end up next to the class file in the
classpath when the project is built - regardless of where it comes from.
(src/main/java/... or src/main/resources/... or wherever)
Petros Petrou wrote:
>
> I think you need to move your FindCoops.properties file to b
e message key itself a binding
> wouldn't be too difficult. It should probably default to literal to
> preserve current behaviour, though.
>
> You can have a go at it yourself or wait a few days for me to do it.
>
> -Filip
>
> On 2008-04-02 20:43, Andy Blower wrote:
Thanks for all the replies everyone.
This is good, but it'd be better if the prefix could be passed in from the
template. I guess it would need another property & setter. I'm still a
novice with Tapestry, but I can't think of a way of doing this without
creating a component and having it take a p
I'm accessing message catalogs using expansion with a prefix. e.g.
${message:this-is-my-key}
1) Is there a list of prefixes anywhere, or have I got them all now?
(literal, prop, message)
2) Is there a way of accessing a message with a key that's partially
generated by another expansion?
e.g. (t
Thanks for your concern Rob, but I'm pretty comfortable evaluating things
myself and have already read that discussion. The backward compatibility
history of Tapestry will certainly be taken into consideration. (that was
the distraction I mentioned) Sometimes it's better to break backwards
compati
Hi there, I'm evaluating Tapestry (among others) for the web framework we'll
use at my company for the next 5 years or so. We've used Struts 1 for the
last 5-6 years and it's served us well, even if it was higher maintenance
than was first apparent. I have spent over two days reading about Tapestr
12 matches
Mail list logo
