| Topic |
Changes |
| Installing JRun |
- The JRun 4 Web Server Configuration tool replaces the JRun 3.1 Connector Wizard.
- JRun 4 requires that IIS be running in order to use the Web Server Configuration tool. JRun 3.1 required that IIS not be running.
- JRun 4 is contained in a single file, jrun.jar.
|
| Starting and stopping servers |
You use the Server Control Panel to start and stop servers. The Server Control Panel is configured in the servers.xml file in the jrun_root/lib directory. For more information about starting servers, see "Starting and stopping JRun servers". |
| Configuring servers |
In JRun 4, JVM properties are set globally in the jrun_root/bin/jvm.config file for all JRun servers in an installation. |
| Configuring web applications |
- You do not use the JMC to modify web.xml files. You edit web.xml files by hand in a text editor.
- JRun 4 replaces the
use-webserver-root property used in JRun 3.1 with a more generalized way to map virtual paths. Use a virtual path only if you use the web server root exclusively. If you do not use a virtual path, JRun searches the web application context root and then the web server root. Virtual path mappings in a jrun-web.xml file in a web application's WEB-INF directory let you map a resource path to a physical system path that might be outside of the web application context root. For example, the following entry sets a virtual path to the c:/InetPub/wwwroot directory:
<virtual-mapping>
<resource-path>/*</resource-path>
<system-path>c:/InetPub/wwwroot</system-path>
</virtual-mapping>
- The following servlet mappings are no longer supported:
*.jrun = invoker *.shtml = ssifilter *.thtml = template
- JRun 4 does not support servlet chaining via comma-separated lists. To achieve equivalent functionality, implement chains as filters.
- You cannot globally map JSP custom tag libraries, as you could the JRun Tag Library in the JRun 3.1 global.properties file.
If you place a copy of the jruntags.jar file in the WEB-INF/lib directory of your web application, you do not need to change existing JSP tag library directives for the JRun Tag Library. You must place tag library classes in a JAR file in the web_app/WEB-INF/lib directory or place loose class files in the WEB-INF/classes directory. A JSP tag library directive's uri attribute starts with a forward slash and is relative to the root of the web application containing the JSP; the tag library directive can point to a TLD file directly or to a JAR file containing a TLD file. If there is a mapping for a TLD in the web.xml file, JRun uses that mapping.
- To use a context-root of "/" for a web application, you must delete the default-ear.ear file in the deploy directory of the same JRun server or change the "/" context-root in its application.xml file.
|
| Developing web applications |
- JRun 4 does not support non-Java languages, including JavaScript, in JSP page directive language parameters.
- JRun 4 does not support the JRun Tag Library xslt and query2xml tags. Macromedia recommends that you use the new JSP Standard Tag Library rather than the JRun Tag Library for new projects; for more information, see jakarta.apache.org/taglibs/doc/standard-doc/intro.html.
- The flush attribute of the jsp:include action is now set to false by default. It was formerly true by default, and false was not an acceptable value.
- The syntax for JSP runtime expressions is different for XML-based JSPs, which are supported in JRun 4. Use the following syntax:
<ct:theTag name="%= var %"/>
- The
ServletContext.getRealPath() method requires that the string argument for the file path begin with a forward slash (/).
- Server -side includes are no longer supported in JSPs. You must change <servlet> and <include> tags to jsp:include actions or
include directives.
- The Apache TCPMonitor program included with JRun 4 replaces the JRun 3.1 Sniffer program. For more information, see JRun Programmer's Guide.
|
| Deploying J2EE modules |
<servlet>
<servlet-name>JSPServlet</servlet-name>
<servlet-class>jrun.jsp.JSPServlet</servlet-class>
<init-param>
<param-name>keepGenerated</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
|
| Using JNDI lookups |
- You use the following syntax to specify an EJB name in a JNDI lookup:
ejb name listed in ejb-jar.xml file or java:ejb name listed in ejb-jar.xml file In JRun 3.1, the syntax was: java:comp/env/ejb
- You use the following syntax to specify a data source name in a JNDI lookup:
data source name In JRun 3.1, the syntax was: java:comp/env/jdbc/data source name
- You use the following syntax to specify a JavaMail session in a JNDI lookup:
mail/session name
In JRun 3.1, the syntax was: java:comp/env/mail/session name
- You use the following syntax to specify a JMS connection factory in a JNDI lookup:
jms/connection factory name
In JRun 3.1, the syntax was: java:comp/env/jms/connection factory name
|
