river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Firmstone (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-341) River's Jini Service Jar Archive Names
Date Sat, 12 Jun 2010 08:20:14 GMT

    [ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878231#action_12878231
] 

Peter Firmstone commented on RIVER-341:
---------------------------------------

Hi Dan,

I'm actually thinking about removing the ui-api.jar, as it doesn't relate to Services, it's
really client platform related, for example a new API relating to JavaFX might be created,
a client would utilise it on it's classpath, then a Services UI implementation jar would implement
a factory that could create a Service UI application on the client.

I'd say it's much better to just add new UI API support directly to River's codebase.

> River's Jini Service Jar Archive Names
> --------------------------------------
>
>                 Key: RIVER-341
>                 URL: https://issues.apache.org/jira/browse/RIVER-341
>             Project: River
>          Issue Type: Improvement
>          Components: doc
>    Affects Versions: AR3
>            Reporter: Peter Firmstone
>         Attachments: Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf
>
>
> A new Standard to define name schemes of jar archives for services.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message