• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

how to execute ejb3.0

 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i deployed a entity bean(ejb3.0) using ant into jboss but how to execute that jar file.
i used run command of ant but it generating exception
 
author & internet detective
Posts: 41905
909
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Srikanth,
You don't execute a jar file. You can call a JPA (EJB 3) entity from a session bean or servlet (or another class using JNDI lookup.)

What does your Ant script do? What error is it giving you? More details will help you get a more targeted answer.
 
srikanth arroju
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
when i enter at command prompt
ant run

[java] Exception in thread "main" javax.naming.NameNotFoundException: remot
e not bound
 
Jeanne Boyarsky
author & internet detective
Posts: 41905
909
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Srikanth,
It sounds like you Ant calls a Java client which calls the EJB. This is allowed for remote beans. Note that there is no such thing as an entity bean in EJB 3.0. JPA replaced it and JPA doesn't have remote calls that I know of. This means that you either have an EJB 2.1 style remote entity bean (which should be avoided for new code since it will not be supported at some point) or something that will not work. Good practice is to wrap the JPA entity or entity bean in a remote session bean.
 
reply
    Bookmark Topic Watch Topic
  • New Topic