[
https://issues.apache.org/jira/browse/AXIS2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3286:
----------------------------------------
Assignee: Saminda Wishwajith Abeyruwan
> Spring AOP integration. Follow up on thread (AXIS2-3258)
> --------------------------------------------------------
>
> Key: AXIS2-3286
> URL: https://issues.apache.org/jira/browse/AXIS2-3286
> Project: Axis 2.0 (Axis2)
> Issue Type: Test
> Affects Versions: 1.3
> Environment: Java, Spring AOP
> Reporter: Rakesh
> Assignee: Saminda Wishwajith Abeyruwan
>
> Hi,
> I was looking at the resolution for the problem of using Spring AOP.
> I get an exception The following error occurred during schema generation:
> Unable to load bytecode for class
> abc.skl.ServiceProvider$$EnhancerByCGLIB$$4a4e81cb
> The thread AXIS2-3258 has a solution where you introduce an interface as
> ServiceClass along with ServiceObjectSupplier.
> My question is does this mean that my implementation class should now be
> split into an interface with all the method signatures and then provide an
> implementation class for this interface. And do this for all the services.
> The problem is that we are building an internal framework and will be
> extended by other systems. So if we do put this condition, then all
> subsystems will have to be modified to do the same too.
> Is it possible that I simply the provider class itself as the ServiceClass
> and also have the ServiceObjectProvider in place.
> Can someone please confirm my understanding.
> Thanks,
> Rakesh.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
