Reacties op: Using GWT to create an OSGi-aware web application

Door: Angelo van der Sijpt

Angelo van der Sijpt — Fri, 22 Apr 2011 19:03:19 +0000

Hm, I’m not sure what’s going on. I rebuilt the bundle with a current GWT version, and it does not seem to import javax.validation, and running it with Pax Runner seems to work fine. Are you sure you followed all steps?

Door: Stefan

Stefan — Fri, 01 Apr 2011 14:18:12 +0000

Hello,

i try this tutorial and it failed by pax-runner

org.osgi.framework.BundleException: Unresolved constraint in bundle net.luminis.gwt.gwtdemo [1]: Unable to resolve 1.0: missing requirement [1.0] package; (package=javax.validation)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3404)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1714)ERROR: Error starting file:bundles/net.luminis.gwt.gwtdemo_0.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle net.luminis.gwt.gwtdemo [1]: Unable to resolve 1.0: missing requirement [1.0] package; (package=javax.validation))

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1143)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:680)

Any idea?

Door: Maven and OSGi Roundup « Knowledge Networks

Maven and OSGi Roundup « Knowledge Networks — Thu, 17 Jun 2010 23:17:19 +0000

[...] Example GWT Application in a OSGi bundle Possibly related posts: (automatically generated)Java Modularity Tutorials (OSGi, Declarative Services and Maven)Build and Dependency Management: Lean MavenCreating Runtime Environments for OSGi Declarative Services in EclipseBook Released – Apache Maven 2: Effective Implementation [...]

Door: Angelo van der Sijpt

Angelo van der Sijpt — Mon, 05 Apr 2010 20:33:00 +0000

I’m afraid I do not; I’m pretty sure someone with more knowledge of wars could answer this?

Door: Jaime Soriano

Jaime Soriano — Mon, 05 Apr 2010 11:07:55 +0000

Thanks a lot for this tutorial, I could use it without any problem to deploy a GWT 2.0.3 application with Pax Runner 1.4.0.
I saw that if “/” is used as webapp context, the application still works but all the contents of the jar file are exposed as static files, so it can be downloaded by anyone.
Do you know if there is another way to set the context to root so the files are not exposed?

Door: Angelo van der Sijpt

Angelo van der Sijpt — Sat, 20 Feb 2010 21:46:14 +0000

The error message on the server had to do with an old servlet jar I included in the zipped project, which is incompatible with the old GWT servlet jar. In the server log, there is a message about this:

com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: Parameter 0 of is of an unknown type 'java.lang.String/2004016611'

This can be solved by just deleting the jar from war/WEB-INF/lib; the build will put the right one there.

I updated the zipped project to include this change.

Door: Raul

Raul — Sat, 20 Feb 2010 13:19:59 +0000

Hello #5 by DODO solve my problem, but I cannot connect to the server. It is displaying the index page demo GWT page, but when I click the Send button, I got the following error:

Sending name to the server:
GWT User

Server replies:
An error occurred while attempting to contact the server. Please check your network connection and try again.

Door: Raul

Raul — Sat, 20 Feb 2010 09:23:37 +0000

Hello, I have tried your method with GWT 2.0. But each time I am having the error
org.osgi.framework.BundleException: Unresolved constraint in bundle com.cisco [1]: package; (package=com.google.gwt.core.ext)->
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:619)

Then I have installed gwt-dev.jar also where the package com.google.core.ext resides, but it does not work.

any suggestion please!

Door: Angelo van der Sijpt

Angelo van der Sijpt — Sun, 07 Feb 2010 20:47:30 +0000

I understand that BND creates all the imports, but as long as its GWT-related, you should get by with trusting the GWT magic, and mark those as optional. The list might indeed have changed, I haven’t tried this on GWT 2 yet.

Could you try marking just the GWT packages as optional, and keep the rest the way they were?

Door: dodo

dodo — Sun, 07 Feb 2010 12:30:58 +0000

The error I got when running your tutorial was
http://yfrog.com/jubasicp

So I included the gwt-jars (resulting in pretty big gwt-demo.jar).
But that didn’t work and gave me :
http://yfrog.com/11includegwtlibsp
So I thought including every demanded jar was not the right way to go, because I probably would have ended with a jar containing every other jar in the java-world

bnd creates a long list of packages to import, but marking them all as optional did the trick.
http://yfrog.com/jualloptionalp