/[cvs]/nfo/perl/libs/Data/Storage.pm
ViewVC logotype

Diff of /nfo/perl/libs/Data/Storage.pm

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.14 by joko, Thu Dec 19 16:27:59 2002 UTC revision 1.17 by joko, Thu Jan 30 21:42:22 2003 UTC
# Line 1  Line 1 
1  # $Id$  ## ------------------------------------------------------------------------
2  #  ##
3  # Copyright (c) 2002  Andreas Motl <andreas.motl@ilo.de>  ##    $Id$
4  #  ##
5  # See COPYRIGHT section in pod text below for usage and distribution rights.  ##    Copyright (c) 2002  Andreas Motl <andreas.motl@ilo.de>
6  #  ##
7  ############################################  ##    See COPYRIGHT section in pod text below for usage and distribution rights.
8  #  ##
9  #  $Log$  ## ------------------------------------------------------------------------
10  #  Revision 1.14  2002/12/19 16:27:59  joko  ##
11  #  - moved 'sub dropDb' to Data::Storage::Handler::DBI  ##  $Log$
12  #  ##  Revision 1.17  2003/01/30 21:42:22  joko
13  #  Revision 1.13  2002/12/17 21:54:12  joko  ##  + minor update: renamed method
14  #  + feature when using Tangram:  ##
15  #    + what? each object created should delivered with a globally(!?) unique identifier (GUID) besides the native tangram object id (OID)  ##  Revision 1.16  2003/01/20 16:52:13  joko
16  #        + patched Tangram::Storage (jonen)  ##  + now using 'DesignPattern::Object' to create a new 'Data::Storage::Handler::Xyz' on demand - before we did this in a hand-rolled fashion
17  #        + enhanced Data::Storage::Schema::Tangram (joko)  ##
18  #        + enhanced Data::Storage::Handler::Tangram 'sub getObjectByGuid' (jonen)  ##  Revision 1.15  2003/01/19 03:12:59  joko
19  #    + how?  ##  + modified header
20  #        + each concrete (non-abstract) class gets injected with an additional field/property called 'guid' - this is done (dynamically) on schema level  ##  - removed pod-documentation - now in 'Storage.pod'
21  #        + this property ('guid') gets filled on object creation/insertion from 'sub Tangram::Storage::_insert' using Data::UUID from CPAN  ##
22  #        + (as for now) this property can get accessed by calling 'getObjectByGuid' on the already known storage-handle used throughout the application  ##  Revision 1.14  2002/12/19 16:27:59  joko
23  #  ##  - moved 'sub dropDb' to Data::Storage::Handler::DBI
24  #  Revision 1.12  2002/12/12 02:50:15  joko  ##
25  #  + this now (unfortunately) needs DBI for some helper functions  ##  Revision 1.13  2002/12/17 21:54:12  joko
26  #  + TODO: these have to be refactored to another scope! (soon!)  ##  + feature when using Tangram:
27  #  ##    + what? each object created should delivered with a globally(!?) unique identifier (GUID) besides the native tangram object id (OID)
28  #  Revision 1.11  2002/12/11 06:53:19  joko  ##        + patched Tangram::Storage (jonen)
29  #  + updated pod  ##        + enhanced Data::Storage::Schema::Tangram (joko)
30  #  ##        + enhanced Data::Storage::Handler::Tangram 'sub getObjectByGuid' (jonen)
31  #  Revision 1.10  2002/12/07 03:37:23  joko  ##    + how?
32  #  + updated pod  ##        + each concrete (non-abstract) class gets injected with an additional field/property called 'guid' - this is done (dynamically) on schema level
33  #  ##        + this property ('guid') gets filled on object creation/insertion from 'sub Tangram::Storage::_insert' using Data::UUID from CPAN
34  #  Revision 1.9  2002/12/01 22:15:45  joko  ##        + (as for now) this property can get accessed by calling 'getObjectByGuid' on the already known storage-handle used throughout the application
35  #  - sub createDb: moved to handler  ##
36  #  ##  Revision 1.12  2002/12/12 02:50:15  joko
37  #  Revision 1.8  2002/11/29 04:48:23  joko  ##  + this now (unfortunately) needs DBI for some helper functions
38  #  + updated pod  ##  + TODO: these have to be refactored to another scope! (soon!)
39  #  ##
40  #  Revision 1.7  2002/11/17 06:07:18  joko  ##  Revision 1.11  2002/12/11 06:53:19  joko
41  #  + creating the handler is easier than proposed first - for now :-)  ##  + updated pod
42  #  + sub testAvailability  ##
43  #  ##  Revision 1.10  2002/12/07 03:37:23  joko
44  #  Revision 1.6  2002/11/09 01:04:58  joko  ##  + updated pod
45  #  + updated pod  ##
46  #  ##  Revision 1.9  2002/12/01 22:15:45  joko
47  #  Revision 1.5  2002/10/29 19:24:18  joko  ##  - sub createDb: moved to handler
48  #  - reduced logging  ##
49  #  + added some pod  ##  Revision 1.8  2002/11/29 04:48:23  joko
50  #  ##  + updated pod
51  #  Revision 1.4  2002/10/27 18:35:07  joko  ##
52  #  + added pod  ##  Revision 1.7  2002/11/17 06:07:18  joko
53  #  ##  + creating the handler is easier than proposed first - for now :-)
54  #  Revision 1.3  2002/10/25 11:40:37  joko  ##  + sub testAvailability
55  #  + enhanced robustness  ##
56  #  + more logging for debug-levels  ##  Revision 1.6  2002/11/09 01:04:58  joko
57  #  + sub dropDb  ##  + updated pod
58  #  ##
59  #  Revision 1.2  2002/10/17 00:04:29  joko  ##  Revision 1.5  2002/10/29 19:24:18  joko
60  #  + sub createDb  ##  - reduced logging
61  #  + sub isConnected  ##  + added some pod
62  #  + bugfixes regarding "deep recursion" stuff  ##
63  #  ##  Revision 1.4  2002/10/27 18:35:07  joko
64  #  Revision 1.1  2002/10/10 03:43:12  cvsjoko  ##  + added pod
65  #  + new  ##
66  #  ##  Revision 1.3  2002/10/25 11:40:37  joko
67  ############################################  ##  + enhanced robustness
68    ##  + more logging for debug-levels
69    ##  + sub dropDb
70    ##
71    ##  Revision 1.2  2002/10/17 00:04:29  joko
72    ##  + sub createDb
73    ##  + sub isConnected
74    ##  + bugfixes regarding "deep recursion" stuff
75    ##
76    ##  Revision 1.1  2002/10/10 03:43:12  cvsjoko
77    ##  + new
78    ## ------------------------------------------------------------------------
79    
80    
81  BEGIN {  BEGIN {
82    $Data::Storage::VERSION = 0.02;    $Data::Storage::VERSION = 0.03;
83  }  }
84    
   
 =head1 NAME  
   
   Data::Storage - Interface for accessing various Storage implementations for Perl in an independent way  
   
   
 =head1 AIMS  
   
   - should encapsulate Tangram, DBI, DBD::CSV and LWP:: to access them in an unordinary (more convenient) way ;)  
   - introduce a generic layered structure, refactor *SUBLAYER*-stuff, make (e.g.) this possible:  
     Perl Data::Storage[DBD::CSV]  ->  Perl LWP::  ->  Internet HTTP/FTP/*  ->  Host Daemon  ->  csv-file  
   - provide generic synchronization mechanisms across arbitrary/multiple storages based on ident/checksum  
     maybe it's possible to have schema-, structural- and semantical modifications synchronized???  
   
   
 =head1 SYNOPSIS  
   
 =head2 BASIC ACCESS  
   
 =head2 ADVANCED ACCESS  
   
   ... via inheritance:  
     
     use Data::Storage;  
     my $proxyObj = new HttpProxy;  
     $proxyObj->{url} = $url;  
     $proxyObj->{payload} = $content;  
     $self->{storage}->insert($proxyObj);  
       
     use Data::Storage;  
     my $proxyObj = HttpProxy->new(  
       url => $url,  
       payload => $content,  
     );  
     $self->{storage}->insert($proxyObj);  
   
   
 =head2 SYNCHRONIZATION  
   
   my $nodemapping = {  
     'LangText' => 'langtexts.csv',  
     'Currency' => 'currencies.csv',  
     'Country'  => 'countries.csv',  
   };  
   
   my $propmapping = {  
     'LangText' => [  
       [ 'source:lcountrykey'  =>  'target:country' ],  
       [ 'source:lkey'         =>  'target:key' ],  
       [ 'source:lvalue'       =>  'target:text' ],  
     ],  
     'Currency' => [  
       [ 'source:ckey'         =>  'target:key' ],  
       [ 'source:cname'        =>  'target:text' ],  
     ],  
     'Country' => [  
       [ 'source:ckey'         =>  'target:key' ],  
       [ 'source:cname'        =>  'target:text' ],  
     ],  
   };  
   
   sub syncResource {  
   
     my $self = shift;  
     my $node_source = shift;  
     my $mode = shift;  
     my $opts = shift;  
       
     $mode ||= '';  
     $opts->{erase} ||= 0;  
       
     $logger->info( __PACKAGE__ . "->syncResource( node_source $node_source mode $mode erase $opts->{erase} )");  
     
     # resolve metadata for syncing requested resource  
     my $node_target = $nodemapping->{$node_source};  
     my $mapping = $propmapping->{$node_source};  
       
     if (!$node_target || !$mapping) {  
       # loggger.... "no target, sorry!"  
       print "error while resolving resource metadata", "\n";  
       return;  
     }  
       
     if ($opts->{erase}) {  
       $self->_erase_all($node_source);  
     }  
     
     # create new sync object  
     my $sync = Data::Transfer::Sync->new(  
       storages => {  
         L => $self->{bizWorks}->{backend},  
         R => $self->{bizWorks}->{resources},  
       },  
       id_authorities        =>  [qw( L ) ],  
       checksum_authorities  =>  [qw( L ) ],  
       write_protected       =>  [qw( R ) ],  
       verbose               =>  1,  
     );  
       
     # sync  
     # todo: filter!?  
     $sync->syncNodes( {  
       direction       =>  $mode,                 # | +PUSH | +PULL | -FULL | +IMPORT | -EXPORT  
       method          =>  'checksum',            # | -timestamp | -manual  
       source          =>  "L:$node_source",  
       source_ident    =>  'storage_method:id',  
       source_exclude  =>  [qw( id cs )],  
       target          =>  "R:$node_target",  
       target_ident    =>  'property:oid',  
       mapping         =>  $mapping,  
     } );  
   
   }  
   
   
 =head2 NOTE  
   
   This module heavily relies on DBI and Tangram, but adds a lot of additional bugs and quirks.  
   Please look at their documentation and/or this code for additional information.  
   
   
 =head1 REQUIREMENTS  
   
   For full functionality:  
     DBI              from CPAN  
     DBD::mysql       from CPAN  
     Tangram 2.04     from CPAN         (hmmm, 2.04 won't do in some cases)  
     Tangram 2.05     from http://...   (2.05 seems okay but there are also additional patches from our side)  
     Class::Tangram   from CPAN  
     DBD::CSV         from CPAN  
     MySQL::Diff      from http://adamspiers.org/computing/mysqldiff/  
     ... and all their dependencies  
   
 =cut  
   
 # The POD text continues at the end of the file.  
   
   
85  package Data::Storage;  package Data::Storage;
86    
87  use strict;  use strict;
88  use warnings;  use warnings;
89    
 use Data::Storage::Locator;  
90  use Data::Dumper;  use Data::Dumper;
91    # FIXME: wipe out!
 # TODO: wipe out!  
92  use DBI;  use DBI;
93    
94    use Data::Storage::Locator;
95    use DesignPattern::Object;
96    
97    
98  # TODO: actually implement level (integrate with Log::Dispatch)  # TODO: actually implement level (integrate with Log::Dispatch)
99  my $TRACELEVEL = 0;  my $TRACELEVEL = 0;
100    
# Line 234  sub new { Line 109  sub new {
109    my $arg_locator = shift;    my $arg_locator = shift;
110    my $arg_options = shift;    my $arg_options = shift;
111    
112      if (!$arg_locator) {
113        $logger->critical( __PACKAGE__ . "->new: No locator passed in!" );
114        return;
115      }
116    
117    #my $self = { STORAGEHANDLE => undef, @_ };    #my $self = { STORAGEHANDLE => undef, @_ };
118    my $self = { STORAGEHANDLE => undef, locator => $arg_locator, options => $arg_options };    my $self = { STORAGEHANDLE => undef, locator => $arg_locator, options => $arg_options };
119    #$logger->debug( __PACKAGE__ . "[$self->{locator}->{type}]" . "->new(@_)" );    #$logger->debug( __PACKAGE__ . "[$self->{locator}->{type}]" . "->new(@_)" );
# Line 261  sub AUTOLOAD { Line 141  sub AUTOLOAD {
141    
142    # advanced logging of AUTOLOAD calls ...    # advanced logging of AUTOLOAD calls ...
143    # ... nice but do it only when TRACING (TODO) is enabled    # ... nice but do it only when TRACING (TODO) is enabled
     if ($TRACELEVEL) {  
144        my $logstring = "";        my $logstring = "";
145        $logstring .= __PACKAGE__ . "[$self->{locator}->{type}]" . "->" . $method;        $logstring .= __PACKAGE__ . "[$self->{locator}->{type}]" . "->" . $method;
146        #print "count: ", $#_, "\n";        #print "count: ", $#_, "\n";
# Line 271  sub AUTOLOAD { Line 150  sub AUTOLOAD {
150        # TODO: only ok if logstring doesn't contain        # TODO: only ok if logstring doesn't contain
151        #            e.g. "Data::Storage[Tangram]->insert(SystemEvent=HASH(0x5c0034c))          (AUTOLOAD)"        #            e.g. "Data::Storage[Tangram]->insert(SystemEvent=HASH(0x5c0034c))          (AUTOLOAD)"
152        # but that would be _way_ too specific as long as we don't have an abstract handler for this  ;)        # but that would be _way_ too specific as long as we don't have an abstract handler for this  ;)
153        if ($TRACELEVEL) {
154        $logger->debug( $logstring );        $logger->debug( $logstring );
155        #print join('; ', @_);        #print join('; ', @_);
156      }      }
157            
158    # filtering AUTOLOAD calls and first-time-touch of the actual storage impl    # filtering AUTOLOAD calls and first-time-touch of the actual storage impl
159    if ($self->_filter_AUTOLOAD($method)) {    if ($self->_filter_AUTOLOAD($method)) {
160      #print "_accessStorage\n";      #print "=== FILTER!", "\n";
161      $self->_accessStorage();      $self->_accessStorageHandle();
162      $self->{STORAGEHANDLE}->$method(@_);      if ($self->{STORAGEHANDLE}) {
163          return $self->{STORAGEHANDLE}->$method(@_);
164        } else {
165          $logger->critical( __PACKAGE__ . "->AUTOLOAD: ERROR: " . $logstring );
166          return;
167        }
168    }    }
169        
170  }  }
# Line 305  sub normalizeArgs { Line 190  sub normalizeArgs {
190    return @result;    return @result;
191  }  }
192    
193  sub _accessStorage {  sub _accessStorageHandle {
194    my $self = shift;    my $self = shift;
195    # TODO: to some tracelevel!    # TODO: to some tracelevel!
196      #print "=========== _accessStorage", "\n";
197    if ($TRACELEVEL) {    if ($TRACELEVEL) {
198      $logger->debug( __PACKAGE__ .  "[$self->{locator}->{type}]" . "->_accessStorage()" );      $logger->debug( __PACKAGE__ .  "[$self->{locator}->{type}]" . "->_accessStorageHandle()" );
199    }    }
200    if (!$self->{STORAGEHANDLE}) {    if (!$self->{STORAGEHANDLE}) {
201      $self->_createStorageHandle();      return $self->_createStorageHandle();
202      }
203    }
204    
205    sub _createStorageHandle1 {
206      my $self = shift;
207      my $type = $self->{locator}->{type};
208      $logger->debug( __PACKAGE__ .  "[$type]" . "->_createStorageHandle()" );
209    
210      my $pkg = "Data::Storage::Handler::" . $type . "";
211      
212      # try to load perl module at runtime
213      my $evalstr = "use $pkg;";
214      eval($evalstr);
215      if ($@) {
216        $logger->error( __PACKAGE__ .  "[$type]" . "->_createStorageHandle(): $@" );
217        return;
218    }    }
219      
220      # build up some additional arguments to pass on
221      #my @args = %{$self->{locator}};
222      my @args = ();
223    
224      # - create new storage handle object
225      # - propagate arguments to handler
226      # - pass locator by reference to be able to store status- or meta-information in it
227      $self->{STORAGEHANDLE} = $pkg->new( locator => $self->{locator}, @args );
228    
229  }  }
230    
231  sub _createStorageHandle {  sub _createStorageHandle {
# Line 321  sub _createStorageHandle { Line 233  sub _createStorageHandle {
233    my $type = $self->{locator}->{type};    my $type = $self->{locator}->{type};
234    $logger->debug( __PACKAGE__ .  "[$type]" . "->_createStorageHandle()" );    $logger->debug( __PACKAGE__ .  "[$type]" . "->_createStorageHandle()" );
235    
236    #print Dumper($self);
237    #exit;
238    
239    my $pkg = "Data::Storage::Handler::" . $type . "";    my $pkg = "Data::Storage::Handler::" . $type . "";
240        
241    # try to load perl module at runtime    # try to load perl module at runtime
242    =pod
243    my $evalstr = "use $pkg;";    my $evalstr = "use $pkg;";
244    eval($evalstr);    eval($evalstr);
245    if ($@) {    if ($@) {
# Line 339  sub _createStorageHandle { Line 255  sub _createStorageHandle {
255    # - propagate arguments to handler    # - propagate arguments to handler
256    # - pass locator by reference to be able to store status- or meta-information in it    # - pass locator by reference to be able to store status- or meta-information in it
257    $self->{STORAGEHANDLE} = $pkg->new( locator => $self->{locator}, @args );    $self->{STORAGEHANDLE} = $pkg->new( locator => $self->{locator}, @args );
258    =cut
259    
260      $self->{STORAGEHANDLE} = DesignPattern::Object->fromPackage( $pkg, locator => $self->{locator} );
261      return 1;
262    
263  }  }
264    
# Line 377  sub removeLogDispatchHandler { Line 297  sub removeLogDispatchHandler {
297    $logger->remove($name);    $logger->remove($name);
298  }  }
299    
300    =pod
301  sub getDbName {  sub getDbName {
302    my $self = shift;    my $self = shift;
303    my $dsn = $self->{locator}->{dbi}->{dsn};    my $dsn = $self->{locator}->{dbi}->{dsn};
# Line 414  sub testDsn { Line 335  sub testDsn {
335      $logger->warning( __PACKAGE__ .  "[$self->{locator}->{type}]" . "->testDsn(): " . "DBI-error: " . $DBI::errstr );      $logger->warning( __PACKAGE__ .  "[$self->{locator}->{type}]" . "->testDsn(): " . "DBI-error: " . $DBI::errstr );
336    }    }
337  }  }
338    =cut
339    
340  1;  1;
341  __END__  __END__
   
   
 =head1 DESCRIPTION  
   
 =head2 Data::Storage  
   
   Data::Storage is a module for accessing various "data structures / kinds of structured data" stored inside  
   various "data containers".  
   We tried to use the AdapterPattern (http://c2.com/cgi/wiki?AdapterPattern) to implement a wrapper-layer  
   around core CPAN modules (Tangram, DBI).  
   
 =head2 Why?  
   
   You will get a better code-structure (not bad for later maintenance) in growing Perl code projects,  
   especially when using multiple database connections at the same time.  
   You will be able to switch between different _kinds_ of implementations used for storing data.  
   Your code will use the very same API to access these storage layers.  
       ... implementation has to be changed for now  
   Maybe you will be able to switch "on-the-fly" without changing any bits in code in the future....  
       ... but that's not the focus  
   
 =head2 What else?  
   
   Having this, we were able to do implement a generic data synchronization module more easy,  
   please look at Data::Transfer.  
   
   
 =head1 AUTHORS / COPYRIGHT  
   
   The Data::Storage module is Copyright (c) 2002 Andreas Motl.  
   All rights reserved.  
   You may distribute it under the terms of either the GNU General Public  
   License or the Artistic License, as specified in the Perl README file.  
   
   
 =head1 ACKNOWLEDGEMENTS  
   
   Larry Wall for Perl, Tim Bunce for DBI, Jean-Louis Leroy for Tangram and Set::Object,  
   Sam Vilain for Class::Tangram, Jochen Wiedmann and Jeff Zucker for DBD::CSV & Co.,  
   Adam Spiers for MySQL::Diff and all contributors.  
   
   
 =head1 SUPPORT / WARRANTY  
   
   Data::Storage is free software. IT COMES WITHOUT WARRANTY OF ANY KIND.  
   
   
 =head1 TODO  
   
   
 =head2 BUGS  
   
 "DBI-Error [Tangram]: DBD::mysql::st execute failed: Unknown column 't1.requestdump' in 'field list'"  
   
   ... occours when operating on object-attributes not introduced yet:  
   this should be detected and appended/replaced through:  
   "Schema-Error detected, maybe (just) an inconsistency.  
   Please check if your declaration in schema-module "a" matches structure in database "b" or try to run"  
   db_setup.pl --dbkey=import --action=deploy  
   
   
 Compare schema (structure diff) with database ...  
   
   ... when issuing "db_setup.pl --dbkey=import --action=deploy"  
   on a database with an already deployed schema, use an additional "--update" then  
   to lift the schema inside the database to the current declared schema.  
   You will have to approve removals and changes on field-level while  
   new objects and new fields are introduced silently without any interaction needed.  
   In future versions there may be additional options to control silent processing of  
   removals and changes.  
   See this CRUD-table applying to the actions occouring on Classes and Class variables when deploying schemas,  
   don't mix this up with CRUD-actions on Objects, these are already handled by (e.g.) Tangram itself.  
   Classes:  
     C create    ->  yes, handled automatically  
     R retrieve  ->  no, not subject of this aspect since it is about deployment only  
     U update    ->  yes, automatically for Class meta-attributes, yes/no for Class variables (look at the rules down here)  
     D delete    ->  yes, just by user-interaction  
   Class variables:  
     C create    ->  yes, handled automatically  
     R retrieve  ->  no, not subject of this aspect since it is about deployment only  
     U update    ->  yes, just by user-interaction; maybe automatically if it can be determined that data wouldn't be lost  
     D delete    ->  yes, just by user-interaction  
     
   It's all about not to be able to loose data simply while this is in pre-alpha stage.  
   And loosing data by being able to modify and redeploy schemas easily is definitely quite easy.  
     
   As we can see, creations of Classes and new Class variables is handled  
   automatically and this is believed to be the most common case under normal circumstances.  
   
   
 =head2 FEATURES  
   
   - Get this stuff together with UML (Unified Modeling Language) and/or standards from ODMG.  
   - Make it possible to load/save schemas in XMI (XML Metadata Interchange),  
     which seems to be most commonly used today, perhaps handle objects with OIFML.  
     Integrate/bundle this with a web-/html-based UML modeling tool or  
     some other interesting stuff like the "Co-operative UML Editor" from Uni Darmstadt. (web-/java-based)  
   - Enable Round Trip Engineering. Keep code and diagrams in sync. Don't annoy/bother the programmers.  
   - Add support for some more handlers/locators to be able to  
      access the following standards/protocols/interfaces/programs/apis transparently:  
     +  DBD::CSV (via Data::Storage::Handler::DBI)  
    (-) Text::CSV, XML::CSV, XML::Excel  
     -  MAPI  
     -  LDAP  
     -  DAV (look at PerlDAV: http://www.webdav.org/perldav/)  
     -  Mbox (use formail for seperating/splitting entries/nodes)  
     -  Cyrus (cyrdeliver - what about cyrretrieve (export)???)  
     -  use File::DiffTree, use File::Compare  
     -  Hibernate  
     -  "Win32::UserAccountDb"  
     -  "*nix::UserAccountDb"  
     -  .wab - files (Windows Address Book)  
     -  .pst - files (Outlook Post Storage?)  
     -  XML (e.g. via XML::Simple?)  
   - Move to t3, look at InCASE  
   - some kind of security layer for methods/objects  
     - acls (stored via tangram/ldap?) for functions, methods and objects (entity- & data!?)  
     - where are the hooks needed then?  
       - is Data::Storage & Co. okay, or do we have to touch the innards of DBI and/or Tangram?  
       - an attempt to start could be:  
          - 'sub getACLByObjectId($id, $context)'  
          - 'sub getACLByMethodname($id, $context)'  
          - 'sub getACLByName($id, $context)'  
             ( would require a kinda registry to look up these very names pointing to arbitrary locations (code, data, ...) )  
   - add more hooks and various levels  
   - better integrate introduced 'getObjectByGuid'-mechanism from Data::Storage::Handler::Tangram  
   
   
 =head3 LINKS / REFERENCES  
   
   Specs:  
     UML 1.3 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-06-08.pdf  
     XMI 1.1 Spec: http://cgi.omg.org/cgi-bin/doc?ad/99-10-02.pdf  
     XMI 2.0 Spec: http://cgi.omg.org/docs/ad/01-06-12.pdf  
     ODMG: http://odmg.org/  
     OIFML: http://odmg.org/library/readingroom/oifml.pdf  
   
   CASE Tools:  
     Rational Rose (commercial): http://www.rational.com/products/rose/  
     Together (commercial): http://www.oi.com/products/controlcenter/index.jsp  
     InCASE - Tangram-based Universal Object Editor  
     Sybase PowerDesigner: http://www.sybase.com/powerdesigner  
     
   UML Editors:  
     Fujaba (free, university): http://www.fujaba.de/  
     ArgoUML (free): http://argouml.tigris.org/  
     Poseidon (commercial): http://www.gentleware.com/products/poseidonDE.php3  
     Co-operative UML Editor (research): http://www.darmstadt.gmd.de/concert/activities/internal/umledit.html  
     Metamill (commercial): http://www.metamill.com/  
     Violet (university, research, education): http://www.horstmann.com/violet/  
     PyUt (free): http://pyut.sourceforge.net/  
     (Dia (free): http://www.lysator.liu.se/~alla/dia/)  
     UMLet (free, university): http://www.swt.tuwien.ac.at/umlet/index.html  
     Voodoo (free): http://voodoo.sourceforge.net/  
     Umbrello UML Modeller: http://uml.sourceforge.net/  
   
   UML Tools:  
     http://www.objectsbydesign.com/tools/umltools_byPrice.html  
   
   Further readings:  
     http://www.google.com/search?q=web+based+uml+editor&hl=en&lr=&ie=UTF-8&oe=UTF-8&start=10&sa=N  
     http://www.fernuni-hagen.de/DVT/Aktuelles/01FHHeidelberg.pdf  
     http://www.enhyper.com/src/documentation/  
     http://cis.cs.tu-berlin.de/Dokumente/Diplomarbeiten/2001/skinner.pdf  
     http://citeseer.nj.nec.com/vilain00diagrammatic.html  
     http://archive.devx.com/uml/articles/Smith01/Smith01-3.asp  
   
Legend:
Removed from v.1.14  
changed lines
  Added in v.1.17
MailToCvsAdmin">MailToCvsAdmin
 ViewVC Help
Powered by ViewVC 1.1.26 RSS 2.0 feed