Could it be that your web.xml is declared using the Servlet 2.4
specification (instead of 2.5) and you are trying to look up a EJB 3.0
bean that has no local home interface?
There should be plenty of examples of how to use ejb-ref and
ejb-local-ref in the EJB specifications. The way to specify them in
web.xml is the same as in ejb-jar.xml.
Once you understand these tags, you can refer to the following FAQ to
check what to do if you have multiple business interfaces or other
less-straightforward cases.
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
digi_pixel wrote:
> Does glassfish create instances of the EJB's if they are registered in
> web.xml?
>
> There are errors that appear in the
> http://www.nabble.com/file/p14934510/Glassfish%2BServer%2BLog%2B%252818-01-08%2529.txt
> Glassfish Server Log when the EAR is deployed, do these messages below have
> anything to do with the errors?
>
> "DPL8017: Ejb-ref type mismatch for ejb reference RegisterAction. Reference
> declares type beans.Register but target ejb RegisterAction has Local Home
> interface of type null."
> "DPL8017: Ejb-ref type mismatch for ejb reference RegisterAction. Reference
> declares type beans.Register but target ejb RegisterAction has Local
> interface of type null."
>
> Can I please see an example of how EJBs should be registered in web.xml just
> in case the configuration is incorrect.