You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2010/05/31 15:06:37 UTC
[jira] Created: (RIVER-341) River's Jini Service Jar Archive Names
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
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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Dan Rollo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878199#action_12878199 ]
Dan Rollo commented on RIVER-341:
---------------------------------
Thanks Peter. Another question, re the ui-api jar. It now says:
Name-ui-api.jar
Service UI Role, Factory and Attribute Type's. It is encouraged that
these be contributed back to Apache River for others to use for new UI
Toolkits such as those contained in the BDJ spec, JavaFX, etc.
May be platform specific. Where name is replaced by the API
Framework the UI is specific to.
Should the "Name" prefix also be removed? (Below includes updated description):
*-ui-api.jar
Service UI Role, Factory and Attribute Type's. It is encouraged that
these be contributed back to Apache River for others to use for new UI
Toolkits such as those contained in the BDJ spec, JavaFX, etc.
May be platform specific.
> 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883062#action_12883062 ]
Peter Firmstone commented on RIVER-341:
---------------------------------------
Thanks Greg, any thoughts about the other archives?
This is still a draft, I'd like to do param.jar if possible, however I concede there are security issues that would need resolving first. It would be possible to mount a denial of service attack using multiple clients each extending a parameter.
However if we can set a size limit constraint on the uploaded archive and place it in a protection domain with no permissions, then it might be workable.
For Jini's current market, that of predominately trusted networks with a handful of developers, this has no use case, for an internet domain untrusted network where there are multiple unknown developers, that's a different story.
There is also the case for evolution of Service API with a client submitting later version parameters to an earlier version service. Although it is expected that a Service API evolve in a Backward compatible manner, there's still the question of where does the service load those classes? In that case it would be in a ClassLoader specifically devoted to api-ext.jar files. When I thought about param.jar it was to remove possible abuse of api-ext.jar.
So in summary lets see if it can be done satisfactorily, otherwise it goes.
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Naming Jini Service Artefacts.odt)
> 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
>
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Naming Jini Service Artefacts.pdf)
> 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
>
> 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Service Bundles.pdf)
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Draft Revision 5, removed Name-ui-api.jar, added *-entry.jar
> 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.odt, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Naming Jini Service Artefacts.odt)
> 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, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Service Bundles rev1.odt)
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Service Bundles.odt
Service Bundles.pdf
Draft documents to define Jar Archive names for Jini Service Developers and deployers.
> 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: Service Bundles.odt, Service Bundles.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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Service Bundles.odt)
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Service Bundles rev1.pdf
Service Bundles rev1.odt
Fixed redundant sentence.
> 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: Service Bundles rev1.odt, Service Bundles rev1.pdf, Service Bundles.odt, Service Bundles.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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Service Bundles rev1.pdf)
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Revised
> 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912932#action_12912932 ]
Peter Firmstone commented on RIVER-341:
---------------------------------------
Might I suggest that we not version API?
Or if we do, make it a convention not to incompatibly change or extend it's public API (bug fixes only)
com.foo.some-service:api:version
instead if we want to add additional API, extend an existing interface, new classes etc, we add an archive:
com.foo.some-service:api-ext1:version
This allows new extended Services to serve existing clients without ClassNotFoundException's, since the client won't have the extended classes, unless they are packaged separately and available for download. In the case of ServiceUI, it also allows the UI to find the new classes in old clients.
New clients will have both installed locally.
ServiceAPI is like an interface, you don't modify it, you extend it ;)
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Added clarifications about additional libraries to be included with proxy's and services.
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Suggest removal of param.jar
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Dan Rollo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877288#action_12877288 ]
Dan Rollo commented on RIVER-341:
---------------------------------
Minor confusion: The first example name pattern uses "service" as a prefix, while others use "*".
I'm not sure what the intended pattern is. Is the intent:
wombat-api.jar
wombat-ui-api.jar
wombat-api-ext.jar
wombat-proxy.jar
wombat-param.jar
wombat-imp.jar
wombat-ui.jar
If the above wombat pattern is correct, then maybe the doc (I looked at the .pdf), should change the first column to always use the same "prefix" (either * or 'service' - l lean towards '*'). eg:
change:
service-api.jar
to:
*-api.jar
change:
*-service-api-ext.jar
to:
*-api-ext.jar
OR, maybe I'm completely missing the point....;)
Dan
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: (was: Naming Jini Service Artefacts.pdf)
> 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Revised as per Dan Rollo's comment.
> 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, 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Gregg Wonderly (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880878#action_12880878 ]
Gregg Wonderly commented on RIVER-341:
--------------------------------------
Regarding the -param.jar entry. I think it is a bad idea to suggest that subclasses can and/or should occur for service defined parameters. I don't think there is really any use case that would require such a thing. The reverse codedownloading path (client->server) is a problematic them to start with, and it provides ample opportunity for arcane and security related problems.
Clients, if they want additional packaging, around a service parameter, could wrap it in another class for example.
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Commented: (RIVER-341) River's Jini Service Jar Archive
Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912929#action_12912929 ]
Peter Firmstone commented on RIVER-341:
---------------------------------------
The following was suggested by Dennis Reedy on river-dev:
What would be more helpful is conventions on how developers that use River and Maven should create their projects. We have had discussions on this in the past (so this is mostly a review), I hope that we can agree on the conventions, document them and eventually create a River archetype that generates a default project structure that produces the requisite artifacts.
We had started out using a Maven-ized classdepandjar (http://www.rio-project.org/classdepandjar-mojo.html), allowing the creation of multiple artifacts from a single project (service.jar, service-dl.jar, service-ui.jar, etc....). While this worked, the pom became overly complicated, the approach became confusing, especially if one of the artifacts had dependencies that the others didnt.
What we have moved to (and I think this is common across other developers) is to create a multi-module project that reflects the basic architectural elements of a River service. Basically, a River service is composed of the following modules:
some-service\
api\
*proxy\
*ui\
service\
* = optional
The api module contains all the classes (interfaces and other classes) that is needed to communicate with the service
The proxy module (optional), depends on the api module, and provides smart proxy support
The ui module (optional), depends on the api module and provides support for a service user interface
The service module, depends on the api module (or proxy module if used) provides the backend service implementation.
Using this approach produces an easy to use and understandable model, doesnt require classdepandjar, and dependency management is handled quite cleanly. Some will argue on the names of the modules, it doesnt really matter what the names are, as long as the project has its constituent elements broken out.
Maven groupId and artifactId conventions we adopted are as follows:
com.foo:some-service:version
com.foo.some-service:api:version
com.foo.some-service:proxy:version
com.foo.some-service:ui:version
com.foo.some-service:service:version
Additionally, if I wanted to use a service (as a client) I would declare a dependency on com.foo.some-service:api:version
I hope this helps, and I do think if we can agree on conventions like this, document them, and produce a simple example that uses them, it will help developers use River and Maven.
Dennis
[1] Higher level frameworks like Rio have this capability.
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
Removed *-entry.jar This wasn't necessary, *-api.jar and *-api-ext.jar is sufficient to handle Entry's.
> 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.odt, Naming Jini Service Artefacts.odt, Naming Jini Service Artefacts.pdf, Naming Jini Service Artefacts.pdf, 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.
[jira] Updated: (RIVER-341) River's Jini Service Jar Archive Names
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-341:
----------------------------------
Attachment: Naming Jini Service Artefacts.odt
Naming Jini Service Artefacts.pdf
> 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.