Test XAdES4J against the plugtest test vectors

[GoogleCodeExporter]

What steps will reproduce the problem?
1. XAdES4J should be tested to verify how well it can interoperate with other 
XAdES implementations. This is the purpose of the ETSI plugtests. Participation 
in the plugtest event itself is too expensive, but XAdES4J can still be tested 
against the plugtest test vectors. A copy of the the plugtest test vectors can 
be downloaded here 
http://www.jipdec.or.jp/archives/ecpc/longtermstorage/en/download.html

What is the expected output? What do you see instead?

It is doubtful the XAdES4J test suite can ship with a copy of those test 
vectors (because of licensing issues). On the other hand, the machinery to run 
those tests can be part of the build at the author's discretion.

The real output of this work would be a public statement of how well XAdES4J 
does on the plugtest test vectors and possibly a list of bugs (if applicable).

What version of the product are you using? On what operating system?
1.2.0
Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by clementp...@gmail.com on 25 Nov 2011 at 2:57

[GoogleCodeExporter]

Original comment by luis.fgoncalv on 20 Jan 2012 at 11:22

• Changed state: Accepted
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

There is also the online XAdES Baseline profile conformance checker tool 
available (after registration) here:
http://xades-portal.etsi.org/pub/index.shtml

Original comment by markuski...@gmail.com on 13 Sep 2013 at 9:30