Adding documentation about beans.xml. Closes #815.

I think this only apply to modules deployed in application servers:

A Java EE container is required by the Java EE specification to support
> Java EE modules. Other containers may or may not provide support for war,
> EJB jar or rar bean archives.


Anyway, I've tested now I our application and VRaptor didn't scanned the
controllers. By the way, VRaptor is warning as expected:

06:42:06,532  WARN [VRaptor             ] A beans.xml isn't found. Check if
is properly located at /WEB-INF/beans.xml or
/WEB-INF/classes/META-INF/beans.xml





--
Chico Sokol

On Wed, Nov 5, 2014 at 11:06 PM, Otávio Garcia <notifications@github.com>
wrote:

> In vraptor-site/content/en/docs/dependencies-and-prerequisites.html:
>
> > @@ -27,6 +27,18 @@
> >  </listener>
> >  ~~~
> >
> > +And the optional `beans.xml` file located under your `WEB-INF` folder with this content:
>
> Yes, is optional as described in CDI spec:
> http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive
>
> Java EE modules like WAR, JAR, EAR is an "Implicit archive", and CDI is
> enabled by default even no beans.xml exists.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/caelum/vraptor4/pull/871/files#r19920062>.
>