You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2015/07/09 09:18:22 UTC
Deprecated the Conversion Library
Since the UnitOfWork now provides a more integrated solution to conversion
between Entities and Values, the Conversion Library has no real purpose.
However, I have one small app still using it, and instead of simply
removing it, I am deprecating it and will be dropped in 3.0
Cheers
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Re: Deprecated the Conversion Library
Posted by Paul Merlin <pa...@nosphere.org>.
Some use-cases:
- don't expose the whole state (eg. password hashes)
- computed/transformed state (eg. entity state ~ value state)
Paul Merlin a écrit :
> Niclas,
>
> I extensively use the Conversion library in my apps.
>
> Does the new UoW support for conversion between Entities and Values
> allows for type-relaxed conversion and does it provide a way to insert
> custom conversion code (see 'prototypeOpportunity' in Conversion library) ?
>
> /Paul
>
>
> Niclas Hedhman a écrit :
>> Since the UnitOfWork now provides a more integrated solution to conversion
>> between Entities and Values, the Conversion Library has no real purpose.
>>
>> However, I have one small app still using it, and instead of simply
>> removing it, I am deprecating it and will be dropped in 3.0
>>
>>
>> Cheers
>
Re: Deprecated the Conversion Library
Posted by Paul Merlin <pa...@nosphere.org>.
Niclas Hedhman a écrit :
> No it doesn't, but then I think we should spend the time to find the
> additional solutions to support these usecases in the primary
> toEntity/toValue mechanism. And with the deprecation, it is clear that
> these cases will have to get some work prior to 3.0.
>
> Makes sense?
Yep, I'm good with that!
Re: Deprecated the Conversion Library
Posted by Niclas Hedhman <ni...@hedhman.org>.
No it doesn't, but then I think we should spend the time to find the
additional solutions to support these usecases in the primary
toEntity/toValue mechanism. And with the deprecation, it is clear that
these cases will have to get some work prior to 3.0.
Makes sense?
Niclas
On Thu, Jul 9, 2015 at 10:24 AM, Paul Merlin <pa...@nosphere.org> wrote:
> Niclas,
>
> I extensively use the Conversion library in my apps.
>
> Does the new UoW support for conversion between Entities and Values
> allows for type-relaxed conversion and does it provide a way to insert
> custom conversion code (see 'prototypeOpportunity' in Conversion library) ?
>
> /Paul
>
>
> Niclas Hedhman a écrit :
> > Since the UnitOfWork now provides a more integrated solution to
> conversion
> > between Entities and Values, the Conversion Library has no real purpose.
> >
> > However, I have one small app still using it, and instead of simply
> > removing it, I am deprecating it and will be dropped in 3.0
> >
> >
> > Cheers
>
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Re: Deprecated the Conversion Library
Posted by Paul Merlin <pa...@nosphere.org>.
Niclas,
I extensively use the Conversion library in my apps.
Does the new UoW support for conversion between Entities and Values
allows for type-relaxed conversion and does it provide a way to insert
custom conversion code (see 'prototypeOpportunity' in Conversion library) ?
/Paul
Niclas Hedhman a écrit :
> Since the UnitOfWork now provides a more integrated solution to conversion
> between Entities and Values, the Conversion Library has no real purpose.
>
> However, I have one small app still using it, and instead of simply
> removing it, I am deprecating it and will be dropped in 3.0
>
>
> Cheers