[commons-sql] Metadata reading with Oracle
Hi ! I've got the following problem using the SqlBuilder.alterDatabase method with Oracle. The problem is the JdbcModelReader is built in the alterDatabase method, so there is no way to set the catalog and schema properties. The effects are that with Oracle, all tables are retrieved including system tables, aso. It took me more that 10 minutes just to build the Database model from the Jdbc connection. It would be great to add a method void alterDatabase(Database desiredDb, Database currentDb, boolean doDrops, boolean modifyColumns) throws IOException, SQLException and redirect the call from void alterDatabase(Database desiredDb, Connection connection, boolean doDrops, boolean modifyColumns) throws IOException, SQLException to the new one Cheers, Guillaume Nodet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[commons-transaction] Transactional queue
Is there any planned transactional wrapper around lists, queues or EDU.oswego.cs.dl.util.concurrent.Channel ? Cheers, Guillaume - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[modeler] explanations
I'm trying to use commons-modeler. I'd like to have explanations on how to use it. * what it the best way to create a MBean: - create a class derived from BasicModelMBean, or - create a class wrapping my resource and use default BasicModelMBean * how can i remove the modelerType attribute that is published with my beans Regards, Guillaume Nodet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[sql] Metadata and columns sizes
I've got a problem when trying to use commons-sql to delete a schema created in hsqldb. For numeric columns, hsqldb does not return any information about the column size, so the JdbcModelReader (line 243 in the latest from cvs) affects null to the local variable columnSize and pass it to the Column model object (line 341) with the setSize method. Unfortunately, the Column#setSize method do not support null values and so an NPE is thrown. The problem is that i do not know wether hsqldb or commons-sql is in fault, and if it is commons-sql, should i modify the Column object so that it handles null values or the JdbcModelReader so that the default value for the columnSize variable is . Thanks in advance, Guillaume Nodet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Configuration] Problems with properties containing integers in the name
I've tried to use the configuration component but ran into the following problems. I wanted to export a configuration (stored in a .properties file) to an xml. The problem is that i had some properties like this: xxx.yyy.1=zzz1 xxx.yyy.2=zzz2 ... Two problems arose: * the xml syntax does not support tag beginning by a numeric character, so the 1, 2 tags are not valid * my list of properties contained more than 10 items and the subset method returned bad things. The subset method does not check for a '.' at the end of the prefix, so that xxx.yyy.10.zzz was returned when asking for a subset beginning with 'xxx.yyy.1'. Regards, Guillaume Nodet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Configuration] Problems with properties containing integers in the name
I got another problem also. I want to have a string representation of the configuration without using a temporary file (as the Configuration interface is not Serializable). I did not see any simple methods get this. The load and store functions do not accept InputSteam or OuputStream objects... Regards, Guillaume -Message d'origine- De : Guillaume Nodet [mailto:[EMAIL PROTECTED] Envoyé : mercredi 11 février 2004 14:28 À : [EMAIL PROTECTED] Objet : [Configuration] Problems with properties containing integers in the name I've tried to use the configuration component but ran into the following problems. I wanted to export a configuration (stored in a .properties file) to an xml. The problem is that i had some properties like this: xxx.yyy.1=zzz1 xxx.yyy.2=zzz2 ... Two problems arose: * the xml syntax does not support tag beginning by a numeric character, so the 1, 2 tags are not valid * my list of properties contained more than 10 items and the subset method returned bad things. The subset method does not check for a '.' at the end of the prefix, so that xxx.yyy.10.zzz was returned when asking for a subset beginning with 'xxx.yyy.1'. Regards, Guillaume Nodet - 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]
