makdimka077 / xades4j

Automatically exported from code.google.com/p/xades4j
GNU Lesser General Public License v3.0
0 stars 0 forks source link

ExclusiveCanonicalXML prefixes should be optional #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Adding a ExclusiveCanonicalXML transform without prefixes is causing validation 
errors because it has an incorrect implementation.

It generates an InclusiveNamespaces object that doesn't contain any prefixes 
while it should ommit the object.

Version: Trunk (so 1.4.0 I would guess)

Original issue reported on code.google.com by eighth.c...@gmail.com on 31 Oct 2012 at 9:56

Attachments:

GoogleCodeExporter commented 9 years ago
could you add a test case for this problem?

Original comment by hubert.k...@gmail.com on 31 Oct 2012 at 1:01

GoogleCodeExporter commented 9 years ago
Sure, here you go.

Original comment by eighth.c...@gmail.com on 31 Oct 2012 at 1:21

Attachments:

GoogleCodeExporter commented 9 years ago
OK, looks good. I can confirm the problem.

There's a whitespace error in second patch, but it's nothing major.

Original comment by hubert.k...@gmail.com on 5 Nov 2012 at 1:38

GoogleCodeExporter commented 9 years ago

Original comment by luis.fgoncalv on 6 Nov 2012 at 9:29

GoogleCodeExporter commented 9 years ago
Thanks! Patch applied on r249.

Original comment by luis.fgoncalv on 6 Nov 2012 at 9:52