[JBoss-dev] CVS update: manual/src/xdocs jbossintro.xml

2001-11-28 Thread Luke Taylor

  User: luke_t  
  Date: 01/11/28 05:59:23

  Modified:src/xdocs jbossintro.xml
  Log:
  corrected bad ulink to jbossgroup support.
  
  Revision  ChangesPath
  3.1   +7 -7  manual/src/xdocs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v
  retrieving revision 3.0
  retrieving revision 3.1
  diff -u -r3.0 -r3.1
  --- jbossintro.xml2001/11/18 20:10:57 3.0
  +++ jbossintro.xml2001/11/28 13:59:23 3.1
  @@ -1,6 +1,6 @@
   ?xml version = 1.0 encoding = UTF-8?
   chapter
  - titleFirst steps/title
  +  titleFirst steps/title
paraAuthors:author
firstnameKevin/firstname
surnameBoone/surname
  @@ -52,12 +52,12 @@
   this starts up automatically with the server (J2EE ships with the
   CloudScape SQL server, which has to be started separately). /para
paraOne of the nicest features of JBoss is its support for 
`hot' 
  -deployment. What this means is that deploying a Bean is a simple as copying its
  -JAR file into the deployment directory. If this is done while the Bean is 
  -already loaded, JBoss automatically unloads it, then loads the new
  -version. Contrast this with the rigmarole that other J2EE server makes us go 
through... 
  -JBoss is distributed under the LGPL, which means that it's free, even for commercial
  -work, and the LGPL ensures that it remains that way. Id you need support, look at 
the JBoss website for the various forums. If you want to pay for the support then 
contact the ulink url = http://www.jboss.org/JBG/support.jsp;JBossGroup 
LLC/ulink./para
  + deployment. What this means is that deploying a Bean is a simple as 
copying its
  + JAR file into the deployment directory. If this is done while the Bean 
is 
  + already loaded, JBoss automatically unloads it, then loads the new
  + version. Contrast this with the rigmarole that other J2EE server makes 
us go through... 
  + JBoss is distributed under the LGPL, which means that it's free, even 
for commercial
  + work, and the LGPL ensures that it remains that way. Id you need 
support, look at the JBoss website for the various forums. If you want to pay for the 
support then contact the ulink url = 
http://www.jboss.org/jbossgroup/services.jsp;JBossGroup LLC/ulink./para
paraThis chapter helps get you started using JBoss 
   by describing step-by-step how a simple EJB can be created, deployed and
   tested on the JBoss server. /para
  
  
  

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



[JBoss-dev] CVS update: manual/src/xdocs jbossintro.xml

2001-10-01 Thread Tobias Frech

  User: gropi   
  Date: 01/10/01 00:21:50

  Modified:src/xdocs jbossintro.xml
  Log:
  Ossie J. H. Moore recommended to reword the sentence to make sense.
  
  Revision  ChangesPath
  1.2   +1 -1  manual/src/xdocs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jbossintro.xml2001/08/29 09:19:36 1.1
  +++ jbossintro.xml2001/10/01 07:21:50 1.2
  @@ -659,7 +659,7 @@
   InitialContext jndiContext = new InitialContext();
   System.out.println(Got context);/programlisting
/para
  - paraThe jndi.properties file that we will used is that located in 
the examples/resources/jndi.properties of the
  + paraThe jndi.properties file we have to use is located in the 
examples/resources/jndi.properties of the
   documentation examples distribution. Its contents 
are:programlistingjava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
   java.naming.provider.url=jnp://localhost:1099
   
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces/programlistingThis 
specifies the InitialContextFactory, provider url, and the packages of object factories
  
  
  

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



[JBoss-dev] CVS update: manual/src/xdocs jbossintro.xml

2001-10-01 Thread Tobias Frech

  User: gropi   
  Date: 01/10/01 01:57:09

  Modified:src/xdocs jbossintro.xml
  Log:
  Some more comments on the JNDI service.
  
  Revision  ChangesPath
  1.3   +18 -14manual/src/xdocs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- jbossintro.xml2001/10/01 07:21:50 1.2
  +++ jbossintro.xml2001/10/01 08:57:09 1.3
  @@ -12,6 +12,7 @@
firstnameTobias/firstname
surnameFrech/surname
/author
  +email[EMAIL PROTECTED]/email
/para
para
author
  @@ -37,7 +38,7 @@
titleAbout JBoss/title
paraJBoss is an implementation of the EJB 1.1 (and parts of 
2.0)
   specification, that is, it is a  server and container for Enterprise JavaBeans. In 
this it is similar to Sun's
  -'J2SDK Enterprise Edition' (J2EE), but JBoss the JBoss core server provides only an 
EJB server.
  +'J2SDK Enterprise Edition' (J2EE), but the JBoss core server provides only an EJB 
server.
   The JBoss core does not include a web container for servlets/JSP pages, although 
there are
   bundles available that include either Tomcat or Jetty.
   
  @@ -56,7 +57,7 @@
   already loaded, JBoss automatically unloads it, then loads the new
   version. Contrast this with the rigmarole that other J2EE server makes us go 
through... 
   JBoss is distributed under the LGPL, which means that it's free, even for commercial
  -work, and is likely to remain that way. You get no support, of course. /para
  +work, and the LGPL ensures that it remains that way. Id you need support, look at 
the JBoss website for the various forums. If you want to pay for the support then 
contact the ulink url = http://www.jboss.org/JBG/support.jsp;JBossGroup 
LLC/ulink./para
paraThis chapter helps get you started using JBoss 
   by describing step-by-step how a simple EJB can be created, deployed and
   tested on the JBoss server. /para
  @@ -76,8 +77,8 @@
titleInstalling Ant/title
paraYou need Ant to compile and run the example presented in the 
JBoss documentation. Ant is
   the standard build tool used by most open source Java projects and is widely being 
used in commercial
  -settings as well. You need Ant version 1.3 or latter. You can download the 1.3 
binaries for Ant from ulink url = 
http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/;HERE/ulink. If you 
have problems finding
  -binaries at that location try the Ant home page which is located ulink url = 
http://jakarta.apache.org/ant/index.html;HERE/ulink./para
  +settings as well. You need Ant version 1.3 or latter. You can download the 1.3 
binaries for Ant from ulink url = 
http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/;this link to the 
Apache/Jakarta website/ulink. If you have problems finding
  +binaries at that location try the Ant home page which is located ulink url = 
http://jakarta.apache.org/ant/index.html;on the Apache/Jakarta 
website/ulink./para
paraOnce you have the Ant distribution unarchive it to create a 
jakarta-ant-1.3 directory.  The Ant documentation
   is located in the docs/manual directory. You should start with the 
docs/manual/index.html file and browse through its
   contents if you want to use Ant. You won't need to know anything about Ant build 
scripts in order to compile and run
  @@ -209,16 +210,15 @@
   need to specify a CLASSPATH environment variable if you don't normally have 
   to./para
paraThe next step will be to download, install and test the JBoss 
server. At 
  -the time of writing the most recent version of JBoss is 2.2.2.
  +the time of updating this the most recent version of JBoss is 2.4.1.
   It doesn't matter where you install JBoss. There is no requirement for root access 
to
  -run JBoss as none of the default ports are below the 1024 privaledged port range.
  +run JBoss as none of the default ports are below the 1024 priveledged port range.
   You will need to define a JBOSS_DIST environment variable that points to the 
installation
   location of the JBoss installation directory. This is required to build and run all 
of the documentation
   examples you will download later./para
paraJBoss is distributed as a ZIP file. You can download the binary
  -distribution which contains the latest offical release (which was 2.2.2
  -at the time of writing) or a source snapshot with the latest
  -version from CVS. This documentation mainly is written for the 2.2.2 version./para
  +distribution which contains the latest offical release or a source snapshot with 
the latest
  +version from CVS. This documentation mainly was written for the 2.2.2 version and