 1 | " /> <url-history size="50" user="true" password |
1 | @Unique String url = ""; @Temporal(javax.persistence.TemporalType.TIMESTAMP) private Date |
1 | Class hierarchy to compare with. To do so, I create a new URLClassLoader with a URL pointing |
1 | ="100" />
|
1 | it also has to be specified by clients in the url connection string when connecting to the database (as explained in |
1 | -server connection url. Thank you support for your answer. What are the pros and cons between an embedded |
1 | Thanks to the new logging capability, I have managed to solve all the deadlock problems, as they were a result of Objectdb encountering new classes in multi-threaded code. I have a suggestion that might be useful for other users - how about an Ant task that, given a database URL, performs |
1 | -timeout="0" />
<url-history size="50" user="true" password="true" />
|
1 | .jdbc.url" value="/tmp/objectdb/testdb.odb"/>
|
1 | {
User user;
public void setUser(User user) {..}
setURL(String url |