[
https://jira.jboss.org/jira/browse/JBSEAM-2972?page=com.atlassian.jira.pl...
]
Jacob Orshalick commented on JBSEAM-2972:
-----------------------------------------
Yes, this is happening at the moment with seam-gen'd projects. By simply creating a
project and running a test this failure occurs. A workaround is to delete the
jboss-seam-wicket.jar from the generated lib directory of the project.
Pete, should the jar simply be excluded from the seam-gen'd project?
Unit test fails because of wicket unavailabity
----------------------------------------------
Key: JBSEAM-2972
URL:
https://jira.jboss.org/jira/browse/JBSEAM-2972
Project: Seam
Issue Type: Task
Components: Wicket
Affects Versions: 2.1.0.A1
Reporter: Joshua Partogi
Assignee: Pete Muir
Fix For: 2.1.0.BETA1
Unit test fails because wicket component is not installed. Here are the message:
java.lang.IllegalStateException: Must set application-class in <web:wicket-filter
/> in components.xml
at org.jboss.seam.web.WicketFilter.init(WicketFilter.java:80)
at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97)
at org.jboss.seam.mock.AbstractSeamTest.createSeamFilter(AbstractSeamTest.java:942)
at org.jboss.seam.mock.AbstractSeamTest.setupClass(AbstractSeamTest.java:921)
at org.jboss.seam.mock.SeamTest.setupClass(SeamTest.java:44)
Developers shouldn't be forced to use wicket. It should be left optional.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira