[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[ews.eclipse.technology.rap] Re: Problems building a war file of my RAP application
|
- From: "Frank Appel" <fappel@xxxxxxxxxxxxxx>
- Date: Fri, 25 Apr 2008 10:40:43 +0200
- Newsgroups: eclipse.technology.rap
- Organization: EclipseCorner
- Thread-index: Acijhg2yrZcbTjFaTHqKNgi/ofUeOAAAAEnIAAAAbhIAAOj7fgAyb1DWAAvVb6EAAAAVxAAj/P/kAAADFKMADXBZSQBYWMd6AADeffA=
Hi,
the current deployment example seems to be somewhat outdated. We will
bring this up to date soon. If you are working with RAP M3 target there
should be no need to have the following projects opened in your
workspace:
javax.servlet
org.apache.commons.logging
org.eclipse.equinox.http.jetty
org.eclipse.equinox.http.registry
org.eclipse.equinox.http.servlet
org.mortbay.jetty
Having an additional javax.servlet project in the workspace seems indeed
to cause the build process to fail.
The current demo build feature uses org.eclipse.update.configurator.
Thanks to a hint of Jeff McAffer we can forget about this one. But it is
important to add org.eclipse.equinox.servletbridge.extensionbundle to
the config.ini's osgi.bundles list. Note that the latter bundle doesn't
exist in your deployment archive - it is created at runtime (that was
the reason we missed it...).
If you still want to use the update configurator bundle use @2:start.
Note also that the latest CVS-Head version comes with a RWT-Split -
RWT-host and RWT-q07-fragment. Don't use @start for the fragment!
Hope that helps.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Ryan Donnelly [mailto:ryanrd1@xxxxxxxxx]
Bereitgestellt: Donnerstag, 24. April 2008 13:26
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problems building a war file of my RAP application
Betreff: Re: Problems building a war file of my RAP application
Thanks for the advice. I've filed a bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=228650
Christian Riedel wrote:
> Hi Ryan,
>
> (full quote below)
>
> Concerning your problem:
>
>> With 1.1M3, if javax is in the workspace i get the error
>> discussed below. Without it, the PDE export completes without error,
>> but when I run it, i get "The requested resource (ProxyServlet:
>> /calc/rap) is not available.".
>
> For me it worked, if manually start org.eclipse.rap.ui from the OSGI
> console. Before the command 'ss' shows that it is either resolved or
> lazy (don't remember right now). When you issue a
>
> start org.eclipse.rap.ui
>
> It should become active.
>
> After doing this the error with the ProxyServlet disappeared and
> calling the app via yourhost/calc/rap should work - at least it worked
for me.
>
> HTH
>
> Christian
>
>
>
>
>
> Ryan Donnelly schrieb:
>> Frank,
>> Thanks, if you could take a look at it soon that would be
>> helpful. I can no longer export even the calc example with the
>> servletbridge projects from CVS.
>>
>> With 1.1M2 as the target platform, if javax is in the workspace i
>> get the error discussed below (and I can see it in logs.zip as well).
>> Without it, the PDE export completes without error but when I run it
>> (http://localhost:8080/calc/rap) I get an error "An entry point named
>> 'default' does not exist". The only thing in .metadata/.log (there
>> are no other log files) is:
>>
>> java.lang.NoClassDefFoundError:
>> org/eclipse/core/internal/runtime/auth/AuthorizationHandler
>>
>> which I always get, even when it is working.
>>
>> If I remove org.eclipse.equinox.http.registry and
>> org.eclipse.equinox.http.servlet from the workspace and export I
>> still get the same thing.
>>
>>
>> With 1.1M3, if javax is in the workspace i get the error
>> discussed below. Without it, the PDE export completes without error,
>> but when I run it, i get "The requested resource (ProxyServlet:
>> /calc/rap) is not available.". There is no .metadata/.log, but there
>> is a log file configuration/1208897299078.log. It only has:
>>
>> java.lang.NoClassDefFoundError:
>> org/eclipse/core/internal/runtime/auth/AuthorizationHandler
>>
>>
>>
>> Thanks,
>>
>> Ryan
>>
>>
>> Frank Appel wrote:
>>> Hi,
>>>
>>> I already have an action item for checking this. We'll keep you
>>> posted - probably we will provide a new psf and have to update the
>>> docu a little bit for the next milestone.
>>>
>>>
>>> Ciao
>>> Frank
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Ryan Donnelly [mailto:ryanrd1@xxxxxxxxx]
>>> Bereitgestellt: Dienstag, 22. April 2008 15:58 Bereitgestellt in:
>>> eclipse.technology.rap
>>> Unterhaltung: Problems building a war file of my RAP application
>>> Betreff: Re: Problems building a war file of my RAP application
>>>
>>>
>>> Also, if we need to close javax, would we also need to close the
>>> following, which appear both in the set of servletbridge CVS
>>> projects and in the RAP target platform?
>>>
>>> org.eclipse.equinox.http.jetty
>>> org.eclipse.equinox.http.registry
>>> org.eclipse.equinox.http.servlet
>>>
>>>
>>>
>>> Ryan Donnelly wrote:
>>>> Hi, RAP Team,
>>>> I am seeing the same error when running:
>>>>
>>>> The type javax.servlet.http.HttpServlet cannot be resolved. It is
>>>> indirectly referenced from required .class files
>>>>
>>>> and I also see that it goes away when I close the javax
project.
>>>> Can you confirm that we should no longer have the javax project in
>>>> the
>>>
>>>> workspace when exporting with webappBuilder.xml?
>>>>
>>>> I also tried running webappBuilder.xml with all of the RAP and
>>>> servletbridge projects (including javax) from CVS, with no RAP
>>>> target platform at all, and I got the same error. Since there is
>>>> no
>>> "conflict"
>>>> in this case between the CVS javax and the one in the target
>>>> platform,
>>>
>>>> I'm not sure why this shouldn't work. Should we not be able to run
>>>> webappBuilder.xml in this way, with all projects from CVS and none
>>>> from the target platform?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Ryan
>>>>
>>>>
>>>> Christian Riedel wrote:
>>>>> Hi Stefan,
>>>>>
>>>>> thanks a lot for your hint. After deleting the servlet 2_4 project
>>>>> from the wokspace, I got rid of these compiler errors! Works like
>>>>> a charm now!
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> Stefan Ruzitschka schrieb:
>>>>>> Christian Riedel wrote:
>>>>>>
>>>>>>> Hi Cheney,
>>>>>>> thanks for this hint, but my first RAP application already does
>>>>>>> import the javax.servlet and javax.servlet.http packages. So
>>>>>>> that does not seem to be the problem.
>>>>>>> However, yesterday I tried building the war using the current
>>>>>>> Eclipse 3.4 milestone release. Which did not produce the compile
>>>>>>> errors.
>>>>>>> Here's how I created my test project:
>>>>>>> - I used the org.eclipse.rap.demo project
>>>>>>> - I included the org.eclipse.rap.demo.feature to my workspace
>>>>>>> from :pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/technology
>>>>>>> - I added the servletBridge by importing the following team
>>>>>>> project
>>>
>>>>>>> set via this link:
>>>>>>>
http://www.eclipse.org/equinox/server/downloads/servletbridge-anon.
>>>>>>> psf
>>>>>>> - I added the org.eclipse.update.configurator from my eclipse
>>>>>>> installation
>>>>>>> - I adapted the ant script to have the right paths
>>>>>>
>>>>>>> No matter what I do, when I now start the ant task, I see the
>>>>>>> progress indicator of the pdeExportFeatures task running ... and
>>>>>>> then, after some time, have this logs.zip file in my destination
>>> dir.
>>>>>>
>>>>>>> I really cannot find what is going wrong there. After all it is
>>>>>>> the
>>>
>>>>>>> unchanged examples I am trying it with.
>>>>>>
>>>>>>> Any more ideas?
>>>>>>> TIA
>>>>>>> Christian
>>>>>>
>>>>>>> Cheney schrieb:
>>>>>>>> Hi,
>>>>>>>> That problem is that you didn't import the javax.servlet and
>>>>>>>> javax.servlet.http packages in your first RAP
>>>>>>>> application.Please check the MANIFEST.MF in your first RAP
>>>>>>>> application include the javax.servlet and javax.servlet.http
import package.
>>>>>>>> Hope helps.
>>>>>>>>
>>>>>>>> cheers,
>>>>>>>> Cheney
>>>>>>>>
>>>>>>>> Christian Riedel wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I am just trying to build a war file of my first RAP
application.
>>>>>>>>> Following Elias' tutorial from
>>>>>>>>>
>>>>>> http://rapblog.innoopract.com/2007/12/rap-deployment-part-2-deplo
>>>>>> yin
>>>>>> g-your.html
>>>>>>
>>>>>>>>> I adapted the ANT script from the
org.eclipse.rap.demo.feature.
>>>>>>>>>
>>>>>>>>> The problem is that the pde.exportFeatures task seems to have
>>>>>>>>> problems finding the javax.servlet.* classes.
>>>>>>>>>
>>>>>>>>> As suggested I used the Import Team Project Set wizard to get
>>>>>>>>> the
>>>
>>>>>>>>> plugins needed for building the war file. My Workspace now has
>>>>>>>>> the following projects:
>>>>>>>>>
>>>>>>>>> META.rap (my project)
>>>>>>>>> META.rap.war.feature (the adapted
>>>>>>>>> org.eclipse.rap.demo.feature)
>>>>>>>>>
>>>>>>>>> org.eclipse.equinox.http.registry
>>>>>>>>> org.eclipse.equinox.http.servlet
>>>>>>>>> org.eclipse.equinox.http.servletbridge
>>>>>>>>> org.eclipse.equinox.servletbridge
>>>>>>>>> org.eclipse.equinox.servletbridge.feature
>>>>>>>>> org.eclipse.update.configurator
>>>>>>>>>
>>>>>>>>> javax.servlet
>>>>>>>>>
>>>>>>>>> As you see, the javax.servlet part is available. Other plugins
>>>>>>>>> reference this part as dependency and eclipse itself does not
>>>>>>>>> show any errors.
>>>>>>>>> However, when I start the pde.exportFeatures task I find a
>>>>>>>>> logs.zip file in the destination folder which contains the
>>>>>>>>> following errors:
>>>>>>>>>
>>>>>>>>> in
>>>>>>>>>
>>> org.eclipse.equinox.http.registry_1.0.100.200804191334/@dot.bin.log:
>>>>>>>>>> # 19.04.08 13:34:44 CEST
>>>>>>>>>> # Eclipse Java Compiler 0.793_R33x, 3.3.2, Copyright IBM Corp
>>>>>>>>>> 2000, 2008.
>>>>>>>>>> # All rights reserved.
>>>>>>>>>> ----------
>>>>>>>>>> 1. ERROR in C:Dokumente und EinstellungenSarekEigene
>>>>>>>>>>
>>>>>> Dateienworkspaceorg.eclipse.equinox.http.registrysrcorgeclipseequ
>>>>>> ino xhttpregistryinternalDefaultRegistryHttpContext.java
>>>>>>
>>>>>>>>>> (at line 1)
>>>>>>>>>>
>>>>>> /****************************************************************
>>>>>> ***
>>>>>> ************
>>>>>>
>>>>>>>>>> ^ The type javax.servlet.http.HttpServletRequest cannot be
>>>>>>>>>> resolved. It is indirectly referenced from required .class
>>>>>>>>>> files
>>>
>>>>>>>>>> ---------- 2.
>>>>>>>>>> ERROR
>>>>>>>>>> in C:Dokumente und EinstellungenSarekEigene
>>>>>>>>>>
>>>>>> Dateienworkspaceorg.eclipse.equinox.http.registrysrcorgeclipseequ
>>>>>> ino xhttpregistryinternalDefaultRegistryHttpContext.java
>>>>>>
>>>>>>>>>> (at line 1)
>>>>>>>>>>
>>>>>> /****************************************************************
>>>>>> ***
>>>>>> ************
>>>>>>
>>>>>>>>>> ^ The type javax.servlet.http.HttpServletResponse cannot be
>>>>>>>>>> resolved. It is indirectly referenced from required .class
>>>>>>>>>> files
>>>
>>>>>>>>>> ---------- 3.
>>>>>>>>>> ERROR
>>>>>>>>>> in C:Dokumente und EinstellungenSarekEigene
>>>>>>>>>>
>>>>>> Dateienworkspaceorg.eclipse.equinox.http.registrysrcorgeclipseequ
>>>>>> ino xhttpregistryinternalDefaultRegistryHttpContext.java
>>>>>>
>>>>>>>>>> (at line 16) import javax.servlet.http.HttpServletRequest;
>>>>>>>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The import
>>>>>>>>>> javax.servlet.http.HttpServletRequest cannot be resolved
>>>>>>>>>> ----------
>>>>>>>>> ... and masses more ...
>>>>>>>>>
>>>>>>>>> The question is what must I do so that the javax.servlet
>>>>>>>>> classes CAN be found and that the compile process does not
fail?
>>>>>>>>>
>>>>>>>>> I double and triple checked everything in my project settings.
>>>>>>>>> I can't find the catch.
>>>>>>>>>
>>>>>>>>> Can you guys help me?
>>>>>>>>>
>>>>>>>>> Thanks in advance
>>>>>>>>>
>>>>>>>>> Christian
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>> Hey Christian,
>>>>>>
>>>>>> i had the same problem. After the step with the
>>>>>> ../servletbridge-anon.psf, you have to delete the javax.servlet
>>>>>> project, because it comes to an conflict with the pre-installed
>>>>>> javax.servlet in the RAP target platform.
>>>>>> From now on you should have no problems with some logs.zip file
>>>>>> in the build directory, after running the webappBuilder.xml.
>>>>>>
>>>>>> Greetings
>>>>>> Stefan R.
>>>>>>
>>>
>