Ok, good,
I'll check it.

I have worked a lot in the past weeks to test GWT on servicemix also by
adapting many examples, and I have many considerations to provide, please
take some time to take into account my feedback ;-)

Cristiano



Il giorno sabato 7 dicembre 2013, Jean-Baptiste Onofré ha scritto:

> FYI:
>
> https://issues.apache.org/jira/browse/SMX4-1634
>
> Regards
> JB
>
> On 12/07/2013 01:45 PM, Jean-Baptiste Onofré wrote:
>
> Hi Christiano,
>
> I already did the gwt bundles in the past.
>
> I gonna create new gwt bundles (for 2.6.0) and include it in the next
> 2013.12 release.
>
> Regards
> JB
>
> On 12/07/2013 01:35 PM, Cristiano Costantini wrote:
>
> Hi All,
>
> as there is no so many interest on supporting OSGi in the GWT community
> (the related issue has only 5 votes:
> https://code.google.com/p/google-web-toolkit/issues/detail?id=8424 and I
> know all of those who have starred it :-D ),
> I wonder if it is more appropriate to make OSGi release
> under org.apache.servicemix.bundles.
>
> It has been done in the past (for
> "org.apache.servicemix.bundles/org.apache.servicemix.
> bundles.gwt-user/2.4.0_1"
>
> and
> "org.apache.servicemix.bundles/org.apache.servicemix.
> bundles.gwt-dev/2.4.0_1").
>
>
> Now it is going to be released GWT version 2.6.0 and I believe it
> should be
> released only gwt-servlet artifact with OSGi headers (so
> "org.apache.servicemix.bundles/org.apache.servicemix.
> bundles.gwt-servlet/2.6.0_1").
>
>
>
> Could someone point me to the right process (where is the source code of
> org.apache.servicemix.bundles.*, where to open related issues, where to
> discuss them, who to involve in the approval process) so I can try to
> push
> and support for this proposal?
>
>
> Thank you!!!
> Cristiano
>
>
>
>
>
>
> 2013/11/19 Cristiano Costantini <[email protected]>
>
>  Hi all!
> Just an update about my ongoing effort to OSGIfy GWT.
>
> I did proposed a patch to GWT community and to validate it I've
> adapted 5
> significant examples from the GWT distribution to run on Apache Karaf,
> (more precisely I used ServiceMix 4.5.3 but I'm not using neither Camel,
> CXF or ActiveMQ).
>
> You can find the examples here:
> https://github.com/cristcost/gwt-karaf-examples
>
> They require GWT compiled using this patch of mine
> https://gwt-review.googlesource.com/#/c/5351/
> If someone want to try them out, I will be glad to help and give more
> detailed instructions.
>
> Actually there is no so much interest from GWT community, so I would
> like
> you all supporting me by starring the related issue:
> https://code.google.com/p/google-web-toolkit/issues/detail?id=8424
> and if you are interested, apply to
> https://gwt-review.googlesource.com/and perform a (non binding)
> review of
> https://gwt-review.googlesource.com/#/c/5351/ so that the patch can be
> noticed more.
>
>
> The patch is not yet ideal, as the .bnd file contains some
> "workaround" to
> address complex dependencies in the GWT jar, but I hope these can be
> addressed by a refactoring in GWT package structure in next release.
> Also,
> there is a rare issue when two applications are deployed together and
> use
> "com.google.web.bindery.requestfactory.server.RequestFactoryServlet".
> Anyhow I would like it to be approved for the upcoming final release of
> GWT 2.6.0 which is expected beginning of december, so that community can
> start developing first prototype applications using this architecture.
>
> To go back to the examples, they actually don't make full use of OSGi
> capabilities (no OSGi service is used for this) but me and some
> friends are
> working on a *full* demo application that make use of the full
> ServiceMix
> stack and have a GWT front-end deployed on ServiceMix. For this demo,
> stay
> tuned on this other github project
> https://github.com/cristcost/sensormix
> We would like to have it working on next version of GWT (2.6.0) and also
> next version of ServiceMix (4.6.0). We would like to finish it before
> mid
> december, and we will present it at next "GDG Firenze Happy Hour"
> meeting
> that should b
>
>

Reply via email to