Re: Accessing schema information from runtime system

I think DState was the "DPath" state, intended to be the part of the state used for the DPath evaluation. The notion was that there are all these components of the state that are used by one or another part of the system, and they should be defined there and be the business of that part. I

Re: Accessing schema information from runtime system

Thanks, I see that I can get to the SchemaSetRuntimeData through a ParseOrUnparseState with state.dataProc.get.ssrd Am I correct in my reading of the code that there is not currently a way to get to it through a DState object? I assume the reason that DState does not have a complete referenc

Re: Accessing schema information from runtime system

The lookup table should become part of the SchemaSetRuntimeData. That way it is global to all. Get Outlook for Android From: Sloane, Brandon Sent: Monday, April 1, 2019 4:43:18 PM To: dev@daffodil.apache.org Subject: Accessing schema infor

Accessing schema information from runtime system

As part of the enum support proposal (https://cwiki.apache.org/confluence/display/DAFFODIL/Proposal%3A+Feature+to+support+enumerations+and+typeValueCalc), there is a need to lookup types by qname from within the runtime system. For instance, suppose the schema defined the following simpleType:

[GitHub] [incubator-daffodil] jadams-tresys commented on a change in pull request #204: Provide more detail for failed assertions

jadams-tresys commented on a change in pull request #204: Provide more detail for failed assertions URL: https://github.com/apache/incubator-daffodil/pull/204#discussion_r270988174 ## File path: daffodil-runtime1/src/main/scala/org/apache/daffodil/processors/parsers/ExpressionEvalu

[GitHub] [incubator-daffodil] jadams-tresys commented on a change in pull request #204: Provide more detail for failed assertions

jadams-tresys commented on a change in pull request #204: Provide more detail for failed assertions URL: https://github.com/apache/incubator-daffodil/pull/204#discussion_r270948702 ## File path: daffodil-runtime1/src/main/scala/org/apache/daffodil/processors/parsers/AssertPatternPa

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #204: Provide more detail for failed assertions

mbeckerle commented on a change in pull request #204: Provide more detail for failed assertions URL: https://github.com/apache/incubator-daffodil/pull/204#discussion_r270942795 ## File path: daffodil-runtime1/src/main/scala/org/apache/daffodil/processors/parsers/AssertPatternParser

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #204: Provide more detail for failed assertions

mbeckerle commented on a change in pull request #204: Provide more detail for failed assertions URL: https://github.com/apache/incubator-daffodil/pull/204#discussion_r270946114 ## File path: daffodil-runtime1/src/main/scala/org/apache/daffodil/processors/parsers/ExpressionEvaluatin

[jira] [Resolved] (DAFFODIL-2095) Confirm all commented out tests either work or have an associated bug number

[ https://issues.apache.org/jira/browse/DAFFODIL-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Adams resolved DAFFODIL-2095. -- Resolution: Fixed Assignee: Dave Thompson (was: Josh Adams) Fix Version/s: 2

[GitHub] [incubator-daffodil] jadams-tresys opened a new pull request #204: Provide more detail for failed assertions

jadams-tresys opened a new pull request #204: Provide more detail for failed assertions URL: https://github.com/apache/incubator-daffodil/pull/204 We used to have more detailed assertion failed messages that included the value that was parsed, but it seems to have been lost over the c

[GitHub] [incubator-daffodil] jadams-tresys merged pull request #202: Daffodil 2095 commented out tests

jadams-tresys merged pull request #202: Daffodil 2095 commented out tests URL: https://github.com/apache/incubator-daffodil/pull/202 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [incubator-daffodil] mbeckerle commented on a change in pull request #202: Daffodil 2095 commented out tests

mbeckerle commented on a change in pull request #202: Daffodil 2095 commented out tests URL: https://github.com/apache/incubator-daffodil/pull/202#discussion_r270911506 ## File path: daffodil-test-ibm1/src/test/scala/org/apache/daffodil/TresysTests.scala ## @@ -123,40 +12

[GitHub] [incubator-daffodil] jadams-tresys closed pull request #203: Daffodil 752 assertion details

jadams-tresys closed pull request #203: Daffodil 752 assertion details URL: https://github.com/apache/incubator-daffodil/pull/203 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [incubator-daffodil] jadams-tresys commented on issue #203: Daffodil 752 assertion details

jadams-tresys commented on issue #203: Daffodil 752 assertion details URL: https://github.com/apache/incubator-daffodil/pull/203#issuecomment-478606977 This didn't work as cleanly as I expected, closing for now and will re-open once #202 is accepted. --

[GitHub] [incubator-daffodil] jadams-tresys opened a new pull request #203: Daffodil 752 assertion details

jadams-tresys opened a new pull request #203: Daffodil 752 assertion details URL: https://github.com/apache/incubator-daffodil/pull/203 Pass along more detail on assertion failures We had originally provided more detail in the assertion failed messages, including the value