[
https://jira.jboss.org/browse/WELD-478?page=com.atlassian.jira.plugin.sys...
]
Dan Allen commented on WELD-478:
--------------------------------
Really the dependencies should not be available in the docs because it's only bound to
fall out of a date. We have a much, much better solution. The dependencies are listed in
the META-INF/DEPENDENCIES.txt file inside the weld-servlet JAR.
Replaced list in docs with this hint.
Tomcat dependencies are incomplete in documentation
---------------------------------------------------
Key: WELD-478
URL:
https://jira.jboss.org/browse/WELD-478
Project: Weld
Issue Type: Task
Components: Documentation
Affects Versions: 1.0.1.Final
Reporter: Hontvári József
Fix For: 1.1.0.CR1
In section 18.3. there is a list of dependencies for servlet containers. This is
incomplete, it does not list all dependecies and it also does not specify their versions.
After tracking some NoClassDefFoundError, here are some additional jars:
-jsr299-api.jar is listed but this does not exist in Weld 1.0.1.Final distribution.
Likely this is cdi-api.jar from the artifacts/cdi directory.
-weld-logging.jar is listed, but I cannot find such jar. Likely this entry is obsolete.
-cal10n-api-0.7.2.jar
-javax.inject-1.jar
-jboss-interceptor-1.0.0-CR11.jar
-jboss-interceptor-api-1.1.jar
-slf4j-ext-1.5.10.jar
After adding these jars Weld starts with the web application but
org.jboss.weld.environment.servlet.Listener throws a
com.google.common.collect.ComputationException:
java.lang.reflect.GenericSignatureFormatError. I tries to follow the maven configuration,
but without success, I can only guess that I included the wrong version of one of the
jars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira