perfsonar development work

[Michael Michalis <>]

Hi Loukik,

That was a problem found both in SQL MA and LS. I think it was solved by
Maciej and Roman by trimming the strings, but I think they both mentioned
that it should be taken care of by the base classes.


Regards,

Michalis Michael


> -----Original Message-----
> From: Loukik Kudarimoti 
> [mailto:]
> Sent: Friday, March 16, 2007 9:01 PM
> To: Roman Lapcz; Jason Zurawski; 
> ;
>  perfsonar-
> ;
>  Michael Michalis; Tsompanidis Ilias; Szymon Trocha
> Subject: IMPORTANT: new line characters and white spaces in xml causing
> problems
> 
> Hi guys,
> 
> I just spent quite a while trying to debug a problem where in I was
> unable to get responses from SQL MA. Turns out, its all because of new
> line characters in xml tag contents which were introduced either in the
> store or in the request message.
> 
> When any part of the service implementation is trying to compare two
> strings - one hardcoded within the implementation (such as eventType
> value) and the second one coming from the xml message (via the Message
> bean), even if the strings are similar except for new-line characters,
> the checks fail. This definitely needs to be taken care of.
> 
> Initially I thought that we could take care of this at the Message bean
> level (by stripping empty strings around a text). But I am not 100% sure
> of the outcome. I am not sure because for some strings, white spaces
> *between the text* are important (command line mp for example). Jason,
> what do you think? I found out the String.trim() method will remove
> leading and trailing white spaces but not sure about white lines?
> 
> Any thoughts anybody? This bug can cause problems because the
> configurations at least are created by the users and its difficult to
> get them to remove such white spaces and new lines. It affects SQL MA
> for sure and maybe RRD MA (Ilias?)
> 
> Loukik.