Ram,
Sorry I haven't had too much time to review your code and this email, but here is what I think:
1.) Ultimately yes, but immediately no. I think you could probably "touch" the remote service using curl, wget or some similar tool. A browser might even do it. As for issue 262, finishing either part of it would result in a sufficient test. Do you know how to look up a remote service from a client? If so, then I'll take a crack at 262 tonight.
Actually I didn't have to change the Client code at all, so it looks like a context.getServiceReference(ICore.class) would still work.
3.) Yes, there are a few. I updated the ticket. In a nutshell, we should probably try to get it running headlessly and then move to 262.
Ok, I have looked at the updated ticket and I will start looking at the subgoals.
Congrats on getting this working, btw! Great work!
Thanks Jay, but the changes I have made are so small (a few extra lines in Core.java) that I am not sure if it's working as intended. The changes were based on R-OSGi tutorial and I am trying to verify that the Core is running as a "Remote" service.
Let me know if you want to merge this back into ICE and we'll help you do it.
I will work on the subgoals and have a completed set of tasks and then look to merge it into ICE, at that point.
Regards,
Ram
