[jbossts-issues] [JBoss JIRA] (JBTM-1287) @DataManagement injection point is null on service invocation

[Paul Robinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729440#comment-12729440 ] 

Paul Robinson edited comment on JBTM-1287 at 10/26/12 9:47 AM:
---------------------------------------------------------------

There's still a problem. Even though we can now intercept calls to a plain old JAX-WS service, the target instance is a proxy rather than the actual instance. This means that we can't read off the annotations on the target class in order to setup the transaction.

Also, as we don't have an instance, we can't do the injection. Moving the injection to CDI would be better as it would reduce the codebase and make it less susceptible to these changes.
                
      was (Author: paul.robinson):
    There's still a problem. Even though we can now intercept calls to a plain old JAX-WS service, the target instance is a proxy rather than the actual instance. This means that we can't read off the annotations on the target class in order to setup the transaction.
                  
> @DataManagement injection point is null on service invocation
> -------------------------------------------------------------
>
>                 Key: JBTM-1287
>                 URL: https://issues.jboss.org/browse/JBTM-1287
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: TXFramework
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M2
>
>
> This causes ATTest to fail.
> The problems seems to be that ServiceRequestSoapHandler#getInstance returns a different instance to that which is invoked by the service. 
> This used to work, but an upgrade in CXF seems to have changed the behavior. 

--
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