Do you plan on hooking up a standard way to load native libs? If so
then don't forget to take account for system type/arch and version which
needs to be in the namespace of the lib somewhere (either as path info
or part of the filename).
These should be put in a lib/ dir under the deployments local space. I
would suggest using the directory for namespace, so something like
lib/${os.name}/${os.arch}/${os.version}.
Will also need to allow for "links" to be made, since not all vms use
the same names for these. (SunOS vs. Solaris... i386-i686 vs x86 and so
on).
--jason
David Jencks wrote:
>Well, after a couple of bug fixes, Hiram's njar protocol works fine. I
>have the MainDeployer working using it instead of unpacking into tmp.
>
>Does anyone object to my committing this?
>
>Note that Hiram's protocol handler works by unpacking things into temp
>files (in the system temp dir). However, it's all hidden, and presumably
>will avoid the security /permissions concerns.
>
>I'll also implement Scott's suggestion of removing the random numbers and
>including the entire path of the original url. (This is not as unique as
>numbers, but it is unlikely anyone will deploy 2 packages with the same
>url.getFile() value.)
>
>I'm also going to have another try at installing native libraries. Any
>ideas about where they should be unpacked to?
>
>Thanks
>david jencks
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
