change to AbstractFileAdapterElement causes getXMLElement to return null

[GoogleCodeExporter]

Thanks for all the improvements over the weekend!

Unfortunately, one of the changes causes a problem: when a DataAdapter is
initialized with the constructor that takes a DOM element, the element is
not saved, and getXMLElement returns null. This can be fixed by putting the
line "this.xmlElement = elem" back from the previous version in
AbstractFileAdapterElement.initialize(Element).

Original issue reported on code.google.com by kenny.pe...@hxti.com on 12 May 2008 at 2:47

[GoogleCodeExporter]

Hi Kenny, after DataAdapter is loaded, the XML element should not be used, 
because we
should not rely on such an XML element. Think about the scenario we load 
DataAdapter
from RDBMS, not from XML file, the XML element doesn't exist.  The other reason 
is to
reduce memory usage. As you have seem, to keep such a reference on all 
DataAdapter
will request more than 1.5G memory when we are trying to load ~10000 policies.

I will make some changes to clarify the usage of DataAdapter.

If you've used the getXMLElement in your application, please change to use other
methods, and I apologize for the inconvenience. If you still have concern about 
it,
please let me know.

-ppzian

Original comment by ppz...@gmail.com on 13 May 2008 at 1:55

• Changed state: WorkByDesign

[GoogleCodeExporter]

What other methods? If I've got a DataAdapter, how do I get the XML out of it?

Original comment by kenny.pe...@hxti.com on 13 May 2008 at 1:04