You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Migration Tool only has a scala api which requires the java user to convert the results (scala futures), which is not very convenient.
It was recommended to introduce a scaladsl and javadsl package, and then to move the existing scala based implementation one to scaladsl packed and then create a subclass (or facade) where it currently resides with the same name, and deprecate that.
Constructor signature should be maintained to stay binary compatible, if possible.
The text was updated successfully, but these errors were encountered:
Currently the Migration Tool only has a scala api which requires the java user to convert the results (scala futures), which is not very convenient.
It was recommended to introduce a
scaladsl
andjavadsl
package, and then to move the existing scala based implementation one toscaladsl
packed and then create a subclass (or facade) where it currently resides with the same name, and deprecate that.Constructor signature should be maintained to stay binary compatible, if possible.
The text was updated successfully, but these errors were encountered: