-
August 22nd, 2016, 09:52 AM
#2
We have separated the Server classpath in these variables in order to allow the Server to setup multiple classloaders. But this is actually internal stuff and could have been hidden in Server code. It was made explicit, hence providing a degree of freedom, for handling special cases and for allowing the integrator to move the jars in different places (just in case there was a reason).
Normally, none of the jars listed by the four JVM properties are visible from the Adapters. The Adapters only see the main classpath, which is the "cpath" variable and is also visible from the kernel. However, this classpath contains very little and no external libraries.
Only by explicit configuration can you have "com.lightstreamer.logging_lib_path" visible from the Adapters. So I suppose that you have the <classloader> element set to "log-enabled" in adapters.xml, perhaps after cloning some of our demos. But this has strong restrictions; see the details of the <classloader> element here (open the file as a text file).
Similar Threads
-
By mnenchev in forum Client SDKs
Replies: 7
Last Post: December 13th, 2011, 04:08 PM
-
By arunj in forum Adapter SDKs
Replies: 4
Last Post: February 10th, 2011, 12:32 PM
-
By Alessandro in forum Client SDKs
Replies: 0
Last Post: October 15th, 2010, 08:07 PM
-
By Alessandro in forum Client SDKs
Replies: 0
Last Post: June 18th, 2010, 03:10 PM
-
By k.mcc2009 in forum Adapter SDKs
Replies: 1
Last Post: May 21st, 2009, 09:41 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 08:33 PM.
Bookmarks