[
https://issues.apache.org/jira/browse/AXIS2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404140#comment-13404140
]
Konrad Garus commented on AXIS2-3258:
-------------------------------------
I understand that. I don't mix them up - I'm saying I get a nasty NPE when I
use it with servlet context, so I decided to go for the option with
ApplicationContextHolder.
This works, as long as my beans are not proxies.
Separate concern, whenever I try to use either ServiceObjectSupplier with
ServiceClass, it attempts to instantiate the ServiceClass. This results in an
obvious exception if it's an interface, and when it's not an interface it
creates a separate instance of the class which is then used instead of Spring
bean.
> Extend Spring support to accept proxies
> ---------------------------------------
>
> Key: AXIS2-3258
> URL: https://issues.apache.org/jira/browse/AXIS2-3258
> Project: Axis2
> Issue Type: New Feature
> Components: deployment, wsdl
> Affects Versions: 1.3
> Reporter: Oleg Efimov
> Priority: Trivial
> Fix For: 1.3
>
>
> ServiceBuilder presently requires service class's byte code to obtain method
> parameter names. This won't work with proxies, thus making Spring support
> really feeble.
> I propose introducing additional service.xml parameter, namely
> ServiceInterface, to enumerate service methods and parameter names.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
