Re: repository.xml partially read
Waouh, was just an awful bad naming. I had forgotten than Windows is not case sensitive !!! Unix is... argh the xml "database" in my repository.xml was named repository_database_rushDB instead of repository_database_rushDb. So confuseD. So sorrY. Thanks again for your help. ++ On Fri, 18 Mar 2005 17:07:47 +0100, Thomas Dudziak <[EMAIL PROTECTED]> wrote: > No, you can have multiple jdbc-connection-descriptor elements, but > they need to differ in the jcd-alias. > > Tom > > - > 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]
Re: repository.xml partially read
No, you can have multiple jdbc-connection-descriptor elements, but they need to differ in the jcd-alias. Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repository.xml partially read
repository.dtd is in classpath, and i tried to declare it in repository.xml with SYSTEM "repository.dtd". No way. I think the failure occurs because i have 2 jdbc-descriptors, and dtd allows only one connector (according to doc in file). But what i cannot understand, is that it works fine with xerces and Tomcat.. It works too if a put only one jdbc-connector, but, that's not my aim, i need to acces the 2 databases !! Can you confirm xml file is made for only one jdbc-connector in dtd grammar? (I'm not a specialist of xml ) Thanks With the fact that my Parser is those who gave me Weblogic... On Fri, 18 Mar 2005 15:10:26 +0100, Martin Kalén <[EMAIL PROTECTED]> wrote: > Bruno CROS wrote: > > I setup a repository.xml as ojb-blank project > > description of my file is below. This file works very well on Tomcat > > over windows, but not at all on AIX ! > > This is the third subject on the same issue in a pretty short time, the > other two were resolved by changing DTD declaration and/or making sure > repository.dtd is in CLASSPATH. > > Did you try that? > > If you have a webaddress in the DTD, change your doctype declaration to > SYSTEM "repository.dtd" to prevent HTTP access as the point of failure > during parsing (not all parsers can do this and it's silly to get DTD > via HTTP in production anyway). > > Regards, > Martin > > - > 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]
Re: repository.xml partially read
Bruno CROS wrote: I setup a repository.xml as ojb-blank project description of my file is below. This file works very well on Tomcat over windows, but not at all on AIX ! This is the third subject on the same issue in a pretty short time, the other two were resolved by changing DTD declaration and/or making sure repository.dtd is in CLASSPATH. Did you try that? If you have a webaddress in the DTD, change your doctype declaration to SYSTEM "repository.dtd" to prevent HTTP access as the point of failure during parsing (not all parsers can do this and it's silly to get DTD via HTTP in production anyway). Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repository.xml partially read
Might be that the XML parser has problems with entities. You can try changing the XML parser, e.g. putting Xerces into the lib folder. Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
repository.xml partially read
Hello, I setup a repository.xml as ojb-blank project description of my file is below. This file works very well on Tomcat over windows, but not at all on AIX ! AIX log tells me that "No repository is loaded", the parsing seems to stop in a subfile !! (see below) so OJB starts with empty metadata and no default connection... Does someone experience such a trouble? Note that my project works fine on a PC Tomcat server with JDK 1.4.1... The trouble occurs only once the project is running on AIX (unix). with IBM JRE 1.4.1. first idea, sax depends of JDK ? Thanks for other ideas. Repository.xml ]> &databaseMathieu; &databaseRushDb; &internal; &user; &rushDb; Logs = 599 INFO [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryPersistor - OJB Descriptor Repository: file:/opt/bea/user_projects/domains/mydomain/applications/mathieu/WEB-INF/classes/repository.xml 599 INFO [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryPersistor - Building repository from :file:/opt/bea/user_projects/domains/mydomain/applications/mathieu/WEB-INF/c lasses/repository.xml 603 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryPersistor - RespostoryPersistor using SAXParser : weblogic.xml.jaxp.RegistrySAXParser 630 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - startDoc 635 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - > descriptor-repository 636 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - isolation-level: read-uncommitted 636 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - proxy-prefetching-limit: 51 636 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - version: 1.0 638 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - > attribute 638 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-name: timeout 638 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-value: 900 638 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - < attribute 638 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - > attribute 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-name: autoSync 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-value: true 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - < attribute 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - > attribute 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-name: cachingKeyType 639 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler -attribute-value: 0 640 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - < attribute 640 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - < object-cache 640 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - Ignoring unused Element connection-pool 640 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - Ignoring unused Element sequence-manager 640 DEBUG [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.RepositoryXmlHandler - Ignoring unused Element jdbc-connection-descriptor 643 INFO [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.MetadataManager - No repository.xml file found, starting with empty metadata and connection configuration 648 INFO [ExecuteThread: '14' for queue: 'weblogic.kernel.Default'] metadata.MetadataManager - No 'default-connection' attribute set in jdbc-connection-descriptors, thus it's currently not possible to use 'defaultPersistenceBroker()' convenience method to lookup PersistenceBroker instances. But it's possible to enable this at runtime using 'setDefaultKey' method. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
