On 08/09/2011 07:47 PM, Christian Köberl wrote:
Another difference is that we use a different zone for the form in the
dialog to prevent problems with server-side validation.
Hi Christian, I looked into this in more detail, but I don't really
understand what kind of validation problems are you
I've been seeing this intermittently as well; it is a timing problem
since the content fades out shortly after being added. Not sure how
to fix it without simply removing the test entirely.
On Fri, Aug 12, 2011 at 11:27 AM, Jon Williams
wrote:
> Hi Tapestrians,
>
> I've been trying over the last
Hi Tapestrians,
I've been trying over the last few days to gradle build the tapestry5 svn
trunk.
I see that Jenkins is happy with whats in the trunk.
However, I can't get a clean build as I'm seeing 2 tests fail in
tapestry-core
Anyone else seeing these failures?
thanks
Jon
in the terminal gradl
That worked and solved the component not yet rendered problem so
${selector:this} ${selector:test}
${selector:this}
${selector:this}
${selector:this} ${selector:first}
outputs
jQuery('#first') jQuery(selector['test'])
jQuery('#any')
jQuery('#any_0')
jQuery('#test') jQuery('#first')
var $ = jQue
On Fri, 12 Aug 2011 09:13:22 -0300, Igor Drobiazko
wrote:
The tapestry-beanvalidator module doesn't has a dependency to any
implementation of the JSR 303. The app developer needs to choose one and
drop it on the classpath. So, the dependency to org.apache.bval.bundle
is correct.
Thanks f
Thanks I know
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-Tapestry-Initializer-s-function-tp4691890p4693526.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e
Vangel,
thank you so much for your clean explanation and the online example you
offer...
I 'll take all this into account,
cheers!
Nicolás.-
On Thu, Aug 11, 2011 at 10:27 PM, Vangel V. Ajanovski wrote:
>
> Of course comments are welcome by anyone, especially regarding how to
> better the sol
On Fri, Aug 12, 2011 at 1:45 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
>
>
> You don't need these dependencies, as Tapestry-BeanValidator already uses
> Hibernate Validator 4 for that.
>
>
The tapestry-beanvalidator module doesn't has a dependency to any
implementation of the J
You placed the annotations on the card bean, but you are passing the page
instance to the form's validate parameter (validate="this"). That's why the
validator doesn't see any validation constrains.
On Fri, Aug 12, 2011 at 9:26 AM, kleanthis wrote:
> Hello all. I am facing a problem and have not
On Fri, 12 Aug 2011 06:19:31 -0300, nillehammer
wrote:
Hi kleanthis,
try t:value="card.cardId" instead of value="card.cardId".
I prefer to use the t: prefix in any parameter which isn't a normal
attribute of the HTML tag used, but it won't make any difference for
Tapestry.
--
Thiago
On Fri, 12 Aug 2011 04:26:19 -0300, kleanthis wrote:
Hello all.
Hi!
I am facing a problem and have not been able to find a solution. I want
to integrate JSR-303 with tapestry 2.5.6.
The problem is that some of my beans/entities come from a diferent domain
model, so i cannot annotate them
On Thu, 11 Aug 2011 10:00:19 -0300, Barry Books wrote:
I'm implementing a selector binding for jQuery. I'd like to be able to
do something like
${selector:this}
and have selector:this emit the html id of its container if it
supports getClientId().
Not out of the box. I'd try to implement a
I changed value to t:value and nothing changed. It seems tapestry cannot
create the necessary validators for the annotations. Removed @NotEampty from
the variable. It was left there while expirementing. Any other ideas?
Did anyone got this to work at least?
-
Do not confuse motion for action.
Hi kleanthis,
try t:value="card.cardId" instead of value="card.cardId". And the annotation
@NotEmpty is not necessary in my opinion.
-
http://www.winfonet.eu
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-and-JSR-303-tp4692368p4692609.html
Sent from the Tap
Hello all. I am facing a problem and have not been able to find a solution. I
want to integrate JSR-303 with tapestry 2.5.6.
The problem is that some of my beans/entities come from a diferent domain
model, so i cannot annotate them with tapestry's @validate annotation.
That's why i want to annotate
15 matches
Mail list logo