Stephan, why do you invalidate the session inside onActivate()?
onActivate is for activating pages. I guess onAction* handlers are
better place for this code.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For add
Has anyone got come code snippets for me on integrating T5.1.0.5 and
Spring-Tapestry 2.1.0
Thanks
-Original Message-
From: Eldred Mullany
Sent: Wednesday, July 22, 2009 1:55 PM
To: 'Tapestry users'
Subject: @Secured annotation handling
Hi All
I am spinning my head here trying to get S
Yes, these are the first 2 lines of my Layout component:
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";>
"
On Thu, Jul 23, 2009 at 12:30 AM, Ulrich Stärk wrote:
> Did you set the correct doctype inside your templates?
>
-
You can secure the directory listing too:
public static void
contributeMasterDispatcher(OrderedConfiguration
configuration) {
configuration.addInstance("DirectoryAsset",
DirectoryAssetDispatcher.class, "before:Asset");
}
public class DirectoryAssetDispatcher implements Dis
Did you set the correct doctype inside your templates?
On 22.07.2009 20:27 schrieb Sergey Didenko:
I just encountered that Form generates invalid xhtml 1.0 strict - it
puts "name" attribute to the "form" tag and that is invalid.
'
---
Julian: Thanks for sharing your solution to this problem. It seems like a
good workaround.
Ulrich: It is good to know that the directory listing has been addressed.
Hopefully this security hole will be fixed in the next release.
Daniel
Ulrich Stärk wrote:
>
> There is no directory listing
I just encountered that Form generates invalid xhtml 1.0 strict - it
puts "name" attribute to the "form" tag and that is invalid.
'
Em Wed, 22 Jul 2009 13:57:16 -0300, Stefan escreveu:
Hi,
Hi!
void beginRender(MarkupWriter writer) {
Link lnk = resources.createEventLink(EVENT_NAME, context);
You should encode the event context before passing it to
createEventLink(). ;)
Then, in your event handler method, yo
Sorry, that turned out to be caused by " z-index: 1" property on my content.
Sorry again.
Regards, Sergey.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apac
Hi,
i'm currently writing my first component, which should work like this
one : http://wiki.apache.org/tapestry/Tapestry5HowToCreateASimpleGraphComponent
Everything works fine so far, but:
I have to pass some complex data structures (encapsulated in objects)
to the component,
doing so:
I
Em Wed, 22 Jul 2009 13:05:09 -0300, Franz Amador
escreveu:
I wondered that also, and I'm waiting on an answer.
Does disabling JavaScript make the Ajax stuff invisible to Tapestry? If
so, it'd be great to have a better error message.
AJAX is all about using Javascript to update a part of
I wondered that also, and I'm waiting on an answer.
Does disabling JavaScript make the Ajax stuff invisible to Tapestry? If so,
it'd be great to have a better error message.
From: Howard Lewis Ship (via Nabble)
To: Franz Amador
Sent: Tuesday, July 21, 2009
I haven't noticed that; which browser is this an issue for?
Please add an issue to JIRA.
On Wed, Jul 22, 2009 at 7:00 AM, Sergey Didenko wrote:
> I propose to add
>
> .t-error-popup {
> z-index: 2;
> }
>
> into common Tapestry css. Without it popup errors are semi-hidden
> behind input lab
I just arrived at OSCON; if any Tapestry folks are here (despite the
anemic Java track) come and fine me! I'll be here through Friday.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
Director of Open Source Technology at Formos
---
I propose to add
.t-error-popup {
z-index: 2;
}
into common Tapestry css. Without it popup errors are semi-hidden
behind input labels, which looks ugly.
I'm going to create a JIRA issue for that. Any remarks, objections?
Regards, Sergey.
Very odd.
I based my comment on what I observed in the M2 POM editor dependencies
tab...
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 22 July 2009 14:22
To: Tapestry users
Subject: Re: T5.1.0.5: StackMapTable format error
Em Wed, 22 Jul 2009
> I do use ChenilleKit but haven't run into this problem (I presume that's
> because Maven always uses the later version if there is a conflict?
In my limited experience with Maven that is not the case, I think it may depend
on a few factors, explicit dependency declarations tend to win out, as d
Em Wed, 22 Jul 2009 07:40:24 -0300, Newham, Cameron
escreveu:
I note that I found this out from an email sent by Howard in 2007
addressing a query on StackMapTable error. I find it somewhat surprising
that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
using the latest Jav
> Specifying the latest Javassist (3.8.GA) in my POM solved the problem.
> I note that I found this out from an email sent by Howard in 2007
> addressing a query on StackMapTable error. I find it somewhat surprising
> that this problem still occurs in 2009. Surely Tapestry 5.1.x should be
> using t
Thanks Peter.
I do use ChenilleKit but haven't run into this problem (I presume that's
because Maven always uses the later version if there is a conflict? And
as I've explicitly brought in the later version of Javassist then that
overrides any earlier versions being included on the classpath)
I d
Em Wed, 22 Jul 2009 05:51:23 -0300, Stephan Windmüller
escreveu:
It is really necessary to use a persistent store when all needed data is
transmitted with each submit of the form?
Tapestry does redirect-after-post by default, so some form of persistence
is needed. You can also use the act
Be sure also to include an exclusion if you use ChenilleKit, or you will run
into similar issues.
org.chenillekit
chenillekit-tapestry
1.0.0
jboss
javassist
Cheers,
Peter
- Original Message -
From: "Cameron Newham"
To: "Tapestry users"
Sent: Wednesday, 22 July, 2009 13:40:24 GM
Hi Geoff,
I suggest to change links from T5.0 to T5.1 documentation.
For example on page
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/input/creatingvalidators1
there are links like "Form Input and Validation" that point to T5.0
docs.
On Thu, Jul 16, 2009 at 8:59 AM, Geoff
Calle
I still think this is a bug... I see it occasionaly but incosistently between
containers (jetty and tomcat), I think there is some inconsistency between 2.3
compliant
and 2.4 compliant Servlet containers when invalidating a session. If you use
the workaround for 5.1 then change:
if (element.sta
The Travel Assistance Committee is taking in applications for those wanting
to attend ApacheCon US 2009 (Oakland) which takes place between the 2nd and
6th November 2009.
The Travel Assistance Committee is looking for people who would like to be
able to attend ApacheCon US 2009 who may need some f
in Tapestry 5.0.18 you were able to create a new HttpSession after you
have
invalidated the old one in the same thread (request). This is not possible
anymore as the implementation is caching the old session and reusing it
for subsequent requests.
as a quick solution: get the HttpSession dire
I wouldn't run the web service through Tapestry at all. Instead, register
your web service as a separate servlet inside your application with a
certain path (e.g. "/ws/"), and make sure the Tapestry filter ignores those
paths by a contribution to your app module:
public static void contrib
Hi All
I am spinning my head here trying to get Spring-Tapestry-security:2.1.0
to work with Tapestry 5.1.0.5 . I have done the upgrade to 2.1.0 and
when place my @secured annotation on the top of my class name is throws
an access denied exception:
Following that intercept.AbstractSecurityInterce
I try to upgrade an application from 5.0.18 to 5.1.0.5. After invalidating
the Session for the user logout I get the included Exception. Everything
works fine with 5.0.18 and I checked hat I do not invalidate the HttpSession
but invalidate the Tapestry Session via the injected
org.apache.tapestry5
Thanks Thiago, although it turned out to be because I'm using Java 1.6
and I had an old(ish) version of Javassist being brought in as a
dependency from tapestry-ioc that wants javassist-3.4.GA.
Specifying the latest Javassist (3.8.GA) in my POM solved the problem.
I note that I found this out fro
I use AjaxFormLoop-addrow-addrowlink-parameter to dynamic add a row , I want
to fill the row with some defult value which base on the link param user
click.
for example:
tml:
Add a row
Add a row
java:
PersonHolder onAddRow(Object value) {
Is there anybody who can help me with this ?
In the tapestry doc page for the component Zone, I found this :
Not shown here, but fully valid, is to include JavaScript libraries and
generate initialization JavaScript. This fully consistent with ordinary
full-page renders.
It said it was fully va
There is no directory listing with 5.2-SNAPSHOT but I'm still able to
access the templates and stuff on the classpath.
Uli
On 21.07.2009 03:13 schrieb Daniel Jones:
Hello,
OK, so here is my problem.
In my page template:
${asset:context:assets/images/layout/add.png}
Tapestry generated URL
-Message d'origine-
De : Stephan Windmüller [mailto:stephan.windmuel...@cs.tu-dortmund.de]
Envoyé : mercredi 22 juillet 2009 10:50
À : Tapestry users
Objet : Re: Passing data to the same page - Understanding
PersistanceContext.FLASH
De Saint Steban Emmanuel wrote:
> PersistanceContext.
Kristian Marinkovic schrieb:
> you can use PersistenceConstants.CLIENT to store all your data
> on the client side - with all iths pros and cons.
This creates a very long URL. I found no way to force client persistence
into a form.
> another way - when using a form - you can use the onPrepare,
De Saint Steban Emmanuel wrote:
> PersistanceContext.FLASH is storing the object for only one time.
> The data will be deleted after the first access.
Okay, but what is meant by "first access"? Even writing the data with a
debug logger? Or after the onActivate-method is finished? Is there a way
t
you can use PersistenceConstants.CLIENT to store all your data
on the client side - with all iths pros and cons.
or can store your data in the session wia SESSION or as
SessionStateObject
another way - when using a form - you can use the onPrepare,
onPrepareForRender and onPrepareForSubmit eve
PersistanceContext.FLASH is storing the object for only one time. The data will
be deleted after the first access.
Use just @Persist (or if you want to access in all page of your application use
@ApplicationState
Emmanuel
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'u
Hi all.
Maybe i missed some info ..
This code was inside a standard T5 page, with a hibernate session injected.
It's curious , because i find no reason for the code not to be commited,
it's even not giving errors ... not even a rollback.
Ups...Sorry Jose i didn't notice u were using the @Comm
Kristian Marinkovic wrote:
> in your case you'd need the session scope (=default)
But this will break if the user is creating several tasks in multiple
browser tabs.
When I summarize my issue it all comes to the following question: How do
I access data that is stored in objects and submitted com
Hello all
I'm actually working on a component library, i would like to generate the
component reference documentation, but it fails with this error :
Embedded error: Error rendering Maven report: Published parameter 'volatile'
(from embedded component class org.apache.tapestry5.corelib.componen
Tapestry 5 handles action requests and page requests.
action requests identify a certain component or event
that will be used to process the request. if the component
request has been processed a redirect (= second request)
page request is generated and issued. the flash persistence
strategy is u
42 matches
Mail list logo
