From: Florian G. H. <f.g...@gm...> - 2003-11-13 22:26:03
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello again. On Thursday 13 November 2003 22:00, Kal Ahmed wrote: | I think that the best way of making this clear in the API is to leave it | as it currently is with an initialise() method that receives the | configuration properties. I don't really like the idea of the | TopicMapProvider pulling properties from the TopicMapProviderFactory. If | I under stand you correctly, I think you feel the same way.=20 Correct. | My proposal | was just that you have TopicMapProviderFactory.newInstance() read a | default set of provider configuration properties.=20 OK -- what would those be? My ideas were quite similar, but I got stuck try= ing=20 to determine an appropriate "default set of provider configuration=20 properties", to be honest... | Then when you call the | newTopicMapProvider() method, those properties get passed through by the | factory to the initialise() method of the Provider. If you call the | newTopicMapProvider(Properties) method, then the properties passed | through to the Provider are the default properties overwritten with the | properteis passed into the newTopicMapProvider(Properties) method. Hmmm. I was actually thinking about catering for configuration properties t= hat=20 affect the entire factory and subsequently created providers. Like a=20 SAXParserFactory which you can configure to create namespace-aware and=20 non-namespace-aware, or validating and non-validating parsers. I must admit= ,=20 however, that I can't currently think of any such factory-wide config=20 settings that would make sense for the TopicMapProviderFactory. So this wou= ld=20 qualify as a nice-but-not-necessary feature. :-)=20 BTW, how is your testing on TopicMapSourceSupport and the modified=20 TopicMapProvider interface coming along? I'd like to add support for=20 TopicMapSource to the TopicMapMerger class (and consequently for the=20 TopicMapMergingTask as well). Could you give me a status update on that? Thanks in advance, =46lorian =2D --=20 =46lorian G. Haas <f.g...@gm...> http://member.ycn.com/~fgh/en/ GnuPG key ID: 0x46D00BE3 Key fingerprint: 18B4 3E7B 191E F534 254A 1F7C 816D 950B 46D0 0BE3 My GnuPG key is available from the public PGP key server at pgp.mit.edu (and various other key servers). =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/tAUMgW2VC0bQC+MRAtepAJ9gKPIkgUvXEFMaqTt8cKOcq/a9iACdFbrm R6heFFXHNX6mNCPKK0vqFww=3D =3DNZ/0 =2D----END PGP SIGNATURE----- |