Skip to main content

Source code revision


summary: Forward ported the fix from 3.1.2 to 4.0
revision: 52589
author: bnevins
date: 2012-02-14 21:23:55 UTC (4 years)
Forward ported the fix from 3.1.2 to 4.0
The problem was that if an App happened to use their own version of DCOM open-source libraries
it would conflict with the ones we re-package.
Solved this (with help from Richard Hall, Sahoo and Joe DiPol) by adding a password to the exported packages -- AND -- limiting the
number of exported packages.
validate-dcom is a great command for testing. If that one command works (it did) then we know for sure that all of the DCOM
plumbing is working perfectly.

Change Path Actions
A trunk/main/nucleus/cluster/common/osgi.bundle
A trunk/main/nucleus/packager/external/j-interop/osgi.bundle
M trunk/main/nucleus/packager/external/j-interop/pom.xml
Please Confirm