Unmarshalling file with & symbol in the name.

[dfoulkes]

WHEN

ResponseEnvelope envelope = unmarshaller.unmarshal(file);

Parsing ofx file with the following statement transaction:

        	<STMTTRN>
                		<TRNTYPE>DEBIT
                		</TRNTYPE>
                		<DTPOSTED>20161110000044</DTPOSTED>
                		<DTUSER></DTUSER>
                		<TRNAMT>-01.01</TRNAMT>
                		<FITID>17</FITID>
                		<NAME>EE & T-MOBILE            </NAME>
                		<MEMO></MEMO>
                	</STMTTRN>

THEN

Caused by: java.io.IOException: Unexpected EOF
	at net.n3.nanoxml.StdXMLReader.read(Unknown Source)
	at net.n3.nanoxml.XMLUtil.read(Unknown Source)
	at net.n3.nanoxml.ContentReader.read(Unknown Source)
	at net.n3.nanoxml.ContentReaderBackdoor.read(ContentReaderBackdoor.java:24)
	at java.io.Reader.read(Reader.java:140)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.readCharacters(NanoXMLOFXReader.java:186)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:159)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.processOFXTag(NanoXMLOFXReader.java:136)
	at com.webcohesion.ofx4j.io.nanoxml.NanoXMLOFXReader.parseV1FromFirstElement(NanoXMLOFXReader.java:45)
	at com.webcohesion.ofx4j.io.BaseOFXReader.parse(BaseOFXReader.java:113)
	at com.webcohesion.ofx4j.io.BaseOFXReader.parse(BaseOFXReader.java:68)
	at com.webcohesion.ofx4j.io.AggregateUnmarshaller.unmarshal(AggregateUnmarshaller.java:44)

[stoicflame]

Thanks for the report.

Seems like the next step is to provide a unit test that reproduces the problem so we can validate a fix.

[ProjectFrank]

This exception is being thrown from the XMLReader itself. It throws this because & is used for escape sequences in XML, so the XML parser is expecting the & to be a part of an escape sequence.

& is itself a character that should be escaped in XML.

Source: https://stackoverflow.com/questions/1091945/what-characters-do-i-need-to-escape-in-xml-documents

[Luiz-Otavio-Dorigon]

What is the forecast for this correction?

[stoicflame]

I actually can't tell if there's a bug? Shouldn't <NAME>EE & T-MOBILE</NAME> be invalid OFX? Shouldn't it be required to escape it to <NAME>EE &amp; T-MOBILE</NAME>