update on my problem: (only one service gets imported from server)
1) both edef files aka. Endpoint Descriptions are parsed in
EndpointDescriptionParser.parse, but _both_ are parsed into an
ECFEndpointDescription like this:
[ECFEndpointDescription[id=ecftcp://peter-desktop:8889/server;endpoint.service.id=0;frameworkid=null]]
and so the second one gets sorted out because it's from that point
of view the same endpoint description like the first.
is that correct/intended?
2) to trigger the discovery of the second service it's enought to do
a
refresh <edef bundle id>
on the osgi console.
Any ideas why it's working with the refresh but not initially on
application start?
BTW: the edef bundles are generated and started programmatically,
but i don't think that matters since both are parsed (see 1)
thanks for any hints ...
bye, peter
Am 11.03.2015 um 12:48 schrieb Peter
Hermsdorf:
Hi Wim,
great tip, that seems to work - better ;)
now one service gets picked up, the other one not, but by stopping
and starting the edef bundle of the second service the service
gets discovered/connected.
Don't know why it's not working immediately but I'll look into
that....
thanks!
bye, peter
Am 11.03.2015 um 11:42 schrieb Wim
Jongman:
Peter can't you just remove the endpoint.service.id
property from the component definition? IIRC ECF is then
generating it's own endpoint id.
Cheers,
Wim
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
|