Adventure builder and verifier

Question

I've deployed adventure builder in JSE8, and verifier shows failure. Are these valid AVK failures?
Output exerpts:
Fail     All classes in this Web Archive are loadable. Please refer to J2EE 1.4 Specification Section #8.1.2 for further information.     For [ /ab/Adventure.war ]
classes [ org.apache.commons.codec.base64.Base64 ] referenced by [ com.sun.j2ee.blueprints.taglibs.smart.ClientStateTag] are not found
classes [ org.apache.commons.codec.base64.Base64 ] referenced by [ com.sun.j2ee.blueprints.waf.controller.impl.ClientStateFlowHandler] are not found
Please either bundle the above mentioned classes in the application or use optional packaging support for them.
Fail     Filter class has a public constructor that takes no argument. Please refer to Java Servlet 2.4 Specification Section #SRV.6.2 for further information.

Answer 1

base64.jar is available as part of the adventurebuilder application from http://java.sun.com/developer/releases/adventure/index.html.
After adding base64.jar, there were further errors resulting from not being able to locate jstl jar.
Some of us have been able to pass all verifier tests by including base64.jar and jstl1.1 jar while others have not been successful. This is probably because of the jstl jar file that is being used. We are trying to sort this out. Once resolved, the plan is to update the sources on portal with the correct set of jars.
The problem appears only while verifying the application; compiling and executing the app works fine. This is apparently because the app uses jstl which in turn uses other libraries which are available as part of the appserver installation. Thus the appserver is able to locate the required libraries. But the verifier is either not able to locate the libraries or loads libraries in a different order....