Answer the question
In order to leave comments, you need to log in
Processing xml attributes, how to organize without intermediate code?
There is an example code
<object Id=“52” />
Where the id attribute can be a number , zero, suddenly a string. I would like to get by with a standard serializer handler, or write your own. Let's say it gives out 0, an integer value, and some kind of abusive handler if it fails. According to the logic of the application, such garbage happens, but about 1 time in 40,000. It's not that I'm against extra classes, but I would like to sail errors in one place
Answer the question
In order to leave comments, you need to log in
No class model is needed here.
Especially if we have information garbage at the entrance.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question