[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [equinox-dev] DefaultAdaptor?
|
John,
From the one liner you gave to describe
what you are trying to achieve, it seems that using a framework adaptor
is not right.
It seems that you should be able to
do what you want with a regular bundle and the typical events.
PaScaL
"John Wells"
<jwells@xxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
03/08/2006 07:00 AM
|
Please respond to
Equinox development mailing list |
|
|
To
| "Equinox development
mailing list" <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [equinox-dev] DefaultAdaptor? |
|
I looked at what you have here
and it looks very nice. Our basic true requirement is to be able
to start our OSGi IP bundle when the framework starts so that it can install
our other bundles and then pass control to our bundle manager. It
seems like a fairly simply “AdaptorHook” should be able to do the trick
for us here.
One question:
The “hookconfigurators.properties”
that is in the base osgi jar file seems to have a lot of Eclipse specific
stuff in it:
org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook,\
org.eclipse.core.runtime.internal.adaptor.EclipseLogHook,\
org.eclipse.core.runtime.internal.adaptor.EclipseErrorHandler,\
org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook,\
org.eclipse.core.runtime.internal.adaptor.EclipseClassLoadingHook,\
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter,\
org.eclipse.core.runtime.internal.stats.StatsManager,\
org.eclipse.osgi.internal.verifier.SignedBundleHook
Do I need to “exlude” these
things if I don’t want their behavior (in particular, something somewhere
makes the system bundle offeI dr a lot of services that I do not particularly
want)? Will the resulting framework work properly if I do take them
away?
Anyway, I love this hook mechanism
(in theory, I haven’t tried it yet, that’ll be my job today) and can’t
wait to see it properly documented and supported (Equinox 3.3?)
John Wells (Aziz)
jwells@bea.comNOSPAM
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Tuesday, March 07, 2006 5:22 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] DefaultAdaptor?
Hi John,
We have removed the DefaultAdaptor in M5 bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=114968.
We are hoping to get a webpage, probably in the form of a WIKI to help
document the adaptor hooks. For now I would recommend you look at
the javadoc from the following packages in the org.eclipse.osgi project
org.eclipse.osgi.baseadaptor
org.eclipse.osgi.baseadaptor.bundlefile
org.eclipse.osgi.baseadaptor.hooks
org.eclipse.osgi.baseadaptor.loader
I remember a post from you a while ago that stated you were extending the
DefaultAdaptor. What is the reason you are doing this? Can
you take a look at the new hooks and see if your needs can be implemented
by a hook. If you cannot please open a bug requesting the necessary
hook you need. I hope to have a WIKI started soon, but I'm currently
focused on EclipseCon and M6 so it may be a week or two before I can get
one ready.
Tom
"John Wells"
<jwells@xxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
03/07/2006 03:07 PM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| "Equinox development
mailing list" <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [equinox-dev] DefaultAdaptor? |
|
So, we *were* using the “org.eclipse.osgi.framework.internal.defaultadaptor.DefaultAdaptor”
class in order to boot our version of Equinox. A while ago (we don’t
refresh very often) this class could be found in the “framework org.eclipse.osgi_3.2.0.jar”
file. This appears to no longer be true. That’s ok, we can
depend on one or two more jar files. But I can’t for the life of
me figure out where it has moved to. I hear talk of the mysterious
“startup.jar” but cannot seem to find the binary distribution of said
JAR from the equinox nightly build pages. Is this class still part
of the JARs that are released as part of the nightly builds?
Furthermore, is there documentation anywhere on the proposed new Adaptor
architecture I hear so much about? We would like to use supported
interfaces from Equinox in our project! But I’ve been looking around
on the Equinox web-site and haven’t found any documentation on the adaptors.
Perhaps I am looking in the wrong places?
John Wells (Aziz)
jwells@bea.comNOSPAM
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
and affiliated
entities, that may be confidential, proprietary, copyrighted
and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
and affiliated
entities, that may be confidential, proprietary, copyrighted
and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
