| Home : Java : EJB |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
EJB Listings
|
|
Total:
41 | Displaying: 21 - 30 | Pages: << 1 2 3 4 5 >> |
|
|
|
This article completes the three-part series on the XMLBeans package (see Resources for the previous two articles in the series). Simply put, XMLBeans can transform a JavaBean in memory into an XML document, or can transform an XML document (of a particular form) into a running JavaBean. Figure 1 shows an extremely simplified schematic of the concept.
Updated: 04/13/2005
|
|
|
The Enterprise JavaBeans component is built around business objects session beans representing different parts of a business model and entity beans representing persistent data in a database. When creating dynamic content, you can reuse these objects by employing tags and custom tags within JavaServer Pages (JSP).
Updated: 04/13/2005
|
|
|
If you've ever used Microsoft's very popular Active Server Pages (ASP) then you'll have a good idea of what JSP is. It consists of HTML or XML markup into which special tags and code blocks are inserted. The code is executed on the server and the result is a dynamic page that is returned to the client browser. Although JSPs are simple to build they have at their disposal the full power of object-oriented Java and the Java Server API.
Updated: 04/13/2005
|
|
|
Today, more and more developers want to write distributed transactional applications for the enterprise, and leverage the speed, security, and reliability of server-side technology. One approach is to use a multitiered model where a thin-client application invokes business logic that executes on the server. Normally, thin-client multitiered applications are hard to write because they involve many lines of intricate code to handle transaction and state.
Updated: 04/13/2005
|
|
|
Software can never be tested sufficiently, and testing usually starts too late, particularly for J2EE TM applications. Since components often behave differently when they are alone than when they have been assembled, testing each component individually before two or more components are joined together ensures each piece of code in a J2EE application will work as it was designed to do.
Updated: 04/13/2005
|
|
|
There is a fundamental problem facing enterprise developers today. Writing distributed business applications is difficult. Writing any large application is difficult. This is compounded if the application is distributed, or lives in multiple pieces on a network. This is further compounded if the application must execute its business logic in a guaranteed, reliable fashion. Another complication that enterprises face is that they are themselves fundamentally.
Updated: 04/13/2005
|
|
|
Testing EJB is different Container matters Enterprise Java Beans, or EJBs, cannot be tested on their own as can plain Java classes. There are additional steps to deploy them to an EJB container before they can be tested. This means that our testing process must include the additional process of deployment and re-deployment of EJBs. The deployment must be automated as well. There are some arguments on the differences between running the EJB test client inside.
Updated: 04/13/2005
|
|
|
Java is an object-oriented language, which means it follows the principles of object-oriented programming, such as encapsulation, inheritance, and polymorphism. (Inheritance and polymorphism pretty much go together, so they are often simply referred to as inheritance, which is what I will do in these articles.) These are great principles and can be used to represent relationships between objects in very powerful ways.
Updated: 04/13/2005
|
|
|
Tomcat is a worldwide-used Web server for JSP and servlets. It runs with proper the JAVA Runtime and supports object-oriented Web application deployement. Running Tomcat is simple; just install Tomcat with the default installer given on Tomcat's website. No one knows fully how dangerous Tomcat is. The major security risks with Tomcat Web applications are the following: Tomcat's JSP or bean called in JSP can do the following highly risky tasks.
Updated: 04/13/2005
|
|
|
I worked with the JavaBeans XML Persistence API for more than a year before I realized that I could use it to serialize any object. When its default mechanisms did the trick, the API produced compact, version-resilient archives. When they failed, however, I thought that extending the API wasn't worth the trouble. This misconception was unfortunate because it kept me from using the full potential of XML persistence. With just a little knowledge.
Updated: 04/13/2005
|
|
|
EJB Listings
|
|
Total:
41 | Displaying: 21 - 30 | Pages: << 1 2 3 4 5 >> |
|
|
