We'll check some out in ICE tomorrow and see what it's doing with them, then go from there.
It might be smart enough to know to get rid of those, some systems don't mind them. Dave Culley Integration Specialist West Suffolk NHS Foundation Trust, Hardwick Lane, Bury St Edmunds, IP33 2QZ Tel: 01284-712594 |Mobile: 07588 505 206 (Wednesdays and Fridays) | E-mail: [email protected] -----Original Message----- From: openEHR-technical [mailto:[email protected]] On Behalf Of [email protected] Sent: 14 December 2015 17:00 To: [email protected] Subject: openEHR-technical Digest, Vol 46, Issue 1 Send openEHR-technical mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of openEHR-technical digest..." Today's Topics: 1. errorhandling in AOM/ADLParser (Bert Verhees) ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Dec 2015 10:23:53 +0100 From: Bert Verhees <[email protected]> To: For openEHR technical discussions <[email protected]> Subject: errorhandling in AOM/ADLParser Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"; Format="flowed" I implemented errorhandling and two errors for testing. To let it work in my code, this must be added to ADL.g4 .... .... grammar Adl; @parser::header{ import nl.rosa.archetype.errorhandling.ADLParserErrorMessages; } // // ============== Parser rules ============== // ad..... ..... ..... The error-handling itself is in the grammar. I needed to change the grammar a little bit: metaDataItem: metaDataTagAdlVersion '=' adlVersion |metaDataTagUid '=' GUID |metaDataTagBuildUid '=' GUID |metaDataTagRmRelease '=' rmRelease |metaDataTagIsControlled |metaDataTagIsGenerated |identifier ('=' metaDataValue )? ; adlVersion:VERSION_ID | .+? {notifyErrorListeners(String.format(ADLParserErrorMessages.getErrorMessage("VARAV"), _localctx.getText()));}//invalid adl_version $1; must be a valid 3-part numeric version identifier ; rmRelease:VERSION_ID | .+? {notifyErrorListeners(String.format(ADLParserErrorMessages.getErrorMessage("VARRV"), _localctx.getText()));}//invalid rm_release $1; must be a valid 3-part numeric version identifier ; You can find a code-example in the test-file ErrorsTest.java During this week I will implement the other errors. If you want to use the error-handling only, copy the different code to your project. Of course you are free to use my code, which is quite compact, has a generated AOM, also. I try to keep the AOM-part generated. Best regards Bert Verhees -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20151214/51dcf09c/attachment-0001.html> ------------------------------ Subject: Digest Footer _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ------------------------------ End of openEHR-technical Digest, Vol 46, Issue 1 ************************************************ ************************************************************************************ This message and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this in error, you should not disseminate or copy this email. Please notify the sender immediately and delete this email from your system. Please also note that any opinions presented in this email are solely those of the author and do not necessarily represent those of West Suffolk NHS Foundation Trust. Email transmission cannot be guaranteed to be secure, or error free as information could be intercepted, corrupted, lost, destroyed, late in arriving or incomplete as a result of the transmission process by communicating with the Trust by email you accept these risks. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. This footnote also confirms that, unless otherwise stated, this email message has been swept by Sophos Anti-virus for the presence of computer malware including viruses and spyware. ************************************************************************************ _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
