| Home : Java : J2EE |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
J2EE Listings
|
|
Total:
100 | Displaying: 41 - 50 | Pages: << 1 2 3 4 5 6 7 8 9 10 >> |
|
|
|
What is JMX? If you think that it is one more collateral framework, not deserving your attention, you are deeply mistaken. Java Management eXtensions (JMX) is actually one of the most basic functional parts of modern process of applications development and management. Today, this technology is used by such manufacturers of J2EE-servers, as JBoss, WebLogic, and many others. Below, we shall consider the structure of JMX and examples of use of this technology. After perusal of this material, you will be able to implement JMX functionality in own applications without problems.
Updated: 05/18/2005
|
|
|
Since JRun 3.0 emerged on the arena of the Web application servers, migrating existing applications from JRun 2.3 to JRun 3.0 is becoming one the hottest topics in the developers' community. The article explores possible migration routines as well as their pros and cons. How to Deploy with JRun 2.3 . How to Re-deploy with JRun 3.0 . The J2EE Approach . Migrate Your Application Using an \"as is\" Approach .
Updated: 05/18/2005
|
|
|
If you have been part of the computer programming world for any length of time you are sure to have heard of, and probably used, Java 2 technologies. Java 2 is Sun Microsystems's development platform for creating end—to—end network applications and embedded applications. Two Java platforms exist, Java 2, Standard Edition (J2SE) and Java 2, Enterprise Edition (J2EE). The J2SE platform contains essential items like compilers, tools, API's, and runtimes for creating and deploying applications as well as applets created with the Java language. The J2EE platform includes support for Web Services and the infrastructure for building secure and robust business applications.
Updated: 05/18/2005
|
|
|
This article begins a series. The first three articles explain the fundamentals of XPath queries, XSD schemas, and XSLT. The following articles look at how well these standards are supported by the .NET framework and what are the most important namespaces and types. This series of articles is not intended as a comprehensive description of all the .NET types around XML. The goal, rather, is to provide a good introduction so you understand the XML capabilities of the .NET framework and can start leveraging them for your current .NET projects.
Updated: 05/18/2005
|
|
|
This article begins a series. The first three articles explain the fundamentals of XPath queries, XSD schemas, and XSLT. The following articles look at how well these standards are supported by the .NET framework and what are the most important namespaces and types. This series of articles is not intended as a comprehensive description of all the .NET types around XML. The goal, rather, is to provide a good introduction so you understand the XML capabilities of the .NET framework and can start leveraging them for your current .NET projects.
Updated: 05/18/2005
|
|
|
With Jim Rhyne, Legacy Applications Architect at IBM about using legacy data within Web services.Rosemarie Graham spoke with Jim Rhyne, Legacy Applications Architect at IBM about using legacy data within Web services. Thank you Jim for taking the time to speak with Developer.com. A lot of our readers are developing or at least considering Web services for their companies so we will focus our attention there.
Updated: 05/18/2005
|
|
|
This material is from the book Java Web Services Architecture, written by James McGovern, Sameer Tyagi, Michael Stevens, and Sunil Mathew, published by Morgan Kaufmann Publishers. In our last article, we have examined the properties, transactions, and specifications for transaction managers in the current Java/J2EE environment. Most, if not all, of today's Java transaction managers implement the flat transaction model, in compliance with JTA and/or JTS.
Updated: 05/18/2005
|
|
|
Most enterprise applications have to interact heavily with their back-end databases. To make such interactions possible and make them efficient and fast, enterprise application developers create a \"persistence layer\" between the application and underlying database, which takes care of storing data from application to the database and retrieving it back, alongside updating and deleting it. In J2EE-based enterprise applications, this persistence layer consists of Java classes that map objects to data and vice versa. This layer is often built using JDBC, entity beans, JDO, and so forth.
Updated: 05/18/2005
|
|
|
Using XDoclet will enable you to work more efficiently within the J2EE framework. You will have a simpler view of your beans and the relationships between them, and many of the annoyances will be taken out of your development. This article will discuss the XDoclet tool, how to use it, and how to extend it. In this article, we will create a session bean that uses the Javadoc tags, and run XDoclet on the bean.
Updated: 05/18/2005
|
|
|
Java applications are often deployed in an environment where future expansion of the user base is anticipated. As a result, some care is taken in choosing an architecture and component model that can allow scalability to higher user loads, often through the use of additional servers, forming an application server cluster, sometimes also called \"horizontal scalability\".
Updated: 05/18/2005
|
|
|
J2EE Listings
|
|
Total:
100 | Displaying: 41 - 50 | Pages: << 1 2 3 4 5 6 7 8 9 10 >> |
|
|
