Hello everyone, I use converter libs for some apps in my company. If this feedback can be usefull, all the better - otherwise, just ignore this mail ;)
Here are the use cases for it : 1. Web service TO to BO conversion (we use jax-ws web services as a facade to our business layer and do not expose our internal business model). We use dozer here (but it's kind of heavyweight - and not sure I like using this kind of lib anymore here : I lose compilation support, so it's quite error-prone). 2. Built-in conversion when using MVC frameworks a la Spring MVC. So if DS provided a MVC framework, I guess it would need to have a conversion lib. 3. Built-in conversion for JSF ;) I think conversion functionnality can be dropped since DS doesn't adress for now points 1 and 2. Regards, P.S. : Gerhard said once about a possibility to have a conversion JSR - but didn't heard about it since. ________________________________ De : Mark Struberg <[email protected]> À : deltaspike <[email protected]> Envoyé le : Jeudi 14 juin 2012 6h44 Objet : [VOTE] Converter framework a.) What is this for? -> no one knows b.) Do we need it in DeltaSpike? -> not yet. c.) Do we need it for JSF? -> No, JSF has it's own Converter logic d.) Do we need it somewhere else? -> No, not afaik So let's drop the Converter stuff which is currently of no use and really complicated to get right? Just remember that this was more or less a 1:1 copy of the Spring logic which has not so easily extendible producer methods. [+1] Drop it, our code will get complicated enough anyway [+0] Meh, don't care [-1] keep it because it is very important (+ give use case and reasons) LieGrue, strub
