[ http://jira.codehaus.org/browse/XFIRE-321?page=all ]
Dan Diephouse updated XFIRE-321:
--------------------------------
Version: (was: 1.0-RC)
(was: 1.0-M6)
(was: 1.0-M5)
(was: 1.0-M4)
(was: 1.0-M3)
(was: 1.0-alpha-2)
(was: 1.0-alpha-1)
(was: 1.1-beta-1)
(was: 1.1)
(was: 1.2)
Fix Version: (was: 1.1-beta-1)
1.1
> Provide a way to tell Aegis what concrete class to use when instantiating a
> complex type rather than just using a dynamic proxy behind an interface
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XFIRE-321
> URL: http://jira.codehaus.org/browse/XFIRE-321
> Project: XFire
> Type: New Feature
> Components: Aegis Module
> Versions: 1.0
> Reporter: Colin Hendricks
> Assignee: Dan Diephouse
> Priority: Minor
> Fix For: 1.1
>
>
> Aegis exports complex types based on the method signatures of the service
> class. For instance, a service method called saveDeal(DealIntegration aDeal)
> causes Aegis to export the DealIntegration type as a complex type. If
> DealIntegration is an interface, then Aegis uses a dynamic proxy at runtime
> to instantiate the object. This causes trouble if the real
> DealIntegrationImpl has some concrete code that should be executed in its
> constructor or something.
> It would be nice if there were a way to tell Aegis what concrete class to
> instantiate (DealIntegrationImpl in this case) rather than using a dynamic
> proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
