<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Classloader issues</title>
<link rel="stylesheet" type="text/css" href="../../style.css">
</head>
<body>
<div class="CommonContent">
<div class="CommonContentArea">
<h1>Classloader issues</h1><p><font color="#990000">This topic applies to Java version only</font> <br></p><p>Db4o needs to know its own classes, of course, and it needs to know the class definitions of the objects it stores. (In Client/Server mode, both the server and the clients need access to the class definitions.) While this usually is a non-issue with self-contained standalone applications, it can become tricky to ensure this condition when working with plugin frameworks, where one might want to deploy db4o as a shared library for multiple plugins, for example.</p><p><div class="childTopicList">More Reading:<ul>
<li><p><a href="classloader_issues/classloader_basics.html" class="wikiLink">Classloader basics</a></p></li>
<li><p><a href="classloader_issues/configuration.html" class="wikiLink">Configuration</a></p></li>
<li><p><a href="classloader_issues/special_cases.html" class="wikiLink">Special Cases</a></p></li>
</ul></div>
<br></p></div>
</div>
<div id="footer">
This revision (8) was last Modified 2006-12-04T07:42:32 by Tetyana.
</div>
</body>
</html>
