Beginner question - Is there an Errai example without CDI?

[pgmjsd]

If I want to use Errai in an application that doesn't yet have CDI, where do I start?   Is there an example of an Errai application without CDI integration?

Also, from a beginner's perspective it's not immediately clear what the difference is between a 'normal' GWT application and an Errai application.   Can someone point me to some documentation that covers that basic differences?

[csa]

Hi Joshua,

We have a set of specific demos that you can take a look at and a tutorial project (the bus and jax-rs examples don't depend on CDI):

https://github.com/errai/errai/tree/master/errai-demos

https://github.com/errai/errai-tutorial/archive/master.zip

You can also create an app from scratch using the Errai Forge Addon which allows you to choose which features you want:

https://github.com/errai/errai/blob/master/errai-forge-addon/

For more information check out the getting started section in our docs:

http://docs.jboss.org/errai/3.0-SNAPSHOT/errai/reference/html_single/#sid-54493220

In general, the use of CDI is optional. You can also choose whether you want to use CDI on the client or the server or both.

Errai leverages GWT and adds a whole set of features. Too many to list here but check out our documentation:

http://docs.jboss.org/errai/3.0-SNAPSHOT/errai/reference/html_single/

We also have a tutorial for converting an existing GWT app into an Errai app:

https://github.com/errai/gwt-to-errai-tutorial

Feel free to stop by our IRC channel #errai on freenode if you need help getting started.

Cheers,

Christian

[pgmjsd]

Thanks Christian!   That helps.   I did pick up on how the Errai IoC container works, but I guess it wasn't entirely clear to me from the main example.

In my case I'm not converting from GWT, but I am considering using Errai to replace a Seam-2-with-remoting-and-lots-of-JavaScript 'page' in an existing Seam 2 app.   The ErraiBus looks like the perfect thing for this particular page/application - lots of async messaging going on.   Eventually, we'll go to CDI but I wanted to explore non-CDI options for migration as that's much smaller.   I still have to figure out how the 'server side' beans would communicate with the Seam 2 backing beans (conversation scope), but... that's something that I will look into once I am more comfortable with GWT/Errai IoC.