Put simply : the tags are using the .toString method of the property instead
of the registered type converters.

This happens when you do a :

$tag.ActualValue  .. This is an instance of an object, that velocity calls
toString() on to print it out.

I guess that I am saying that I want a new method $tag.StringValue to use
the registered type converter to convert the $tag.ActualValue to string.
And for all of the UI taglib .vm templates to use this.

Also, I would like a xwork-conversion.properties that allows the
specification of default type -> converter mappings that are the global
defaults. 

..cam..

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Pat Lightbody
> Sent: Friday, 30 May 2003 2:43 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] XW: TypeConversion support
> 
> 
> Well, we could check all super classes up until 
> Object-conversion.properties, but the real problem is that we 
> have yet to come up with a good game plan for how type 
> conversion should be handled. I've heard lots of small 
> suggestions, but what we really need is a list of problems 
> with the current implementation and then we can work on 
> addressing them.
> 
> -Pat
> 
> ----- Original Message -----
> From: "Cameron Braid" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 29, 2003 4:46 AM
> Subject: RE: [OS-webwork] XW: TypeConversion support
> 
> 
> > One problem with the current implementation of the 'action property 
> > specific' type converters is that if you have the properties in an 
> > action superclass, you need to re-state the converters for the each 
> > subclass.
> >
> > I think it is very important to allow system wide type 
> converter for 
> > each type. i.e. xwork-xwork-converter.properties
> >
> > Is there any indication of when this may be implemented, or an 
> > alternate procedure for the meantime... Ie can we specify the class 
> > name of a custom class that extends XWorkConverter to allow 
> the custom 
> > registration of converters ? Currently there is no way to 
> change the 
> > default converters.
> >
> > Thanks,
> >
> > ..Cam..
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] 
> On Behalf 
> > > Of Pat Lightbody
> > > Sent: Thursday, 15 May 2003 5:54 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [OS-webwork] XW: TypeConversion support
> > >
> > >
> > > Yeah, I think that makes sense.
> > >
> > > The only question is.. should type converteres be 
> specified in XML 
> > > to allow for parameterized options? Ie: DateConverter 
> could take a 
> > > param that is the format...
> > >
> > > -Pat
> > >
> > > ----- Original Message -----
> > > From: "Heng Sin Low" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Wednesday, May 14, 2003 8:26 AM
> > > Subject: Re: [OS-webwork] XW: TypeConversion support
> > >
> > >
> > > > I think it make sense to allow the specifying of default
> > > converter by
> > > > destination property, perhaps in a properties file name 
> > > > xwork-converter.properties
> > > >
> > > > For e.g,
> > > java.util.Date=com.opensymphony.xwork.converter.DateConverter
> > > >
> > > java.math.BigDecimal=com.opensymphony.xwork.converter.BigDecim
> > > alConverter
> > > >
> > > > To make things more flexible, it should also have api 
> to allow the
> > > programatic
> > > > registration of converter by destination type or the 
> combination 
> > > > of property-name + class-name.
> > > >
> > > > Btw, are others also facing frequent difficulty connecting to 
> > > > sourceforge
> > > cvs ?
> > > > Pretty annoying.
> > > >
> > > > Regards,
> > > > Low
> > > > --- Pat Lightbody <[EMAIL PROTECTED]> wrote:
> > > > > OK, I just checked in much better type conversion 
> support. A few
> > > > > things:
> > > > >
> > > > > - XWorkConverter is a singleton now.
> > > > >
> > > > > - XWorkConverter is not the -only- type converter
> > > supported by XWork
> > > > > and WebWork. You can specify other type converters by...
> > > > >
> > > > > - Special type conversion is by creating a file called 
> > > > > YourClass-conversion.properties (XML anyone?) with a
> > > key-value pair
> > > > > of propertyName=typeConversionClass. The type 
> conversion class 
> > > > > is used for
> > > all
> > > > > kinds of type conversion (meaning for both setters as well as 
> > > > > getters
> > > when
> > > > > displayed to the web as String). I've got some examples in 
> > > > > OgnlUtilTest
> > > and
> > > > > XWorkConverter.
> > > > >
> > > > > One thing that is still left open is that the default type 
> > > > > conversion
> > > logic
> > > > > in XWorkConverter (used if a different converter isn't
> > > specified in
> > > > > a properties file) isn't very i18n friendly yet. It uses
> > > MM/dd/yyyy
> > > > > still. Anyone have any ideas how this can be fixed? Obviously 
> > > > > one could just
> > > create
> > > > > property files for all their date fields and using a special
> > > DateConverter
> > > > > that uses your desired format, but that's not really 
> acceptable 
> > > > > either.
> > > > >
> > > > > -Pat
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 
> 2003, Santa 
> > > > > Clara The only event dedicated to issues related to Linux
> > > enterprise
> > > > > solutions www.enterpriselinuxforum.com
> > > > >
> > > > > _______________________________________________
> > > > > Opensymphony-webwork mailing list 
> > > > > [EMAIL PROTECTED]
> > > > > 
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwor
> > > > > k
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> > >
> > >
> > > -------------------------------------------------------
> > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa 
> > > Clara The only event dedicated to issues related to Linux 
> enterprise 
> > > solutions www.enterpriselinuxforum.com
> > >
> > > _______________________________________________
> > > Opensymphony-webwork mailing list 
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >
> >
> >
> > -------------------------------------------------------
> > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, 
> Santa Clara 
> > The only event dedicated to issues related to Linux enterprise 
> > solutions www.enterpriselinuxforum.com
> >
> > _______________________________________________
> > Opensymphony-webwork mailing list 
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: eBay
> > Get office equipment for less on eBay! 
> > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> > _______________________________________________
> > Opensymphony-webwork mailing list 
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: eBay
> Get office equipment for less on eBay! 
> http://adfarm.mediaplex.com/ad/ck/711-11697-> 6916-5
> 
> _______________________________________________
> 
> Opensymphony-webwork mailing list 
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to