The map file has been updated for the following Bug changes:
+ Bug 224432. Memory Leak in install -> start -> stop -> uninistall cycle
(FIXED)
+ Bug 224905. [AAP001] The source issue (FIXED)
+ Bug 224990. org.eclipse.core.runtime.adaptor.run() covers up all
exceptions (FIXED)
The following projec
I have this error with my data service destination, when I commit changes :
[RPC Fault faultString="Unable to access UserTransaction in DataService."
faultCode="Server.Processing" faultDetail="null"]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::dispatchFa
It is up to you. If the framework removes them, they will be removed in a
random order. If you have several listeners and registered services which
should be shutdown in some orderly manner, you will need to shut them down
yourself.
--
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fello
It is more clear to clean up your service registrations and service
listeners in your BundleActivator.stop method. In many cases you want to
unregister your listeners and services before you do other clean-up that
will invalidate the services/listeners and cause them to behave
incorrectly. For ex
I find below description in the OSGi R4 specification section '4.3.6
Activation':
stop(BundleContext) – This method must undo all the actions of the
BundleActivator.start(BundleContext) method. However, it is unnecessary to
unregister services or Framework listeners, because they must be cleaned
Ciao PaScaL :)
Thanks for answering all these! :)
I will look into the classes you mentioned and continue from that.
Sure enough there will be other questions along the way but for now I've
got a good picture of what to do :)
cu, and good luck with M6! :)
Chao,
hh
-Original Message-
From: