<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent posts to news</title><link>https://sourceforge.net/p/j-interop/news/</link><description>Recent posts to news</description><atom:link href="https://sourceforge.net/p/j-interop/news/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 22 Dec 2014 06:16:01 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/j-interop/news/feed.rss" rel="self" type="application/rss+xml"/><item><title>j-Interop 3.0 Released ! discussion</title><link>https://sourceforge.net/p/j-interop/news/2013/06/j-interop-30-released-/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hey Vikram,&lt;/p&gt;
&lt;p&gt;I am Madhur Chaini working as Java Software Developer.Here we are using your J-interop and J-interopdeps jars for supporting WMI. And now we want to support both ipv4 and ipv6 address in our product.Related jar i.e. JCIFS-1.2.19.jar is also not supporting for file sharing between two ipv6 system.We have our product running in one machine and i.e. Linux and we want to communicate to two Windows machines over ipv6 address for file transfer and Replication.Kindly Mail us back if you are interested in making these changes in j-interop jar and its dependent jars i.e JCIFS-1.2.19.jar and J-interopdeps. We will be waiting for your response.and we are ready to pay some amount for this changes also.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Madhur Chaini</dc:creator><pubDate>Mon, 22 Dec 2014 06:16:01 -0000</pubDate><guid>https://sourceforge.net64420f4b174025c9e0b2dba27109d501f420ae22</guid></item><item><title>j-Interop 3.0 Released !</title><link>https://sourceforge.net/p/j-interop/news/2013/06/j-interop-30-released-/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Dear all,&lt;br /&gt;
         This release (v3.0.0) includes:-&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;We have moved from LGPL v3 to EPL v1.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Removed GNU Crypto and moved to BouncyCastle. &lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Removed Wombat classes and moved to Java implementation of the same.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Upgraded to DCOM 5.7 protocol. j-Interop will now "negotiate" (as per DCOM &lt;br /&gt;
   specs) and use the latest protocol if supported by the Server.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Bunch of minor fixes.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;That's it,&lt;br /&gt;
best regards,&lt;br /&gt;
j-Interop Team.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Fri, 28 Jun 2013 01:36:57 -0000</pubDate><guid>https://sourceforge.netdf739a2ef44e0a91734c01d62c5a68f05d0c5857</guid></item><item><title>j-Interop 2.07 Released</title><link>https://sourceforge.net/p/j-interop/news/2009/12/j-interop-207-released-223/</link><description>Dear All,
Introducing NTLMv2 security support in this release. Also includes some minor bug fixes.

thanks,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Sun, 13 Dec 2009 12:07:35 -0000</pubDate><guid>https://sourceforge.net61ceea1f72d09fae5a37518439c54c83ad42f524</guid></item><item><title>j-Interop 2.07 Released</title><link>https://sourceforge.net/p/j-interop/news/2009/12/j-interop-207-released/</link><description>Dear All,
Introducing NTLMv2 security support in this release. Also includes some minor bug fixes.

thanks,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Sun, 13 Dec 2009 12:05:53 -0000</pubDate><guid>https://sourceforge.net8d9e06c707d7fcfdfa98ece03c157560c71192f7</guid></item><item><title>j-Interop 2.06 Released ! </title><link>https://sourceforge.net/p/j-interop/news/2009/05/j-interop-206-released--/</link><description>Dear All,
This is a bug fix release. Primary issue addressed here is related to releasing of COM references more than once during GC by the library. This causes &amp;quot;RPC server has disconnected&amp;quot; exception. There are also one or two minor fixes , but not worth mentioning.

until next time,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Fri, 01 May 2009 08:55:17 -0000</pubDate><guid>https://sourceforge.net197a317a10178edf3736630f3250b1a02ade369c</guid></item><item><title>j-Interop 2.05 (Final) Released ! </title><link>https://sourceforge.net/p/j-interop/news/2009/02/j-interop-205-final-released--/</link><description>Dear All,
Long awaited final build. We have gone over the published MS DCOM specifications and reconciled any differences we could find. Of course j-Interop does not fully implement the Bi-Directional feature so those parts of the protocol have been left out \(until someone pays us to do so\).

take care,
best regards,
Vikram  </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Wed, 11 Feb 2009 13:23:59 -0000</pubDate><guid>https://sourceforge.neta41791a24a6f522bff667ae83ec4dbd3c6d232f0</guid></item><item><title>j-Interop 2.04 (RC. 8) Released ! </title><link>https://sourceforge.net/p/j-interop/news/2009/01/j-interop-204-rc-8-released--/</link><description>Dear All,
\(still retaining RC 8 status\). This drop fixes issues related to reference counting done by the library for each COM object. It is highly recommended to move to this release as soon as time permits.

thanks,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Tue, 27 Jan 2009 13:16:04 -0000</pubDate><guid>https://sourceforge.net13d2b1779306a3fed32463334f77375bfae20841</guid></item><item><title>j-Interop 2.03 (RC 8) Released !</title><link>https://sourceforge.net/p/j-interop/news/2008/12/j-interop-203-rc-8-released-/</link><description>Dear All,
This is a bug fix release. 

1\. Main issue addressed in this is a Deadlock faced in JISession under heavy threading.

2\. Also if destroySession was invoked, any existing call to COM server would block till that call was complete. This has been corrected now. Any call in progress would be terminated and destroySession allowed to continue.

that's it,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Wed, 17 Dec 2008 13:24:33 -0000</pubDate><guid>https://sourceforge.netc4cad54dcdfa485dafe7c7a824495afab169c5be</guid></item><item><title>j-Interop 2.02 (RC. 7) Released !  </title><link>https://sourceforge.net/p/j-interop/news/2008/11/j-interop-202-rc-7-released---/</link><description>Dear All,
This is also a bug fix release. Major issues addressed in this are:- 

1.A deadlock condition which came up when stale COM objects where being cleaned out by the j-Interop GC thread has been resolved. 

2\. Introduced JIVariant.OUT\_IUNKNOWN\(\) and JIVariant.OUT\_IDISPATCH\(\) as helpers for COM methods asking for \[in,out\] IUnknown \*.
and \[in,out\] IDispatch \* references.

3\. Also introduced a new subclass of JIException, the JIAutomationException taking care of automation related exceptions and enclosing the
COM EXCEPINFO structure. 

That's it \! Until next time,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Sun, 09 Nov 2008 13:51:56 -0000</pubDate><guid>https://sourceforge.netf2b378d6aa73df197a04d4811ecb02f45ce8a500</guid></item><item><title>j-Interop 2.01 (RC. 6) Released ! </title><link>https://sourceforge.net/p/j-interop/news/2008/07/j-interop-201-rc-6-released--/</link><description>Dear All,
This is a bug fix release \(aren't they all :\)...\). Major issues addressed in this are:-

a\) A deadlock condition which came up when COM references were being added to the session and being deferenced by the cleanup thread simultaneously.
b\) Callback are now multithreaded \(system used to hang sometimes during heavy event call backs\).
c\) JIVariant has a fix to take care of unsually high arrays.
d\) There was a protocol error reported on Windows 2K3 servers during heavy multithreading, this has been resolved.
e\) Reference mechanism has been enhanced , now an addRef implicitly takes place when ever the library acquires a COM interface reference.
f\) A new method has been introduced in JISystem to allow users to set the hostname to IP mappings in those cases where such a mapping cannot be resolved via Java subsystem. 
g\) Importantly, our licensing is now changed to LGPL 3.0. If they are some users requiring LGPL 2.1 exception, please contact us. 

That's it, until next time,
best regards,
Vikram</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vikram Roopchand</dc:creator><pubDate>Thu, 24 Jul 2008 06:08:27 -0000</pubDate><guid>https://sourceforge.netf81e9ccc8fccfe68446415e726d6da336ffdd2ae</guid></item></channel></rss>