[ 
https://issues.apache.org/jira/browse/DAFFODIL-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Beckerle closed DAFFODIL-576.
----------------------------------
    Resolution: Not A Problem

Really a scallop library limitation. 

> CLI: Gracefully handle trailing flags
> -------------------------------------
>
>                 Key: DAFFODIL-576
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-576
>             Project: Daffodil
>          Issue Type: Bug
>          Components: CLI, Usability
>    Affects Versions: s7
>            Reporter: Jessie Chab
>            Priority: Minor
>              Labels: beginner
>
> I was running pcap tests with the CLI and I wanted to save the output to a 
> file so I could copy it over to a TDML file. I added "-o outfile" to my 
> command, not thinking about the fact that it came after the infile trailing 
> argument. Depending on the file I was parsing I got one of the following 
> errors:
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; 
> {color:red}Content is not allowed in prolog.{color}
>       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
> Source)
>       at 
> edu.illinois.ncsa.daffodil.xml.DaffodilXMLLoader.loadXML(DaffodilXMLLoader.scala:435)
>       at scala.xml.factory.XMLLoader$class.load(XMLLoader.scala:56)
> ........
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; 
> {color:red}Invalid byte 2 of 2-byte UTF-8 sequence.{color}
>       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
> Source)
>       at 
> edu.illinois.ncsa.daffodil.xml.DaffodilXMLLoader.loadXML(DaffodilXMLLoader.scala:435)
>       at scala.xml.factory.XMLLoader$class.load(XMLLoader.scala:56)
> Would it be possible for the CLI to either acknowledge a flagless argument as 
> an infile, so the arguments can be in any ordering, or to catch this kind of 
> situation and alert the user that there cannot be arguments after the infile 
> before trying to parse?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to