Unfortunately, I don't think so. The Scala reflection is completely
separate from Java reflection. We reuse the PojoTypeInformation,
though.
On Tue, Jan 6, 2015 at 1:16 PM, Stephan Ewen wrote:
> Okay. My last question was aiming towards whether we can consolidate code
> there and not have two red
Okay. My last question was aiming towards whether we can consolidate code
there and not have two redundant paths (in scala and in java)
On Tue, Jan 6, 2015 at 12:18 PM, Aljoscha Krettek
wrote:
> Sorry, for the long wait, I had to retry some of my earlier tests.
>
>
>
> On Tue, Jan 6, 2015 at 11:
Sorry, for the long wait, I had to retry some of my earlier tests.
On Tue, Jan 6, 2015 at 11:04 AM, Stephan Ewen wrote:
> Some questions to understand that better:
>
> - When can the Scala type extractor not determine the same than the Java
> one? What additional cases could the Java Type Extr
Some questions to understand that better:
- When can the Scala type extractor not determine the same than the Java
one? What additional cases could the Java Type Extractor find?
- How do you distinguish between a Java-created and a Scala-created class?
- Does it make sense to use the same log
Hi,
Right now, the Scala Type Extraction logic falls back to using the
Java TypeExtractor when it encounters a class that was written in Java
or when it cannot analyse a Scala Type. I did this because the Java
TypeExtractor might catch some additional cases. The other option
would be to directly fa
