Changes between Version 132 and Version 133 of j2p

Timestamp:

09/24/24 15:32:17 (5 weeks ago)

Author:

wouter

Comment:

--

j2p

@@ -386 +386 @@
 ||I get UnsupportedOperationException ... ResolvedWildcard||This happens sometimes in complex method calls with complex parameters. Usually this happens in a stream() context. We suggest using manual translation in such case||
 ||I get {{{Inner classes can not be translated}}}||Check the section on [wiki:j2p#Innerclasses inner classes]||
-||I get something like {{{from com.X.Y.Z import Z: ModuleNotFoundError: No module named 'com'}}}. {{{com.X.Y.Z}}} is a java package that does not exist in python. ||You did not provide  a library or code translate {{{com.X.Y.Z}}} and the translator now uses a "stub" translator that assumes the package on the python side is identical. To fix, you have to add a translator for the {{{com.X.Y.Z}}} package.||
+||I get something like {{{from com.X.Y.Z import Z: ModuleNotFoundError: No module named 'com'}}}. {{{com.X.Y.Z}}} is a java package that does not exist in python. ||You did not provide  a library or code translate {{{com.X.Y.Z}}} and the translator now uses a "stub" translator that assumes the package on the python side is identical. To fix, you have to add a translator for the {{{com.X.Y.Z}}} package. Or avoid using the package in java||