RE: [equinox-dev] DS invocation order of bind and activate(timing issue???)
Not sure if the following is related. Maybe someone more familiar w/
equinox ds/util could comment on this.
1) equinox ds imports packages from util
2) equinox util is NOT lazy started
Q: Is equinox ds dependent upon service provide by equinox util that may
not be yet registered when ds is started before util?
If equinox util was lazy started, than I would assume that the 2nd
startup sequence listed below should have worked.
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Foerster, Stefan
Sent: Monday, February 25, 2008 4:24 AM
To: Equinox development mailing list
Subject: RE: [equinox-dev] DS invocation order of bind and
activate(timing issue???)
I think I've got a test case and test sequence to reproduce the timing
problem.
The problem arises from the start order of the bundles.
if the framework starts the bundles in the following order:
1) org.eclipse.osgi_3.4.0.v20080218
2) org.eclipse.equinox.ds_1.0.0.v20080218
3) org.eclipse.equinox.log_1.1.0.v20071203
4) org.eclipse.equinox.util_1.0.0.v20080218
5) javax.servlet_2.4.0.v200711021030
6) org.eclipse.osgi.services_3.1.200.v20071203
7) a_2.0.0
8) d_2.0.0
everything is OK (see attached running.txt), both services A and D get
activated as expected.
Now, If i stop bundles 2-8 and start them in the following order (bundle
1 was not stopped):
2) javax.servlet_2.4.0.v200711021030
3) org.eclipse.equinox.ds_1.0.0.v20080218
4) org.eclipse.equinox.log_1.1.0.v20071203
5) org.eclipse.osgi.services_3.1.200.v20071203
6) a_2.0.0
7) d_2.0.0
8) org.eclipse.equinox.util_1.0.0.v20080218
I get the timeouts in the SCR (see fail.txt).
I also attached the two bundles I used to debug the problem. The source
code
is located within the OSGI-INF/src.
Based on this observation I think the SCR gets confused and does not
obey the
activation/bind order as I reported before.
-Original Message-
From: [EMAIL PROTECTED] on behalf of BJ Hargrave
Sent: Fri 22.02.2008 20:05
To: Equinox development mailing list
Subject: Re: [equinox-dev] DS invocation order of bind and
activate(timing issue???)
I think you should put this in a bug report against DS.
--
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
office: +1 386 848 1781
mobile: +1 386 848 3788
From:
Foerster, Stefan [EMAIL PROTECTED]
To:
equinox-dev@eclipse.org
Date:
2008-02-22 11:52
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}
RE: [equinox-dev] DS invocation order of bind and activate(timing issue???)
Stefan, Please open a bug against Equinox-Bundles and supply your testcase as an attachment to the bug report. Thanks. Tom From: Foerster, Stefan [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 02/25/2008 07:46 AM Subject:RE: [equinox-dev] DS invocation order of bind and activate(timing issue???) Hi, the timeouts of the SCR are gone if I use the latest build of the ds (org.eclipse.equinox.ds_1.0.0.N20080224-0010.jar) However, the other problem (B1 activated before A1) still exists. I prepared two bundles b1 and b2 (attached to this mail). Using these bundles and having the following start order: 0ACTIVE org.eclipse.osgi_3.4.0.v20080218 2ACTIVE org.eclipse.equinox.log_1.1.0.v20071203 3ACTIVE org.eclipse.equinox.util_1.0.0.v20080218 5ACTIVE javax.servlet_2.4.0.v200711021030 6ACTIVE org.eclipse.osgi.services_3.1.200.v20071203 15 ACTIVE org.eclipse.equinox.ds_1.0.0.N20080224-0010 21 ACTIVE b1_2.0.0 22 ACTIVE b2_2.0.0 23 ACTIVE d_2.0.0 25 ACTIVE a_2.0.0 of the framework. A1 is always used NOT activated! I get the following output (via System.err.println()): osgi DEBUG: D: activate() setD() DEBUG: Activator: activate() DEBUG: B2: startup() A: setB() called while not activated !! setD() DEBUG: Activator: activate() DEBUG: A: begin startup DEBUG: A: finished startup setD() DEBUG: Activator: activate() DEBUG: B1: startup() DEBUG: A: setB() -Original Message- From: [EMAIL PROTECTED] on behalf of O'Flynn, Dennis Sent: Mon 25.02.2008 14:18 To: Equinox development mailing list Subject: RE: [equinox-dev] DS invocation order of bind and activate(timingissue???) Not sure if the following is related. Maybe someone more familiar w/ equinox ds/util could comment on this. 1) equinox ds imports packages from util 2) equinox util is NOT lazy started Q: Is equinox ds dependent upon service provide by equinox util that may not be yet registered when ds is started before util? If equinox util was lazy started, than I would assume that the 2nd startup sequence listed below should have worked. The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Foerster, Stefan Sent: Monday, February 25, 2008 4:24 AM To: Equinox development mailing list Subject: RE: [equinox-dev] DS invocation order of bind and activate(timing issue???) I think I've got a test case and test sequence to reproduce the timing problem. The problem arises from the start order of the bundles. if the framework starts the bundles in the following order: 1) org.eclipse.osgi_3.4.0.v20080218 2) org.eclipse.equinox.ds_1.0.0.v20080218 3) org.eclipse.equinox.log_1.1.0.v20071203 4) org.eclipse.equinox.util_1.0.0.v20080218 5) javax.servlet_2.4.0.v200711021030 6) org.eclipse.osgi.services_3.1.200.v20071203 7) a_2.0.0 8) d_2.0.0 everything is OK (see attached running.txt), both services A and D get activated as expected. Now, If i stop bundles 2-8 and start them in the following order (bundle 1 was not stopped): 2) javax.servlet_2.4.0.v200711021030 3) org.eclipse.equinox.ds_1.0.0.v20080218 4) org.eclipse.equinox.log_1.1.0.v20071203 5) org.eclipse.osgi.services_3.1.200.v20071203 6) a_2.0.0 7) d_2.0.0 8) org.eclipse.equinox.util_1.0.0.v20080218 I get the timeouts in the SCR (see fail.txt). I also attached the two bundles I used to debug the problem. The source code is located within the OSGI-INF/src. Based on this observation I think the SCR gets confused and does not obey the activation/bind order as I reported before. -Original Message- From: [EMAIL PROTECTED] on behalf of BJ Hargrave Sent: Fri 22.02.2008 20:05 To: Equinox development mailing list Subject: Re: [equinox-dev] DS invocation order of bind and activate(timing issue???) I think you should put this in a bug report against DS. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Foerster, Stefan [EMAIL PROTECTED] To: equinox-dev@eclipse.org Date: 2008-02-22 11:52 Subject: [equinox-dev] DS
Re: [equinox-dev] Adding 3rd party jar to Bundle.
A couple of things to check: 1) Does your bundle work when run from your workspace? 2) When you build the bundle can you confirm the lib/TestParser.jar is actually included in your bundle content? 3) Does your bundle manifest file end in an empty line after the Bundle-ClassPath header? If yes to the above questions then I recommend you create a testcase and open a bug for us to investigate. Thanks. Tom From: Srijith Kochunni [EMAIL PROTECTED] To: equinox-dev@eclipse.org Date: 02/25/2008 06:08 AM Subject:[equinox-dev] Adding 3rd party jar to Bundle. Hi All, I am trying to add a 3rd party jar to my bundle. I put it in a lib/ folder and update the manifest file and build properties file as follows. --- MANIFEST.MF Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Xparse Plug-in Bundle-SymbolicName: xparse Bundle-Version: 1.0.0 Import-Package: org.osgi.framework;version=1.4.0, org.osgi.util.xml;version=1.0.0 Bundle-Activator: org.osgi.util.xml.XMLParserActivator Bundle-ClassPath: ., lib/TestParser.jar my build.properties file is as follows source.. = src/ output.. = bin/ bin.includes = META-INF/,\ .,\ lib/ When I start my bundle I keep getting a java.lang.ClassNotFoundException when I refer the class within the jar. However if I were to specify the absolute path of the jar file in Bundle-Classpath I get no error, and the bundle starts properly. I`ve searched for any articles regarding this. I found this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=108781 It contains example code and can`t spot any difference.. Is there something i am missing. ? Or has there been any change regarding this..? Any help would be greatly appreciated.? P.S: Please find attached the entire stack trace. Thanks, Srijith. (See attached file: StackTrace.txt) ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: ecblank.gif StackTrace.txt Description: Binary data ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Sprint releases OSGi based Next Gen Mobile Java Platform
RCP developers, I'd like to inform you that Sprint has made publicly available their Titan platform based on OSGi and Eclipse eRCP. This platform for Windows Mobile devices brings the power of OSGi and Eclipse to mobile phones in a big way. You can run eRCP applications and may even be inclined to port your existing Eclipse apps to eRCP so you can always have them with you. The reference platform for Titan is a Sprint Mogul device, but I think any WM6 Classic or Professional device should do pretty well. Go to http://developer.sprint.com/site/global/develop/technologies/sprint_titan/p_sprint_titan.jsp to download the runtime and tools and learn more about Titan. There will also be a session on this topic at EclipseCon 2008 (with some give-aways I hear). Mark___ 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
Hey Simon -- I updated and resync'd and still have the same issue. I'm beginning to think that it's a problem with the 3.4M5 Eclipse IDE I'm using but that's just a guess. Just to restate, the MetaData Generator SDK is working (as far as I can tell). I get a directory created that looks like this C: equinox.p2 servers features native plugins artifacts.xml content.xml Then running the director app fails with the error as stated below. Anything I can verify on my end? Thanks! Jeff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Kaegi Sent: Friday, February 22, 2008 8:37 PM To: Equinox development mailing list Subject: 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
[equinox-dev] [prov] Repository and bugzilla migration
The p2 code base will be migrating into its new CVS repository location tomorrow morning, around 9am EST. I'll send a message to this list when it is complete. Please stop checking in code into the old CVS location by 8am EST at the latest to make sure your changes are not lost. Since the repository is being copied at the file system level, all branches of the affected projects, and all version history, will be retained. You may want to consider branching if you have work in progress that needs carrying over. The new code location is /cvsroot/eclipse/org.eclipse.equinox/p2/. The p2 bugzilla migration will happen tonight. All open p2 bugs in the Equinox Incubator component will be moved to the new Equinox p2 component. You may want to consider not listening to these inboxes overnight tonight, to avoid the ~300 emails that will occur. Keep in mind if you make changes on bug reports overnight tonight, people might not notice them if they bulk delete the resulting emails. John___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] [prov] Repository and bugzilla migration
The bugzilla migration is now complete. From now on, all p2 related bugs should be open against the Equinox p2 component. Also the [prov] prefix in the bug summary is no longer necessary. PaScaL | | From: | | --| |John Arthorne/Ottawa/[EMAIL PROTECTED] | --| | | To:| | --| |equinox-dev@eclipse.org | --| | | Date: | | --| |02/25/2008 05:57 PM | --| | | Subject: | | --| |[equinox-dev] [prov] Repository and bugzilla migration | --| The p2 code base will be migrating into its new CVS repository location tomorrow morning, around 9am EST. I'll send a message to this list when it is complete. Please stop checking in code into the old CVS location by 8am EST at the latest to make sure your changes are not lost. Since the repository is being copied at the file system level, all branches of the affected projects, and all version history, will be retained. You may want to consider branching if you have work in progress that needs carrying over. The new code location is /cvsroot/eclipse/org.eclipse.equinox/p2/. The p2 bugzilla migration will happen tonight. All open p2 bugs in the Equinox Incubator component will be moved to the new Equinox p2 component. You may want to consider not listening to these inboxes overnight tonight, to avoid the ~300 emails that will occur. Keep in mind if you make changes on bug reports overnight tonight, people might not notice them if they bulk delete the resulting emails. John___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [prov] project tagged EOM/
___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
