Many components inherit their persistence strategy from the page
annotating the page thus is the official word:
@Meta(tapestry.persistence-strategy=client)
or: use cookies
http://wiki.apache.org/tapestry/Tapestry5HowToUsePersistentFieldStrategy
not as clever as Joshes solution, but it doesn't
style=display:none
its just html / css
On Mon, Jun 9, 2008 at 11:27 AM, Janko Muzykant [EMAIL PROTECTED] wrote:
hi, i have a couple of t:block components on my page:
t:block t:id=b1 .. /t:block
t:block t:id=b2 .. /t:block
and i would like initially block b1 to be visible. how may I do
actually, I would...
currently I have to click the property key in order to be able to set it...
I tried the in-grid approach, but just went around it when it didn't work...
Please share.
On Mon, Jun 2, 2008 at 11:47 AM, daniel alonso [EMAIL PROTECTED]
wrote:
Sorry again people, I have just
For what its worth:
+1: org.apache.tapestry5
On Mon, May 19, 2008 at 4:42 PM, Sven Homburg [EMAIL PROTECTED]
wrote:
my vote for org.apache.tapestry5
2008/5/19 Howard Lewis Ship [EMAIL PROTECTED]:
A few people have noticed some significant changes in Tapestry
5.0.12-SNAPSHOT.
Hi
Alex's book is based on 5.0.5 from memory...
I started at 5.0.10 and upgraded to 5.0.11 (early).
With the latest maven, this command worked for me:
mvn archetype:create -DarchetypeGroupId=org.apache.tapestry
-DarchetypeArtifactId=quickstart -DarchetypeVersion=5.0.11 -DgroupId=koncept
, May 10, 2008 at 12:30 PM, Mark W. Shead [EMAIL PROTECTED] wrote:
Nicholas,
Would you mind sharing code snippets of what you are doing?
Mark
On May 9, 2008, at 11:20 AM, nicholas Krul wrote:
Thanks, works just fine... so now everything is bundled into a String[]
anyway
of the
parameters, and retrieve each in whatever type you like (Tapestry will
value decode or type coerce as necessary).
On Fri, May 2, 2008 at 5:43 AM, nicholas Krul [EMAIL PROTECTED]
wrote:
Hi guys.
I have a question about onActivate(Object[]) and onActivate(String[])...
The simplest way
Hi... Sorry it took so long, tonight is the first free (ish) nigh I've had
for a while.
for point 4... try this:
@Environmental
private PageRenderSupport pageRenderSupport;
@Inject
@Path(tiny_mce/tiny_mce.js) //CLASSPATH ref (relative for me)
private Asset mceEditor;
void
Hi guys.
I have a question about onActivate(Object[]) and onActivate(String[])...
The simplest way to explain it is what I want to do on my login page.
At the moment when you bounce through it it stores the page name in the
activation context, but because of the variable number of context args,
Hi.
'My intention is to defer session creation until it is absolutely necessary'
I agree with you on that...
Why don't you use persistence and store it in a cookie? for simple
(non-hibernate) objects, its fine.
Form Validation creates a session for flash persistence... nothing in the
session,
Perhaps some code would help us out.
.tml loop checkbox snippet
.java index getter setter snippet
? I can only try
On Thu, Apr 24, 2008 at 10:54 AM, Peter Stavrinides
[EMAIL PROTECTED] wrote:
I have also noticed that the value parameter on the checkbox component is
a read only boolean,
Perhaps trimming it back to the minimum might help... if it doesn't fix it,
it might help diagnosis.
I don't know why this isn't working.
1) remove the id attribute from the checkbox. T5 will generate one, and it
will be unique
2) remove the encoder. Just because _I_ don't understand it... and I
try adding an index to the loop, and then using this index to do the
translation b/n the getters/setters.
(but I don't know anything about encoders)
--nK
On Wed, Apr 23, 2008 at 3:24 PM, Peter Stavrinides
[EMAIL PROTECTED] wrote:
Hi All
I this scenario:
t:loop source=myDOA
technically*, I think that all you need to do is set the page up so that its
onPassivate() call is 'correct' (and so will become input to the onActivate
call). Then return the page object (or page class). Tapesty should wrap it
up in passivate/activate calls automatically.
Personally, I think
@Persist(flash)
http://tapestry.apache.org/tapestry5/tapestry-core/guide/persist.html
and, since I can peddle my own wares
@Persist(flashcookie)
http://wiki.apache.org/tapestry/Tapestry5HowToUsePersistentFieldStrategy
I've had one (or two) too many glasses of wine. May your night be as good as
bind it as a paramater
@Paramater(required=true) //only if required
Object needed
On Fri, Apr 18, 2008 at 11:07 AM, Chris Lewis [EMAIL PROTECTED]
wrote:
Jan,
There's probably a simpler way, but you should be able to use
@InjectContainer in your component to get the page and call whatever
.
On Fri, 2008-04-18 at 11:23 +0100, nicholas Krul wrote:
bind it as a paramater
@Paramater(required=true) //only if required
Object needed
On Fri, Apr 18, 2008 at 11:07 AM, Chris Lewis
[EMAIL PROTECTED]
wrote:
Jan,
There's probably a simpler way, but you
the @Property annotation to dummy in component class to provide
getter+setter?
-Original Message-
From: Jan Vissers [mailto:[EMAIL PROTECTED]
Sent: 18 April 2008 11:59
To: nicholas Krul
Cc: Tapestry users
Subject: Re: T5: How do I access a page property in my component
? is your crumb property of type BreadCrumbBean, or is it type String?
should be same as breadCrumbs?TYPE
On Fri, Apr 18, 2008 at 1:56 PM, Chris Lewis [EMAIL PROTECTED]
wrote:
I can't speak about your t:if bit because I don't know what LastCrumb
would be, but assuming that your page class has
_that sounds like a bug to me. It should stay as an Object, and since its
not rendered, shouldn't need to string-itised.
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry/corelib/components/Loop.html
value type is Object
weird... so far I've only looped enums, so I
Wasn't there something about being able to push components onto the render
stack at runtime?
ahh:
http://www.nabble.com/T5%3A-Pushing-Multiple-Components-into-Render-Queue-td16699167.html#a16706639
might help. on thet5 website there are page lifecycle methods, I guess you
hook in there
Filip got it for me
the method is contributePersistenceStrategry (or something like that - from
TapestryModule)... just include the RequestGlobals interface (or Cookies, or
whatever) and its taken care of.
because its automatically injected into the method signature (no annotation
needed), it
Hello
Rob, I asked for help... I got it. If you cant contribute, don't. I have no
respect for people who only seek to tear down and not to build.
And to everyone else
http://wiki.apache.org/tapestry/Tapestry5HowToUsePersistentFieldStrategy
:)
thanks
--nK
On Mon, Apr 14, 2008 at
trying to get something similar.
This works for me with @Inject PageRenderSupport
textarea t:type=any id=${id} t:validate=required
t:cols=prop:cols t:rows=prop:rows
${document}
/textarea
works for rendering... but I'd prefer to be able to use t:textarea and
specify the id (?)
_and since
the @Meta(tapestry.persistence-strategy=X) works beautifully... no more
sessions till logged in.
On Mon, Apr 7, 2008 at 7:14 PM, Robert Zeigler [EMAIL PROTECTED] wrote:
On Apr 7, 2008, at 4/712:53 PM , Fernando Padilla wrote:
so.. the client strategy stores it in a cookie?
Client
Hi guys.
I have implemented a new PersistentFieldStrategy (cookie based), and am
having just one problem...
@Inject
private RequestGlobals requestGlobals
isn't processed... and I know of no other way to get it into the strategy to
make it work (it is from the base package).
I don't care
of this, nor have I needed to put in server side
comments... I find they tend to contain old code that may be needed again
(or 'uncomment this for...')
--just a thought.
--nK
nicholas Krul
On Fri, Apr 11, 2008 at 7:57 PM, Jim [EMAIL PROTECTED] wrote:
That's perfect, thanks Josh.
Josh Canfield
doesn't T5 autoflush the hibernate session at the end of the page render,
though?
so either the user will see a valid page (and the transaction committed in
the database), or an error page (and no commits).
I hope so, as I'm trusting to this.
--nK
On Fri, Mar 14, 2008 at 5:07 PM, Josh Canfield
28 matches
Mail list logo