Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Instances changing their type [was:Discover data patternsor Create data patterns?]

From: Manos Batsis <manos_lists@----------.--->
To: Michael Kay <mike@--------.--->, XML Developers List <xml-dev@-----.---.--->
Date: 9/22/2008 7:09:00 AM
Michael Kay wrote:
> Of course all problems in computing can be solved by adding a layer of
> indirection. You can design a wrapper object that implements the interface
> and delegates all the work to either an ArrayList or a LinkedList. This
> wrapper object is the only object to know about the implementation object so
> only one place has to change when the implementation changes. But it would
> be nice if this were built into the language, not something you have to
> program yourself. Apart from anything else, forwarding all the method
> invocations is expensive.


Just for the discussion (I've seen Saxon's code ;-), a more efficient 
method would be to only use the List interface and eliminate all 
implementation class references, including initial creation, using a 
"dynamic" Factory. That Factrory could offer, besides some initial 
configuration via property file or whatnot, a runtime method to change 
the implementation at runtime through a console etc.

Cheers,

Manos


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent