Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem using JBOSS

 
vijay makam
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
vijay makam
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Pie
Posts: 18212
53
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


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.
 
vijay makam
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

Thanks for your time. I got that working finally :
 
Mudassar Nazar
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
kishore,

You already have a new topic open in this forum to discuss this issue. Let's continue the discussion there.
 
Andres Fuentes
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic