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/01/11 01:02:54 UTC
[jira] Created: (RIVER-328) OSGi Bundles for Versioning Control and
Codebase Evolution
OSGi Bundles for Versioning Control and Codebase Evolution
----------------------------------------------------------
Key: RIVER-328
URL: https://issues.apache.org/jira/browse/RIVER-328
Project: River
Issue Type: Improvement
Reporter: Peter Firmstone
Assignee: Peter Firmstone
Fix For: AR3
Use of OSGi Bundles and OSGi core framework to control dependencies and code base evolution.
Common components between a Service and its download client jar need to be packaged separately, such that both the Service and client depend on this package, forming an indirect dependency link between the client and service. The common component also needs to be downloadable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RIVER-328) OSGi Bundles for Versioning Control
and Codebase Evolution
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798564#action_12798564 ]
Peter Firmstone commented on RIVER-328:
---------------------------------------
"Common components between a Service and its download client jar need to be packaged separately, such that both the Service and client depend on this package, forming an indirect dependency link between the client and service. The common component also needs to be downloadable."
Whether the same or a later compatible bundle version is selected for the client would depend upon the common component bundle jini service interface. Provided the service interface hasn't changed there should be no problem using later client bundle versions, the client is abstracted from the server implementation and does not depend upon it, both the Server and Client depend on the common service interface component and are otherwise independent. Other client and server implementations could also depend upon the common components in a jini service interface bundle and participate.
I'm not sure how version information can be included into Marshalled Instances, such that when performing a lookup, incompatible types with identical names are not compared. This will require further thought.
> OSGi Bundles for Versioning Control and Codebase Evolution
> ----------------------------------------------------------
>
> Key: RIVER-328
> URL: https://issues.apache.org/jira/browse/RIVER-328
> Project: River
> Issue Type: Improvement
> Reporter: Peter Firmstone
> Assignee: Peter Firmstone
> Fix For: AR3
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Use of OSGi Bundles and OSGi core framework to control dependencies and code base evolution.
> Common components between a Service and its download client jar need to be packaged separately, such that both the Service and client depend on this package, forming an indirect dependency link between the client and service. The common component also needs to be downloadable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (RIVER-328) OSGi Bundles for
Versioning Control and Codebase Evolution
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798567#action_12798567 ]
Peter Firmstone edited comment on RIVER-328 at 1/11/10 2:36 AM:
----------------------------------------------------------------
River-149: The service provider functionality and Classloader visibility might be better controlled with an OSGi service instance.
was (Author: pfirmst):
The service provider functionality and Classloader visibility might be better controlled with an OSGi service instance.
> OSGi Bundles for Versioning Control and Codebase Evolution
> ----------------------------------------------------------
>
> Key: RIVER-328
> URL: https://issues.apache.org/jira/browse/RIVER-328
> Project: River
> Issue Type: Improvement
> Reporter: Peter Firmstone
> Assignee: Peter Firmstone
> Fix For: AR3
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Use of OSGi Bundles and OSGi core framework to control dependencies and code base evolution.
> Common components between a Service and its download client jar need to be packaged separately, such that both the Service and client depend on this package, forming an indirect dependency link between the client and service. The common component also needs to be downloadable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-328) OSGi Bundles for Versioning Control and
Codebase Evolution
Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone updated RIVER-328:
----------------------------------
Remaining Estimate: 300h (was: 5h)
Original Estimate: 300h (was: 5h)
> OSGi Bundles for Versioning Control and Codebase Evolution
> ----------------------------------------------------------
>
> Key: RIVER-328
> URL: https://issues.apache.org/jira/browse/RIVER-328
> Project: River
> Issue Type: Improvement
> Reporter: Peter Firmstone
> Assignee: Peter Firmstone
> Fix For: AR3
>
> Original Estimate: 300h
> Remaining Estimate: 300h
>
> Use of OSGi Bundles and OSGi core framework to control dependencies and code base evolution.
> Common components between a Service and its download client jar need to be packaged separately, such that both the Service and client depend on this package, forming an indirect dependency link between the client and service. The common component also needs to be downloadable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.