Error parsing deployment structure xml (EAP6)

[bes.comcom]

I built my own jboss-deployment-structure.xml using the XSD as reference (attached), but I kept getting this error (which in my past experience comes from an XML not conforming to the expected schema),

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018748: Error loading jboss-deployment-structure.xml from C:\jboss-eap-6.1\standalone\tmp\vfs\tempc08651b1fabbf20d\my.ear-7d56240c7dc68a53\contents\META-INF\jboss-deployment-structure.xml

...

Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag().

at [row,col {unknown-source}]: [2,2]

so I loaded up just the example from here (not caring about anything past parsing) and I still get there error. 

Is this a problem with EAP6?

[bes.comcom]

I brought up my app in 7.1.1 Final and I get the same error.  So what is wrong with my xml, it validates as far as I can tell?!

[shane_dev]

You have some extra characters after the </exclusions> and </dependencies> elements. Once removed, it parses fine.

[bes.comcom]

That's pretty bad when spaces after an element break the parser.

[shane_dev]

For what it's worth, spaces are not a problem. There were non whitespace albeit invisible characters in this file. You can configure Eclipse or vi, for example, to expose standard whitespace characters.

[bes.comcom]

Ah ha! I blame windows/eclipse.  Never had this problem in vi, oddly when I configure visibility in eclipse I can now see where those extra characters are (or rather the abscense of things in that space) and they're none of the eclipse "invisible characters" types.  Anway, thanks again.

[shane_dev]

No worries

I've encountered the same issue when doing development in Windows too!