Nativelib jar fails to get unpacked

Question

I have packaged my app for java web start, and all of the jars get downloaded ok, and the application launches. From this we can conclude that all jars are present and properly signed.
The problem I am seeing is that the <nativelib> elements get downloaded, and a folder gets created for them in the JWS cache, however the folder is always empty, and the app experiences an unsatisfied link error. The actual jar file containing the native libraries is present in the cache, it just does not get unpacked.
If I go into the file system, and manually unpack the nativelib jar file, and place the DLLs into the empty folder already created for them, then the app runs properly.
So, what is it that actually causes the nativelib jar to be unpacked into a folder in the JWS cache? When I run the JDIC browser demo, for example, its native libraries that it uses are properly unpacked, however my files are not.
In my case, I am trying to unpack the SWT libraries, not that it matters what the actual DLLs are -- What could be causing the problem

Answer 1

The problem was that the DLLs in the nativelib jar file had an associated path -- I was unable to get NetBeans 3.6 to build the jar without some path, so I used the root path of "/". Turns out that this was a problem...
When I used jar.exe to create the jar, there were no paths in the file. Then I resigned it, and things worked as expected.