|
|
|
| Re: RAP 2.1 War is not working [message #1125507 is a reply to message #1125499] |
Fri, 04 October 2013 15:37   |
|
This doesn't look like a RAP issue to me. Your log contains lines like the following:
Nagaraju Nadendla wrote on Fri, 04 October 2013 17:29
org.osgi.framework.BundleException: The bundle "org.eclipse.emf.common_2.9.0.v20130528-0742 [21]" could not be resolved. Reason: Another singleton version selected: org.eclipse.emf.common_2.9.1.v20130827-0309, Another singleton version selected: org.eclipse.emf.common_2.9.1.v20130827-0309
org.osgi.framework.BundleException: The bundle "org.eclipse.emf.ecore.xmi_2.9.0.v20130528-0742 [32]" could not be resolved. Reason: Another singleton version selected: org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309, Another singleton version selected: org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309
I'd say you have multiple versions of these bundles in your .war file and you are trying to activate all of them, but due to the 'singleton' nature of these specific bundles they cannot be activated and the whole activation process fails.
Regards,
Markus
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
| Re: RAP 2.1 War is not working [message #1126201 is a reply to message #1125602] |
Sat, 05 October 2013 09:06 |
|
In your first message you were writing that you are building a .war and you want to deploy this in your JBoss application server, right?
By looking at your list of bundles, I can see e.g. all Jetty bundles, but no servletbridge bundle at all. I assume that you are ending up running a webserver in a webserver, and that's for sure not what you want. You can see the output of the Jetty server start at port 63003 in the following lines:
Quote:
2013-10-04 13:30:00.653:INFO:oejs.Server:jetty-8.1.10.v20130312
osgi> 2013-10-04 13:30:00.698:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:63003
If you are starting your RAP application from within your IDE, you are starting a Equinox OSGi runtime, and inside the OSGi runtime (a) a Jetty web application server providing the http services and (b) your RAP application. This is a good approach at development time.
In case of a .war deployment it is your web application server that provides the http service (and not Jetty).
[1] in the RAP Developers Guide provides an introduction to war deployments, a troubleshooting guide, and uses the warproduct tooling which could be a better starting point to get something running compared to a Tycho/Maven build. And then there's the RAP FAQ at [2] with some information about this, especially the lines
Quote:
...make sure that there is a org.eclipse.equinox.servletbridge.extensionbundle in the ss-listing whose state is RESOVLED
Make sure that the WAR does not contain the javax.servlet bundle because it is provided by the hosting servlet container.
should be helpful.
[1] http://eclipse.org/rap/developers-guide/devguide.php?topic=deployment.html&version=2.1
[2] http://wiki.eclipse.org/RAP/FAQ#Exported_WAR_file_does_not_work
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
[Updated on: Sat, 05 October 2013 09:07] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.04713 seconds
] 
Search
Help
Register
Login
Home
