You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (JIRA)" <ji...@apache.org> on 2013/04/18 11:33:16 UTC
[jira] [Resolved] (WW-4048) WW-3994 breaks instantiation of
CompositeActionMapper
[ https://issues.apache.org/jira/browse/WW-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukasz Lenart resolved WW-4048.
-------------------------------
Resolution: Fixed
Resolved also dosc were updated! Thanks for reporting!
https://cwiki.apache.org/confluence/display/WW/ActionMapper
> WW-3994 breaks instantiation of CompositeActionMapper
> -----------------------------------------------------
>
> Key: WW-4048
> URL: https://issues.apache.org/jira/browse/WW-4048
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.3.14
> Reporter: Christoph Lenggenhager
> Fix For: 2.3.15
>
>
> The fix for WW-3994 breaks the instantiation of the CompositeActionMapper in
> {{com.opensymphony.xwork2.inject.ContainerImpl.ConstructorInjector.findConstructorIn(Class<T> implementation)}}
> The exception (which seems to be swallowed somewhere along the request processing) is the following:
> {code}
> Caused by: java.lang.RuntimeException: com.opensymphony.xwork2.inject.DependencyException: Could not find a suitable constructor in org.apache.struts2.dispatcher.mapper.CompositeActionMapper.
> at com.opensymphony.xwork2.inject.ContainerImpl.inject(ContainerImpl.java:502)
> at com.opensymphony.xwork2.inject.ContainerImpl$7.call(ContainerImpl.java:539)
> at com.opensymphony.xwork2.inject.ContainerImpl.callInContext(ContainerImpl.java:593)
> at com.opensymphony.xwork2.inject.ContainerImpl.inject(ContainerImpl.java:537)
> at com.opensymphony.xwork2.config.impl.LocatableFactory.create(LocatableFactory.java:32)
> at com.opensymphony.xwork2.inject.ContainerBuilder$4.create(ContainerBuilder.java:130)
> ... 32 more
> {code}
> Thank you for having a look at this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira