XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » EDI parsing questions
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2016)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Israel EvansSubject: EDI parsing questions
Author: Israel Evans
Date: 21 Jun 2006 05:08 PM
I have a couple of questions regarding parsing EDI to XML using the Java API.

1.) Is there a way to collect more than just the first validation error?
We are doing something like the following, inside a try/catch block, where validation errors show up as an Exception.

StylusFileFactory sff = StylusFileFactory.getFactory();
sf = sff.createStylusFile(strAdapterURL, isEDIFACT);
isSF = sf.getInputStream();
StreamUtil.copyStream(isSF, osXML);

When the Exception is thrown, the stream is ended. Which means I only get the first validation error.

Is there a way to continue parsing after a validation error in order to find all the validation errors in a document?

2.) If StylusStudio is attempting to parse a document that is malformed enough that it cannot parse, even with validation off for the adapter, will it always throw an exception?

adapter:EDI:newline=crlf:val=no:decode=yes:field=yes:len=no:seg=no:tbl=no:typ=no:opt=no:eol=yes

I hope someone can answer these questions, but I have a suspicion that the answer to #1 is "no" and the answer to #2 is "yes".

Thanks!
Posttop
Tony LavinioSubject: EDI parsing questions
Author: Tony Lavinio
Date: 22 Jun 2006 08:44 AM
You are right on both counts.

It would be possible to have the parser continue after an error, but
the InputStream interface doesn't really allow for that. You would
need something like the ErrorListener or ErrorHandler interfaces from
JAXP or SAX, which categorize errors into 'warnings,' non-fatal 'errors'
and 'fatal errors.'

I will add to our suggestion database the idea of an EDI validator.
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.