BTW, I agree with other posters that it seems like an awfully weird thing to do. Perhaps you just want to run a client in an OSGI environment?
Jim C. On 07/22/2014 02:39 PM, jcllings wrote: > I can give you some tips. > > Figure out what Cassandra does when it starts up. Best way to do that > is to read the startup script. Then all you have to do is convince > the OSGI container to do what ever prep is done by the script. Trick > to that is usually figuring out where to do it. For example if there > are environment variables set in the script for Cassandra, you should > add them to the script for your OSGI container. If there are any -D > options, you would have to use what ever mechanism your OSGI container > uses to pass them. There might be a properties file for example or > there might be actual -D settings, depending. You should probably > make your best guess as to where to put the configuration files but > watch the logs for errors to this effect, e.g. "ERROR: Doh! Can't find > the config dir / file / etc." Of course, if the Cassandra libs aren't > OSGI-ified you would have to do that also. > > Jim C. > > On 07/22/2014 01:19 PM, Robert Stupp wrote: >> What's your intention to do this? >>
signature.asc
Description: OpenPGP digital signature
