Re: LDAP Annotation and Database Hashing Proposal
toggle quoted messageShow quoted text
We can't add additional methods to an interface later on. This would make WAR files packages and compiled against JAVA EE 8, break when they are deployed on a Java EE 9 server for example which has the additional methods in the interface.
So if we decide now (today?) that they are out, they are out forever.
Or we have to define new interface classes.
On 24 July 2017 at 07:46, Guillermo González de Agüero <z06.guillermo@...>
I was going to raise the same concern, although I think properties could be supported in the future by providing a new method and specifying that the old one y to be used when there are no parameters defined, and the new one when there are.
If that is acceptable and can be done in the future, I think it's not such a big deal to leave them for now if the EG don't find consensus.
Guillermo González de Agüero
El lun., 24 de julio de 2017 6:49, Rudy De Busscher <rdebusscher@...
regarding the properties. Indeed when we do not support the properties, they don't need to be specified at the method.
But then, we will never be able to support them in any further version since it would break the backward compatibility of the interface methods. Once this release is out, we can't change anything anymore to interface (no change in the method parameters, method count, etc ... only we can add default implemented methods)
So I guess it is in now or leave out for ever.
Join email@example.com to automatically receive all group messages.