I am using JSF and JPA with toplink implementation in JBOSS. I am not able to deploy the application as I am using entity bean and jboss is treating this as EJB. so the deployment is failing. Can I disable EJB deployer in jboss as I'm not using it. Also, is there a way out in JBOSS to make it work with JPA with out disabling ejb
In EJB3, there are no Entity beans anymore, just JPA.
I am assuming you are using EJB3 here, the only way JBoss could think it is an Entity Bean in EJB 2.x is if you declare it in an ejb-jar.xml file, which I am sure you don't.
What is the actual deployment error and stacktrace and please post it here, inside CODE tags.
In JBoss, datasources are defined in files named "xxxxx-datasource.xml". JBoss digests them, creates the datasource/connection pool objects, and files them in the JNDI directory so that apps can reference them.
For JPA EJB entities JBoss will inject the entity manager into the appropriately-designated places, and at that point, I'll have to leave you to the tender mercies of the JBoss docs, since the last time I worked with it, I was trying to get a non-EJB JPA app installed and I ended up falling back to just basic Tomcat after wearing myself out on JSF portability issues.
There are still Entity Beans in EJB3/JPA, Mark. I think you might have been referring to BMP beans, but I'd have to RFTM on that one, since while JPA makes self-managing entity beans rather silly, BMP still may be supported as a remotable data access mechanism.
If a low price is more important to you than getting good value for your money, you're not as prosperous as you think you are.