+1 Regards, Michael
> Am 07.02.2018 um 10:13 schrieb Taher Alkhateeb <[email protected]>: > > I propose a feature freeze on anything related to minilang. Let's just fix > bugs and try to slowly move out. > >> On Feb 7, 2018 11:36 AM, "Rishi Solanki" <[email protected]> wrote: >> >> Jacques, >> As far as I remember when you raised this in past, and no proposal on how >> to replace it. >> As simple map processor is used for mapping and validation, So I think we >> should take a pause on it and let the remaining minilang to groovy >> complete. >> >> From my side having simple map processor in minilang (we could also use >> XML) should be fine for now. And we can discuss/think/propose on the >> alternative ways of doing the same once solution is in place and we agree, >> then we can decide weather to remove old way or keep it. >> >> I see similar approach in other projects and they keep supporting both ways >> to invoke validation methods for a while. >> >> Best, >> >> >> Rishi Solanki >> Sr Manager, Enterprise Software Development >> HotWax Systems Pvt. Ltd. >> Direct: +91-9893287847 >> http://www.hotwaxsystems.com >> www.hotwax.co >> >> On Wed, Feb 7, 2018 at 2:57 AM, Jacques Le Roux < >> [email protected]> wrote: >> >>> Hi, >>> >>> I recently see some activity to replace the minilang by Groovy and that's >>> great. >>> >>> There is though a question I asked 2 times[1][2] without any answers. >> It's >>> about the Simple Map Processor Mini-Language: >>> >>> https://cwiki.apache.org/confluence/pages/viewpage.action? >>> pageId=50233697#Mini-LanguageGuide(Version1-Deprecated)-TheS >>> impleMapProcessorMini-Language >>> >>> Shall we keep it as is or replace it, and then by what? Is there already >> a >>> plan for that? I saw none I'm not wrong. >>> >>> [1] http://markmail.org/message/z63ff7s7hgm4rb3e >>> [2] https://s.apache.org/Nm9B >>> >>> Jacques >>> >>> >>> >>
