User: jules_gosnell
  Date: 02/04/11 13:44:13

  Modified:    jetty    FAQ
  Log:
  add stuff about sar
  
  Revision  Changes    Path
  1.6       +21 -0     contrib/jetty/FAQ
  
  Index: FAQ
  ===================================================================
  RCS file: /cvsroot/jboss/contrib/jetty/FAQ,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- FAQ       10 Apr 2002 22:39:26 -0000      1.5
  +++ FAQ       11 Apr 2002 20:44:13 -0000      1.6
  @@ -187,6 +187,27 @@
   Let me know of any problems and I shall look into them ASAP.
   
   
  +Why is Jetty packaged in a .SAR ?
  +----------------------------------
  +
  +The bad thing about a .sar, is that it makes it awkward for a user to
  +edit jetty's configuration.
  +
  +The good thing is that if the Jetty team roll out a new release, we
  +can package it all up in a sar, which you just copy into ./deploy.
  +
  +We are going with sars for the moment. If you really don't like it
  +simply do the following:
  +
  +Unpack the sar somewhere.
  +move all the jars inside into ./lib
  +copy the jboss-service.xml to e.g. ./deploy/jetty-service.xml
  +
  +This should have exactly the same effect as the .sar. You can now edit
  +the jetty-service.xml at your leisure and each time you save it, jetty
  +will restart with the new configuration. Be careful though - emacs and
  +vi both write backup files which can upset the JBoss deployer.
  +
   Development
   ------------
   
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to