Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » RAP 2.1 War is not working(RAP 2.1 war is not working)
RAP 2.1 War is not working [message #1107628] Thu, 12 September 2013 18:02 Go to next message
Nagaraju Nadendla is currently offline Nagaraju Nadendla
Messages: 5
Registered: September 2013
Junior Member
HI,

I am using RAP 2.1 in my project. I am build my war using maven (pom.xml). I can able to create .war. If I deploy that war in my Jboss 7 I cannot access my application using URL : localhost:8788\mywar\servletpath

I followed bellow link to create war
//eclipse.org/rap/noteworthy/2.0/migration-guide/

and another thing is I am using IApplicaiton as entrypoint for my applicaiton.

Please let me know what wrong I am doing.

my web.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app id="WebApp">
<servlet id="bridge">
<servlet-name>equinoxbridgeservlet</servlet-name>
<display-name>Equinox Bridge Servlet</display-name>
<description>Equinox Bridge Servlet</description>
<servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet</servlet-class>

<!-- Framework Controls could be useful for testing purpose, but
we disable it per default -->
<init-param>
<param-name>enableFrameworkControls</param-name>
<param-value>false</param-value>
</init-param>

<!-- Enable multi-language support for the extension registry -->
<!-- the OSGi console is useful for trouble shooting but will fill up your
appserver log quickly, so deactivate on production use. Uncomment
the -console parameter to enabled OSGi console access. -->
<init-param>
<param-name>commandline</param-name>
<param-value>-registryMultiLanguage <!-- -console --> -ws rap</param-value>
</init-param>

<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>equinoxbridgeservlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>

</web-app>


Re: RAP 2.1 War is not working [message #1107660 is a reply to message #1107628] Thu, 12 September 2013 19:04 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan Furnadjiev
Messages: 1821
Registered: July 2009
Senior Member
Hi,
please enable the OSGi console and post the output form "ss" command.
This [1] article could be useful too.

[1] http://wiki.eclipse.org/RAP/FAQ#Exported_WAR_file_does_not_work
Best,
Ivan

On 9/12/2013 9:19 PM, Nagaraju Nadendla wrote:
> HI,
>
> I am using RAP 2.1 in my project. I am build my war using maven
> (pom.xml). I can able to create .war. If I deploy that war in my Jboss
> 7 I cannot access my application using URL :
> localhost:8788\mywar\servletpath
>
> I followed bellow link to create war
> //eclipse.org/rap/noteworthy/2.0/migration-guide/
>
> and another thing is I am using IApplicaiton as entrypoint for my
> applicaiton.
>
> Please let me know what wrong I am doing.
> my web.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
> Application 2.2//EN" "://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
> <web-app id="WebApp">
> <servlet id="bridge"> <servlet-name>equinoxbridgeservlet</servlet-name>
> <display-name>Equinox Bridge Servlet</display-name>
> <description>Equinox Bridge Servlet</description>
> <servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet</servlet-class>
>
> <!-- Framework Controls could be useful for testing purpose, but
> we disable it per default -->
> <init-param>
> <param-name>enableFrameworkControls</param-name>
> <param-value>false</param-value> </init-param>
> <!-- Enable multi-language support for the extension registry -->
> <!-- the OSGi console is useful for trouble shooting but will fill
> up your appserver log quickly, so deactivate on production
> use. Uncomment
> the -console parameter to enabled OSGi console access. -->
> <init-param>
> <param-name>commandline</param-name>
> <param-value>-registryMultiLanguage <!-- -console --> -ws
> rap</param-value> </init-param>
>
> <load-on-startup>1</load-on-startup> </servlet>
>
> <servlet-mapping>
> <servlet-name>equinoxbridgeservlet</servlet-name>
> <url-pattern>/*</url-pattern>
> </servlet-mapping>
>
> </web-app>
>
>
>

--
Ivan Furnadjiev

Twitter: @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 #1125499 is a reply to message #1107660] Fri, 04 October 2013 15:29 Go to previous messageGo to next message
Nagaraju Nadendla is currently offline Nagaraju Nadendla
Messages: 5
Registered: September 2013
Junior Member
I tried all the ways but still it is not working. Please find my log bellow.

It is working fine through eclipse. I mean if I run through eclipse it is working but if I make a war and deploy in Jboss then I am getting 404 error. I never able to reach my path.


!SESSION 2013-10-04 11:26:33.047 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_45
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -dev file:C:/Users/NNadendla/keplerWorkspace/.metadata/.plugins/org.eclipse.pde.core/mdm-portal/dev.properties -os win32 -ws win32 -arch x86_64 -console -consolelog -data C:\Users\NNadendla\keplerWorkspace/.metadata/.plugins/org.eclipse.rap.tools.launch/mdm-portal

!ENTRY org.eclipse.emf.common 4 0 2013-10-04 11:26:34.211
!MESSAGE FrameworkEvent ERROR
!STACK 0
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
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.eclipse.emf.ecore.xmi 4 0 2013-10-04 11:26:34.263
!MESSAGE FrameworkEvent ERROR
!STACK 0
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
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.eclipse.emf.ecore 4 0 2013-10-04 11:26:34.270
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: The bundle "org.eclipse.emf.ecore_2.9.0.v20130528-0742 [38]" could not be resolved. Reason: Another singleton version selected: org.eclipse.emf.ecore_2.9.1.v20130827-0309, Another singleton version selected: org.eclipse.emf.ecore_2.9.1.v20130827-0309
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
2013-10-04 11:26:34.360:INFO:oejs.Server:jetty-8.1.10.v20130312
osgi> 2013-10-04 11:26:35.718:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:61659

!ENTRY org.eclipse.osgi 4 0 2013-10-04 11:26:35.839
!MESSAGE Bundle initial@reference:file:../../libs/emf-runtime-2.9.0/eclipse/plugins/org.eclipse.emf.ecore.xmi_2.9.0.v20130528-0742.jar was not resolved.

!ENTRY org.eclipse.osgi 4 0 2013-10-04 11:26:35.853
!MESSAGE Bundle initial@reference:file:../../libs/emf-runtime-2.9.0/eclipse/plugins/org.eclipse.emf.ecore_2.9.0.v20130528-0742.jar was not resolved.

!ENTRY org.eclipse.osgi 4 0 2013-10-04 11:26:35.854
!MESSAGE Bundle initial@reference:file:../../libs/emf-runtime-2.9.0/eclipse/plugins/org.eclipse.emf.common_2.9.0.v20130528-0742.jar was not resolved.

!ENTRY org.eclipse.osgi 2 0 2013-10-04 11:26:35.886
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2013-10-04 11:26:35.886
!MESSAGE Bundle org.eclipse.emf.common_2.9.0.v20130528-0742 [21] was not resolved.
!SUBENTRY 2 org.eclipse.emf.common 2 0 2013-10-04 11:26:35.887
!MESSAGE Another singleton version selected: org.eclipse.emf.common_2.9.1.v20130827-0309
!SUBENTRY 2 org.eclipse.emf.common 2 0 2013-10-04 11:26:35.887
!MESSAGE Another singleton version selected: org.eclipse.emf.common_2.9.1.v20130827-0309
!SUBENTRY 1 org.eclipse.osgi 2 0 2013-10-04 11:26:35.887
!MESSAGE Bundle org.eclipse.emf.ecore.xmi_2.9.0.v20130528-0742 [32] was not resolved.
!SUBENTRY 2 org.eclipse.emf.ecore.xmi 2 0 2013-10-04 11:26:35.888
!MESSAGE Another singleton version selected: org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309
!SUBENTRY 2 org.eclipse.emf.ecore.xmi 2 0 2013-10-04 11:26:35.888
!MESSAGE Another singleton version selected: org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309
!SUBENTRY 1 org.eclipse.osgi 2 0 2013-10-04 11:26:35.888
!MESSAGE Bundle org.eclipse.emf.ecore_2.9.0.v20130528-0742 [38] was not resolved.
!SUBENTRY 2 org.eclipse.emf.ecore 2 0 2013-10-04 11:26:35.889
!MESSAGE Another singleton version selected: org.eclipse.emf.ecore_2.9.1.v20130827-0309
!SUBENTRY 2 org.eclipse.emf.ecore 2 0 2013-10-04 11:26:35.889
!MESSAGE Another singleton version selected: org.eclipse.emf.ecore_2.9.1.v20130827-0309
ss
"Framework is launched."


id State Bundle
0 ACTIVE org.eclipse.osgi_3.9.0.v20130529-1710
1 ACTIVE org.eclipse.core.databinding.beans_1.2.200.v20130515-1857
2 ACTIVE org.eclipse.rap.rwt.supplemental.fileupload_2.0.0.20130226-1002
3 ACTIVE org.eclipse.equinox.registry_3.5.300.v20130327-1442
4 ACTIVE org.eclipse.core.runtime_3.9.0.v20130326-1255
5 ACTIVE org.eclipse.core.databinding.property_1.4.200.v20130515-1857
6 ACTIVE org.eclipse.jetty.util_8.1.10.v20130312
7 ACTIVE org.eclipse.jetty.servlet_8.1.10.v20130312
8 ACTIVE org.apache.felix.gogo.command_0.10.0.v201209301215
10 ACTIVE com.ibm.icu_50.1.1.v201304230130
11 ACTIVE org.eclipse.rap.jface.databinding_2.1.0.20130506-1748
12 ACTIVE org.eclipse.core.resources_3.8.100.v20130521-2026
13 ACTIVE org.eclipse.core.expressions_3.4.500.v20130515-1343
14 ACTIVE org.eclipse.core.commands_3.6.100.v20130515-1857
15 ACTIVE org.eclipse.jetty.security_8.1.10.v20130312
16 ACTIVE org.eclipse.rap.rwt.osgi_2.1.0.20130506-1748
17 ACTIVE org.eclipse.rap.ui.workbench_2.1.0.20130506-1748
18 ACTIVE org.eclipse.jetty.http_8.1.10.v20130312
19 ACTIVE org.eclipse.help_3.6.0.v20130326-1254
20 ACTIVE org.eclipse.equinox.app_1.3.100.v20130327-1442
21 INSTALLED org.eclipse.emf.common_2.9.0.v20130528-0742
22 ACTIVE org.eclipse.birt.chart.engine.extension_4.3.0.v201306041519
23 ACTIVE org.apache.commons.io_2.0.1.v201105210651
24 ACTIVE org.eclipse.osgi.util_3.2.300.v20130513-1956
25 ACTIVE org.apache.commons.codec_1.4.0.v201209201156
26 ACTIVE org.eclipse.equinox.console_1.0.100.v20130429-0953
27 ACTIVE org.eclipse.equinox.event_1.3.0.v20130327-1442
28 ACTIVE org.eclipse.jetty.io_8.1.10.v20130312
29 ACTIVE org.eclipse.rap.rwt.supplemental.filedialog_2.0.0.20130302-1418
30 ACTIVE org.eclipse.birt.core_4.3.0.v201306041519
31 ACTIVE org.eclipse.jetty.continuation_8.1.10.v20130312
32 INSTALLED org.eclipse.emf.ecore.xmi_2.9.0.v20130528-0742
33 ACTIVE org.apache.commons.logging_1.1.1.v201101211721
34 ACTIVE org.eclipse.jetty.server_8.1.10.v20130312
35 ACTIVE org.eclipse.rap.ui_2.1.0.20130604-1251
36 ACTIVE org.eclipse.rap.jface_2.1.0.20130506-1748
37 ACTIVE org.eclipse.core.databinding_1.4.1.v20130515-1857
38 INSTALLED org.eclipse.emf.ecore_2.9.0.v20130528-0742
39 ACTIVE org.mozilla.javascript_1.7.2.v201005080400
40 ACTIVE org.eclipse.equinox.preferences_3.5.100.v20130422-1538
41 ACTIVE org.eclipse.equinox.http.registry_1.1.300.v20130402-1529
42 ACTIVE org.eclipse.core.jobs_3.5.300.v20130429-1813
43 ACTIVE org.eclipse.equinox.http.servlet_1.1.400.v20130418-1354
44 ACTIVE org.eclipse.equinox.common_3.6.200.v20130402-1505
45 ACTIVE org.eclipse.rap.rwt_2.1.0.20130611-2139
46 ACTIVE org.eclipse.birt.chart.engine_4.3.0.v201306041519
47 ACTIVE javax.servlet_3.0.0.v201112011016
48 ACTIVE org.eclipse.core.contenttype_3.4.200.v20130326-1255
49 ACTIVE org.eclipse.osgi.services_3.3.100.v20130513-1956
50 ACTIVE org.eclipse.birt.chart.device.extension_4.3.0.v201306041519
51 ACTIVE org.apache.felix.gogo.runtime_0.10.0.v201209301036
52 ACTIVE org.eclipse.core.databinding.observable_1.4.1.v20130515-1857
53 ACTIVE org.apache.commons.fileupload_1.2.2.v20111214-1400
54 ACTIVE org.eclipse.equinox.http.jetty_3.0.100.v20130327-1442
55 ACTIVE org.apache.felix.gogo.shell_0.10.0.v201212101605
56 ACTIVE org.eclipse.core.filesystem_1.4.0.v20130514-1240
171 ACTIVE org.eclipse.emf.ecore_2.9.1.v20130827-0309
172 ACTIVE org.eclipse.emf.common_2.9.1.v20130827-0309
173 ACTIVE org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309
177 ACTIVE mdm-portal_0.0.1.qualifier
osgi>

Re: RAP 2.1 War is not working [message #1125507 is a reply to message #1125499] Fri, 04 October 2013 15:37 Go to previous messageGo to next message
Markus Knauer is currently offline Markus Knauer
Messages: 109
Registered: July 2009
Senior Member

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


--
Markus Knauer

Twitter: @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 #1125594 is a reply to message #1125507] Fri, 04 October 2013 17:34 Go to previous messageGo to next message
Nagaraju Nadendla is currently offline Nagaraju Nadendla
Messages: 5
Registered: September 2013
Junior Member
Thanks for you quick reply. apprisheted that. I removed those duplicate entry's. Still I am facing same issues accessing my URL and getting same error Ex: HTTP Status 404 - ProxyServlet: /warfilename/path. my out put for osgi as bellow. Am I doing any wrong..? thanks in advance.

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
ss
"Framework is launched."


id State Bundle
0 ACTIVE org.eclipse.osgi_3.9.0.v20130529-1710
2 ACTIVE org.eclipse.rap.rwt.supplemental.fileupload_2.0.0.20130226-1002
10 ACTIVE com.ibm.icu_50.1.1.v201304230130
11 ACTIVE org.eclipse.rap.jface.databinding_2.1.0.20130506-1748
12 ACTIVE org.eclipse.core.resources_3.8.100.v20130521-2026
16 ACTIVE org.eclipse.rap.rwt.osgi_2.1.0.20130506-1748
17 ACTIVE org.eclipse.rap.ui.workbench_2.1.0.20130506-1748
22 ACTIVE org.eclipse.birt.chart.engine.extension_4.3.0.v201306041519
23 ACTIVE org.apache.commons.io_2.0.1.v201105210651
24 ACTIVE org.eclipse.osgi.util_3.2.300.v20130513-1956
25 ACTIVE org.apache.commons.codec_1.4.0.v201209201156
27 ACTIVE org.eclipse.equinox.event_1.3.0.v20130327-1442
29 ACTIVE org.eclipse.rap.rwt.supplemental.filedialog_2.0.0.20130302-1418
30 ACTIVE org.eclipse.birt.core_4.3.0.v201306041519
33 ACTIVE org.apache.commons.logging_1.1.1.v201101211721
35 ACTIVE org.eclipse.rap.ui_2.1.0.20130604-1251
36 ACTIVE org.eclipse.rap.jface_2.1.0.20130506-1748
39 ACTIVE org.mozilla.javascript_1.7.2.v201005080400
45 ACTIVE org.eclipse.rap.rwt_2.1.0.20130611-2139
46 ACTIVE org.eclipse.birt.chart.engine_4.3.0.v201306041519
50 ACTIVE org.eclipse.birt.chart.device.extension_4.3.0.v201306041519
53 ACTIVE org.apache.commons.fileupload_1.2.2.v20111214-1400
56 ACTIVE org.eclipse.core.filesystem_1.4.0.v20130514-1240
171 ACTIVE org.eclipse.emf.ecore_2.9.1.v20130827-0309
172 ACTIVE org.eclipse.emf.common_2.9.1.v20130827-0309
173 ACTIVE org.eclipse.emf.ecore.xmi_2.9.1.v20130827-0309
178 ACTIVE org.apache.felix.gogo.runtime_0.10.0.v201209301036
179 ACTIVE org.eclipse.core.databinding.observable_1.4.1.v20130515-1857
180 ACTIVE org.eclipse.help_3.6.0.v20130326-1254
181 ACTIVE org.apache.felix.gogo.shell_0.10.0.v201212101605
182 ACTIVE org.eclipse.core.expressions_3.4.500.v20130515-1343
183 ACTIVE org.eclipse.core.contenttype_3.4.200.v20130326-1255
184 ACTIVE org.eclipse.jetty.util_8.1.10.v20130312
185 ACTIVE org.eclipse.jetty.security_8.1.10.v20130312
186 ACTIVE javax.servlet_3.0.0.v201112011016
187 ACTIVE org.eclipse.jetty.io_8.1.10.v20130312
188 ACTIVE org.apache.felix.gogo.command_0.10.0.v201209301215
189 ACTIVE org.eclipse.equinox.http.servlet_1.1.400.v20130418-1354
190 ACTIVE org.eclipse.jetty.servlet_8.1.10.v20130312
191 ACTIVE org.eclipse.jetty.server_8.1.10.v20130312
192 ACTIVE org.eclipse.core.commands_3.6.100.v20130515-1857
193 ACTIVE org.eclipse.jetty.http_8.1.10.v20130312
194 ACTIVE org.eclipse.core.databinding.property_1.4.200.v20130515-1857
195 ACTIVE org.eclipse.equinox.http.jetty_3.0.100.v20130327-1442
196 ACTIVE org.eclipse.osgi.services_3.3.100.v20130513-1956
197 ACTIVE org.eclipse.core.jobs_3.5.300.v20130429-1813
198 ACTIVE org.eclipse.core.databinding_1.4.1.v20130515-1857
199 ACTIVE org.eclipse.equinox.http.registry_1.1.300.v20130402-1529
200 ACTIVE org.eclipse.core.databinding.beans_1.2.200.v20130515-1857
201 ACTIVE org.eclipse.equinox.common_3.6.200.v20130402-1505
202 ACTIVE org.eclipse.equinox.preferences_3.5.100.v20130422-1538
203 ACTIVE org.eclipse.core.runtime_3.9.0.v20130326-1255
204 ACTIVE org.eclipse.equinox.console_1.0.100.v20130429-0953
205 ACTIVE org.eclipse.equinox.app_1.3.100.v20130327-1442
206 ACTIVE org.eclipse.jetty.continuation_8.1.10.v20130312
207 ACTIVE org.eclipse.equinox.registry_3.5.300.v20130327-1442
209 ACTIVE mdm-portal_0.0.1.qualifier
osgi>
Re: RAP 2.1 War is not working [message #1125602 is a reply to message #1125594] Fri, 04 October 2013 17:43 Go to previous messageGo to next message
Nagaraju Nadendla is currently offline Nagaraju Nadendla
Messages: 5
Registered: September 2013
Junior Member
my RAP 2.1 branding changes are as bellow.


<extension point="org.eclipse.rap.ui.entrypoint">
<entrypoint
applicationId="myapplication.application"
brandingId="myapplication.branding"
id="myapplication.application.entrypoint"
path="/myapplication.application"/>
</extension>
<!-- RAP 2.0 Migration changes start-->
<extension
id="myapplication.application"
point="org.eclipse.core.runtime.applications">
<application thread="main" cardinality="singleton-global" visible="true">
<run
class="com.mypackage.controller.Application">
</run>
</application>
Re: RAP 2.1 War is not working [message #1126201 is a reply to message #1125602] Sat, 05 October 2013 09:06 Go to previous messageGo to next message
Markus Knauer is currently offline Markus Knauer
Messages: 109
Registered: July 2009
Senior Member

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


--
Markus Knauer

Twitter: @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

Re: RAP 2.1 War is not working [message #1128700 is a reply to message #1126201] Mon, 07 October 2013 23:51 Go to previous messageGo to next message
Nagaraju Nadendla is currently offline Nagaraju Nadendla
Messages: 5
Registered: September 2013
Junior Member
thanks for your replay. How to add org.eclipse.equinox.servletbridge.extensionbundle

bundle. I added this one in my runtime classpath configuration in my MANIFEST.MF. I am not able to add in to required plugin-ins.

RAP 1.5 was working fine with my existing setup. After I done Migration into RAP 2.1 I am not able to access my url as i explained early. I feel it is RAP issue.
Re: RAP 2.1 War is not working [message #1130216 is a reply to message #1128700] Wed, 09 October 2013 10:20 Go to previous message
Ivan Furnadjiev is currently offline Ivan Furnadjiev
Messages: 1821
Registered: July 2009
Senior Member
Hi,
could you provide a non working simple war for debugging?
Best,
Ivan

On 10/8/2013 2:51 AM, Nagaraju Nadendla wrote:
> thanks for your replay. How to add
> org.eclipse.equinox.servletbridge.extensionbundle
>
> bundle. I added this one in my runtime classpath configuration in my
> MANIFEST.MF. I am not able to add in to required plugin-ins.
> RAP 1.5 was working fine with my existing setup. After I done
> Migration into RAP 2.1 I am not able to access my url as i explained
> early. I feel it is RAP issue.

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Previous Topic:Change background-color of systemmessage-dialog
Next Topic:How to change themes per-user?
Goto Forum:
  


Current Time: Wed Oct 01 10:29:44 GMT 2014

Powered by FUDForum. Page generated in 0.01991 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software