On 13 June 2017 at 09:06, Gunnar Morling wrote:
> 2017-06-13 7:54 GMT+02:00 Christian Beikov :
>> Hi,
>>
>> this might work for a limited set of use cases, but what exactly are you
>> expecting from that approach? Performance might be a bit better, but
>> that's probably negligible. Apart from tha
2017-06-13 7:54 GMT+02:00 Christian Beikov :
> Hi,
>
> this might work for a limited set of use cases, but what exactly are you
> expecting from that approach? Performance might be a bit better, but
> that's probably negligible. Apart from that, I only see "encapsulation"
> or "ease of use with oth
Hi,
this might work for a limited set of use cases, but what exactly are you
expecting from that approach? Performance might be a bit better, but
that's probably negligible. Apart from that, I only see "encapsulation"
or "ease of use with other languages" being your argument. Is that
correct,
To work, yes. This would be an optional means of injecting. I was thinking
some code like this (very very rough):
public void prep(DataSource source)
throws SQLException, NoSuchMethodException,
IllegalAccessException, InvocationTargetException,
InstantiationException {
ResultSet resultSet =
Hi,
Wouldn't that require all entities be compiled with?
javac -parameters
Vlad
On Mon, Jun 12, 2017 at 10:19 PM, Christian Bongiorno <
christian.bongio...@gmail.com> wrote:
> Now that java 8 supports named parameters it becomes possible (potentially
> preferrable) to use constructor injection
