overview.xtp

RESIN 3.2 最新源码

<ul>
<li>See <a href="ejb.xtp">Resin EJB 3.0</a> documentation</li>
<li>See <a href="amber.xtp">Amber (JPA)</a> documentation</li>
</ul>

<p>Resin's EJB support is fully integrated with Resin-IoC and WebBeans.
This integration means you can use only the EJB capabilities you need
without the overhead of .ear packaging.  (Although, .ears are
fully supported.)  A servlet, for example, can use EJB's
@TransactionAttribute without any special packaging.</p>

</s1>

<s1 title="Server Push (Comet)">

<ul>
<li>See <a href="resin-comet.xtp">Resin Comet</a> documentation.</li>
</ul>

<p>As web users are expecting dynamic responses from web sites, the
server push HTTP processing model has become important.  Also called
Comet, server push sends event or streaming data from the server
to the client without waiting for a client poll.</p>

<p>Resin's Comet support focuses on solving the concurrency issues around
server push.  Since the servlet is now responding to events from internal
services as well as managing HTTP data, the synchronization issues become
more complex.  The Resin Comet API is designed to cleanly separate the
concurrency roles, letting the servlet continue to operate as a
single-threaded request, while letting the event services send asynchronous
messages.</p>

<p>JavaScript browsers and Flash applications are both supported by
Resin's Comet.  Flash can take advantage of Resin's Hessian support
to stream binary-encoded events.</p>

</s1>

<s1 name="jsp" title="JSP 2.1 (Java Server Pages)">

<ul>
<li>See <a href="jsp.xtp">Resin JSP</a> documentation</li>
</ul>

<p>Resin's JSP implementation is tightly integrated with the JSTL
and JSF implementations.  Because of the tight binding, Resin can
generate optimized JSP code, improving performance, reducing code size
and reducing memory consumption.</p>

<p>Even JSP tag libraries can run faster with Resin's JSP.  Resin
bytecode-analyzes your tag libraries to determine which capabilities
your actually using, and generates only that code necessary to run the
features you're using.</p>

<p>The JSP implementation aggressively reuses your tag library instances,
reducing memory consumption and improving performance.  Because of Resin's
reuse, application libraries must strictly follow the JSP tag
specification.</p>

<p>Resin-IoC beans are always available through JSP EL expressions.
This IoC integration means your custom components and beans are directly
accessible to your HTML generating code.</p>

</s1>

<s1 name="jstl" title="JSTL 1.01 (Java Standard Template Library)">
<ul>
<li>See <a href="jstl.xtp">Resin JSTL</a> documentation</li>
</ul>

<p>Resin's JSTL works together with its JSP implementation to provide
efficient, generated Java code.  Since Resin's JSP is fully JSTL-aware,
it can implement the JSTL tags directly in Java code, without involving
the overhead of the JSTL tag libraries.</p>

</s1>

<s1 name="servlet" title="Servlet 2.5">
<ul>
<li>See <a href="servlet.xtp">Resin servlet</a> documentation</li>
</ul>

<p>Since the servlet engine of Resin is built on a Resin-IoC foundation,
servlets can use WebBeans dependency injection, event observation, and
interception.  Remember that Resin-IoC is fully integrated with its
EJB support?  By transitivity, Resin servlets automatically have access
to EJB transaction aspects without any extra overhead.</p>

<p>Remote services are tied into servlet capabilities as well.  Because remote
services are URL-based, they naturally fit into the the familiar servlet
processing model.  There's no need to introduce complexities like standard
EJB deployment or add extra frameworks just to expose a service as a URL.</p>

</s1>

<s1 title="Resin Embedding">
<ul>
<li>See <a href="resin-embedding.xtp">Resin embedding</a> documentation</li>
</ul>

<p>Resin embedding is a lightweight facade over the core Resin server
suitable for automated testing frameworks and IDE environments.  With
Resin's embedded testing interface, your tests can send HTTP requests directly
to the server, skipping the overhead of TCP connections, and saving
time on test setup and teardown.</p>

<p>The embedded API gives you hooks into Resin-IoC, so you can
inject mock services into your tests, and still ensure that your application
is tested in the full application server environment.  Since integration
testing uses the actual, deployment environment, elusive production bugs
are easier to catch and destroy.</p>

</s1>

<s1 title="Resin Remoting">
<ul>
<li>See <a href="resin-remoting.xtp">Resin remoting</a> documentation</li>
</ul>

<p>Resin remoting builds on the strengths of the Servlet architecture.
As developers turn away from complicated remoting frameworks,
the simplicity and elegance of the Servlet model becomes more appealing.
Multithreaded, IoC-enabled, designed for HTTP and the web's URL
architecture, well-known, well-documented, and well-integrated with
application servers, the Servlet model has enjoyed phenomenal success.</p>

<p>Services expose remote APIs with the same interfaces and classes their
clients will use, taking advantage of the Java compiler to enforce
protocol compatiblity.  Since Resin remoting protocols are available using
a simple driver API based on Servlets, your services can choose the
protocol to expose at deployment time, whether its a fast, binary
wire-protocol like Hessian, or an XML-based wire-protocol like SOAP.
Resin remoting clients select the wire-protocol matched with service API,
and register with Resin-IoC/WebBeans, so
application code can obtain the client proxy with simple, typed
dependency injection.</p>

</s1>

<s1 title="JPA (Java Persistence Architecture)">
<ul>
<li>See <a href="amber.xtp">Resin's Amber</a> documentation</li>
</ul>

</s1>

<s1 title="Resin Watchdog">

<ul>
<li>See <a href="resin-watchdog.xtp">Resin watchdog</a> documentation</li>
</ul>

<p>The Resin watchdog service manages each Resin instance, allowing for
graceful recovery and restart from critical server deadlocks and crashes.
As a management capability, it offers a centralized interface for starting,
stopping, and checking the status of multiple JVM instances.  Because the
watchdog is well-placed to gather information, it is responsible for
management and logging of the server's debugging or warning messages.</p>

<p>For unix systems, the watchdog also improves system security.  While
the watchdog will run as the root user, Resin JVM instances run as
low-authorization users, protecting your system from application bugs
and security holes.</p>

<p>As a side benefit of the watchdog, JVM parameters like heap settings,
agent configuration, remote JMX and system properties can be configured
in the resin.xml itself.  The watchdog can read the same resin.xml as
the server itself, putting all configuration relevant to the server in
one location.</p>

<p>For more complicated configurations like an ISP setting, the watchdog
can use a separate configuration file readable only by root.  The watchdog
will launch Resin JVMs with assigned resin.xml files, ports, and user
assignment, protecting each Resin JVM user from each other.</p>

</s1>

<s1 name="jms" title="Messaging (JMS 1.1)">

<ul>
<li>See <a href="resin-messaging.xtp">Resin messaging</a> documentation</li>
</ul>

<p>Resin's messaging focuses on simplifying the use and deployment of
messaging applications.  At the core, a messaging system is really just
a queue with extra reliability and performance features like persistence,
transactions, and clustered distribution.  So Resin provides
the standard queueing APIs like the JDK <code>BlockingQueue</code> as
facades to the JMS API.</p>

<p>On the receiving end, <code>MessageListener</code> implementations are
just Java services implementing a single <code>onMessage</code> method to
receive the message, so there's no need for complications.  The only
configuration needed is a binding between the service class and the
queue it wants to receive messages from.  Three lines of XML is sufficient
for that binding, with no need for any extra packaging.</p>

<p>Of course, the message listeners are can use all Resin-IoC capabilities,
including injecting JPA <code>EntityManager</code> for database management, or
other queues to filter and pass the message along.</p>

</s1>

<s1 name="jta" title="Transactions (JTA 1.0.1b)">

<p>Resin's transaction manager handles full two-phase XA transaction
suppport, including transaction logging for reliable transaction recovery.
The transaction capabilities are integrated throughout Resin, so your
databases, JCA connections, and EJBs work together.  Since Resin's
<code>UserTransaction</code> and <code>TransactionManager</code> are
registered with Resin-IoC, injecting these managers into any IoC-enabled
component is just adding an @In annotation.</p>

</s1>

<s1 name="os" title="Operating Systems">

<p>Resin and Resin-Professional are tested and supported on
the following operating systems:</p>

<ul>
<li>Linux</li>
<li>Solaris</li>
<li>Windows</li>
<li>Mac OS X</li>
</ul>

<p>Resin is known to work on the following operating systems:</p>

<ul>
<li>AIX
</li><li>HP-UX
</li><li>Free-BSD
</li></ul>

<p>
Resin is used on these operating systems, however there may or may not be
difficulties with Apache integration, and the JNI code that Resin uses to
increase performance may not be available.
</p>

</s1> <!-- os -->


</body>
</document>