That describes the situation very well :-)
The proxy generator for version 0.8.x is crap, but it is able to wrap
If you are able to wrap your api then fine. If you are not able to do
it, because of proxygen bugs, I suggest that you create facade which
is simpler and wrap that.
The 0.8.6 runtime is stable and I think many people use it in
So, if it passed your testing, it would not fail on you in production.
There is version 0.9 rewrite in progress. Proxygen there is much
better code, but unfinished. The runtime there has bugs to be fixed.
Overall 0.9 I spent year of my late night oil on 0.9 and it will need
couple of months yet.
I'm not sure when I'll find the motivation to continue on it.
On Tue, Jul 24, 2012 at 3:19 PM, Daniel Manzke
> Hi guys,
> we are thinking about using jni4net to create .NET Wrapper for our Java API.
> At the moment I don't see a big problem to do that until I have read the
> sentence "Status - currently Alpha quality. Lot of work ahead, lot of ideas,
> lot of missing features, looking forward to community feedback.". Any
> thoughts about it? :)
> You received this message because you are subscribed to