|
| Re: Extending the OSGI Console with your own commands? [message #46911 is a reply to message #46874] |
Thu, 24 February 2005 18:01   |
Eclipse User |
|
|
|
Originally posted by: chaves.inf.no.ufsc.spam.br
Extension points are a runtime thing, the OSGi framework does/cannot not
use the concept. You can provide your own command provider by
registering it as an OSGi service. See EclipseCommandProvider as an
example (adds a few commands).
Rafael
Bob Balfe wrote:
>
> Looking at the internal code it looks like there is an open object model
> to do this but there doesn't appear to be an extension point or access
> to the underlying OSGI console object.
>
> Is anyone aware if this is possible in 3.0.x or 3.1?
>
> --
> Bob
|
|
|
|
| Re: Extending the OSGI Console with your own commands? [message #46970 is a reply to message #46941] |
Thu, 24 February 2005 19:28 |
| Eclipse User |
|
|
|
Originally posted by: chaves.inf.no.ufsc.spam.br
EclipseAdaptor instantiates and requests its registration (just look for
references to EclipseCommandProvider). Oh right, there is this
issue... services are registered programatically, so your command
provider can only be registered when/if your plug-in is activated.
To register a service programatically, see BundleContext#registerService.
Rafael
Bob Balfe wrote:
> Thanks for the response.
>
>
>>Extension points are a runtime thing, the OSGi framework does/cannot not
>> use the concept. You can provide your own command provider by
>>registering it as an OSGi service. See EclipseCommandProvider as an
>>example (adds a few commands).
>
>
> I did find that but I can not seem to locate how that class is instantiated
> or invoked. Would you happen to know that?
>
|
|
|
|
| Re: Extending the OSGI Console with your own commands? [message #47027 is a reply to message #46970] |
Thu, 24 February 2005 20:57 |
 Bob Balfe
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0110_01C51A89.7AFD4EB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ok, in order to get that to work (which it does work doing this) you =
have to export the "org.eclipse.osgi.framework.console" package in the =
org.eclipse.osgi manifest file.
Is this a bug? I would think since these packages are public and the =
object model seems to be very open (which BTW is great) that this would =
be available to use.
--=20
Bob
IBM Software Group
Workplace Client Technology Platform, Rich Edition
"Rafael Chaves" <chaves@inf.no.ufsc.spam.br> wrote in message =
news:cvl9sd$8kg$1@www.eclipse.org...
> EclipseAdaptor instantiates and requests its registration (just look =
for=20
> references to EclipseCommandProvider). Oh right, there is this=20
> issue... services are registered programatically, so your command=20
> provider can only be registered when/if your plug-in is activated.
>=20
> To register a service programatically, see =
BundleContext#registerService.
>=20
> Rafael
>=20
> Bob Balfe wrote:
> > Thanks for the response.
> >=20
> >=20
> >>Extension points are a runtime thing, the OSGi framework does/cannot =
not
> >> use the concept. You can provide your own command provider by
> >>registering it as an OSGi service. See EclipseCommandProvider as an
> >>example (adds a few commands).
> >=20
> >=20
> > I did find that but I can not seem to locate how that class is =
instantiated
> > or invoked. Would you happen to know that?
> >
------=_NextPart_000_0110_01C51A89.7AFD4EB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Ok, in order to get that to work (which =
it does=20
work doing this) you have to export the =
"org.eclipse.osgi.framework.console"=20
package in the org.eclipse.osgi manifest file.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Is this a bug? I would think =
since these=20
packages are public and the object model seems to be very open (which =
BTW is=20
great) that this would be available to use.</FONT></DIV><FONT =
face=3DArial=20
size=3D2></FONT>
<DIV><BR><FONT face=3DArial size=3D2>-- <BR>Bob<BR>IBM Software =
Group<BR>Workplace=20
Client Technology Platform, Rich Edition</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>"Rafael Chaves" <</FONT><A=20
href=3D"mailto:chaves@inf.no.ufsc.spam.br"><FONT face=3DArial=20
size=3D2>chaves@inf.no.ufsc.spam.br</FONT></A><FONT face=3DArial =
size=3D2>> wrote=20
in message </FONT><A href=3D"news:cvl9sd$8kg$1@www.eclipse.org"><FONT =
face=3DArial=20
size=3D2>news:cvl9sd$8kg$1@www.eclipse.org</FONT></A><FONT face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> EclipseAdaptor =
instantiates=20
and requests its registration (just look for <BR>> references =
to=20
EclipseCommandProvider). Oh right, there is this <BR>> issue... =
services are=20
registered programatically, so your command <BR>> provider can only =
be=20
registered when/if your plug-in is activated.<BR>> <BR>> To =
register a=20
service programatically, see BundleContext#registerService.<BR>> =
<BR>>=20
Rafael<BR>> <BR>> Bob Balfe wrote:<BR>> > Thanks for the=20
response.<BR>> > <BR>> > <BR>> >>Extension points =
are a=20
runtime thing, the OSGi framework does/cannot not<BR>> >> =
use the=20
concept. You can provide your own command provider by<BR>>=20
>>registering it as an OSGi service. See EclipseCommandProvider as =
an<BR>> >>example (adds a few commands).<BR>> > <BR>> =
>=20
<BR>> > I did find that but I can not seem to locate how that =
class is=20
instantiated<BR>> > or invoked. Would you happen to know=20
that?<BR>> ></FONT></BODY></HTML>
------=_NextPart_000_0110_01C51A89.7AFD4EB0--
|
|
|
| Re: Extending the OSGI Console with your own commands? [message #47057 is a reply to message #47027] |
Thu, 24 February 2005 21:13 |
| Eclipse User |
|
|
|
Originally posted by: chaves.inf.no.ufsc.spam.br
Oops... missed that...
Bob, could you open an enhancement request against Platform/Runtime
asking to have org.eclipse.osgi.framework.console exported? Even though
its design seems to be well thought, it is intended for internal use,
and forcing it to follow Eclipse API rules is a strong commitment, so it
may not be as simple as just adding another exported package to the
bundle manifest.
Thanks.
Rafael
Bob Balfe wrote:
> Ok, in order to get that to work (which it does work doing this) you
> have to export the "org.eclipse.osgi.framework.console" package in the
> org.eclipse.osgi manifest file.
>
> Is this a bug? I would think since these packages are public and the
> object model seems to be very open (which BTW is great) that this would
> be available to use.
>
> --
> Bob
> IBM Software Group
> Workplace Client Technology Platform, Rich Edition
>
>
> "Rafael Chaves" <chaves@inf.no.ufsc.spam.br
> <mailto:chaves@inf.no.ufsc.spam.br>> wrote in message
> news:cvl9sd$8kg$1@www.eclipse.org...
> > EclipseAdaptor instantiates and requests its registration (just look for
> > references to EclipseCommandProvider). Oh right, there is this
> > issue... services are registered programatically, so your command
> > provider can only be registered when/if your plug-in is activated.
> >
> > To register a service programatically, see BundleContext#registerService.
> >
> > Rafael
> >
> > Bob Balfe wrote:
> > > Thanks for the response.
> > >
> > >
> > >>Extension points are a runtime thing, the OSGi framework
> does/cannot not
> > >> use the concept. You can provide your own command provider by
> > >>registering it as an OSGi service. See EclipseCommandProvider as an
> > >>example (adds a few commands).
> > >
> > >
> > > I did find that but I can not seem to locate how that class is
> instantiated
> > > or invoked. Would you happen to know that?
> > >
|
|
|
|
Powered by
FUDForum. Page generated in 0.03689 seconds
] 
Search
Help
Register
Login
Home
