Bug 11783 - jcifs: binding generator tools miss some methods that involves derivation in different jars
Summary: jcifs: binding generator tools miss some methods that involves derivation in ...
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 4.7.x
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2013-04-14 18:32 UTC by Atsushi Eno
Modified: 2013-04-15 15:26 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Atsushi Eno 2013-04-14 18:32:01 UTC
Some customer feedback: http://jcifs.samba.org/ does not bind due to some missing methods.

My comments to the customer:

> conflicting method overloads - this is complicated bug, but basically it is bug that needs some fix in binding generator tool. There are several cases that cause this kind of method conflicts and many of them can be workarounded by manipulating Metadata.xml, but this case it couldn't. I have a nasty hack to workaround it - copy generated C# code for MD4 and HMACT64 into "Additions", fix those bogus "virtual" as "override", and then enable metadata <remove-node>s for them.

It is likely due to failing reflected dll methods which smells like a generator bug.
Comment 1 Atsushi Eno 2013-04-15 15:26:18 UTC
Fixed. [master 0630213]