<html>
<head>
<base href="http://www.jacorb.org/bugzilla/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - JacORB unusable with Java Webstart in Java 1.7.0u55"
href="http://www.jacorb.org/bugzilla/show_bug.cgi?id=984#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - JacORB unusable with Java Webstart in Java 1.7.0u55"
href="http://www.jacorb.org/bugzilla/show_bug.cgi?id=984">bug 984</a>
from <span class="vcard"><a class="email" href="mailto:christian.bindseil@capgemini.com" title="Christian Bindseil <christian.bindseil@capgemini.com>"> <span class="fn">Christian Bindseil</span></a>
</span></b>
<pre>(In reply to Christian Bindseil from <a href="show_bug.cgi?id=984#c7">comment #7</a>)
<span class="quote">> With JacORB 3.4 it seems to work, but we have other problems, e. g. that
> server and client can only communicate with each other while running on the
> same machine. Until now, we have no idea why this happens.</span >
After solving the issue in communication (see <a class="bz_bug_link
bz_status_NEW "
title="NEW - Missing config parameter OAIAddr leads to an only locally working IOR"
href="show_bug.cgi?id=985">Bug 985</a>) I can confirm that
JacORB 3.4 (and a snapshot of 3.5) works in our(!) Environment. Someone other
told me bay mail, that for him 3.4 doesn't fix the problem.
So far I have no idea why it is like it is, but we simply changed the JARs,
fixed some problems caused by changes in API and redeployed the application in
two seperate Webstart-environments: the classloader finds the JacORB classes
and does no longer stop in JRE implementations of ORB or ORBSingleton. I've
tested with Java 7u55 and 8u05, both in 32 Bit.
Beginning next week we will test our whole system to ensure that there are no
new problems.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>