Eclipse Community Forums: Equinox » Problems when exporting a product.

Help

Home

Home » Eclipse Projects » Equinox » Problems when exporting a product.

Show: Today's Messages :: Show Polls :: Message Navigator

Problems when exporting a product. [message #521115]

Tue, 16 March 2010 13:54

SMaton

Messages: 6
Registered: March 2010

Junior Member

Hello everyone,

hopefully this is the right forum Smile

I'm currently developing an application using the eclipse framework and osgi. I've created a .product file for my application containing the configuration and dependencies.

During the entire development cycle I used the "Launch an Ecplipse application" and "Launch an Ecplipse application in Debug mode" buttons which are available on the top right corner of the page that opens when you open the .product file. The application always worked as a charm. I didn't encounter any problems and clicking onto the "Validate..." button doesn't show any problem.

The problem arises when I want to launch an exported application. In fact, I just click onto "Export an Eclipse product" and keep the settings "as is". The application is generated and I can find it in the folder as expected.

When I start the application, it doesn't work as expected. Examining the started bundles via the console reveals that some bundles aren't started. Among those is org.springframework.osgi.extender.

Here's a complete list of all bundles and their state just after starting the application:

osgi> ss

Framework is launched.

id State Bundle
0 ACTIVE org.eclipse.osgi_3.5.2.R35x_v20100126
Fragments=1, 2
1 RESOLVED org.eclipse.equinox.weaving.hook_1.0.0.200905031323
Master=0
2 RESOLVED org.eclipse.persistence.jpa.equinox.weaving_1.1.2.v20090612-
r4475
Master=0
3 ACTIVE be.sidema.amplitude.crams.client.core_0.1.0
4 ACTIVE be.sidema.amplitude.crams.client.investors_0.1.0
5 ACTIVE be.sidema.amplitude.crams.client.reports_0.1.0
6 ACTIVE be.sidema.amplitude.crams.client.transactions_0.1.0
7 ACTIVE be.sidema.amplitude.crams.controller_0.1.0
8 RESOLVED be.sidema.amplitude.crams.log4j_1.0.0
Master=30
9 RESOLVED be.sidema.amplitude.crams.model_0.1.0
10 ACTIVE be.sidema.amplitude.crams.model.jpa_0.1.0
11 RESOLVED be.sidema.shared.databinding_1.0.0
12 RESOLVED be.sidema.shared.osgi_1.0.0
13 ACTIVE com.ibm.icu_4.0.1.v20090822
14 RESOLVED com.jasperassistant.swtjasperviewer_1.1.2
15 RESOLVED com.publicobject.glazedlists_1.8.0
16 RESOLVED com.springsource.antlr_2.7.7
17 RESOLVED com.springsource.com.lowagie.text_2.0.8
18 RESOLVED com.springsource.com.mchange.v2.c3p0_0.9.1.2
19 RESOLVED com.springsource.com.mysql.jdbc_5.1.6
20 RESOLVED com.springsource.javassist_3.3.0.ga
21 RESOLVED com.springsource.javax.persistence_1.0.0
22 RESOLVED com.springsource.javax.transaction_1.1.0
23 RESOLVED com.springsource.javax.validation_1.0.0.CR3
24 RESOLVED com.springsource.javax.xml.stream_1.0.1
25 RESOLVED com.springsource.net.sf.cglib_2.1.3
26 RESOLVED com.springsource.net.sf.ehcache_1.6.0
27 RESOLVED com.springsource.org.aopalliance_1.0.0
28 RESOLVED com.springsource.org.apache.commons.collections_3.2.1
29 RESOLVED com.springsource.org.apache.commons.logging_1.1.1
30 RESOLVED com.springsource.org.apache.log4j_1.2.15
Fragments=8
31 RESOLVED com.springsource.org.aspectj.runtime_1.6.5.RELEASE
32 ACTIVE com.springsource.org.aspectj.weaver_1.6.5.RELEASE
33 RESOLVED com.springsource.org.dom4j_1.6.1
34 RESOLVED com.springsource.org.hibernate.validator_4.0.0.Beta2
35 RESOLVED com.springsource.org.jgroups_2.5.1
36 RESOLVED com.springsource.org.objectweb.asm_1.5.3
37 RESOLVED com.springsource.org.objectweb.asm.attrs_1.5.3
38 RESOLVED com.springsource.slf4j.api_1.5.6
Fragments=39, 40
39 RESOLVED com.springsource.slf4j.jcl_1.5.6
Master=38
40 RESOLVED com.springsource.slf4j.log4j_1.5.6
Master=38
41 RESOLVED com.springsource.slf4j.org.apache.commons.logging_1.5.6
42 RESOLVED com.springsource.slf4j.org.apache.log4j_1.5.6
43 RESOLVED freechart_1.0.0
44 RESOLVED javax.persistence_1.99.0.v200906021518
45 RESOLVED opencvs_1.0.0
46 RESOLVED org.apache.poi_3.2.0
47 RESOLVED org.eclipse.core.commands_3.5.0.I20090525-2000
48 <<LAZY>> org.eclipse.core.contenttype_3.4.1.R35x_v20090826-0451
49 <<LAZY>> org.eclipse.core.databinding_1.2.0.M20090819-0800
50 RESOLVED org.eclipse.core.databinding.beans_1.2.0.I20090525-2000
51 ACTIVE org.eclipse.core.databinding.observable_1.2.0.M20090902-0800

52 <<LAZY>> org.eclipse.core.databinding.property_1.2.0.M20090819-0800
53 ACTIVE org.eclipse.core.expressions_3.4.101.R35x_v20100209
54 <<LAZY>> org.eclipse.core.filesystem_1.2.0.v20090507
Fragments=55
55 RESOLVED org.eclipse.core.filesystem.win32.x86_1.1.0.v20080604-1400
Master=54
56 ACTIVE org.eclipse.core.jobs_3.4.100.v20090429-1800
57 <<LAZY>> org.eclipse.core.resources_3.5.0.v20090512
Fragments=58
58 RESOLVED org.eclipse.core.resources.win32.x86_3.5.0.v20081020
Master=57
59 ACTIVE org.eclipse.core.runtime_3.5.0.v20090525
60 ACTIVE org.eclipse.equinox.app_1.2.1.R35x_v20091203
61 ACTIVE org.eclipse.equinox.common_3.5.1.R35x_v20090807-1100
62 RESOLVED org.eclipse.equinox.ds_1.1.1.R35x_v20090806
63 RESOLVED org.eclipse.equinox.launcher_1.0.201.R35x_v20090715
Fragments=64
64 RESOLVED org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v200905
19
Master=63
65 ACTIVE org.eclipse.equinox.preferences_3.2.301.R35x_v20091117
66 ACTIVE org.eclipse.equinox.registry_3.4.100.v20090520-1800
67 <<LAZY>> org.eclipse.equinox.simpleconfigurator_1.0.101.R35x_v2009080
7-1100
68 <<LAZY>> org.eclipse.equinox.util_1.0.100.v20090520-1800
69 ACTIVE org.eclipse.equinox.weaving.aspectj_1.0.0.200905031323
70 ACTIVE org.eclipse.equinox.weaving.caching_1.0.0.200905031323
71 ACTIVE org.eclipse.equinox.weaving.caching.j9_1.0.0.200905031323
72 ACTIVE org.eclipse.equinox.weaving.springweaver_0.1.0
73 ACTIVE org.eclipse.help_3.4.1.v20090805_35x
74 <<LAZY>> org.eclipse.jdt.core_3.5.0.v_963
75 ACTIVE org.eclipse.jface_3.5.2.M20100120-0800
76 RESOLVED org.eclipse.jface.databinding_1.3.1.M20090826-0800
77 RESOLVED org.eclipse.nebula.widgets.calendarcombo_1.0.0
78 RESOLVED org.eclipse.osgi.services_3.2.0.v20090520-1800
79 RESOLVED org.eclipse.persistence.antlr_1.1.2.v20090612-r4475
80 RESOLVED org.eclipse.persistence.asm_1.1.2.v20090612-r4475
81 RESOLVED org.eclipse.persistence.core_1.1.2.v20090612-r4475
82 RESOLVED org.eclipse.persistence.jpa_1.1.2.v20090612-r4475
Fragments=83
83 RESOLVED org.eclipse.persistence.jpa.equinox_1.1.2.v20090612-r4475
Master=82
84 <<LAZY>> org.eclipse.rcp_3.5.0.v201002111343
85 RESOLVED org.eclipse.swt_3.5.2.v3557f
Fragments=86
86 RESOLVED org.eclipse.swt.win32.win32.x86_3.5.2.v3557f
Master=85
87 RESOLVED org.eclipse.text_3.5.0.v20090513-2000
88 ACTIVE org.eclipse.ui_3.5.2.M20100120-0800
89 ACTIVE org.eclipse.ui.forms_3.4.0.v20090526
90 ACTIVE org.eclipse.ui.workbench_3.5.2.M20100113-0800
91 <<LAZY>> org.eclipse.update.configurator_3.3.0.v20090312
92 RESOLVED org.jasperforge.jasperreports_3.6.0
93 RESOLVED org.springframework.aop_2.5.6.SEC01
94 RESOLVED org.springframework.beans_2.5.6.SEC01
95 RESOLVED org.springframework.context_2.5.6.SEC01
96 RESOLVED org.springframework.core_2.5.6.SEC01
97 RESOLVED org.springframework.jdbc_2.5.6.SEC01
98 RESOLVED org.springframework.orm_2.5.6.SEC01
99 RESOLVED org.springframework.osgi.core_1.2.0
100 RESOLVED org.springframework.osgi.extender_1.2.0
101 ACTIVE org.springframework.osgi.extensions.annotations_1.2.0
102 RESOLVED org.springframework.osgi.io_1.2.0
103 RESOLVED org.springframework.transaction_2.5.6.SEC01

I then manually tried to start all bundles. The only ones I couldn't start are these:

id State Bundle
1 RESOLVED org.eclipse.equinox.weaving.hook_1.0.0.200905031323
Master=0
2 RESOLVED org.eclipse.persistence.jpa.equinox.weaving_1.1.2.v20090612- r4475
Master=0
8 RESOLVED be.sidema.amplitude.crams.log4j_1.0.0
Master=30
39 RESOLVED com.springsource.slf4j.jcl_1.5.6
Master=38
40 RESOLVED com.springsource.slf4j.log4j_1.5.6
Master=38
55 RESOLVED org.eclipse.core.filesystem.win32.x86_1.1.0.v20080604-1400
Master=54
58 RESOLVED org.eclipse.core.resources.win32.x86_3.5.0.v20081020
Master=57
64 RESOLVED org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v200905
19
Master=63
83 RESOLVED org.eclipse.persistence.jpa.equinox_1.1.2.v20090612-r4475
Master=82
86 RESOLVED org.eclipse.swt.win32.win32.x86_3.5.2.v3557f
Master=85
100 RESOLVED org.springframework.osgi.extender_1.2.0

When trying to start "be.sidema.amplitude.crams.log4j" I get this exception:

org.osgi.framework.BundleException: A fragment bundle cannot be started: be.side
ma.amplitude.crams.log4j_1.0.0 [8]
at org.eclipse.osgi.framework.internal.core.BundleFragment.star tWorker(B
undleFragment.java:228)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(Abstrac
tBundle.java:280)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(Abstrac
tBundle.java:272)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandPro vider._st
art(FrameworkCommandProvider.java:253)
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.osgi.framework.internal.core.FrameworkCommandInt erpreter.
execute(FrameworkCommandInterpreter.java:155)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.do command(F
rameworkConsole.java:303)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.co nsole(Fra
meworkConsole.java:288)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.ru n(Framewo
rkConsole.java:224)
at java.lang.Thread.run(Unknown Source)

"be.sidema.amplitude.crams.log4j" has plug-in dependencies on com.springsource.org.apache.log4j, org.eclipse.equinox.weaving.hook, org.eclipse.osgi and org.eclipse.persistence.jpa.equinox.weaving

Now what hits me is the fact that the application perfectly starts and works when starting from within the eclipse framework. I was under the impression (and tests seem to confirm that) that the configuration I create within the .product pages, is used to actually handle the application.

Why is there a difference between the application as it is handled within Eclipse and after it has been exported? Normally the same bundles are used and they're started in the same way, aren't they?

So... sorry if I sound stressed... I am Smile

Report message to a moderator

Re: Problems when exporting a product. [message #521145 is a reply to message #521115]

Tue, 16 March 2010 14:58

Thomas Watson

Messages: 503
Registered: July 2009

Senior Member

I think the issue is in your custom config.ini. The following is not supported by the runtime

com.springsource.antlr@default:default,

I think the "default" string is something used by PDE to mark what should be filled in when actually running the application. Also I would not expect you to have to set all these bundles in your osgi.bundles property if you are using simpleconfigurator. I assume you are because you have:

org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.e clipse.equinox.simpleconfigurator/bundles.info

When you launch from Eclipse PDE will general a config.ini for you in your workspace at:

<workspace location>/
.metadata/org.eclipse.core.pde/
<launch config name>/configuration/config.ini

Take a look at this config.ini and see how it is different from the config.ini you generate for the product export.

You may also want to try the PDE forum.

Tom.

Report message to a moderator

Re: Problems when exporting a product. [message #521323 is a reply to message #521115]

Wed, 17 March 2010 09:38

SMaton

Messages: 6
Registered: March 2010

Junior Member

Hi there,

I'm back just to tell you that the issue has been solved. In fact, I had to do 3 changes to make the application work after exporting (thanks to Marcus who helped me out here):

1. I had to remove the slf4j.jcl bundle. It was creating a stack overflow. I suppose it conflicted with other logging facilities.

2. We turned of the metadata repository upon export.

3. Marcus and I found out that the generated application ini actually contained invalid information. The content of the generated ini-file was:
"-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} -console"

As you can see, neither the OS nor any other information held valid entries. As Marcus pointed out, this seems to be a known bug under Mac OSX. That's why he checked the file out and discovered the invalid entries.

After having done both of the above mentioned changes, the application ran fine. Unfortunately, I have to re-do the third changement after any product export.

Thanks for helping,
Stefan

Report message to a moderator

Previous Topic:	automatic update of workspace bundles
Next Topic:	Storing preferences across bundle versions

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 07:59:04 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter