Issue: The aacli.sh produces a large stack trace on a default install of 2.3.8 due to the servlet-api.jar not being found in the normal location shibboleth-idp/lib.
Fix: (pick one)
place the servlet-api.jar file into the extracted lib area prior to deploying the IdP
place the servlet-api.jar file into the /opt/shibboleth-idp/lib area post deployment.
Fix was mostly as described by Chad, except turns out it's ok to just put them in the installed IdP's /lib directly, as the current Ant installer <war> task as defined in build.xml specifically excludes the servlet-api and jsp-api jars from being copied into the war file, which is the desired behavior.
Scott Cantor
November 6, 2012 at 1:34 AM
Per Chad:
There is a way to do it. The assembly file for the distributions can take a scope a dependency file set. The current assembly, I believe, has two dep sets: one for compile time deps which is what ends up in the WAR and lib directory and one for then endorsed libs. I believe the correct way to address that issues is to add a third dep set with a provided scope and an inclusion set of only the servlet jar (and perhaps the jsp-api jar just for good measure) and put those libraries in some other directory (maybe a subdir of lib) and include that library on the command line tool classpath.
Scott Cantor
October 24, 2012 at 6:49 PM
I'm not sure if we'd want that jar in the distribution, regardless of the downsides, but we'll check on it and close one way or the other.
Issue:
The aacli.sh produces a large stack trace on a default install of 2.3.8 due to the servlet-api.jar not being found in the normal location shibboleth-idp/lib.
Fix: (pick one)
place the servlet-api.jar file into the extracted lib area prior to deploying the IdP
place the servlet-api.jar file into the /opt/shibboleth-idp/lib area post deployment.
This is a rehash of SIDP-422: aacli.sh Exception in thread "main" Closed must have been able to sneak back in.