samoa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianmarco De Francisci Morales <g...@apache.org>
Subject Re: [jira] [Created] (SAMOA-46) copy() in abstractOptionHandler clashes with copy() in OptionsHandler
Date Tue, 20 Oct 2015 07:11:56 GMT
Hi,

Thanks for reporting the bug.
As far as I see, the copy method in AbstractOptionHandler is inherited from
the same interface MOAObject, which is extended by InstanceStream.
So you should tighten the return type of the copy() method and declare it
as:

  @Override
  public OptionHandler copy() {
    return null;
  }

Given that OptionHandler is a MOAObject, it should work.

Hope it helps,

--
Gianmarco

On 13 October 2015 at 13:03, Amir Rahnama (JIRA) <jira@apache.org> wrote:

> Amir Rahnama created SAMOA-46:
> ---------------------------------
>
>              Summary: copy() in abstractOptionHandler clashes with copy()
> in OptionsHandler
>                  Key: SAMOA-46
>                  URL: https://issues.apache.org/jira/browse/SAMOA-46
>              Project: SAMOA
>           Issue Type: Bug
>             Reporter: Amir Rahnama
>
>
> In org.apache.samoa.streams package, I tried to add a new TwitterStream
> source so I coded a new class:
>
> public class TwitterStreamInstance extends AbstractOptionHandler implements
>     InstanceStream {
> }
>
> Problem is that the copy object which in this case should be overriden
> becomes a bottleneck:
>
>     @Override
>     public MOAObject copy()
>     {
>         return null;
>     }
>
> This very same issue happens when I opened FileStream.java in the same
> package.
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message