You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.
What is the expected output? What do you see instead?
OpXmlReader should be able to mapp fields to associates xml attributes ( Pojo ->Xml). It doesn't.
In function readProperties(..) of OpXmlReaderImpl I see: value = element.selectValue("display",REMOVE),
but in readProperties(..) of ObjXmlReaderImpl the same line is : value = element.selectValue("@display",REMOVE).
It look like in subClasses, Piriti forgot that the class files was mapped to an attribute of the current element, and instead look for an child element ...
As a result I can't mapp any attributes to subclasses of class Obj.
What version of the product are you using? On what operating system?
Pririti 0.8, Restlet 2.05, Gwt 2.4, Windows XP, Firefox 3.6
What steps will reproduce the problem?
OpXmlReader should be able to mapp fields to associates xml attributes ( Pojo ->Xml). It doesn't.
In function readProperties(..) of OpXmlReaderImpl I see: value = element.selectValue("display",REMOVE),
but in readProperties(..) of ObjXmlReaderImpl the same line is : value = element.selectValue("@display",REMOVE).
It look like in subClasses, Piriti forgot that the class files was mapped to an attribute of the current element, and instead look for an child element ...
As a result I can't mapp any attributes to subclasses of class Obj.
What version of the product are you using? On what operating system?
Pririti 0.8, Restlet 2.05, Gwt 2.4, Windows XP, Firefox 3.6
https://code.google.com/p/piriti/issues/attachmentText?id=58&aid=580002001&name=Op.java&token=NNIGCtYwlCdmNqfxfDZ_uyyaKcU%3A1351504668855
https://code.google.com/p/piriti/issues/attachmentText?id=58&aid=580002000&name=Obj.java&token=H3VR7g2Mkbdgm-YHrhtQr62Smjg%3A1351504668855
The text was updated successfully, but these errors were encountered: