| Home : Java : Core Java |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Core Java Listings
|
|
Total:
28 | Displaying: 21 - 28 | Pages: << 1 2 3 |
|
|
|
Purpose. These notes were written to fill in missing or weak topics in textbooks that I've taught from. Many pages are useful for reference, but not as an ordered tutorial. Some pages are still rough drafts, and now that I'm back to teaching Java I'm working on them a little every week and considering putting some of them into an orderly tutorial form
Updated: 03/24/2005
|
|
|
The corporate firewall is a double-edged sword. It helps prevent unauthorized access to the corporate Web services, but can disable access for legitimate clients. Due to the number of safety measures taken by system administrators, HTTP has become the universal entry mechanism to the corporate network. Where technologies such as CORBA and DCOM have failed because of the firewall, technologies such as SOAP have been developed to provide safe and reliable access through firewall protection. In this article, we will explore an alternative to SOAP, the use of Java objects over HTTP. In addition, we will use J2EE servlet technology as server-side middleware to the business data
Updated: 03/24/2005
|
|
|
Distinguish appropriate from inappropriate techniques for providing acess to a legacy system from Java technology code given an outline description of that legacy system"
Updated: 03/24/2005
|
|
|
Very few project teams have the benefit of being able to start from scratch, something often referred to as greenfield development. Instead, the cold, hard truth of the matter is that most Java project teams need to take into account existing legacy systems when they are developing new applications. Perhaps you need to access an existing inventory control system, a legacy customer database, or a mainframe-based security access control service. If so, then you have a legacy integration issue, often called Enterprise Application Integration (EAI) issue, on your hands. The advantage to your team is that if the legacy systems are reasonably well designed, then you can take advantage of significant amounts of existing functionality. However, if the legacy systems aren't well designed, or at least not designed with integration in mind, then you will find that your integration efforts are a significant portion of your project. This is particularly true when adequate documentation isn't available or when the owners of the legacy systems are unwilling to work with your team (never underestimate the effect of politics on your project).
Updated: 03/24/2005
|
|
|
Does your IT organization deliver enterprise applications efficiently and cost-effectively? BEA WebLogic Server 8.1 provides an industrial-strength application infrastructure for developing, integrating, securing, and managing distributed service-oriented applications. By simplifying and unifying the enterprise infrastructure, IT organizations can now deliver greater value in less time, at reduced cost to the overall business
Updated: 03/24/2005
|
|
|
Because most developers build their Web applications in a nonclustered environment, those applications often break when moved into a cluster. In this article, the second of two, Abraham Kang explains the programming, setup, and management issues related to clustering. With this knowledge, you will be able to write code that is clusterable from its inception, thus avoiding pitfalls later.
Updated: 03/24/2005
|
|
|
Java In A Nutshell
Updated: 03/11/2005
|
|
|
This is 32 page presentation on The Object-Oriented SDLC and JDeveloper.
Updated: 02/21/2005
|
|
|
Core Java Listings
|
|
Total:
28 | Displaying: 21 - 28 | Pages: << 1 2 3 |
|
|
