Hi Dan!
* We have an internal t5-based library (or 3 actually) that aids in
building CMS and other administrative applications. One library
provides super-slick Lucene integration for Hibernate entities.
We're just looking through Lucene to use it in our T5/Hibernate apps.
We're just
There are two good practices to do database i18n:
http://www.theserverside.com/tt/blogs/showblog.tss?id=HibernateInternational
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/i18n/i18n5.html
We do quite the same with just one table for all texts.
Cheers,
Chris
Jan Vissers [EMAIL PROTECTED] wrote:
Our layout component has:
link rel=shortcut icon href=favicon.ico/
If you have this in your code the browser will request
/yourpage/favicon.ico or mypackage/mypage/favicon.ico. Tapestry treats
favicon.ico as an activation context. I think you have a
However when I come back to the form - the respective fields are (still)
marked as erroneous. Any way around that?
This is related to this issue:
https://issues.apache.org/jira/browse/TAPESTRY-2354
I think this is fixed in the trunk - or at least you can specify the
persistence scope of the
inherit: binding - however this doesn't work for me.
That should work.
With the inherit keyword you can forward parameters to sub-components,
like this example of a zebra Grid component:
public class MyGrid
{
@Parameter(required = true)
private GridDataSource source;
Robert Zeigler wrote:
the code works: Nope, it doesn't.
Now, it's getting interesting! This is what I get, when I try your code:
html
head
link type=text/css rel=stylesheet
href=/assets/tapestry/default.css
/link
titleIf t:container replaces $content$, this shouldn't render/title
/head
body
will render the html tags (outside the t:container) every time the
component is used (in another component, in my case).
I just tried this out with 5.0.10 - with my test it doesn't render the
html tags.
I checked in jumpstart 3.3.3 as well, and it has the same problem (see
You can override and extend Grid like this:
package com.poi.egh.turntable.ui.components;
/**
* Grid component to be used in ProjectX.
*
* Provides the following extensions to the Tapestry TurntableGrid:
* ul
* liclass=odd for all odd rows/li
* /ul
*
* @author Christian Kouml;berl
*/
Jesper Zedlitz [EMAIL PROTECTED] wrote
This is the T4 feature:
http://tapestry.apache.org/tapestry4/UsersGuide/template.html#template.directives.content
Is something like this possible with T5?
The replacement of $content$ is the t:container construct (see
Ich werde ab 26.09.2007 nicht im Büro sein. Ich kehre zurück am
27.09.2007.
Bitte kontaktieren Sie in dringenden Fällen das Porsche Informatik Customer
Care Center:
http://www.porsche-informatik.at/sup_kontakt.htm
oder per Web:
http://support.porscheinformatik.at/
Grüße,
Christian Köberl
Ich werde ab 23.09.2007 nicht im Büro sein. Ich kehre zurück am
26.09.2007.
Bitte kontaktieren Sie in dringenden Fällen das Porsche Informatik Customer
Care Center:
http://www.porsche-informatik.at/sup_kontakt.htm
oder per Web:
http://support.porscheinformatik.at/
Grüße,
Christian Köberl
After packaging new package, but occur NullPointer Exception:
because request.getCharacterEncoding() == null
You also have to add the UTF-8 filter described in
http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding
--
Chris
Is this a bug of UploadFile or I should change the code?
This is a bug, see: https://issues.apache.org/jira/browse/TAPESTRY-1723
You can checkout the code, apply the patch and build your own
tapestry-upload.jar
--
Chris
followup. Strange thing is - looking at the actuall log4j.Logger - it
has an isTraceEnabled, so I'm really unclear as to why this would
happen.
The problem is the log4j lib in the Jetty ext directory - replace it with
the newer log4j (1.2.12 or higher) version.
--
Chris
Hello!
Has anybody ever tried to set clientValidation=false in a form with
validators?
The T5 validators still generate the validation JavaScript but the form
does not inlude the required JS-libs. This leads to an JS error on the
client side.
This script is generated with
Hello T5 developers!
As everybody likes to have a different JavaScript Framework for Ajax use,
it's probably
the best to make that flexible as Kristian suggested in:
https://issues.apache.org/jira/browse/TAPESTRY-1650
I think of something like tapestry-upload - you can use it or you can
build
Not everyone is using tapestry-upload and not everyone is using fancy
file names and tapestry-upload module is the younger in T5 space so...
anyway you´re is indeed a good catch so propably will be evaluated.
It's not the file name. The problem is: as soon as you add a upload
component to a
I have a form with a 'textfield' and a 'upload' field .
The Chinese words I input in textfield will be irrecognizable when I
submit the form .
I wondered, why nobody found this bug before. Anyway, I filed the
bug yesterday and provided a fix.
Angelo Chen [EMAIL PROTECTED] wrote:
Hi,
I'm learning by trying out the hi/lo game, everytime I clicked one of
the
number links, the onActionFromLink was not called, here is the template:
It should be onActionFromGuess because the link's id is guess.
--
Chris
Tapestry just supports a ValueEncoder for String and Enum. If you want
additional
encoders you have to implement them yourself:
class LongValueEncoder implements ValueEncoderLong
{
public String toClient(Long value)
{
return value == null ? : value.toString();
By making it @Persist (i.e. with default), then the container (i.e., your page) can set a @Meta to control the default persistence of componentsbelow it. Thus, if you want the default to be "flash", you're in luck.So, you think every page in every T5 app in the world should override the default
Couldyougiveusanexampleofhowtoaccomplishthis?What we did is to extend the Form component with a flash-persist defaultTracker. We're using our Form component everywhere:public class Form extends org.apache.tapestry.corelib.components.Form{ @Persist("flash") private ValidationTracker
Hi!
I was wondering why the _defaultTracker in the Form component is marked
as @Persist not as @Persist(flash).
In my opinion it should be @Persist(flash)!!
Persisting the ValidationTracker in the session leads to some (usually)
not wanted
behaviour: the validation is not reset, even though a
23 matches
Mail list logo
