 |
Certified J2EE
1.3 Compatible |
|
|
| |
JRun 4 was one of
the first application servers to become certified J2EE 1.3
compatible, demonstrating the Macromedia commitment to J2EE.
This is your guarantee that any J2EE-compatible application
will run with JRun 4. |
|
|
| |
|
|
|
|
Built-in Web
Services Support |
|
|
| |
Building web services
in JRun 4 is as simple as editing a deployment descriptor
to expose your regular Java classes or Enterprise JavaBeans
as web services. Consuming web services is equally easy: JRun
4 automatically generates Java proxies for web services based
on their WSDL files. The JRun Web Service Tag Library can
also be used to dynamically invoke web services from JavaServer
Pages (JSPs). |
|
|
| |
|
|
|
|
Hot Deployment
and Hot Modification |
|
|
| |
In JRun 4, deploying an application is as simple as copying
an EAR, JAR, WAR, or RAR file to the server directory. JRun
4 automatically senses the new file, deploys it, and makes
it available in the target server—without restarting
the server.
During development, you can hot modify any application
component (servlets, JavaServer Pages, Enterprise JavaBeans,
Java classes, deployment descriptors). Your changes take
effect immediately—there's no need to restart the server,
ever.
|
|
|
| |
|
|
|
|
Superior EJB
2.0 Support |
|
|
| |
The JRun 4 EJB container
has been redesigned to provide superior support for the new
EJB 2.0 features, including local interfaces, message-driven
beans, and the new Container Managed Persistence (CMP 2.0). |
|
|
| |
|
|
|
|
JINI-Based Enterprise-Class
Clustering |
|
|
| |
JRun 4 provides
enterprise-class server clustering, allowing load balancing
and automatic fail-over at all levels. In-memory session replication
ensures that state information is preserved. An objects' state
is also replicated in an optimized manner to provide the highest
level of reliability while maintaining performance. |
|
|
| |
|
|
|
|
JMX Service-Based
Architecture |
|
|
| |
All the JRun 4 features
(EJB container, web container, logging, etc.) are implemented
as JMX services (called MBeans) plugged into the JRun kernel.
This elegant service-based architecture provides both a highly
customizable (you use only the services you need) and an easily
extensible (you can create your own custom services) deployment
platform. |
|
|
|
EJB Development
and Deployment Tool |
|
|
| |
The Enterprise
Deployment Wizard streamlines the process of developing and
deploying Enterprise JavaBeans. With its new O/R mapping capabilities
for CMP 1.1 and CMP 2.0, you can generate and deploy a fully
functional entity bean in minutes. |
|
|
| |
|
|
|
|
Macromedia Flash
Remoting |
|
|
| |
JRun 4 provides
native connectivity to Macromedia Flash, enabling the easy
exchange of data. Macromedia Flash communicates with JRun
4 using the Action Message Format (AMF) over HTTP, providing
lightweight binary transfer of data between the Macromedia
Flash UI and JRun 4. Native Macromedia Flash connectivity
allows you to access EJBs, Java classes, and MBeans with ease,
speed, and security. |
|
|
| |
|
|
|
|
New JRun Management
Console |
|
|
| |
The redesigned,
JMX-enabled JRun Management Console (JMC) provides an easy-to-use,
intuitive graphical user interface to manage your local and
remote JRun servers. Using the JMC, you easily create servers,
define clusters, manage applications, and implement JAAS-based
security. |
|
|
| |
|
|
|
|
XDoclet Integration |
|
|
| |
XDoclet is a popular
Java utility that can greatly simplify the development of
J2EE components (such as Enterprise JavaBeans, servlets, and
custom tags) by allowing you to maintain your component meta-data
using Javadoc-style comments in a single source file. XDoclet
is now wholly integrated into JRun 4. JRun 4 senses modifications
to the source file and automatically generates the auxiliary
files (such as interfaces and deployment descriptors). |
|
|
| |
|
|
|
