User: jules_gosnell Date: 02/02/18 23:48:15 Modified: jetty README Log: about time this was updated Revision Changes Path 1.8 +48 -69 contrib/jetty/README Index: README =================================================================== RCS file: /cvsroot/jboss/contrib/jetty/README,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- README 19 Jan 2002 00:49:50 -0000 1.7 +++ README 19 Feb 2002 07:48:15 -0000 1.8 @@ -1,5 +1,3 @@ -WARNING: This needs updating... - This plugin integrates Jetty with JBoss. @@ -12,92 +10,73 @@ The integration basically maps Jetty's lifecycle to that of a JBoss Service, exposes Jetty's webapp deployment functionality to -AbstractWebContainer, and bridges the gap between Jetty's -authentication interfaces and JBossSX, the JBoss security module. - +AbstractWebContainer, and integrates the following functionality: -There is a 'devel' target in the buildfile which should rebuild and -deploy the plugin then run the WebIntergration test suite. You need a -JBoss up and running. +log: +---- -Work in progress ----------------- +We supply a Jetty Logger which maps to the JBoss logging scheme -JSPs - compiling JSPs is tricky because Jasper needs all necessary -jars on it's classpath. +security: +--------- -Jetty is only aware of the classes and jars within the war - so if you -are sharing classes across an ear, this is currently not supported. +We supply a Jetty UserRealm which maps a Jetty SimplePrincipal onto a +JBoss UserPrincipal and provides the necessary authentication and +authorisation API. (JAAS is supported). -I have the following coomented out of WebIntegrationUnitTestCase.java: +session: +-------- -testUserTransactionServlet() -testIncludeEJB() +STILL UNDER DEVELOPMENT - We extend Jetty's HttpSession management to +support distributable sessions by reusing infrastructure available +from JBoss (JBossHA, EJBs etc). Various strategies are configurable in +jetty.xml. -I'm working on them. +xml: +---- +We provide local resolution for a number of webapp descriptors and are +responsible for parsing said descriptors and sharing results with +AbstractWebContainer, whence it may set up e.g. JNDI bindings +(java:/comp/env) etc. -PERSISTANT/DISTRIBUTED HTTPSESSION MANAGEMENT: Now that Jetty4 is in -CVS this is my main goal. I'm still just tidying up the last few -issues with JBos3/Jetty4 at the moment.... - -EMACS users +DEVELOPMENT ------------ -I have the following in my .emacs.... - - -;;----------------------------------------------------------------------------- -;; this should be useful - automagically rebuild after a file is saved - -;; list of (REGEXP COMPILE-COMMAND) - -(defvar autocompile-dirs - '() - ) - -(defun register-autocompile (regexp action) - (setq autocompile-dirs - (cons (cons regexp action) autocompile-dirs))) +There is a 'devel' target in the build.xml which should rebuild and +deploy the plugin then (perhaps) run the WebIntergration test +suite. You need a JBoss up and running. -(defun autocompile (dir regexp command) - (register-autocompile - (concat dir regexp) - (eval (list 'lambda (list 'buffer) - (list 'compile (list 'concat "cd " dir "; " command)))))) +RUNNING +-------- -;; go through an alist of (regexp . value) pairs with a key until we -;; find the first matching regexp - return this pair -(defun match-assoc (key alist) - (if (not (null alist)) - (let* ((head (car alist)) - (rgxp (car head)) - (actn (cdr head))) - (if (string-match rgxp key) - head - (let ((tail (cdr alist))) - (match-assoc key tail)))))) +Just start JBoss3. Jetty should deploy from the jetty-plugin.sar. The +HTTP server will be on 8080 by default. This and other proprietary +features are configurable in jetty.xml which you will find in +jetty-plugin.sar. Unpack it, make your changes, repack it and copy it +back whence you found it. JBoss will notice, reload and restart Jetty +with it's new configuration. If you hit localhost:8080/ with your +browser, don't expect anything to be there, unless you have deployed +it yourself. If you haven't you will see a 404 - DO NOT BE ALARMED, +THIS IS CORRECT BEHAVIOUR. +CONFIGURATION +------------- -;; what if a compilation is already running ? +The proprietary aspects of Jetty and webapps may be configured in +jetty.xml and META-INF/jetty-web.xml respectively. The file format is +an XML veneer over Jetty's native Java API, so have your JavaDoc to +hand - for further info see jetty.mortbay.org. -(defun do-autocompile () - (interactive) - (if (and - (stringp (buffer-file-name)) ;we are a file/dir - (not (car (file-attributes (buffer-file-name)))) ;we are a file - ) - (let* ((filename (expand-file-name (buffer-file-name))) - (action (cdr (match-assoc filename autocompile-dirs)))) - (if action - (funcall action (current-buffer)))))) +The non-proprietary parts are configurable through the standard J2EE +webapp descriptors. -(add-hook 'after-save-hook 'do-autocompile) +The Jetty MBean is configures via META-INF/jboss-service.xml in +jetty-plugin.sar. -;; and now we say what we want autocompiled... +Enjoy, -(autocompile (expand-file-name "~/cvs/JBoss/3.0/testsuite/") "src/.*\.java$" "./build.sh -Djavac.debug=true -Dtest=WebIntegrationUnitTestCase -emacs one-test") -(autocompile (expand-file-name "~/cvs/JBoss/3.0/plugins/jetty/") "src/.*\.java$" "./build.sh -Djavac.debug=true -emacs devel") +Jules ([EMAIL PROTECTED])
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
