You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <de...@tuscany.apache.org> on 2008/09/22 02:43:44 UTC
[jira] Commented: (TUSCANY-2396) Model and runtime should be in
separate modules
[ https://issues.apache.org/jira/browse/TUSCANY-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633116#action_12633116 ]
Jean-Sebastien Delfino commented on TUSCANY-2396:
-------------------------------------------------
Did more work on this today and split binding-rmi, next on my list is implementation-script.
> Model and runtime should be in separate modules
> -----------------------------------------------
>
> Key: TUSCANY-2396
> URL: https://issues.apache.org/jira/browse/TUSCANY-2396
> Project: Tuscany
> Issue Type: Wish
> Components: Build System
> Reporter: Jean-Sebastien Delfino
> Fix For: Java-SCA-Next
>
>
> A number of extensions are still putting their model and runtime implementation in a single module. This makes them difficult to use in:
> - development tools
> - deployment tools
> - administration applications
> - nodes which need to load and inspect composites without necessarily running all their contents
> We've done some refactoring work on a number of implementation and binding extensions. The following modules still need to be refactored:
> - dwr
> - jms
> - notification
> - rmi
> - osgi
> - script
> - spring
> - xquery
> When doing that, the dwr, rmi, and script extensions should be migrated from the extension-helper to the assembly and core-spi SPI used by all other extensions, as extension-helper doesn't provide the proper separation between model and runtime.
> More extensions which I'm not sure about as they are not in Tuscany distributions:
> - das
> - data-xml
> - openjpa
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.