Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » RAP export as WAR using Tooling(Problems with ServletBridge ExtensionBundle WAR exports)
RAP export as WAR using Tooling [message #1027121] Tue, 26 March 2013 15:22 Go to next message
John Gymer is currently offline John GymerFriend
Messages: 198
Registered: November 2012
Location: UK
Senior Member
Hi all (Ralf?),

I've hit some problems this week trying to use the Libra WAR Tooling to export existing RAP projects as WARs for deploy to appservers.

This process was working ok a few weeks ago, and I haven't done an export for a while, but now (after updating various components including nightly RAP build), I can no longer used the exported WAR file.

In the WAR configuration panel, I now get a problem on org.eclipse.equinox.servletbridget.extensionbundle, although it isn't clear what the problem is. Something is not getting resolved somewhere along the lines.

I can continue to export the WAR, but the bundles refused to go beyond "INSTALLED" state as they are missing constraints. The one that seems to be causing the problems is this one:
"...Missing Constraint: Import-Package: javax.servley; version=[2.3.0,4.0.0)"

I see from various posts that there has been some discussion, and wonder what the state of play is?

link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348045
and link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398780

Thanks, John

p.s. I'm away not for a couple of weeks, but any info and progress greatly appreciated as I can no longer deploy my applications to WARs (vital!!)


---
Just because you can doesn't mean you should
Re: RAP export as WAR using Tooling [message #1031967 is a reply to message #1027121] Tue, 02 April 2013 12:16 Go to previous messageGo to next message
Vikas K is currently offline Vikas KFriend
Messages: 8
Registered: January 2012
Junior Member
Hi John

Rap application uses jetty server while launching. Jetty server has some servlet plugins and when you will deploy to a app server like tomcat will have its own servlets plugins. This will cause problem.

You can try below things:

1-You need to make sure that none of the below plugins are added in the product configuration:
org.eclipse.equinox.http.jetty
org.eclipse.jetty.http
org.eclipse.jetty.continuation.source
org.eclipse.jetty.io
org.eclipse.jetty.security
org.eclipse.jetty.server
org.eclipse.jetty.servlet
org.eclipse.jetty.util

2-Make sure javax.servlet is added as import packages ,not as required plugin in dependencies and remove the version.

Let me know if the above helps.
Thanks
Vikas
Re: RAP export as WAR using Tooling [message #1031981 is a reply to message #1027121] Tue, 02 April 2013 12:35 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 1872
Registered: July 2009
Senior Member
Hi John,
you already found all the needed information:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=348045
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398780
Libra WAR Product Tooling needs an update ( bug 398780 ) in order to
export application based on RAP nightly.
Best,
Ivan

On 3/26/2013 5:22 PM, John Gymer wrote:
> Hi all (Ralf?),
>
> I've hit some problems this week trying to use the Libra WAR Tooling
> to export existing RAP projects as WARs for deploy to appservers.
>
> This process was working ok a few weeks ago, and I haven't done an
> export for a while, but now (after updating various components
> including nightly RAP build), I can no longer used the exported WAR file.
>
> In the WAR configuration panel, I now get a problem on
> org.eclipse.equinox.servletbridget.extensionbundle, although it isn't
> clear what the problem is. Something is not getting resolved
> somewhere along the lines.
>
> I can continue to export the WAR, but the bundles refused to go beyond
> "INSTALLED" state as they are missing constraints. The one that seems
> to be causing the problems is this one:
> "...Missing Constraint: Import-Package: javax.servley;
> version=[2.3.0,4.0.0)"
>
> I see from various posts that there has been some discussion, and
> wonder what the state of play is?
>
> link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348045
> and link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=398780
>
> Thanks, John
>
> p.s. I'm away not for a couple of weeks, but any info and progress
> greatly appreciated as I can no longer deploy my applications to WARs
> (vital!!)
>

--
Ivan Furnadjiev

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

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RAP export as WAR using Tooling [message #1058554 is a reply to message #1031981] Tue, 14 May 2013 12:59 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 198
Registered: November 2012
Location: UK
Senior Member
Hi Ivan,

I wonder if you could help me resolve my WAR issues now that I am upgraded to Kepler M7, and still having similar problems?

Firstly, I have installed the "WAR Products (Incubation)" from "Mylyn for Eclipse Kepler - http://download.eclipse.org/mylyn/releases/kepler". I assume this is the correct place to get the updated version?

Next I use my working RAP Run Configuration to base a new WAR product on, and export it. On deploying the WAR into WebLogic (the creation of the WAR and the deploy into WebLogic both work ok), I use the OSGI command ss to list the bundles... result below:

osgi> ss
"Framework is launched."


id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.9.0.v20130305-2200
1       ACTIVE      com.ibm.icu.base_50.1.0.v20121116-2
2       INSTALLED   iet.co.uk.rapide.RAP_85.80.0
3       ACTIVE      javax.xml_1.3.4.v201005080400
4       ACTIVE      org.apache.felix.gogo.command_0.10.0.v201209301215
5       ACTIVE      org.apache.felix.gogo.runtime_0.10.0.v201209301036
6       ACTIVE      org.apache.felix.gogo.shell_0.10.0.v201212101605
7       ACTIVE      org.eclipse.core.commands_3.6.100.v20130220-2151
8       ACTIVE      org.eclipse.core.contenttype_3.4.200.v20130221-0103
9       ACTIVE      org.eclipse.core.databinding_1.4.1.v20130220-2151
10      ACTIVE      org.eclipse.core.databinding.beans_1.2.200.v20130220-2151
11      ACTIVE      org.eclipse.core.databinding.observable_1.4.1.v20130220-2151

12      ACTIVE      org.eclipse.core.databinding.property_1.4.200.v20130220-2151

13      ACTIVE      org.eclipse.core.expressions_3.4.500.v20130221-0103
14      ACTIVE      org.eclipse.core.jobs_3.5.300.v20130221-0103
15      ACTIVE      org.eclipse.core.runtime_3.9.0.v20130221-0103
16      ACTIVE      org.eclipse.equinox.app_1.3.100.v20130225-1702
17      ACTIVE      org.eclipse.equinox.common_3.6.100.v20130225-1702
18      ACTIVE      org.eclipse.equinox.console_1.0.100.v20130225-1702
19      INSTALLED   org.eclipse.equinox.http.registry_1.1.200.v20130225-1702
20      INSTALLED   org.eclipse.equinox.http.servlet_1.1.300.v20130225-1702
21      INSTALLED   org.eclipse.equinox.http.servletbridge_1.0.300.v20130225-170
2
22      ACTIVE      org.eclipse.equinox.preferences_3.5.0.v20130225-1702
23      ACTIVE      org.eclipse.equinox.registry_3.5.300.v20130225-1702
24      INSTALLED   org.eclipse.equinox.servletbridge_1.2.200.v20130225-1702
25      ACTIVE      org.eclipse.equinox.util_1.0.400.v20130307-2007
26      ACTIVE      org.eclipse.help_3.6.0.v20130221-0120
27      ACTIVE      org.eclipse.osgi.services_3.3.100.v20130225-1645
28      INSTALLED   org.eclipse.rap.clientscripting_0.1.100.201305141337
29      INSTALLED   org.eclipse.rap.jface_2.1.0.20130225-1108
30      INSTALLED   org.eclipse.rap.jface.databinding_2.1.0.20130220-2001
31      INSTALLED   org.eclipse.rap.rwt_2.1.0.20130410-0853
32      INSTALLED   org.eclipse.rap.rwt.osgi_2.1.0.20130220-2001
33      INSTALLED   org.eclipse.rap.ui_2.1.0.20130220-2001
34      INSTALLED   org.eclipse.rap.ui.forms_2.1.0.20130306-1637
35      INSTALLED   org.eclipse.rap.ui.views_2.1.0.20130220-2001
36      INSTALLED   org.eclipse.rap.ui.workbench_2.1.0.20130225-1531
osgi> start 31
gogo: BundleException: The bundle "org.eclipse.rap.rwt_2.1.0.20130410-0853 [31]"
 could not be resolved. Reason: Missing Constraint: Import-Package: javax.servle
t; version="[2.3.0,4.0.0)"
osgi>


If I try to start the various bundles in turn and follow the dependency reported, the final problem appears to be still that RWT needed javax.servlet, similar to previous (before I upgraded to M7).

javax.servlet is listed as an Imported Package in my project, and is required in order for me to run the RAP application within Eclipse.

If I attempt to add javax.servlet into the WAR configuration, and then export, the export is not allowed because javax.servlet is a 'forbidden bundle'... I think this is as expected with the WAR tooling update?

Can you help identify what I have missed, or what extra I need to include to make this exported WAR work?

For info, my RAP Target is 2.1 Nightly from 10th April. I tried using one from 13th May, but couldn't get the RAP application to work at all within Eclipse, so reverted. Hope that's just a transitory problem with the nightly that will go away soon.

Thanks, John


---
Just because you can doesn't mean you should
Re: RAP export as WAR using Tooling [message #1058565 is a reply to message #1058554] Tue, 14 May 2013 13:20 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan FurnadjievFriend
Messages: 1872
Registered: July 2009
Senior Member
Hi John,
there are still problems with latests WAR Product from Libra. The bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398780 has been reopened.
I hope that the issue will be fixed in Kepler RC1.
Best,
Ivan

On 5/14/2013 3:59 PM, John Gymer wrote:
> Hi Ivan,
>
> I wonder if you could help me resolve my WAR issues now that I am
> upgraded to Kepler M7, and still having similar problems?
>
> Firstly, I have installed the "WAR Products (Incubation)" from "Mylyn
> for Eclipse Kepler -
> http://download.eclipse.org/mylyn/releases/kepler". I assume this is
> the correct place to get the updated version?
>
> Next I use my working RAP Run Configuration to base a new WAR product
> on, and export it. On deploying the WAR into WebLogic (the creation of
> the WAR and the deploy into WebLogic both work ok), I use the OSGI
> command ss to list the bundles... result below:
>
>
> osgi> ss
> "Framework is launched."
>
>
> id State Bundle
> 0 ACTIVE org.eclipse.osgi_3.9.0.v20130305-2200
> 1 ACTIVE com.ibm.icu.base_50.1.0.v20121116-2
> 2 INSTALLED iet.co.uk.rapide.RAP_85.80.0
> 3 ACTIVE javax.xml_1.3.4.v201005080400
> 4 ACTIVE org.apache.felix.gogo.command_0.10.0.v201209301215
> 5 ACTIVE org.apache.felix.gogo.runtime_0.10.0.v201209301036
> 6 ACTIVE org.apache.felix.gogo.shell_0.10.0.v201212101605
> 7 ACTIVE org.eclipse.core.commands_3.6.100.v20130220-2151
> 8 ACTIVE org.eclipse.core.contenttype_3.4.200.v20130221-0103
> 9 ACTIVE org.eclipse.core.databinding_1.4.1.v20130220-2151
> 10 ACTIVE org.eclipse.core.databinding.beans_1.2.200.v20130220-2151
> 11 ACTIVE
> org.eclipse.core.databinding.observable_1.4.1.v20130220-2151
>
> 12 ACTIVE
> org.eclipse.core.databinding.property_1.4.200.v20130220-2151
>
> 13 ACTIVE org.eclipse.core.expressions_3.4.500.v20130221-0103
> 14 ACTIVE org.eclipse.core.jobs_3.5.300.v20130221-0103
> 15 ACTIVE org.eclipse.core.runtime_3.9.0.v20130221-0103
> 16 ACTIVE org.eclipse.equinox.app_1.3.100.v20130225-1702
> 17 ACTIVE org.eclipse.equinox.common_3.6.100.v20130225-1702
> 18 ACTIVE org.eclipse.equinox.console_1.0.100.v20130225-1702
> 19 INSTALLED
> org.eclipse.equinox.http.registry_1.1.200.v20130225-1702
> 20 INSTALLED org.eclipse.equinox.http.servlet_1.1.300.v20130225-1702
> 21 INSTALLED
> org.eclipse.equinox.http.servletbridge_1.0.300.v20130225-170
> 2
> 22 ACTIVE org.eclipse.equinox.preferences_3.5.0.v20130225-1702
> 23 ACTIVE org.eclipse.equinox.registry_3.5.300.v20130225-1702
> 24 INSTALLED
> org.eclipse.equinox.servletbridge_1.2.200.v20130225-1702
> 25 ACTIVE org.eclipse.equinox.util_1.0.400.v20130307-2007
> 26 ACTIVE org.eclipse.help_3.6.0.v20130221-0120
> 27 ACTIVE org.eclipse.osgi.services_3.3.100.v20130225-1645
> 28 INSTALLED org.eclipse.rap.clientscripting_0.1.100.201305141337
> 29 INSTALLED org.eclipse.rap.jface_2.1.0.20130225-1108
> 30 INSTALLED org.eclipse.rap.jface.databinding_2.1.0.20130220-2001
> 31 INSTALLED org.eclipse.rap.rwt_2.1.0.20130410-0853
> 32 INSTALLED org.eclipse.rap.rwt.osgi_2.1.0.20130220-2001
> 33 INSTALLED org.eclipse.rap.ui_2.1.0.20130220-2001
> 34 INSTALLED org.eclipse.rap.ui.forms_2.1.0.20130306-1637
> 35 INSTALLED org.eclipse.rap.ui.views_2.1.0.20130220-2001
> 36 INSTALLED org.eclipse.rap.ui.workbench_2.1.0.20130225-1531
> osgi> start 31
> gogo: BundleException: The bundle
> "org.eclipse.rap.rwt_2.1.0.20130410-0853 [31]"
> could not be resolved. Reason: Missing Constraint: Import-Package:
> javax.servle
> t; version="[2.3.0,4.0.0)"
> osgi>
>
>
> If I try to start the various bundles in turn and follow the
> dependency reported, the final problem appears to be still that RWT
> needed javax.servlet, similar to previous (before I upgraded to M7).
>
> javax.servlet is listed as an Imported Package in my project, and is
> required in order for me to run the RAP application within Eclipse.
>
> If I attempt to add javax.servlet into the WAR configuration, and then
> export, the export is not allowed because javax.servlet is a
> 'forbidden bundle'... I think this is as expected with the WAR tooling
> update?
>
> Can you help identify what I have missed, or what extra I need to
> include to make this exported WAR work?
>
> For info, my RAP Target is 2.1 Nightly from 10th April. I tried using
> one from 13th May, but couldn't get the RAP application to work at all
> within Eclipse, so reverted. Hope that's just a transitory problem
> with the nightly that will go away soon.
>
> Thanks, John
>

--
Ivan Furnadjiev

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

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RAP export as WAR using Tooling [message #1058599 is a reply to message #1058565] Tue, 14 May 2013 14:17 Go to previous message
John Gymer is currently offline John GymerFriend
Messages: 198
Registered: November 2012
Location: UK
Senior Member
Hi Ivan,
Fantastic - and thanks for the link to the bug which shows how to workaround it in the meantime!
I've exported the WAR, manually edited the config.ini inside to include "org.eclipse.equinox.servletbridge.extensionbundle,\" and now it works perfectly in WebLogic!
Excellent!
Cheers, John


---
Just because you can doesn't mean you should
Previous Topic:RAP 2.0 FileDialog configuration problems
Next Topic:RAP-2.0 - UnsupportedOperationException in SimpleLifeCycle.sleep() Using JDialog.open().
Goto Forum:
  


Current Time: Thu Dec 18 05:53:56 GMT 2014

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

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