AW: [equinox-dev] How do I write an Application Container
Hi, perhaps you find some useful information here: http://dz.prosyst.com/user-manuals/mBS_Extensions_6.1.5/meg/index.html Go to Developer Guide / Foreign Application Container. The JavaDoc (same source) might give you some insights as well. Regards, Jo -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Srijith Kochunni Gesendet: Donnerstag, 21. Februar 2008 13:46 An: equinox-dev@eclipse.org Betreff: [equinox-dev] How do I write an Application Container Hi, I am interested in knowing how an Application container is written. Went through the specification, but am not really able to get a good picture of how they are built and how they interact with each other. I was therefore interested in knowing if there is any examples or documentation relevant to this either on the internet / elsewhere, which could help me. I am looking at writing a small application instance, a descriptor for it, and an Application Manager implementation to manage it. How is an Application Handle retrieved and also knowing how to schedule my application would be an added bonus..! The code snippets and details provided in the spec, don`t seem complete. Please excuse me for the avalanche of questions. Any help or leads would be greatly appreciated. Thanks, Srijith. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equin ox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Eclipse and the Mac System Log - Runaway CPU
I would recommend entering a bug against SWT, just because it's a platform specific issue and they handle many of those. If they don't know what's up, they can probably find someone from Apple who would. McQ. Hal Hildebrand [EMAIL PROTECTED] racle.com To Sent by: Equinox development mailing list equinox-dev-bounc equinox-dev@eclipse.org [EMAIL PROTECTED] cc Subject 02/20/08 14:25Re: [equinox-dev] Eclipse and the Mac System Log - Runaway CPU Please respond to Equinox development mailing list [EMAIL PROTECTED] pse.org Thanks for the reply. Yea, I have no idea where this is coming from, but it's definitely coming from the Eclipse process (via pid). Things got so bad I literally had to turn off the system log - which is a lovely way to be running your system, I might add ;) On Feb 20, 2008, at 11:18 AM, John Arthorne wrote: No idea For what it's worth, these don't look like log messages produced by the platform or framework log. I don't recall ever seeing log output like this before. John Hal wrote on 02/19/2008 06:38:16 PM: Sorry if this is a really inappropriate message for this list, but I'm at my whit's end and I doubt my question will be answered on the newsgroup. Basically, I'm seeing MEGABYTES of info logged from Eclipse. There's no errors, just reams and reams and reams of info regarding the libraries I'm using everything I runt junit tests or whatever. It's literally causing poor syslogd to chew up more than 1 CPU (and 120 megabytes so far, after 1/2 hour) trying to digest this stuff. So, the question is, how on earth do I stop this useless info from being logged to the system log? Is there some hidden flag I can turn on (please say yes) and/or modify which will stop it? I think what happened is that with the latest (10.5.2) update to Leopard, syslog changes (some new db format or something) is now causing way more CPU usage than normal. So it could well be that Eclipse was spewing out this much info all along and I just never noticed it. I've completely reinstalled Eclipse from the latest download and nothing changed - still get periodic swarms of Eclipse spew. Unfortunately, I'm noticing it now. With this happening all the time, it basically makes battery mode operation an impossibility. Any help? Or pointers? Hopefully, I'm not abusing this list, but as I said I am extremely desperate here... Any help appreciated... Sys info: Mac OS X 10.5.2 Eclipse: Version: 3.3.1.1 Build id: M20071023-1652 sample of log output: Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82 [0x0-0x18018].org.eclipse.eclipse[182]: LIBRARY: /System/Library/Java/ Extensions/CoreAudio.jar Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82 [0x0-0x18018].org.eclipse.eclipse[182]: LIBRARY (original): /System/ Library/Java/Extensions/dns_sd.jar Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82 [0x0-0x18018].org.eclipse.eclipse[182]: LIBRARY: /System/Library/Java/ Extensions/dns_sd.jar Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82 [0x0-0x18018].org.eclipse.eclipse[182]: LIBRARY (original): /System/ Library/Java/Extensions/j3daudio.jar Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82 [0x0-0x18018].org.eclipse.eclipse[182]: LIBRARY: /System/Library/Java/ Extensions/j3daudio.jar Feb 19 15:33:06 dhcp-2op9-2op10-west-130-35-99-82
RE: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide
Still having the same issue. I removed everything and started over from the beginning. anything further I can look at to diagnose the problem? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pascal Rapicault Sent: Thursday, February 21, 2008 3:53 PM To: Equinox development mailing list Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED] Subject: Re: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide I have released a change to the launch configuration that should fix the problem. Please try after having synchronized with CVS the org.eclipse.equinox.p2.ui.admin.rcp | | From: | | --| |Jeff Hamm [EMAIL PROTECTED] | --| | | To:| | --| |equinox-dev@eclipse.org equinox-dev@eclipse.org | --| | | Date: | | --| |02/21/2008 12:57 PM | --| | | Subject: | | --| |[equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide | --| All -- I have been trying to work through the Getting Started for Developers Guide( http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers%20) and I'm having a problem running the director app part of the setup. I have downloaded the src code for p2 and built the project based on the steps listed in the guide. I have successfully run the Metadata Generator SDK and had it do its work against a 3.3 eclipse instance that I had previously installed. When running the director app in the next step of the guide, I get the following exception. osgi !SESSION 2008-02-21 12:35:51.494 --- eclipse.buildId=unknown java.version=1.5.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -application org.eclipse.equinox.p2.director.app.application -metadataRepository file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo Command-line arguments: -dev file:C:/jehamm/dev/open_source/.metadata/.plugins/org.eclipse.pde.core/director app/dev.properties -console -consolelog -application org.eclipse.equinox.p2.director.app.application -metadataRepository file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo !ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:72) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:362) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at
Re: [equinox-dev] [prov] manifest changes
I have reverted this change and also gone through the p2 bundles to ensure that the EEs are set correctly. There is currently a problem in the way that we compute the classpath w.r.t. EEs so we need to leave the higher EEs first in the manifest for now. For reference, the bug is described here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=219979 Also it is important to note that when you change the EE in the bundle manifest editor, you must also update the classpath for the project using the link below the EE section. If you don't, then you will have an EE listed first in the manifest (e.g. Foundation 1.1) but PDE will be using a different one to compile the project in your workspace (e.g. 1.4) and when a new VM (e.g. Foundation 1.1) is added to the builder, then the build will fail because you may be referencing methods not found in those libraries. I have updated the p2 bundles to have matching manifests and classpath files. Thanks. [EMAIL PROTECTED] wrote on 02/21/2008 03:47:04 PM: I have released a change to the manifest file for the org.eclipse.equinox.p2.artifact.repository project so Kim can test the Foundation EE in the build. If you have this project (and this change) loaded into your workspace and a Foundation 1.1 VM set up, it will also require that you have a project like Xerces also in your workspace. Xerces is already in the project set file so you should be good, but I just wanted to give you a heads up in case you see strange errors about not finding XML classes. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] DS invocation order of bind and activate (timing issue???)
The optional reference from A1 to B1 creates a cycle. The DS
implementation should be able to handle this since the reference is
optional it should be able to break the cycle and I assume provide a
consistent activation order of A1 and B1.
I recommend opening a bug against Equinox-Bundles to track the issue. It
would really help if you could provide a testcase to reproduce.
Tom
From: Foerster, Stefan [EMAIL PROTECTED]
To: equinox-dev@eclipse.org
Date: 02/22/2008 10:52 AM
Subject:[equinox-dev] DS invocation order of bind and activate (timing
issue???)
Hello,
I'm having three bundles providing three services using the declarative
service (version 1.0.0.v20080218):
bundle A:
component name=A1 immediate=true
implementation class=A1/
service
provide interface=IA/
/service
property name=service.pid value=A1/
property name=service.ranking value=1000/
reference name=b interface=IB bind=setB unbind=unsetB
cardinality=0..n policy=dynamic/
reference name=c interface=IC bind=setC unbind=unsetC
cardinality=0..1 policy=dynamic/
reference name=d interface=ID bind=setD unbind=unsetD
cardinality=1..1/
reference name=e interface=IE bind=setE unbind=unsetE
cardinality=0..n policy=dynamic/
/component
bundle B:
component name=B1
implementation class=B1/
service
provide interface=IB/
/service
property name=service.pid value=B1/
property name=service.ranking value=1000/
reference name=a interface=IA bind=setA unbind=unsetA
cardinality=1..1/
reference name=d interface=ID bind=setD unbind=unsetD
cardinality=1..1/
/component
bundle D:
component name=D1
implementation class=D1/
service
provide interface=ID/
/service
property name=service.pid value=D1/
property name=service.ranking value=1000/
reference name=logger interface=org.osgi.service.log.LogService
bind=setLog unbind=unsetLog cardinality=0..1 policy=dynamic/
/component
Reading the OSGi DS spec I assume the only valid method invocation order
(if the methods exists and are accessible) is:
1) D1.activate() - some instanceD
2) A1.setD(instanceD)
3) A1.activate() - some instanceA
4) B1.setA(instanceA) and B1.setD(instanceD) in any order
5) B1.activate() - some instanceB
6) A1.setB(instanceB)
Sometimes, it happens that B1 is activated before!!! A1. and I get the
following
order of calls from the OSGi log (calls to setD() are not logged!):
==
1: Debug [51] D1: activate() [EMAIL PROTECTED]:file:../../build/d1.jar/
2: Info [51] ServiceEvent REGISTERED {service.id=29}
3: Info [54] ServiceEvent REGISTERED {service.id=30}
4: Info [37] ServiceEvent REGISTERED {service.id=31}
5: Info [52] ServiceEvent REGISTERED {service.id=32}
6: Info [53] ServiceEvent REGISTERED {service.id=33}
7: Warn [4] ComponentReference.bind(): bind method setE is not accessible!
[EMAIL PROTECTED]:file:org.eclipse.equinox.ds_1.0.0.v20080218.jar/
8: Warn [4] ComponentReference.bind(): bind method setB is not accessible!
[EMAIL PROTECTED]:file:org.eclipse.equinox.ds_1.0.0.v20080218.jar/
9: Debug [51] B1: activate() [EMAIL PROTECTED]:file:../../build/d1.jar/
10:Debug [51] A1: setB() [EMAIL PROTECTED]:file:../../build/d1.jar/
11:Debug [51] A1: setB() A1 not yet activated!!! [EMAIL PROTECTED]:
file:../../build/d1.jar/
12:Debug [51] A1: activate() [EMAIL PROTECTED]:file:../../build/d1.jar/
13:Debug [51] E1: activate() [EMAIL PROTECTED]:file:../../build/d1.jar/
14:Debug [51] A1: setE() [EMAIL PROTECTED]:file:../../build/d1.jar/
15:Debug [51] B2: activate() [EMAIL PROTECTED]:file:../../build/d1.jar/
16:Debug [51] A1: setB() [EMAIL PROTECTED]:file:../../build/d1.jar/
17:Warn [4] ComponentReference.bind(): service reference already bound:
{IB}={service.ranking=1000, service.pid=B1, component.name=B1,
component.id=4, service.id=33} [EMAIL PROTECTED]:
[equinox-dev] Equinox-Framework tagged for next I-Build
I tagged Equinox-Framework for the next I-Build (today?). It will be good to get extra testing on bug 199103. The map file has been updated for the following Bug changes: + Bug 67220. Location.setUrl needs more error information (FIXED) + Bug 217503. DefaultAuthorizationEngine should allow policy to be set (FIXED) + Bug 218001. Using internal FrameworkSecurityManager should be easier (FIXED) + Bug 219512. CachedManifest should should cache Bundle-ManifestVersion and Bundle-ActivationPolicy (FIXED) + Bug 21. SignedContent missing a since tag (FIXED) + Bug 199103. ServiceRegistrationImpl has improper synchronization The following projects have changed: org.eclipse.osgi.tests org.eclipse.osgi Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
RE: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide
Hi Jeff, I just updated the director.app launch config and retested. Could you resynch to HEAD and try again. -Simon [EMAIL PROTECTED] wrote on 02/22/2008 11:13:04 AM: Still having the same issue. I removed everything and started over from the beginning. anything further I can look at to diagnose the problem? -Original Message- From: [EMAIL PROTECTED] [mailto:equinox-dev- [EMAIL PROTECTED] On Behalf Of Pascal Rapicault Sent: Thursday, February 21, 2008 3:53 PM To: Equinox development mailing list Cc: equinox-dev@eclipse.org; [EMAIL PROTECTED] Subject: Re: [equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide I have released a change to the launch configuration that should fix the problem. Please try after having synchronized with CVS the org.eclipse.equinox.p2.ui.admin.rcp | | From: | | -- | |Jeff Hamm [EMAIL PROTECTED] | -- | | | To:| | -- | |equinox-dev@eclipse.org equinox-dev@eclipse.org | -- | | | Date: | | -- | |02/21/2008 12:57 PM | -- | | | Subject: | | -- | |[equinox-dev] Equinox p2 -Problem running director app from the Getting Started for Developers Guide | -- | All -- I have been trying to work through the Getting Started for Developers Guide( http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers%20) and I'm having a problem running the director app part of the setup. I have downloaded the src code for p2 and built the project based on the steps listed in the guide. I have successfully run the Metadata Generator SDK and had it do its work against a 3.3 eclipse instance that I had previously installed. When running the director app in the next step of the guide, I get the following exception. osgi !SESSION 2008-02-21 12:35:51.494 --- eclipse.buildId=unknown java.version=1.5.0_12 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -application org.eclipse.equinox.p2.director.app.application -metadataRepository file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo Command-line arguments: -dev file:C:/jehamm/dev/open_source/.metadata/.plugins/org.eclipse.pde. core/director app/dev.properties -console -consolelog -application org.eclipse.equinox.p2.director.app.application -metadataRepository file:C:\equinox.p2\servers\ -artifactRepository file:C:\equinox.p2\servers\ -installIU sdk -destination C:\equinox.p2\eclipseApp\ -flavor tooling -profile foo !ENTRY org.eclipse.osgi 4 0 2008-02-21 12:35:52.212 !MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher. start(EclipseAppLauncher.java:72) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:362) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:564) at
