[seam-issues] [JBoss JIRA] Updated: (SEAMWICKET-40) Make dependency on weld-servlet-core truly optional

Make dependency on weld-servlet-core truly optional --------------------------------------------------- Key: SEAMWICKET-40 URL: https://issues.jboss.org/browse/SEAMWICKET-40 Project: Seam for Apache Wicket Issue Type: Enhancement Affects Versions: 3.0.0.Final Environment: An app with weld-se-core and embedded container (like embedded Jetty) running servlet/filter based web app. Reporter: Ondrej Zizka Sometimes, you may need a standalone (Java SE) application, with an optional web module. For project which are (for any reason, e.g. historically) not based on an app server, you would need a weld-se-core for the core. weld-se-core can't co-exist with weld-servlet-core because they are different impl of the same API. However, seam-wicket silently relies on having weld-servlet-core, at least to support RequestContext. I suggest to make this need 1) explicitly stated in POM, 2) optional. To make it optional, it's enough to make this block {code} if( conversation.isActive() ){ ... } {code} in SeamRequestCycleProcessor's response() optional, because without active RequestContext, it fails.