Two Laptop Bag*
The moose likes JBoss/WildFly and the fly likes Problem using  JBOSS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Problem using  JBOSS" Watch "Problem using  JBOSS" New topic
Author

Problem using JBOSS

vijay makam
Ranch Hand

Joined: Sep 06, 2008
Posts: 31
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


Regards,
vijay
Mark Spritzler
ranger
Sheriff

Joined: Feb 05, 2001
Posts: 17260
    
    6

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.

Thanks

Mark


Perfect World Programming, LLC - Two Laptop Bag - Tube Organizer
How to Ask Questions the Smart Way FAQ
vijay makam
Ranch Hand

Joined: Sep 06, 2008
Posts: 31
Hi Mark,

This is the error trace.


This is my persistence.xml file


Please let me know the steps to define a non-jta-data-source, as I have never used datasource anytime.


Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16305
    
  21



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.


Customer surveys are for companies who didn't pay proper attention to begin with.
vijay makam
Ranch Hand

Joined: Sep 06, 2008
Posts: 31
Hi All,

Thanks for your time. I got that working finally :
Mudassar Nazar
Greenhorn

Joined: Feb 09, 2010
Posts: 1
vijay makam wrote:Hi All,

Thanks for your time. I got that working finally :


How did you resolve this JPA problem with JBoss?
kishore nag
Greenhorn

Joined: Feb 18, 2010
Posts: 17
can you please explain me how you deploy in jboss same error i am also getting now please explain me i have very urgent reqiurement
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10288
    
168

kishore,

You already have a new topic open in this forum to discuss this issue. Let's continue the discussion there.

[My Blog] [JavaRanch Journal]
Andres Fuentes
Greenhorn

Joined: Mar 04, 2010
Posts: 1
vijay makam wrote:Hi All,

Thanks for your time. I got that working finally :


Can you explain how did you fix it?
michele mike
Greenhorn

Joined: Apr 26, 2010
Posts: 1
To make it works you have to define a new data source in the deploy directory, and then use that.
You cannot define your own data source connection inside your persistence.xml.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problem using JBOSS