Tamas Palfy created NIFI-10955:
----------------------------------
Summary: In JASN1Reader allow preprocess of ASN files to reconcile
unsupported features
Key: NIFI-10955
URL: https://issues.apache.org/jira/browse/NIFI-10955
Project: Apache NiFi
Issue Type: Improvement
Reporter: Tamas Palfy
The ASN specification allows the creation of valid ASN files that has features
unrecognized by the asn1bean library we are using in JASN1Reader.
We can add a preprocessing step that creates modified versions of the provided
ASN files (leaving the originals intact) that removes unsupported features in a
way that makes them less strict but otherwise should still be compatible with
incoming data.
Identified unsupported features:
* Certain constraint types
** E.g.
{code:java}
SomeType ::= INTEGER (ALL EXCEPT (0..15))
{code}
* Extension marker (a.k.a "ellipsis" or
{code:java}
...
{code}
)
** Can occur in constraints (e.g.
{code:java}
SomeType ::= INTEGER (0..8,...,100..200)
{code}
although
{code:java}
SomeType ::= INTEGER (0..8,...)
{code}
works)
** or in type definitions (e.g.
{code:java}
RootType::= SEQUENCE {
field1 INTEGER,
field2 INTEGER,
...,
field3 INTEGER
}
{code}
but this seems to work as well).
* Version brackets e.g.
{code:java}
SomeType ::= SEQUENCE {
integerField1 INTEGER,
integerField2 INTEGER,
...,
[[ -- from version 2
integerField3 INTEGER,
integerField4 INTEGER ]]
}
{code}
Seems to require extension marker as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
