[shale-validator] CommonsValidator doesn't take component converters into account!

2007-02-21 Thread Hasan Turksoy

hi all,

Env: jsf1.1, commons-validator1.3.1, shale1.0.4..

i'am trying to put a required validator for my date entering field.. My
field has a f:convertDateTime to make conversion between String -
java.util.Date. it's like;

h:inputtext ...
 f:convertDateTime dateStyle=short /
 s:commonsvalidator type=required arg=... client=true server=true
/
/h:inputtext

When i entered a valid value into my date field it throws a
ConverterException as below;

javax.faces.ConverterException: You have requested a conversion for type
java.util.Date, but there is no by-type converter registered for this type.

as i understand; it needs a converter for the java.util.Date class.. But in
JSF, one can assign custom converter tags as above sample...

this means, (my suggestion) commonsvalidator should get the converter for
that type from component. if component don't have any converters assigned,
it should lookup for a by-type converter then... Otherwise, i will have to
define by-type converters for all my component converters! this will be
stupid i think...

any comments?? or solutions??

thanks in advance,
hasan...


Re: [shale-validator] CommonsValidator doesn't take component converters into account!

2007-02-21 Thread Gary VanMatre
From: Hasan Turksoy [EMAIL PROTECTED] 

 hi all, 
 
 Env: jsf1.1, commons-validator1.3.1, shale1.0.4.. 
 
 i'am trying to put a required validator for my date entering field.. My 
 field has a f:convertDateTime to make conversion between String - 
 java.util.Date. it's like; 
 
 
h:inputtext ...
  f:convertDateTime dateStyle=short /
  s:commonsvalidator type=required arg=... client=true server=true
/
/h:inputtext
 
 When i entered a valid value into my date field it throws a 
 ConverterException as below; 
 
 javax.faces.ConverterException: You have requested a conversion for type 
 java.util.Date, but there is no by-type converter registered for this type. 



I'm not sure why you are seeing this exception.  I belive that the 
java.util.Data 
converter should be registered with the JSF runtime.

Can you tell where the exception is being raised from the stack trace?  
The reason for asking is that the shale commons validator uses JSF 
converters to coerce data types to match the signatures of the server
side validation methods.


 

 
 as i understand; it needs a converter for the java.util.Date class.. But in 
 JSF, one can assign custom converter tags as above sample... 
 
 this means, (my suggestion) commonsvalidator should get the converter for 
 that type from component. if component don't have any converters assigned, 
 it should lookup for a by-type converter then... Otherwise, i will have to 
 define by-type converters for all my component converters! this will be 
 stupid i think... 
 
 any comments?? or solutions?? 
 
What version of the JSF runtime are you using?  This sounds like a rutime issue.



 thanks in advance, 
 hasan..


Gary.

Re: Clay challange

2007-02-21 Thread Ryan Wynn

On 2/14/07, Gary VanMatre [EMAIL PROTECTED] wrote:

From: [EMAIL PROTECTED]

 Hi

 Thanks, Ryan. This is what you get when you copy/paste and then go blind :) (I
 need to sit down and repeat to my self: DO NOT DO THIS! a thousand times)


You are not alone there.  Hey Ryan, what's the status of that Eclipse 3.2 plug 
in that you are trying to get IBM to donate?



The donation is coming along.  I need to submit a couple of documents
to ibm and then a review will be held on it.  Sorry for the wait, it
has been mostly due to my busyness and somewhat the tedious process
ibm has in place.

For those of you that don't know I was planning to donate an eclipse
plugin with a gui and drag n drop for building clay config files.  It
dynamically finds all the clay config defs in your project and builds
a component palette.  When you create new component defs they get
added to the palette.  So it's all about reusablilty.




 Hermod


Gary

 -Original Message-
 From: Ryan Wynn [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 13, 2007 11:23 PM
 To: user@shale.apache.org; [EMAIL PROTECTED]
 Subject: Re: Clay challange


 On 2/13/07, Hermod Opstvedt wrote:
  Hi
 
  I'm struggling with a component that I have defined:
 
 
 
 
 
 
 
 
 
 
 
 
   
  value=#{messages['navnpanel.text']}
 
 
 
 
 
 
value=#{messages['navnpanel.text']}
 
 
 
 
 
  It is supposed to render a fieldset with a legend, and a label inside it.
  However the label never appears and there are no errors what so ever.

 I think you might need to look at your renderIds. The renderId
 attribute is a way of ordering component children. RenderIds are only
 relevant for sibling elements. If you have 2 sibling elements with
 the same renderId value then one of the elements will be
 lost/replaced.

 In your case the t:htmlTag and outputLabel both have the same parent
 (t:htmlTag) but they also use the same renderId (2). They should
 instead be 1 and 2.

 My renderIds usually start at 1 for each element set and increment
 from there. I think only the relative values matter, so you could
 have renderIds 6 and 3 and you would still get 2 children with the 3
 renderId as the first child.

 With inheritance you are able to override a component's children
 selectively by specifying another component with the same renderId.


 ...
 ...



 ..


 both c1 and c2 produce a clay component with 2 children. c2 uses
 inheritance and the renderId attribute to override the second
 outputText in c1 with an inputText. But, c2 still inherits the first
 outputText child from c1.

 Hope this helps.

 
  Hermod
 
 
 


 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 This email with attachments is solely for the use of the individual or
 entity to whom it is addressed. Please also be aware that DnB NOR cannot
 accept any payment orders or other legally binding correspondence with
 customers as a part of an email.

 This email message has been virus checked by the anti virus programs used
 in the DnB NOR Group.

 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *



SV: Clay challange

2007-02-21 Thread Hermod Opstvedt
Hi

I am so excited I can hardly wait.

Hermod


-Opprinnelig melding-
Fra: Ryan Wynn [mailto:[EMAIL PROTECTED] 
Sendt: 21. februar 2007 23:31
Til: user@shale.apache.org
Emne: Re: Clay challange

On 2/14/07, Gary VanMatre [EMAIL PROTECTED] wrote:
 From: [EMAIL PROTECTED]
 
  Hi
 
  Thanks, Ryan. This is what you get when you copy/paste and then go blind
:) (I
  need to sit down and repeat to my self: DO NOT DO THIS! a thousand
times)
 

 You are not alone there.  Hey Ryan, what's the status of that Eclipse 3.2
plug in that you are trying to get IBM to donate?


The donation is coming along.  I need to submit a couple of documents
to ibm and then a review will be held on it.  Sorry for the wait, it
has been mostly due to my busyness and somewhat the tedious process
ibm has in place.

For those of you that don't know I was planning to donate an eclipse
plugin with a gui and drag n drop for building clay config files.  It
dynamically finds all the clay config defs in your project and builds
a component palette.  When you create new component defs they get
added to the palette.  So it's all about reusablilty.



  Hermod
 

 Gary

  -Original Message-
  From: Ryan Wynn [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, February 13, 2007 11:23 PM
  To: user@shale.apache.org; [EMAIL PROTECTED]
  Subject: Re: Clay challange
 
 
  On 2/13/07, Hermod Opstvedt wrote:
   Hi
  
   I'm struggling with a component that I have defined:
  
  
  
  
  
  
  
  
  
  
  
  

   value=#{messages['navnpanel.text']}
  
  
  
  
  
  
 value=#{messages['navnpanel.text']}
  
  
  
  
  
   It is supposed to render a fieldset with a legend, and a label inside
it.
   However the label never appears and there are no errors what so ever.
 
  I think you might need to look at your renderIds. The renderId
  attribute is a way of ordering component children. RenderIds are only
  relevant for sibling elements. If you have 2 sibling elements with
  the same renderId value then one of the elements will be
  lost/replaced.
 
  In your case the t:htmlTag and outputLabel both have the same parent
  (t:htmlTag) but they also use the same renderId (2). They should
  instead be 1 and 2.
 
  My renderIds usually start at 1 for each element set and increment
  from there. I think only the relative values matter, so you could
  have renderIds 6 and 3 and you would still get 2 children with the 3
  renderId as the first child.
 
  With inheritance you are able to override a component's children
  selectively by specifying another component with the same renderId.
 
 
  ...
  ...
 
 
 
  ..
 
 
  both c1 and c2 produce a clay component with 2 children. c2 uses
  inheritance and the renderId attribute to override the second
  outputText in c1 with an inputText. But, c2 still inherits the first
  outputText child from c1.
 
  Hope this helps.
 
  
   Hermod
  
  
  
 
 
  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
 
  This email with attachments is solely for the use of the individual or
  entity to whom it is addressed. Please also be aware that DnB NOR cannot
  accept any payment orders or other legally binding correspondence with
  customers as a part of an email.
 
  This email message has been virus checked by the anti virus programs
used
  in the DnB NOR Group.
 
  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
 



Has anybody got the shale-usecases app to deploy

2007-02-21 Thread Alessio Harri
Has anybody got the shale-usecases app to deploy on any J2EE1.4 app server 
besides tomcat 5.5 ?



Metropolitan is an authorised Financial Services Provider.

NOTE: This e-mail (including attachments) is subject to the restrictions, 
qualifications and disclaimers (the disclaimer) published at 
http://www.metropolitan.co.za Please read the disclaimer before opening any 
attachments or taking any other action in terms of this e-mail.
If you cannot access the disclaimer, kindly send an e-mail to [EMAIL PROTECTED] 
or contact [EMAIL PROTECTED] and a copy will be sent to you.
By reading this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.

Web: http://www.metropolitan.co.za/
Disclaimer: http://www.metropolitan.co.za/email_disclaimer.html


Metropolitan Life subscribes to KPMG, a completely independent crime disclosure 
service - make a contribution to the establishment of a fraud free environment 
by reporting any suspicion to the KPMG Hotline
 
 * RSA 0800 22 14 18 
 * NAMIBIA 0800 00 00 77