Hi,
We have a html and java plugin which uses some third party jar libraries. We converted these jars to OSGi bundle. When virgo server is launched from eclipse (localhost:9443), the plugin works fine. The problem is when plugin is installed on a vcenter and launched from webclient connected to vcenter(vCenterDNS:9443), a NoClassDefFoundError thirdParty/pkg/C (wrong name: thirdParty/pkg/c) error is thrown as seen in virgo server logs (for a class in third party jar). All import-package, export-package statements look fine.
I am wondering why this works in development environment but not in vcenter?
One difference I notice is, in development environment, I place the jars in vsphere-client-sdk\server\repository\usr\ directory and also project buildpath points to it. In vcenter I see the jars at C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\myPlugin-1.0.0.0\ and I find the extracted jar at C:\Program Files\VMware\vCenter Server\WebClient\server\work\deployer\s\global\125. Development environment doesn't have any extracted copy of the jar in global directory.
