verapdf / verapdf-rest Goto Github PK

• mustache templates to render profiles
• navigation between rules

• disable steps 2 & 3 until file selected

It would be great if you could upload and test a PDF without having to know in advance which profile to select. If it were up to me, this would be the default option. I'm working on implementing this in my fork. If you're aware of any obstacles, I'm all ears. Also, if you want a pull request, let me know.

Hi,

Which version and branch is deployed on http://demo.verapdf.org? When I checkout and run the rest client, I get other validation errors than on http://demo.verapdf.org.

Thanks
Stefan

As a user of veraPDF, I would prefer knowing exactly which version of the validation library the demo at http://demo.verapdf.org/ is based upon.

It doesn't matter where exactly this information is placed, but I think the footer is the most natural place.

Hi folks,

I wrote a Kubernetes Helm Chart to run the verapdf/rest image on your own Kubernetes cluster. Maybe you are interested in linking to it?

The repository URL ist https://gitlab.com/MatthiasLohr/verapdf, and it's also included in the official Helm Chart directory, ArtifactHub: https://artifacthub.io/packages/search?page=1&ts_query_web=verapdf

Best regards
Matthias

Following the merge of the PR #53
when I try to start veraPDF-rest, I get a Java backtrace:

% java -jar target/verapdf-rest-0.1.0-SNAPSHOT.jar server
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.fasterxml.jackson.module.afterburner.util.MyClassLoader (file:/home/alexis/new_boite/dev/veraPDF-rest/target/verapdf-rest-0.1.0-SNAPSHOT.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.fasterxml.jackson.module.afterburner.util.MyClassLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
INFO  [2021-03-29 08:48:39,565] io.dropwizard.server.DefaultServerFactory: Registering jersey handler with root path prefix: /
INFO  [2021-03-29 08:48:39,568] io.dropwizard.server.DefaultServerFactory: Registering admin handler with root path prefix: /
INFO  [2021-03-29 08:48:39,568] io.dropwizard.assets.AssetsBundle: Registering AssetBundle with name: css for path /css/*
INFO  [2021-03-29 08:48:39,585] io.dropwizard.assets.AssetsBundle: Registering AssetBundle with name: js for path /js/*
INFO  [2021-03-29 08:48:39,585] io.dropwizard.assets.AssetsBundle: Registering AssetBundle with name: img for path /img/*
java.lang.IllegalStateException: You need to provide an instance of SwaggerBundleConfiguration
at io.federecio.dropwizard.swagger.SwaggerBundle.run(SwaggerBundle.java:59)
at io.federecio.dropwizard.swagger.SwaggerBundle.run(SwaggerBundle.java:46)
at io.dropwizard.setup.Bootstrap.run(Bootstrap.java:200)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:42)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:87)
at io.dropwizard.cli.Cli.run(Cli.java:78)
at io.dropwizard.Application.run(Application.java:93)
at org.verapdf.rest.app.VeraPdfRestApplication.main(VeraPdfRestApplication.java:45)
zsh: exit 1     java -jar target/verapdf-rest-0.1.0-SNAPSHOT.jar server

I'm on Ubuntu 20.04 LTS with openJDK 11 (same error with openJDK 14). I'm not the only one to have this problem, cf the comments in the PR.

The workaround is to checkout the code before the merge of the PR:

git checkout 7f1970f81d3d55e1804dafbc60596d3f2c5cfb38
mvn clean package

Then veraPDF-rest starts without problem.

Dropwizard is now on 1.1.2, and other dependencies are due for upgrade as well. I've done this in my fork, and not encountered any bugs. I'll submit a pull request if you like.

Can't build for the past days due to openpreservation.org being down.

[ERROR] Non-resolvable parent POM for org.verapdf:verapdf-rest:0.1.0-SNAPSHOT: Could not transfer artifact org.verapdf:verapdf-parent:pom:1.0.17 from/to vera-pdfbox (http://artifactory.opf-labs.org/artifactory/vera-pdfbox-local): Failed to transfer file: http://artifactory.opf-labs.org/artifactory/vera-pdfbox-local/org/verapdf/verapdf-parent/1.0.17/verapdf-parent-1.0.17.pom. Return code is: 502 , ReasonPhrase:Bad Gateway. and 'parent.relativePath' points at wrong local POM @ line 6, column 11 -> [Help 2]

Siegfried and Clamv Anti virus have a service/daemon operational mode. You may look at this for inspiration.

Being able to operate the suggested way decreases dramatically the time necessary to process a large number of files as it reduces the need to boot up the java virtual machine for each file and to pass large chunks of data over the network.

http://demo.verapdf.org/ is failing with http 500 for the last 24 hours.

• add option to record passed tests
• improve failure display
• feature reporting clean up
• option to download reports

openAPI is a file format which specifies machine-readably how REST APIs can be used, with the swagger editor one can then create sample clients in 53 languages. There is a swagger/openapi plugin for dropwizard which allows that the according swagger.yml file is created automatically from some annotations.

Somebody who presents this (unfortunately in german) https://media.ccc.de/v/froscon2017-1985-einfache_rest-apis_mit_dropwizard_und_swagger (Slides https://programm.froscon.de/2017/system/event_attachments/attachments/000/000/469/original/20170818_LeanIX_Presentation_Froscon.pdf )

VeraPDF-Rest brought me to dropwizard. I'm using the swagger plugin on my own project ( https://github.com/ZUGFeRD/mustangserver ) and I would like to try to integrate it with verapdf-rest. First step: upgrade dropwizard to exactly that version which works with the swagger plugin.
Second step: add some annotations, maybe use a bundle, change the config file slightly.

• stages should be tabs not circles
• use button look and feel from site

• client should detect no file selected
• server should catch empty file

I've had some feedback at an OPF event and the demo.verapdf.org domain seems to be a problem for some organisations. It suggests that the product isn't "ready". Maybe we should use validator.verapdf.org and forward the old URL.

[ERROR] Failed to execute goal on project verapdf-rest: Could not resolve dependencies for project org.verapdf:verapdf-rest:jar:0.1.0-SNAPSHOT: Failed to collect dependencies at com.yunspace.dropwizard:dropwizard-xml:jar:41: Failed to read artifact descriptor for com.yunspace.dropwizard:dropwizard-xml:jar:41: Could not transfer artifact com.yunspace.dropwizard:dropwizard-xml:pom:41 from/to jcenter (http://jcenter.bintray.com): Access denied to: http://jcenter.bintray.com/com/yunspace/dropwizard/dropwizard-xml/41/dropwizard-xml-41.pom -> [Help 1]

https://jfrog.com/blog/secure-jcenter-with-https/

Steps to reproduce:

1. Select a file in step 1, click Next.
2. Select a profile in step 2, click Next.
3. Click the circle for step 2, change the selected profile, click Next. Then click circle 3.
4. Click the circle for step 1, change the selected file, click Next.

Observed behavior:

1. When I try to go back to step 2 to change my selection and repeat the previous operation, nothing happens when I click next. When I click circle 3, an Exception message appears briefly and then I get the same report as I did the first time I was on step 3.
2. If change the selected file and attempt to repeat the same operation (without refreshing the page) I get the same validation report as I did the first time.

Expected behavior:

1. It should be more clear to end users that a page refresh is required to perform a new operation.
2. It's not obvious that the form inputs, which aren't disabled and can have their inputs changed, have no effect on the resulting report on step 3 unless/ until the page is refreshed.

Notes:
It seems like maybe some instructions are needed and/or perhaps the form inputs should be disabled once the form is used. I don't want to disappear the report without some kind of intentional user action because they might not have saved the report results from the previous operation. I'm working on this in my fork, but I'm not sure what the best solution might be yet.