tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Stärk <...@spielviel.de>
Subject Re: Nabble (WAS: Re: Validation Message with Tapestry 4)
Date Tue, 11 Dec 2012 18:01:10 GMT
Google will find everything in Apache's archives (as it does now).


Am 11.12.2012 um 18:18 schrieb Jochen Frey <jochen@jochenfrey.com>:

> FWIW
> 
> Nabble is, in my experience, the best source for google search results when it comes
to Tapestry mailing lists.  Removing the list from Nabble would make that go away, which I
think would be a real loss for users and Tapestry.
> 
> Read-only (or similar) seems reasonable.
> 
> Jochen
> 
> On Dec 11, 2012, at 3:49 AM, Ulrich Stärk <uli@spielviel.de> wrote:
> 
>> This is Nabble stupidity. They don't mark clearly that you 1) have to subscribe in
order to post
>> which means more stuff to moderate for us and 2) what the purpose of the two different
lists is.
>> 
>> Does someone knowledgable with their software know if we can have some descriptive
text or force
>> users to subscribe before being able to post?
>> 
>> Given the quality of the contributions from most Nabble only users I'm inclined to
ask them to
>> remove the Tapestry-Dev "Forum" there or make it read only.
>> 
>> Thoughts?
>> 
>> Uli
>> 
>> 
>> -------- Original Message --------
>> Subject: Re: Validation Message with Tapestry 4
>> Date: Tue, 11 Dec 2012 09:28:38 -0200
>> From: Thiago H de Paula Figueiredo <thiagohp@gmail.com>
>> Reply-To: Tapestry development <dev@tapestry.apache.org>
>> To: Tapestry development <dev@tapestry.apache.org>
>> 
>> Hi!
>> 
>> Please don't post the same message to two different mailing lists. This
>> one should have been posted only in the users one, not in dev.
>> 
>> On Tue, 11 Dec 2012 08:36:33 -0200, SAMPY <sameerprajapati13@gmail.com>
>> wrote:
>> 
>>> I have got few simple IformComponent elements in a page. But the page
>>> contains some of dynamic components, those again have some IformComponent
>>> fields.
>>> 
>>> How can I delegate validation messages in that case.
>>> 
>>> Let me show with an example.
>>> 
>>> 
>>> where this PaymentSelection is component, that renders the html  
>>> dynamically.
>>> 
>>> Validation Java Code :
>>> 
>>>       FormBean bean = this.getHotelsFormBean();
>>>       IValidationDelegate delegate = this.getValidationDelegate();
>>> 
>>>       boolean isValid = super.validateForm(bean, delegate);
>>> 
>>>       try {
>>>           if(Utils.isNullOrEmpty(bean.getHotelName())) {
>>>               String message =  
>>> this.getMessages().getMessage("bb_ERR5");
>>>               this.error(delegate, (IFormComponent)
>>> this.getComponent("hotelName"), message,
>>>                          ValidationConstraint.REQUIRED);
>>>               isValid = false;
>>>           }
>>> 
>>> 
>>> message =  this.getMessage("valid", new String[] { "cardnum" });
>>> this.error(delegate, (IFormComponent)
>>> this.getComponent("paymentSelectionComponent").getComponent("code"),
>>> message,
>>>                            ValidationConstraint.REQUIRED);
>>>   isValid = false;
>>>   break;
>>> 
>>> In general, it delegates the error message for hotel fields(that hotel  
>>> name
>>> not given sort of message), but it doesn't  delegate the dynamic
>>> component(PaymentSelection) error message with above message.
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:  
>>> http://tapestry.1045711.n5.nabble.com/Validation-Message-with-Tapestry-4-tp5718594.html
>>> Sent from the Tapestry - Dev mailing list archive at Nabble.com.
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>> 
>> 
>> 
>> -- 
>> Thiago H. de Paula Figueiredo
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>> 
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>> 
> 
> ---
>  jochen@jochenfrey.com
>  +1.415.366.0450
>  @jochen_frey
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message