You can't out of the box. I believe the t5components project has a mixin
for this. Alternatively you could submit your form using javascript.
Something like onchange=this.form.submit().
Try searching the mailing list archives at tapestry.markmail.org, this
has been discussed before.
Also
Kalle Korhonen wrote:
Just FYI for those interested; I made the initial implementation of my
conversation-within-page concept available as an independent Trails module:
trails-conversations (for T5). More information at
Hi Howard,
Are you planning to attend? I never saw any Tapestry sessions on the schedule,
are you planning anything informal?
Kind regards,
Peter
- Original Message -
From: Howard Lewis Ship hls...@gmail.com
To: Tapestry users users@tapestry.apache.org
Sent: Tuesday, 27 January, 2009
In general, the @EJB annotation is intercepted by EJB containers only,
but I notice some server providers have been extending it to JSF (and
servlets?).
It would be nice to have Tapestry handle the @EJB annotation, too, but
in the meantime, I think a service locator is a pretty painless
Howard,
could you please explain to me how the two pipelines work and how to add
filters to them and also how to use this new facade service? I couldn't
find any documentation on them and the is logged in scenario you are
aiming at seems so common that it should be documented somewhere...
On Wed, Jan 28, 2009 at 1:57 PM, Ulrich Stärk u...@spielviel.de wrote:
Howard,
could you please explain to me how the two pipelines work and how to add
filters to them and also how to use this new facade service? I couldn't find
any documentation on them and the is logged in scenario you are
Hi!
I have a form and a grid component on one of my pages (the grid is
outside the form). All operates normally (using Jetty) unless I leave
it for 10 minutes. If I then attempt to perform a submit I get the
Null Pointer Exception listed below. It only happens on pages with the
grid
1. Has anyone figured out how to use Tapesry5-acegi with SpringSecurity 2.0.4
and Tapestry5 5.0.18 yet? I have tried the last few days to recompile
tapestry5 against SpringSecurity 2.0.4 but have not made any progress yet.
2. I have read Tapestry5 howto to find out alternative way to use
Use Tapestry-Spring Security instead of Tapestry-Acegi:
http://www.localhost.nu/java/tapestry-spring-security/
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
tapestry5 does not work with T5 5.0.18. I got error messages that say
serivice SaltSource is built twice. If I removed the buildSourceSource
static method. The error went away.
Also tapestry5-acegi depends on acegi old version 1.0x which hinders to
projects that integrates with SpringFramework
That server is slow. It takes quite long to access to that server.
-B
Robin Helgelin wrote:
On Mon, Oct 27, 2008 at 2:22 PM, Mahen Perera
mahen.per...@igindex.co.uk wrote:
nslookup is giving me:
DNS request timed out.
timeout was 2 seconds.
Also, when I try to use the IP
Em Wed, 28 Jan 2009 13:53:57 -0300, bongosdude bongosd...@gmail.com
escreveu:
tapestry5 does not work with T5 5.0.18. I got error messages that say
serivice SaltSource is built twice. If I removed the buildSourceSource
static method. The error went away.
You cannot use both at the same
Thank you,
yes problem is in Form. I do not know how to switch off persistence of
validation so I will use standard form tag.
Meta did not work, because I can't use it on component variable. It can
be used only to @Target(TYPE). Maybe you have different version.
Also thanks to Andreas
Em Wed, 28 Jan 2009 15:04:35 -0300, Tomas Kolda ko...@web2net.cz
escreveu:
Meta did not work, because I can't use it on component variable. It can
be used only to @Target(TYPE). Maybe you have different version.
Put it in the page class at which the Form component is used. I was wrong
Hmm, I do not know what I'm doing wrong, but it does not work. It still
create session.
@Meta(tapestry.persistence-strategy=client)
public class Layout {
@Component
private Form queryForm;
..
Thiago H. de Paula Figueiredo napsal(a):
Em Wed, 28 Jan 2009 15:04:35 -0300, Tomas Kolda
Have you put this annotation in all pages with Form components and
restarted you application (to clear the session)?
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
Layout's still a component (unless you have a page named Layout), need to be
in the page class. I can verify the meta annotation works ok.
Kalle
On Wed, Jan 28, 2009 at 10:48 AM, Tomas Kolda ko...@web2net.cz wrote:
Hmm, I do not know what I'm doing wrong, but it does not work. It still
I am looking at tapestry-spring-security now. I have one question though,
1. If I do not use hibernate but JDBC, then what AuthenticationProvider
should be? Should it be OK with daoAuthenticationProvider? How is about if I
am using OpenJPA instead of Hibernate?
public static void
Yes restarted. I deleted all from Index, but form. What am I doing
wrong? Using 5.0.18, Jetty, Eclipse 3.4.
Index.java:
@Meta(tapestry.persistence-strategy=client)
public class Index
{
@Property
private String query;
}
Index.tml:
html
hardcoded value in AppModule.contributeApplicationDefaults method is not a
best practice.
class AppModule {
..
public static void contributeApplicationDefaults(
MappedConfigurationString, String configuration ) {
configuration.add( SymbolConstants.SUPPORTED_LOCALES,
you can put them into your web.xml file:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
web-app
display-nameMyApp/display-name
context-param
How are about other values like production_mode, cookie age which have
different values in DEV, QA and Production environments?
Even put it in the web.xml is not good either? I cannot change web.xml when
we release software to QA and production.
Thanks
-B
Harald Geritzer-2 wrote:
you can
Hi,
I am using PlainText password encoder now to test before I can change logic
to provision UserDetails with MD5 or SHA encoded password. The problems are:
1. org.springframework.security append saltsource to plain text password if
saltsource is not null or emtpy. If my password is 123456 and
Whether you use AppModule.java, app.properties, or web.xml, it's still
hard-coding. Only constants belong in there.
Environment-specific properties can be set as system properties before
starting the server,
eg. for JBoss on Unix: setenv JAVA_OPTS '-Dtapestry.production-
mode=false
In the case of Tomcat, you can also store these in a Context.xml file,
which can be configured differently for each server (including your
development machine). The context.xml file can be unique to each
Tomcat instance, and live in Tomcat/conf/context.xml or
25 matches
Mail list logo
