bndtools
bndtools copied to clipboard
bndtools
Add view to browse services/remote services
It would be very useful to have a user interface that presented the registered services...and associated metadata (svc properties), etc...and was able to connect to some externally running framework.
Also this view could be used to present and interact with remote services via the remote service admin specification. This would make the running, publishing, discovering, testing, etc of remote services much easier.
ECF http://www.eclipse.org/ecf is starting a sub-project to create tooling for remote services/RSA, and we would be willing to contribute/collaborate on such a ui/view/set of views, etc.
- This is handled awfully well imho with Apache Felix Webconsole (you can open a browser in Eclipse)
- Of course we'd love a pull request for a view inside bndtools ...
Until that moment, this is moved in abeyance
Webconsole does an ok job for what it does, but it does have many limitations...e.g. browser request/response limits the service dynamics, not much wrt DS/service dependencies (e.g. graphical model of service relationships/dependencies), and other things. Also, I believe there could (should) be remote services specifics (e.g. indication that it's a remote service, support for discovery + RSA API, etc).
WRT view inside bndtools...yes, that would be the general idea. I would suggest attempting to do something collaborative/community based...i.e. coordinated via this bug to start...rather than waiting for someone (i.e. me) to just do it all.
Well, you seem to not have looked at XRay (and it does have RSA support, albeit small, the services are marked for import/export) ... And to be honest, I think the web is the future ...
- Easier to develop for
- Will work anywhere there is a web server in the framework
- Graphics in the browser are plain awesome nowadays, just no comparison with anything available inside Eclipse
So I am totally supportive of an independent Eclipse console for a running framework but I would focus on something with a web based interface. You can make quite rich interactions with the web browser nowadays inside Eclipse.
On 18 jul. 2014, at 02:13, Scott Lewis [email protected] wrote:
Webconsole does an ok job for what it does, but it does have many limitations...e.g. browser request/response limits the service dynamics, not much wrt DS/service dependencies (e.g. graphical model of service relationships/dependencies), and other things. Also, I believe there could (should) be remote services specifics (e.g. indication that it's a remote service, support for discovery + RSA API, etc).
WRT view inside bndtools...yes, that would be the general idea. I would suggest attempting to do something collaborative/community based...i.e. coordinated via this bug to start...rather than waiting for someone (i.e. me) to just do it all.
— Reply to this email directly or view it on GitHub.
I don't have anything in particular against a web interface, but how would this be consistent with bndtools? Does this imply that bndtools is moving to a web interface?
WRT dev tooling specifically (as opposed to general graphics programming), I don't agree with 1-3, but to each his own.
Huh? For developing Java I think Eclipse is still a great tool and to use JDT we need to be inside Eclipse. However, tools to monitor OSGi have lots more places to go than development. Seems therefore much more effective to develop them independent of Eclipse?
Basic modularity, dear Watson? :-)
Hey Peter,
Modularity isn't the issue. I'm not saying that there shouldn't be multiple UIs for OSGi tooling...e.g. web ui, Eclipse, native apps, etc. Clearly there should be. But this bug is wrt bndtools, bndtools ui is based upon Eclipse UI, I assert that there would be user/usability advantage to ui integration. For example, it allows direct interaction between views.