Re: [vfs] JDBC FileSystem: planning an implementation
looks neat, but I presume this is the one file one blob version? or am I wrong (the parts can be clustered with the link field, but that would require a lot of duplicate inode data?) (FS attributes can be meta data for the root-file) I'll look into hybernate3 Wouter On Mon, 28 Mar 2005 07:13:45 +0200, Mario Ivankovits [EMAIL PROTECTED] wrote: Hello Wouter! I think we should split files and contents at least for performance reason. A database might cache a table without blob better and it is possible to put the content into another tablespace (oracle). What about using inodes? CREATE TABLE Files ( parent_inode numeric(22) not null, inode numeric(22) not null, name VARCHAR(200) NOT NULL, type numeric(1) not null, link_inode numeric(22) not null, lastModified TIMESTAMP NOT NULL, created TIMESTAMP NOT NULL, lastAccessed TIMESTAMP NOT NULL, ); PRIMARY KEY parent_inode, inode, ALTERNATE unique key parent_inode, name type: 0=file, 1=directory, 2=link The root inode is 0 per definition. CREATE TABLE Contents ( inode numeric(22) not null, content LONGBLOB NULL, ); PRIMARY KEY inode CREATE TABLE MetaAttributes ( inode numeric(22) not null, id numeric(22) not null, key varchar(200), value blob ); PRIMARY KEY inode, id I am not sure if the value should really be blob but what if one would store a serialized java object as attribute (filehandler ;-) To answer Rami's mail, I think the url should be something like: dbfs://user:[EMAIL PROTECTED]:dbname/ So one filesystem per database instance. I think the schema could be taken from the user and if this is not sufficient we could add a filesystemconfig where one could explicitely set the schema. And yes. All the database stuff should be abstracted and put into its own (replaceable) class. Thus we could try to provide specialised versions for different databases - or provide one using hibernate3 and get rid of the blob/clob handling too. This is something I could try to do. Ciao, Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r159228 [6/6] - in jakarta/commons/proper/logging/branches/DON_QUIXOTE: ./ classic/ classic/src/ classic/src/conf/ classic/src/java/ classic/src/java/org/ classic/src/java/org/apache/ classic/src/java/org/apache/commons/ classic/src/java/org/apache/commons/logging/ classic/src/java/org/apache/commons/logging/impl/ classic/src/media/ classic/src/test/ classic/src/test/org/ classic/src/test/org/apache/ classic/src/test/org/apache/commons/ classic/src/test/org/apache/commons/logging/ classic/src/test/org/apache/commons/logging/avalon/ classic/src/test/org/apache/commons/logging/jdk14/ classic/src/test/org/apache/commons/logging/log4j/ classic/src/test/org/apache/commons/logging/simple/ classic/xdocs/ classic/xdocs/images/ kernel/ kernel/src/ kernel/src/conf/ kernel/src/java/ kernel/src/java/org/ kernel/src/java/org/apache/ kernel/src/java/org/apache/commons/ kernel/src/java/org/apache/commons/logging/ kernel/src/java/org/apache/commons/logging/impl/ kernel/src/media/ kernel/src/test/ kernel/src/test/org/ kernel/src/test/org/apache/ kernel/src/test/org/apache/commons/ kernel/src/test/org/apache/commons/logging/
Added: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/org/apache/commons/logging/package.html URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/org/apache/commons/logging/package.html?view=autorev=159228 == --- jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/org/apache/commons/logging/package.html (added) +++ jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/org/apache/commons/logging/package.html Mon Mar 28 02:36:50 2005 @@ -0,0 +1,22 @@ +!-- + + Copyright 2001-2004 The Apache Software Foundation. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + +-- + +body +pJCL2 Kernel API./p + +/body Added: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/overview.html URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/overview.html?view=autorev=159228 == --- jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/overview.html (added) +++ jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/java/overview.html Mon Mar 28 02:36:50 2005 @@ -0,0 +1,46 @@ +html +!-- + + Copyright 2001-2004 The Apache Software Foundation. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + +-- +headtitleJCL Kernel/title/head +body +h2JCL Kernal/h2 +p +Contains JCL2 API kernel. +Code that uses the API should access only these classes. +/p +p +This differs from the JCL1 API in several important ways. +/p +ul + liThe size is much reduced./li + liCode using this distribution will run with just this code./li + liThe base implementation is simplified. + It should be possible to create JCL implementations + that run on early JVMs and in reduced library environments./li + liNo bridging implementations are included./li + liMinimal discovery code is included and none is exposed by the API. + This allows flexibility in the chose of discovery strategy. + /li +/ul +p +codeLogFactory/code now extends codeLogManager/code +and has been retrofitted with compatibility code. +This allows backwards compatibility for components compiled +against JCL1. +/p +/body \ No newline at end of file Added: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.png URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.png?view=autorev=159228 == Binary file - no diff available. Propchange: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.png -- svn:mime-type = application/octet-stream Added: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.xcf URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.xcf?view=autorev=159228 == Binary file - no diff available. Propchange: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/media/logo.xcf -- svn:mime-type = application/octet-stream Added: jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/test/org/apache/commons/logging/TestJCL.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/test/org/apache/commons/logging/TestJCL.java?view=autorev=159228 == --- jakarta/commons/proper/logging/branches/DON_QUIXOTE/kernel/src/test/org/apache/commons/logging/TestJCL.java (added) +++
Re: [vfs] JDBC FileSystem: planning an implementation
Wouter De Borger wrote: but I presume this is the one file one blob version? Yes. One file one Blob. Now I have seen your Content has a number - what was the indention of it? Every entry (file/directory/link) do have only one inode which is unique for the whole filesystem. E.g. this makes it easy to rename/move a whole tree. or am I wrong (the parts can be clustered with the link field, but that would require a lot of duplicate inode data?) The link field was meant to allow inserting the same inode at another place in the structure e.g. /root/dir1/file1.txt /root/dir2/file2.txt /root/dir2/file3.txt - /root/dir1/file1.txt which means file3.txt is the same as file1.txt e.g. its link_inode points to the same inode as file1.txt. This is called hard link and only possible within the same filesystem - in other word its topmost parent_inode has to be the same as the link destination. But hey. For sure we wont need this for version 1.0 - Maybe I carried too far ;-) --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r159230 - jakarta/commons/sandbox/vfs/trunk/project.xml
Author: imario Date: Mon Mar 28 03:32:46 2005 New Revision: 159230 URL: http://svn.apache.org/viewcvs?view=revrev=159230 Log: no longer extending commons-build changed siteAddress Modified: jakarta/commons/sandbox/vfs/trunk/project.xml Modified: jakarta/commons/sandbox/vfs/trunk/project.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/vfs/trunk/project.xml?view=diffr1=159229r2=159230 == --- jakarta/commons/sandbox/vfs/trunk/project.xml (original) +++ jakarta/commons/sandbox/vfs/trunk/project.xml Mon Mar 28 03:32:46 2005 @@ -1,10 +1,11 @@ ?xml version=1.0 encoding=UTF-8? project -extend../commons-build/sandbox-project.xml/extend +pomVersion3/pomVersion nameCommons VFS/name idcommons-vfs/id logo/images/vfs-logo-white.png/logo +urlhttp://jakarta.apache.org/commons/sandbox/vfs//url currentVersion1.0-dev/currentVersion inceptionYear2002/inceptionYear packageorg.apache.commons.vfs/package @@ -14,6 +15,42 @@ VFS is a Virtual File System library. /description +organization +nameThe Apache Software Foundation/name +urlhttp://jakarta.apache.org/url +logohttp://jakarta.apache.org/images/original-jakarta-logo.gif/logo +/organization + +licenses +license +nameThe Apache Software License, Version 2.0/name +url/LICENSE.txt/url +distributionrepo/distribution +/license +/licenses +issueTrackingUrlhttp://issues.apache.org/bugzilla//issueTrackingUrl +siteAddresscvs.apache.org/siteAddress +siteDirectory/www/jakarta.apache.org/commons/sandbox/vfs//siteDirectory + distributionDirectory/www/jakarta.apache.org/builds/jakarta-commons-sandbox/vfs//distributionDirectory +repository + connectionscm:svn:http://svn.apache.org/repos/asf/jakarta/commons/sandbox/vfs/trunk/connection +urlhttp://svn.apache.org/viewcvs.cgi/url +/repository +mailingLists +mailingList +nameCommons Dev List/name +subscribe[EMAIL PROTECTED]/subscribe +unsubscribe[EMAIL PROTECTED]/unsubscribe + archivehttp://mail-archives.eu.apache.org/mod_mbox/jakarta-commons-dev//archive +/mailingList +mailingList +nameCommons User List/name +subscribe[EMAIL PROTECTED]/subscribe +unsubscribe[EMAIL PROTECTED]/unsubscribe + archivehttp://mail-archives.eu.apache.org/mod_mbox/jakarta-commons-user//archive +/mailingList +/mailingLists + developers developer nameAdam Murdoch/name @@ -141,4 +178,22 @@ /resource /resources /build + +reports +reportmaven-changelog-plugin/report +reportmaven-changes-plugin/report +reportmaven-checkstyle-plugin/report +reportmaven-clover-plugin/report +reportmaven-developer-activity-plugin/report +reportmaven-file-activity-plugin/report +reportmaven-javadoc-plugin/report +reportmaven-jellydoc-plugin/report +reportmaven-junit-report-plugin/report +reportmaven-jxr-plugin/report +reportmaven-license-plugin/report +!-- reportmaven-linkcheck-plugin/report -- +!-- reportmaven-statcvs-plugin/report -- +reportmaven-tasklist-plugin/report +/reports + /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34206] New: - DateLocaleConverter should deal with empty strings (null)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34206. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34206 Summary: DateLocaleConverter should deal with empty strings (null) Product: Commons Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Bean Utilities AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] DateLocaleConverter method parse(Object value, String pattern) should just return null if value.equals() instead of trying to parse it and crash. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34206] - [beanutils] DateLocaleConverter should deal with empty strings (null)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34206. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34206 [EMAIL PROTECTED] changed: What|Removed |Added Summary|DateLocaleConverter should |[beanutils] |deal with empty strings |DateLocaleConverter should |(null) |deal with empty strings ||(null) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34204] - [configuration] XMLConfiguration ignore a specific encoding in XML declaration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34204. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34204 [EMAIL PROTECTED] changed: What|Removed |Added OS/Version|Linux |All Platform|PC |All -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
No, it's good, so, i've made up my mind for a 0.1 version, structure: -inodes (with links) -metadata ¿¿how long sould the blob feeld be?? (we could split them up, but that's kind of out of scope I think) -chunks (they have numbers to reconstruct them in the right order) -chunksize as an attribute (metadata for inode 0), -max filesize as an attribute implentation -plain jdbc (I'll add hybernate or whatever later on, I'd like to hold off all the external configuration until we have something to work on) so, when I have some time, I'll get it done Wouter On Mon, 28 Mar 2005 12:25:24 +0200, Mario Ivankovits [EMAIL PROTECTED] wrote: Wouter De Borger wrote: but I presume this is the one file one blob version? Yes. One file one Blob. Now I have seen your Content has a number - what was the indention of it? Every entry (file/directory/link) do have only one inode which is unique for the whole filesystem. E.g. this makes it easy to rename/move a whole tree. or am I wrong (the parts can be clustered with the link field, but that would require a lot of duplicate inode data?) The link field was meant to allow inserting the same inode at another place in the structure e.g. /root/dir1/file1.txt /root/dir2/file2.txt /root/dir2/file3.txt - /root/dir1/file1.txt which means file3.txt is the same as file1.txt e.g. its link_inode points to the same inode as file1.txt. This is called hard link and only possible within the same filesystem - in other word its topmost parent_inode has to be the same as the link destination. But hey. For sure we wont need this for version 1.0 - Maybe I carried too far ;-) --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE]Configuration release 1.1
Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
the URL still is a problem: it needs to specify the database type (JDBC subprotocol) dbfs://user:[EMAIL PROTECTED]:host:dbname/ OR dbfs:subprotocol://user:[EMAIL PROTECTED]:dbname/ if we plan on making use of intermediats like hibernate, we may or may not put that in the url too or leave that to internal configuration dbfs:hyb3:DBCP:mysql://user:[EMAIL PROTECTED]:dbname/ dbfs:JDBC:mysql://user:[EMAIL PROTECTED]:dbname/ sugestions? Wouter On Mon, 28 Mar 2005 15:03:39 +0200, Wouter De Borger [EMAIL PROTECTED] wrote: No, it's good, so, i've made up my mind for a 0.1 version, structure: -inodes (with links) -metadata ¿¿how long sould the blob feeld be?? (we could split them up, but that's kind of out of scope I think) -chunks (they have numbers to reconstruct them in the right order) -chunksize as an attribute (metadata for inode 0), -max filesize as an attribute implentation -plain jdbc (I'll add hybernate or whatever later on, I'd like to hold off all the external configuration until we have something to work on) so, when I have some time, I'll get it done Wouter On Mon, 28 Mar 2005 12:25:24 +0200, Mario Ivankovits [EMAIL PROTECTED] wrote: Wouter De Borger wrote: but I presume this is the one file one blob version? Yes. One file one Blob. Now I have seen your Content has a number - what was the indention of it? Every entry (file/directory/link) do have only one inode which is unique for the whole filesystem. E.g. this makes it easy to rename/move a whole tree. or am I wrong (the parts can be clustered with the link field, but that would require a lot of duplicate inode data?) The link field was meant to allow inserting the same inode at another place in the structure e.g. /root/dir1/file1.txt /root/dir2/file2.txt /root/dir2/file3.txt - /root/dir1/file1.txt which means file3.txt is the same as file1.txt e.g. its link_inode points to the same inode as file1.txt. This is called hard link and only possible within the same filesystem - in other word its topmost parent_inode has to be the same as the link destination. But hey. For sure we wont need this for version 1.0 - Maybe I carried too far ;-) --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
+1 ! Thank you for managing the release Oliver. Emmanuel Bourg Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - 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: [vfs] JDBC FileSystem: planning an implementation
the URL still is a problem: it needs to specify the database type (JDBC subprotocol) dbfs://user:[EMAIL PROTECTED]:host:dbname/ OR dbfs:subprotocol://user:[EMAIL PROTECTED]:dbname/ if we plan on making use of intermediats like hibernate, we may or may not put that in the url too or leave that to internal configuration dbfs:hyb3:DBCP:mysql://user:[EMAIL PROTECTED]:dbname/ dbfs:JDBC:mysql://user:[EMAIL PROTECTED]:dbname/ sugestions? I think for now letz go with dbfs://user:[EMAIL PROTECTED]:dbname/ Any additional configuration needet should be passed via a FilesystemOption. See the *FilesystemConfigBuilder stuff e.g. SftpFileSystemConfigBuilder. later we might simplify things by allowing a jndi datasource dbfs://user:[EMAIL PROTECTED]:dbname/ How we deal with hibernate or some other additional implementation lets consider if the time has come. --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
we need at least one extra field, jdbc can't connect without a subprotocol, so ill put it in front of the host portion Wouter On Mon, 28 Mar 2005 16:24:22 +0200, Mario Ivankovits [EMAIL PROTECTED] wrote: the URL still is a problem: it needs to specify the database type (JDBC subprotocol) dbfs://user:[EMAIL PROTECTED]:host:dbname/ OR dbfs:subprotocol://user:[EMAIL PROTECTED]:dbname/ if we plan on making use of intermediats like hibernate, we may or may not put that in the url too or leave that to internal configuration dbfs:hyb3:DBCP:mysql://user:[EMAIL PROTECTED]:dbname/ dbfs:JDBC:mysql://user:[EMAIL PROTECTED]:dbname/ sugestions? I think for now letz go with dbfs://user:[EMAIL PROTECTED]:dbname/ Any additional configuration needet should be passed via a FilesystemOption. See the *FilesystemConfigBuilder stuff e.g. SftpFileSystemConfigBuilder. later we might simplify things by allowing a jndi datasource dbfs://user:[EMAIL PROTECTED]:dbname/ How we deal with hibernate or some other additional implementation lets consider if the time has come. --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
Wouter De Borger wrote: we need at least one extra field, jdbc can't connect without a subprotocol, so ill put it in front of the host portion Ah, yes, you are right. So we end up with something like this: dbfs://user:[EMAIL PROTECTED]:host:dbname/ But this is not the end of the story. Unhappily the differences begin with the url * *jdbc:odbc:dsn_name;UID=your_uid;PWD=your_pwd* - JDBC-ODBC Bridge Driver URL. * *jdbc:oracle:thin:@machine_name:port_number:instance_name* - Orace Type 4 JDBC Driver. * *jdbc:mysql://host_name:port/dbname* - MySQL Connector/J JDBC Driver. What do you think if we start with something like a registry? It could be a simple global one. Then we could do this: DbfsRegistry.addDatasource(name, url, driver, username, password) And end with a simple url like dbfs://user:[EMAIL PROTECTED]/ And as I said, later we allow to not only have to use our registry but also jndi. (user:pass only allowed if there was no username/password given in addDatasource) --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
Ah, I hadn't noticed that one, so, a register, I'll also add addDatasource(Connection con) (and make it ouput just connections) On Mon, 28 Mar 2005 17:02:31 +0200, Mario Ivankovits [EMAIL PROTECTED] wrote: Wouter De Borger wrote: we need at least one extra field, jdbc can't connect without a subprotocol, so ill put it in front of the host portion Ah, yes, you are right. So we end up with something like this: dbfs://user:[EMAIL PROTECTED]:host:dbname/ But this is not the end of the story. Unhappily the differences begin with the url * *jdbc:odbc:dsn_name;UID=your_uid;PWD=your_pwd* - JDBC-ODBC Bridge Driver URL. * *jdbc:oracle:thin:@machine_name:port_number:instance_name* - Orace Type 4 JDBC Driver. * *jdbc:mysql://host_name:port/dbname* - MySQL Connector/J JDBC Driver. What do you think if we start with something like a registry? It could be a simple global one. Then we could do this: DbfsRegistry.addDatasource(name, url, driver, username, password) And end with a simple url like dbfs://user:[EMAIL PROTECTED]/ And as I said, later we allow to not only have to use our registry but also jndi. (user:pass only allowed if there was no username/password given in addDatasource) --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gmail rules - Wouter De Borger - if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. - www.nosoftwarepatents.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
Hi Mario Wouter, Could you still clarify what is the purpose of making a relational database work as filesystem. This is just for curiosity (and maybe good for docs). I had the idea that someone might want to attach more metadata to files through attributes. Another reason that came to my mind was to have transactions to prevent corruption when many users use the same file (but personally I think that this kind of integrity control is rather weak since the database is ignorant of the structure if the file's contents.) Anyway, in your first email Wouter mentioned that he needs it for ranking and reporting system for climbing contest. What is missing in a regular filesystem? Or why not just build your app on rel.db using JDBC? - rami - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34212] New: - No way to resolve proxied objects
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34212.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34212
Summary: No way to resolve proxied objects
Product: Commons
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Betwixt
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]
I have a small problem while using betwixt. We are using hibernate to
retrieve/store objects to the database. However, hibernate uses cglib to put
dynamic proxies around lazily loaded objects. Even when these objects are
fetched, the proxy still remains. There seems no way to dynamically resolve
proxied objects into the real implementation classes using BeanWriter. I've
seen the ClassNormalizer on the Configuration object, and I'd like the same
capability on the BeanWriter:
public interface BeanNormalizer {
Object normalizeBean(Object bean);
}
Then, i could create a class:
public class HibernateNormalizer {
public Object normalizerBean(Object bean) {
if (bean instanceof HibernateProxy) {
return ((HibernateProxy)bean).getHibernateLazyInitializer().
getImplementation();
}
else {
return bean;
}
}
}
I should be able to set this on any BeanWriter:
BeanWriter beanWriter = new BeanWriter(...);
beanWriter.setObjectNormalizer(new HibernateNormalizer());
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 34212] - [betwixt] No way to resolve proxied objects
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34212. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34212 [EMAIL PROTECTED] changed: What|Removed |Added Summary|No way to resolve proxied |[betwixt] No way to resolve |objects |proxied objects -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
On Mon, 28 Mar 2005 17:15:56 +0200, Emmanuel Bourg [EMAIL PROTECTED] wrote: +1 ! Thank you for managing the release Oliver. Emmanuel Bourg Oliver Heger wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - 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] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE]Configuration release 1.1
Looks good +1. On Mon, 28 Mar 2005 16:12:14 +0200, Oliver Heger [EMAIL PROTECTED] wrote: Dear community, since the 1.0 release of [configuration] we made some progress and added a couple of new features. To make these available for a larger user base, I think it is time to cut out a new 1.1 release. A complete list of changes since the 1.0 releaes can be found here: http://www.apache.org/~oheger/commons-configuration-1.1rc3-docs/changes-report.html. In the process of preparing the release there have been some release candidates. The latest is 1.1rc3, which can be inspected at http://www.apache.org/~oheger/commons-configuration-1.1rc3 (the tag for 1.1RC3 is named CONFIGURATION_1_1RC3). Here is my +1! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
Rami Ojares wrote: Could you still clarify what is the purpose of making a relational database work as filesystem. I think it would be a nice addition. How valuable it is depends on the environment one has to work. E.g. if it is not possible to setup a ftp/ssh server but already have a working database connection (e.g. in webshop environments) it might be nice if VFS could use this database as filestore e.g. for pictures too. And then it is easier if we could use our well known interface to handle files instead of implementing all this JDBC stuff again. Or maybe in an distributed environment. Multiple clients working with the same filesystem - again without setup for a fileserver. Or what about fileupload forms? We could use the database as storage and dont have the risk someone uploads and executes a trojan. We could leave the reorganisation to the database administrator. It introduces no new dependency so why NOT do it and see if there are others finding other usages for it. --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs] JDBC FileSystem: planning an implementation
Rami Ojares wrote: Could you still clarify what is the purpose of making a relational database work as filesystem. I think it would be a nice addition. Agree. I'm interested in using it e.g. to store the thumbnails that are being used in one of my applications.. Also for some versioning systems it may prove usefull. - Filip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
