Mauro Molinari

> The standard JnlpDownloadServlet was made available by the maven webstart plugin: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.codehaus.mojo%22%20AND%20a%3A%22webstart-jnlp-servlet%22 I saw that artifact but I was not sure about the versioning policy. Also, I'm using the...

Hi Tobias, thank you very much. I think that some quick documentation like this would be very useful to be included here on GitHub in README files or such. Just...

> `jnlp.versionEnabled` and `jnlp.packEnabled` are removed, because they are handled by the servlet instead of the JNLP client. The Feature of letting the client handle them was added in Java...

Hi Tobias, is there a way to tell the `jnlp-war` plugin to put everything into a subdirectory of the WAR? By default, the JNLP is put on the root of...

> No, that is not possible. But why do you need to create one big jar? You can create one ria.war to have http://host:port/ria/launch.jnlp and a second war for the...

> And it must be checked if the defaults for codebase and href are still correct. I opened #47. I don't think anything in `codebase` and `href` defaults should be...

Right now it may be the only showstopper. However I could not do a complete test yet. The other problem may be the difficulty to use the `jnlp-war` plugin from...

Mi sono "scontrato" anch'io con Giuseppe su questa cosa in passato :-) Di fatto le specifiche SPID non dicono che il server web debba restituire un HTTP Status Code d'errore...

Grazie Giuseppe, spero che il rinnovo degli strumenti di test possa essere l'occasione anche per una riflessione approfondita su quanto dovrebbero spingersi i vincoli di validazione che vengono imposti. Alcuni...

@AntonioGiovanniSchiavone è proprio questo il fatto, non lo vedo citato da alcuna parte! Nelle specifiche SAML 2.0 l'attributo è opzionale: >`ProviderName` [Optional] >Specifies the human-readable name of the requester for...