You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Andrew Eberbach (JIRA)" <ji...@apache.org> on 2007/02/26 23:21:06 UTC

[jira] Resolved: (MUSE-172) Change the structure of server-side code

     [ https://issues.apache.org/jira/browse/MUSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Eberbach resolved MUSE-172.
----------------------------------

    Resolution: Fixed

I restructured the server synthesizer to be more like the proxy. There are now two synthesizers, one for the interface and one for the implementation class. The abstract stuff doesn't seem to make sense anymore after talking through this a bit more.

> Change the structure of server-side code 
> -----------------------------------------
>
>                 Key: MUSE-172
>                 URL: https://issues.apache.org/jira/browse/MUSE-172
>             Project: Muse
>          Issue Type: Improvement
>          Components: Tooling - Code Generation
>            Reporter: Andrew Eberbach
>         Assigned To: Andrew Eberbach
>             Fix For: 2.2.0
>
>
> The structure for server-side generated code should change so that it is easier to regenerate into the same directory. 
> I propose that each capability generates to
> 1. An interface (IMyCapability)
> This is exactly the same as it is today
> 2. An abstract class (AbstractMyCapability)
> This has getters/setters and other generated constants 
> 3. The user-defined data (MyCapability)
> This would have any user-defined methods and any initialize, destroy -related methods. 

-- 
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org