enhydra
Greetings! I've been looking for a web host that provides JSP along with Beans. I came across one that mentioned it uses Enhydra. I've looked at the Enhydra web page and was left wondering if Enhydra is a replacement Servlet engine for Tomcat? Or, does it need Tomcat to run? Thanks, Eric -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: enhydra
Enhydra uses Tomcat internally. the version of tomcat is very old, though. It depends on what version of Enhydra the ISP is using. If it is the open source one, then it is likely very old indeed. If it is the now defunct Lutris Enhydra EAS, then it would be something like Tomcat-3.2.x. There is a new project called Aonyx which will be Enhydra 5.0 when released. The current version is 5.0beta2. http://sourceforge.net/projects/webdocwf If you want to use Enhydra, that is your best bet since it is actually an active project. Not sure what version of Tomcat it uses internally, though. Jake At 09:47 AM 8/3/2002 +0200, you wrote: Greetings! I've been looking for a web host that provides JSP along with Beans. I came across one that mentioned it uses Enhydra. I've looked at the Enhydra web page and was left wondering if Enhydra is a replacement Servlet engine for Tomcat? Or, does it need Tomcat to run? Thanks, Eric -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: enhydra
Jake, Thanks for the info. I'll download Enhydra and play with it. They are using Enhydra 3.1. Eric On Saturday 03 August 2002 09:59, Jacob Kjome wrote: Enhydra uses Tomcat internally. the version of tomcat is very old, though. It depends on what version of Enhydra the ISP is using. If it is the open source one, then it is likely very old indeed. If it is the now defunct Lutris Enhydra EAS, then it would be something like Tomcat-3.2.x. There is a new project called Aonyx which will be Enhydra 5.0 when released. The current version is 5.0beta2. http://sourceforge.net/projects/webdocwf If you want to use Enhydra, that is your best bet since it is actually an active project. Not sure what version of Tomcat it uses internally, though. Jake At 09:47 AM 8/3/2002 +0200, you wrote: Greetings! I've been looking for a web host that provides JSP along with Beans. I came across one that mentioned it uses Enhydra. I've looked at the Enhydra web page and was left wondering if Enhydra is a replacement Servlet engine for Tomcat? Or, does it need Tomcat to run? Thanks, Eric -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: help is needed --- running enhydra application under tomcat 4
And in my case, the url that I use is http://localhost:8080/Simple/Simple Xin -Original Message- From: Xin Li [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 06, 2001 3:53 PM To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: help is needed --- running enhydra application under tomcat 4 Importance: High Hey, all, I'm trying to make my enhydra application (Simple) running under tomcat 4. Here is what I did so far. Please let me know what I have been missing, since it doesn't work. 1) created a directory structure named Simple/WEB-INF under webapps/ 2) created three directories (classes, lib and output) under WEB-INF 3) copied the classes directory from enhydra application to this classes folder 4) copied enhydra.jar and Simple.jar over to the lib directory 5) copied enhydra app configure file (Simple.conf) under output/conf/ 6) edited WEB-INF/web.xml like this (bear me to write so much in detail): web-app servlet servlet-namesimpleApp/servlet-name servlet-classorg.enhydra.Servlet/servlet-class init-param param-nameConfFile/param-name param-value/home/webapp/xindo/tc4/webapps/Simple/WEB-INF/output/conf/Simpl e.conf/param-value /init-param /servlet !-- The mapping for the default servlet -- servlet-mapping servlet-namesimpleApp/servlet-name url-pattern/Simple/*/url-pattern /servlet-mapping /web-app 7) add Context path=/Simple docBase=Simple debug=0 reloadable=true/ into server.xml 8) took out org.apache.tomcat classes from enhydra.jar Thanks in advance! Xin -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: help is needed --- running enhydra application under tomcat 4
Oh, forgot to mention that I also added the patch to
HttpPresentationServlet.java according to the previous message sent by Dave
Li.
381MultiClassLoader appClassLoader;
382if (lbsContext != null)
383appClassLoader = lbsContext.getClassLoader();
384else {
385 // Not using MultiServer, so must create class loader from scratch
386appClassLoader = new MultiClassLoader(logChannel);
387appClassLoader.setParent(this.getClass().getClassLoader());
388}
-Original Message-
From: Xin Li [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 06, 2001 3:53 PM
To: Tomcat Users List
Cc: [EMAIL PROTECTED]
Subject: help is needed --- running enhydra application under tomcat 4
Importance: High
Hey, all,
I'm trying to make my enhydra application (Simple) running under tomcat 4.
Here is what I did so far. Please let me know what I have been missing,
since it doesn't work.
1) created a directory structure named Simple/WEB-INF under webapps/
2) created three directories (classes, lib and output) under WEB-INF
3) copied the classes directory from enhydra application to this classes
folder
4) copied enhydra.jar and Simple.jar over to the lib directory
5) copied enhydra app configure file (Simple.conf) under output/conf/
6) edited WEB-INF/web.xml like this (bear me to write so much in detail):
web-app
servlet
servlet-namesimpleApp/servlet-name
servlet-classorg.enhydra.Servlet/servlet-class
init-param
param-nameConfFile/param-name
param-value/home/webapp/xindo/tc4/webapps/Simple/WEB-INF/output/conf/Simpl
e.conf/param-value
/init-param
/servlet
!-- The mapping for the default servlet --
servlet-mapping
servlet-namesimpleApp/servlet-name
url-pattern/Simple/*/url-pattern
/servlet-mapping
/web-app
7) add Context path=/Simple docBase=Simple debug=0
reloadable=true/ into server.xml
8) took out org.apache.tomcat classes from enhydra.jar
Thanks in advance!
Xin
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]
--
To unsubscribe: mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]
help is needed --- running enhydra application under tomcat 4
Hey, all, I'm trying to make my enhydra application (Simple) running under tomcat 4. Here is what I did so far. Please let me know what I have been missing, since it doesn't work. 1) created a directory structure named Simple/WEB-INF under webapps/ 2) created three directories (classes, lib and output) under WEB-INF 3) copied the classes directory from enhydra application to this classes folder 4) copied enhydra.jar and Simple.jar over to the lib directory 5) copied enhydra app configure file (Simple.conf) under output/conf/ 6) edited WEB-INF/web.xml like this (bear me to write so much in detail): web-app servlet servlet-namesimpleApp/servlet-name servlet-classorg.enhydra.Servlet/servlet-class init-param param-nameConfFile/param-name param-value/home/webapp/xindo/tc4/webapps/Simple/WEB-INF/output/conf/Simpl e.conf/param-value /init-param /servlet !-- The mapping for the default servlet -- servlet-mapping servlet-namesimpleApp/servlet-name url-pattern/Simple/*/url-pattern /servlet-mapping /web-app 7) add Context path=/Simple docBase=Simple debug=0 reloadable=true/ into server.xml 8) took out org.apache.tomcat classes from enhydra.jar Thanks in advance! Xin -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
tomcat 4 and enhydra 3.1 application
Hi, This is Xin. A new user of tomcat4. I need to run my enhydra application under Tomcat4. I read the discussion about this issue from last month, it is very helpful. However, I still have some questions on the instruction that Dave Li provided. Any help will be appreciated. Question 1: In order to let it work, we need to 1. Patch the Enhydra 3.1 HttpPresentationServlet (see attached) Simple patch to linked up the classloader of the servlet May I know where the patch should be placed? Question 2: in server.xml, we should add Context path=/enhydra docBase=enhydra debug=1/ in it. Should path be /EnhydraWebApp if the folder's name under webapps is EnhydraWebApp? Question 3: There is an example of web.xml (I suppose this web.xml is the file under webapps/EnhydraWebApp/WEB-INF/, is it right?) web-app servlet servlet-name enhydra /servlet-name servlet-class com.lutris.appserver.server.httpPresentation.servlet.HttpPresentationServlet /servlet-class init-param param-nameConfFile/param-name param-value/home/david/work/SkunkWorks/EnhydraWebApp/WebApp/output/conf/We bApp.conf/param-value /init-param /servlet !-- The mapping for the default servlet -- servlet-mapping servlet-nameenhydra/servlet-name url-pattern/*/url-pattern /servlet-mapping /web-app Is there any special requirement about the servlet-name? Can it be something else? Thanks, Xin -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
[Fwd: Enhydra: Enhydra Enterprise Beta 1 Milestone]
FYI, Enhydra Enterprise embeds Tomcat 3.2.1 as it's Servlet and JSP engine. Tomcat is the "best of breed" open source servlet engine with some great developers working on it. Shawn -- Shawn McMurdo mailto:[EMAIL PROTECTED] Lutris Technologieshttp://www.lutris.com Enhydra.Orghttp://www.enhydra.org We are happy to announce the first beta milestone release of Enhydra Enterprise (EE). The prebuilt package is available immediately from http://enterprise.enhydra.org/software/downloads/index.html We encourage evaluators and developers using 'alpha' versions to change to this version. Enhydra Enterprise represents the next generation of application server. It is structured as an "operating system of the Internet," with a kernel that provides some essential facilities and a mechanism for selecting additional services to provide configurable platform functionality. We call the overall structure the Enhydra Services Architecture (ESA). ESA services can be deployed at runtime, and started on demand. This allows the deployer to choose just the services required for a particular deployment, and supports runtime upgrading of services. We aim to offer a trading post for ESA services, and we encourage the contribution of services to the community. In this milestone build we have aggregated a set of API-implementing services on top of the J2SE 1.3 platform, providing many of those APIs required by the J2EE[TM] specification: Servlet 2.2, JSP[TM] 1.1, EJB[TM] 1.1, JNDI[TM] 1.2, JDBC[TM] 2.0 with optional package, JTA[TM] 1.0.1. The configuration includes other APIs, as well as services for deployment, service initialization, and versioned library support. This sample configuration lets you write portable enterprise-scale applications. You can imagine many different configurations and platforms being built on the Enhydra Enterprise project modular architecture. For example, one collection of ESA services might be equivalent to Enhydra 3.x today (perhaps JNDI, JDBC, and Servlet/JSP Container). Another collection of services might be a communications server (perhaps JNDI, SOAP, BXXP, XML/RPC, etc). Finally, yet another might be a messaging server (perhaps JNDI, JMS, etc). When you add a new service to the EE platofrm, that new service can be available to some or all of the applications running on the platform; visibility is under your per-application control. We hope that the ability to create new cross-application services will allow for us all to benefit from radical customization of the concept of what an application server is and can be. What It Does: The beta 1 configuration of EE provides services and APIs needed by web-interfaced applications (as described abAlso, tve). It can be run on a range of deployment configurations, from standalone laptop to multi-tier multi-machine setups. It includes its own web server, or it can be connected to a third-party web server front end. EE also includes the complete Enhydra Application Framework from previous Enhydra versions (most recently Enhydra 3.1); the XMLC ver 2.0 tool for separating web page presentation design from dynamic data programming; and the Kelp toolset for building applications in third-party IDEs. There are several examples included showing how to run J2EE-style applications (including Sun's PetStore demo app) and how to write your own services. We have run this configuration on Windows NT/2000, RedHat Linux 6.1, and Solaris 2.7. The server maintains all configuration information directly in a persistent JNDI namespace for unified management and rapid system restart. Server management is provided through JMX-compatible MBeans, exposed through the Enhydra Web Console. This release begins integration of the Enhydra Authorization and Authentication Library (EAAL) which will provide JAAS-like security throughout the server, even when we incorporate J2SE1.2 support. What It Doesn't Do Yet: Some of the EE Alpha 4 codebase has not yet been ported to the new ESA-based server: most importantly, JMS is not yet available. The J2EE API set is not yet complete. Some capabilities are only partially implemented (in the security work, for example, permission checking is only partially implemented, we need more LoginModules, and the toolset is not yet started). We need to complete the J2EE set of capabilities as a proof of adequacy of the server, and add more samples as proof of flexibility. Specific current versions and limitations are listed in the Release Notes, and should be reflected in the ongoing TODO.txt list. What You Can Do: We hope the Enhydra community will lend a hand in shaking down and building up the new server; there is room for contribution in every part of the effort. As you begin to use the server, please note bugs and what needs to be made better, and tell us on the mailto:[EMAIL PROTECTED] mail list - or fix it yourself (see the various Working Groups to discuss and coordinate you
Re: Enhydra: Enhydra Enterprise Beta 1 Milestone]
FYI, Enhydra Enterprise embeds Tomcat 3.2.1 as it's Servlet and JSP engine. Tomcat is the "best of breed" open source servlet engine with some great developers working on it. Shawn Enhydra needs to update their web site, then, since it talks about 3.1 only (as of yesterday, anyway). David
