• 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

abstract schema name

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello again

what is the difference between an "abstract schema" and an entity bean? It seems they are both representations of data in the db.
 
Sheriff
Posts: 3063
12
Mac IntelliJ IDE Python VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
<abstract-schema-name> is simply a tag in the entity beans's deployment descriptor. The name that it specifies is what you must use to refer to the bean in EJB-QL. Usually you just set it to the same value as the EJB name. Can you think what advantage you could gain by setting it to something other than the EJB name? In other words, can you figure out why the specifiers felt it necessary to have an <abstract-schema-name> tag at all, instead of just using the EJB name? If so, you're smarter than I am.
 
reply
    Bookmark Topic Watch Topic
  • New Topic