On 5 May 2004, at 22:38, Paul Libbrecht wrote:
THere has been many mentions about Jelly "not converting my string into an array as expected"...
Same thing happens in j:forEach: people expect the list to be "naturally" separated by some spaces, commas, or whatever...
Everytime I read this I keep being frightened if such a feature would be introduced in Jelly... It would be very very unpredictable (suppose I am using this with the input of a user...).
+1
In order for such a patch and several others to be applied, I would like to become convinced that one can do this in a way developers expect.
+1
One way could be to have separators as extra attribute:
- this would work well for j:forEach
- it would solve the problem here except that "separator" or "separators" couldn't be a bean-property-name
Remember, though, that we would need a syntax for such separators, in particular if one wishes to express categorie of characters like "whitespace".
in general, i agree.
i have observed (from betwixt where the comma is the only separator that's been requested) that comma separation is the pseudo-standard (most common use case). so, a specific solution for this use case may well be good enough.
Anyone else with good ideas ? A global setting impacting BeanUtils ?
there are a number of beanutils related stuff that we could think about trying. beanutils has become critical (there are lot of applications that require a beanutils release that is compatible with the incompatible 2.1 and 3.0 versions of collections very soon) and so the beanified version is going to get sorted out now. this means that it'd be both an opertunity to look at what jelly needs from beanutils and also to reconsider the jelly tag's use of the older, static jelly methods.
(i'm going to be busy tomorrow and friday but hopefully i'll be able to pick up this thread this weekend...)
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
