> The reason I have an issue with this is that as I, and > others, have previously highlighted you cannot simply extend > an SDI class to implement a CDI equivalent. Java does not > allow us to reduce the visibility of the inherited SDI setter > methods, but we need to to make the contract of the CDI class > clear.
What does a public setter break in the contract with a CDI environment? BTW, I think someone should start with the POJOs... "s/public (set|get)/protected \1/g" is a what you can use later ;-) . It will take less time the refactoring than this discussion ;-) Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
