Issue 16024

EML parser not using first information

16024
Reporter: mdoering
Type: Bug
Summary: EML parser not using first information
Priority: Critical
Status: Open
Created: 2014-07-01 14:39:53.721
Updated: 2014-07-01 14:40:30.84
        
Description: The EMLparser digester rules simply call property setters regardless whether we have multiple elements (for example with language attribute). Thus the last called setter remains. This gets pretty bad when we have complex objects like contacts and information might come from the first or second address in case for example city was given in just one address. For example this contact:

{noformat}
      
Universitestparken 15 Copenhagen Copenhagen 2100 DK
London UK
{noformat} results in a single address in our model with delivery point from the first adress, but city and country from the last.]]>