You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2010/02/20 02:41:28 UTC
[jira] Resolved: (ARIES-197) Fix the Export-Service /
Import-Service headers
[ https://issues.apache.org/jira/browse/ARIES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved ARIES-197.
-----------------------------------
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/incubator/aries/trunk ...
M application/application-management/pom.xml
M application/application-obr-resolver/pom.xml
M application/application-runtime/pom.xml
M application/application-utils/pom.xml
M blueprint/blueprint-bundle/pom.xml
M jpa/jpa-container-context/pom.xml
M transaction/transaction-blueprint/pom.xml
M transaction/transaction-manager/pom.xml
M web/web-urlhandler/pom.xml
Committed r912059
> Fix the Export-Service / Import-Service headers
> -----------------------------------------------
>
> Key: ARIES-197
> URL: https://issues.apache.org/jira/browse/ARIES-197
> Project: Aries
> Issue Type: Improvement
> Components: Application, Blueprint, JPA, Transaction, Web
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Minor
> Fix For: 1.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (ARIES-197) Fix the Export-Service /
Import-Service headers
Posted by Guillaume Nodet <gn...@gmail.com>.
I do agree those headers are mostly useful for the OBR capabilities generation.
I'd be more than happy to remove them once we have something better
based on blueprint.
In the mean time, I think it's quite harmless to keep them in. They
really help when generating OBR requirements, so that in Karaf, i can
simply write the following command:
obr:start "Apache Aries Application Management"
Another way would be to write some obr.xml extensions so that the
listed capabilities and requirements will be added to the resource
definition by the plugin:
http://svn.apache.org/repos/asf/felix/trunk/bundlerepository/obr.xml
I don't mind using that instead, all I really care about is that the
capabilities and requirements are actually defined somehow...
On Mon, Feb 22, 2010 at 13:12, Timothy Ward <ti...@apache.org> wrote:
>
> Hi,
>
> I am concerned by the work done under this JIRA. I see several issues with it.
>
> * The Import-Service and Export-Service headers are deprecated (and have been for some time), we should not build things that rely upon them
>
> * Import-Service and Export-Service do not provide enough information to be useful for resolution as they do not include service properties or allow multiple registered interfaces. The header also provides no way to express an optional dependency.
>
> * The methodology used is inconsistent. If a bundle exports a service which has a mandatory requirement on an imported service then it is not listed. This is not what we do for export package. If a bundle exports a package, but has a mandatory dependency on a package import, then it is still listed.
>
> I personally think that we should be avoiding the use of Import-Service and Export-Service, and providing some blueprint integration that allows us to generate OBR requirements and capabilities for <reference> and <service> elements. I'm sorry if I missed an opportunity to comment on this earlier, but I didn't see anything about it on the mailing list until the JIRA comment on Friday.
>
> Regards,
>
> Tim
>
>
>> Date: Sat, 20 Feb 2010 01:41:28 +0000
>> From: jira@apache.org
>> To: aries-dev@incubator.apache.org
>> Subject: [jira] Resolved: (ARIES-197) Fix the Export-Service / Import-Service headers
>>
>>
>> [ https://issues.apache.org/jira/browse/ARIES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Guillaume Nodet resolved ARIES-197.
>> -----------------------------------
>>
>> Resolution: Fixed
>>
>> Committing to https://svn.apache.org/repos/asf/incubator/aries/trunk ...
>> M application/application-management/pom.xml
>> M application/application-obr-resolver/pom.xml
>> M application/application-runtime/pom.xml
>> M application/application-utils/pom.xml
>> M blueprint/blueprint-bundle/pom.xml
>> M jpa/jpa-container-context/pom.xml
>> M transaction/transaction-blueprint/pom.xml
>> M transaction/transaction-manager/pom.xml
>> M web/web-urlhandler/pom.xml
>> Committed r912059
>>
>>
>> > Fix the Export-Service / Import-Service headers
>> > -----------------------------------------------
>> >
>> > Key: ARIES-197
>> > URL: https://issues.apache.org/jira/browse/ARIES-197
>> > Project: Aries
>> > Issue Type: Improvement
>> > Components: Application, Blueprint, JPA, Transaction, Web
>> > Reporter: Guillaume Nodet
>> > Assignee: Guillaume Nodet
>> > Priority: Minor
>> > Fix For: 1.0
>> >
>> >
>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>
> _________________________________________________________________
> Send us your Hotmail stories and be featured in our newsletter
> http://clk.atdmt.com/UKM/go/195013117/direct/01/
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
RE: [jira] Resolved: (ARIES-197) Fix the Export-Service /
Import-Service headers
Posted by Timothy Ward <ti...@apache.org>.
Hi,
I am concerned by the work done under this JIRA. I see several issues with it.
* The Import-Service and Export-Service headers are deprecated (and have been for some time), we should not build things that rely upon them
* Import-Service and Export-Service do not provide enough information to be useful for resolution as they do not include service properties or allow multiple registered interfaces. The header also provides no way to express an optional dependency.
* The methodology used is inconsistent. If a bundle exports a service which has a mandatory requirement on an imported service then it is not listed. This is not what we do for export package. If a bundle exports a package, but has a mandatory dependency on a package import, then it is still listed.
I personally think that we should be avoiding the use of Import-Service and Export-Service, and providing some blueprint integration that allows us to generate OBR requirements and capabilities for <reference> and <service> elements. I'm sorry if I missed an opportunity to comment on this earlier, but I didn't see anything about it on the mailing list until the JIRA comment on Friday.
Regards,
Tim
> Date: Sat, 20 Feb 2010 01:41:28 +0000
> From: jira@apache.org
> To: aries-dev@incubator.apache.org
> Subject: [jira] Resolved: (ARIES-197) Fix the Export-Service / Import-Service headers
>
>
> [ https://issues.apache.org/jira/browse/ARIES-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Guillaume Nodet resolved ARIES-197.
> -----------------------------------
>
> Resolution: Fixed
>
> Committing to https://svn.apache.org/repos/asf/incubator/aries/trunk ...
> M application/application-management/pom.xml
> M application/application-obr-resolver/pom.xml
> M application/application-runtime/pom.xml
> M application/application-utils/pom.xml
> M blueprint/blueprint-bundle/pom.xml
> M jpa/jpa-container-context/pom.xml
> M transaction/transaction-blueprint/pom.xml
> M transaction/transaction-manager/pom.xml
> M web/web-urlhandler/pom.xml
> Committed r912059
>
>
> > Fix the Export-Service / Import-Service headers
> > -----------------------------------------------
> >
> > Key: ARIES-197
> > URL: https://issues.apache.org/jira/browse/ARIES-197
> > Project: Aries
> > Issue Type: Improvement
> > Components: Application, Blueprint, JPA, Transaction, Web
> > Reporter: Guillaume Nodet
> > Assignee: Guillaume Nodet
> > Priority: Minor
> > Fix For: 1.0
> >
> >
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
_________________________________________________________________
Send us your Hotmail stories and be featured in our newsletter
http://clk.atdmt.com/UKM/go/195013117/direct/01/