[
https://issues.apache.org/jira/browse/PYLUCENE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085963#comment-17085963
]
Petrus Hyvönen commented on PYLUCENE-53:
----------------------------------------
Hi Andi,
Hope all well. Just wanted to check with you if you did spend any more thinking
on this.. I almost understand what you write but way too complex for me to
enter. I guess a generic way to solve this would be the best. Otherwise would
there be a way basically to check the interfaces for default implementations
and then refer on the "Cat" class up to "Being"? But it is likely some caveats
on that..
I guess this is also related to the need of sometimes casting objects to
"visualize" the right interface?
Regards
/P
> JCC Default implementations from Interfaces not exposed
> -------------------------------------------------------
>
> Key: PYLUCENE-53
> URL: https://issues.apache.org/jira/browse/PYLUCENE-53
> Project: PyLucene
> Issue Type: Bug
> Reporter: Petrus Hyvönen
> Priority: Major
> Attachments: Test_default_implementation.zip
>
>
> Hi,
> This may be related to PYLUCENE-27 but not sure.
> Default implementations of methods in an interface does not seem to be
> exposed currently.
> For example:
> The interface:
> interface Being {
> public void printName();
> default int getFeets()
> {
> return 4;
> }
> }
> Implemented in the class:
> public class Cat extends Feline implements Being {
> public void printName() {
> System.out.println("Cat");
> }
> public int getJavaFeets()
> {
> return this.getFeets();
> }
> }
> When wrapped in Python, the getJavaFeets is exposed to the Python side, but
> not the getFeets method.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
