SCJA
Flashcards for SCJA exam
Terms
undefined, object
copy deck
- Java Native Interface
- A programming framework that allows Java code running in the JVM to call and be called by native applications and libraries written in other languages.
- Java Activation Framework
- used for delivering complex attachments along with email
- Java Naming and Directory Interface
- An API for directory service that allows clients to discover and lookup data and objects via a name.
- Java Application Descriptor file
- Describes the MIDlets (Java ME applications) that are distributed as JAR files
- Polymorphism
- Anytime I need an object, any type or sub-type of that object will do
- JavaMail
- API for sending email (related to JAF, SMTP)
- Encapsulation
- The idea of protecting data, in the form of instance variables by making them private.
- varargs
- allows a developer to declare that a method can take a variable number of parameters for a given argument. The vararg must be the last argument in the formal argument list.
- Universal Description Discovery and Integration
- A platform independent XML registry for web services.
- Workload Managed Environment
- A cluster of two or more JVMs, deployed potentially across many computers, supporting and fulfilling the processing requirements for a given J2EE application.
- Java Messaging Service
- allows J2EE applications to place messages on a queue and read messages off of a queue
- Singleton Design Pattern
- A design pattern that is used to restrict instantiation of a class to one object
- static imports
- Enables programmers to refer to the imported static members of a class as if they were declared in the class that uses them.
- Relational DataBase Management System
- DBMS in which data is stored in the form of tables and the relationship among the data is also stored in the form of tables.
- Stateless Session Bean
- Coordinates the activities of entity beans and other business objects.
- Simple Object Access Protocol
- A protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. SOAP forms the foundation layer of the web services protocol stack providing a basic messaging framework upon which abstract layers can be built.
- Java Server Faces
- A Java-based Web application framework that simplifies the development of user interfaces for Java EE applications.
- Container Managed Interface
- Associated with database interactions. Its life-cycle is controlled by the EJB container. It is responsible for persisting the bean's fields to and from the database.
- fat clients
- java applet, standalone java application
- Generics
- allows Applications to create classes and objects that can operate on any defined types.
- JTA
- Java Transaction API
- Web Services Description Language
- An XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
- Bean Managed Persistence
- Associated with database interactions. Its life-cycle is triggered by the EJB container through notifications to the bean's implementation class, but the actual persistence to and from the database is left to the bean itself.
- Stateful Session Bean
- Maintains internal data in form of instance variable which is tied to the user who created it. Not being reliable in a workload managed environment.
- Information Module Profile (IMP)
- Used for designing J2ME applications without normal user interfaces
- Java DataBase Connectivity
- An API for the Java programming language that defines how a client may access a database.
- RMI Over IIOP
- Enterprise JavaBean's communication method
- Java API for XML based RPC
- provides Java programs the ability to invoke methods on other Java components remotely using a web services based architecture
- Context
- A connection to a JNDI server
- Enterprise JavaBeans
- A managed, server-side component architecture for modular construction of enterprise applications.
- Autoboxing
- the automatic conversion the Java compiler makes between the primitive (basic) types and their corresponding object wrapper classes
- Model-View-Controller
- Decoupling data access, business logic, and data presentation and user interaction