You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rakesh (JIRA)" <ji...@apache.org> on 2007/10/18 16:59:50 UTC
[jira] Created: (AXIS2-3286) Spring AOP integration. Follow up on
thread (AXIS2-3258)
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
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3286) Spring AOP integration. Follow up on
thread (AXIS2-3258)
Posted by "robert lazarski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535967 ]
robert lazarski commented on AXIS2-3286:
----------------------------------------
Hmm, CGLIB indicates you have hibernate mixed in somehow. When you say "during schema generation" - are you implying java2wsdl ? Apart from the interface question - which generally is a good idea anyways as it allows a different implementation for each project, which is a nice plus for spring beans and pluggability - there isn't enough info here to understand your problem.
Furthermore, could you try clarifying what you mean by "Is it possible that I simply the provider class itself as the ServiceClass and also have the ServiceObjectProvider in place. "
> 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
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-3286) Spring AOP integration. Follow up on
thread (AXIS2-3258)
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org