I found jni4net bridge between Java and .NET (intraprocess, fast, object oriented, open-source).

Hi guys?!

There might be other dependencies between DLLs which are not listed in the SDK.

It is not possible to generate Java proxies for these DLLs. You see also listed the error messages of JNI4NET for each DLL:

Sdl.Core.Api.dll                                                                    Object reference not set to an instance of an object.

Sdl.LanguagePlatform.TranslationMemory.dll                     Sdl.LanguagePlatform.TranslationMemoryApi.dll

Sdl.LanguagePlatform.TranslationMemoryApi.dll                Sdl.LanguagePlatform.TranslationMemoryApi.dll

Also the SDK recommends to choose the installation folder of SDL Trados Studio 2014 as build output path for SDL TM API implementations.

Please is anybody out there?

Jörg

Hi guys?!

There might be other dependencies between DLLs which are not listed in the SDK.

It is not possible to generate Java proxies for these DLLs. You see also listed the error messages of JNI4NET for each DLL:

Sdl.Core.Api.dll                                                                    Object reference not set to an instance of an object.

Sdl.LanguagePlatform.TranslationMemory.dll                     Sdl.LanguagePlatform.TranslationMemoryApi.dll

Sdl.LanguagePlatform.TranslationMemoryApi.dll                Sdl.LanguagePlatform.TranslationMemoryApi.dll

Also the SDK recommends to choose the installation folder of SDL Trados Studio 2014 as build output path for SDL TM API implementations.

Please is anybody out there?

Jörg

Have you considered coming at this from the other end, meaning compiling the java to .NET with IKVM? I use that a lot to compile fairly complex java libraries into .NET IL, so I can use them in a .NET application, and it works pretty well. I'd guess it'd be a lot easier to drive the SDK this way ... Have a look at www.ikvm.net/uses.html and www.ikvm.net/.../java2net.html

Kevin

SDK dll's depend on various other assemblies which can only be find in the SDL Trados Studio 2014 installation folder. This assemblies are not registered in GAC so the only option is to run your application in the same folder with the SDL Trados Studio 2014.

Kevin and Romulus, thank you for your kind support!

I still have a chance. The JNI4NET framework allows to add dependencies in the command to generate Java proxies. I hope SDL is open minded and provides me the information about all dependencies/ GAC conflicts.

From this state of view the SDK is somehow buggy. I have to deploy in the Studio folder to catch all dependencies by luck or reasoned by the Global Assembly Cache.

Otherwise I need to switch from Tomcat Servlets to IIS ASP.NET. But I don't need to compile from Java to .NET with IKVM, but good to know!

I keep you updated! Kind regards from Berlin

Jörg

If you would like to know how you might be able to deploy your Studio application in any location please have a look here: Assembly Resolver