The first one of course. I'm not on crack ;-). I actually figured it out from the docs on the website. They are quite good so kudo's to whomever wrote them.
-----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: Tue 11/18/2003 5:00 PM To: Avalon framework users Cc: Subject: Re: Repository Question On Wednesday 19 November 2003 06:50, Steve Harris wrote: > Ok, as a first step to merlin goodness I am moving a rather monolithic > piece of code in to the container. This big hunk of burnin code requires > a c lib and some -D inputs when started normally. What is the > certified proper way to do this kind of stuff in merlin? I have > the jar in the repository so I think that part is ok. I hope you are saying; I have an existing application that I am making into a component to be run as one or more services in the container. How do I define the -D input, especially the java.library.path that contains my native code. and not I am putting the native code into Merlin. If the first, The java.library.path property is not magic. Define a Configuration entry for you native libraries or a path entry for your native library, and System.setProperty( "java.library.path", libPath ) prior to loading the natives. For all the other system properties, you should take them out where possible, and have them supplied in constructors (your own creations). If that is not feasible, just do the same as the java.library.path, at least for the moment, and put this on the "Code Debt Account" to fix later. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
