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

2001-07-19 Thread Tobias Frech

  User: gropi   
  Date: 01/07/19 12:58:06

  Modified:src/docs jbossintro.xml
  Log:
  Included advice from Chiew Kwooi Lee for NoClassDefFoundError.
  
  Revision  ChangesPath
  1.19  +3 -1  manual/src/docs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- jbossintro.xml2001/06/25 21:39:01 1.18
  +++ jbossintro.xml2001/07/19 19:58:06 1.19
  @@ -537,7 +537,9 @@
   
   Total time: 2 seconds/computeroutput
/literallayout
  - paraThis has compiled the EJB classes and created the ejb-jar for 
deployment. The contents of the
  + paraThis has compiled the EJB classes and created the ejb-jar for 
deployment. 
  +If got a java.lang.NoClassDefFoundError here instead of a successful created jar 
file try clearing your classpath.
  +The contents of the
   interest.jar include the structure we discussed previously as shown by running the 
jar -tvf
   command:/para
literallayout
  
  
  

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



[JBoss-dev] CVS update: manual/src/docs jbossintro.xml howtotomcat.xml howtomssql.xml howtojetty.xml

2001-06-16 Thread gropi

  User: gropi   
  Date: 01/06/16 05:32:24

  Modified:src/docs jbossintro.xml howtotomcat.xml howtomssql.xml
howtojetty.xml
  Log:
  broken links fixed, in sync with new website
  
  Revision  ChangesPath
  1.16  +1 -1  manual/src/docs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- jbossintro.xml2001/05/20 19:24:56 1.15
  +++ jbossintro.xml2001/06/16 12:32:24 1.16
  @@ -139,7 +139,7 @@
paraIn this step we will write and compile a simple Enterprise 
JavaBean.
   You can download the source code for this example in either zip (interestEJB.zip) or
   tar/gzip (interestEJB.tar.gz) format from the file section of the documentation 
section
  -on ulink url=http://www.jboss.org/documentation/files/;www.jboss.org/ulink.
  +on www.jboss.org.
   You will need to unpack the archive into an empty directory./para
paraThe example, which is called 'Interest', is a simple stateless 
session EJB.
   Its job is to calculate the amount of compound interest payable on a sum
  
  
  
  1.6   +2 -2  manual/src/docs/howtotomcat.xml
  
  Index: howtotomcat.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/howtotomcat.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- howtotomcat.xml   2001/05/28 14:26:07 1.5
  +++ howtotomcat.xml   2001/06/16 12:32:24 1.6
  @@ -71,13 +71,13 @@
   
para
Questions about the J2EE deployer and the integration should be posted to 
  - ulink url=http://www.jboss.org/business/lists.html;our lists/ulink 
(JBoss)/para
  + ulink url=http://www.jboss.org/lists.jsp;our lists/ulink (JBoss)/para
/section
section
titleDistribution and CVS/title

para
  - JBoss Tomcat is shipped as part of the ulink 
url=http://www.jboss.org/business/binary.html;standard JBoss/Server/ulink 
  + JBoss Tomcat is shipped as part of the ulink 
url=http://www.jboss.org/binary.jsp;standard JBoss/Server/ulink 
package. However, the current distribution is based on an earlier version of 
EmbeddedTomcat that does not parse Tomcat's
server.xml. If you don't need server.xml parsed (ie, you're not trying to 
integrate with Apache),
then the current version may be the easiest route for you. /para
  
  
  
  1.9   +2 -2  manual/src/docs/howtomssql.xml
  
  Index: howtomssql.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/howtomssql.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- howtomssql.xml2001/05/16 17:10:31 1.8
  +++ howtomssql.xml2001/06/16 12:32:24 1.9
  @@ -60,7 +60,7 @@
Not so fast amigos. You need to obtain a copy of the 
JBoss distribution 
from the ulink url=http://www.jboss.org/;JBoss 
website/ulink. 
General information about all JBoss products as well 
as instructions on how to get a copy of 
  - JBoss for yourself can be found in the ulink 
url=/business/faq.htmlJBoss FAQ/ulink or on 
  + JBoss for yourself can be found in the ulink 
url=/faq.jspJBoss FAQ/ulink or on 
the ulink url=http://www.jboss.org/;JBoss 
website/ulink. The 
rest of this document covers the following tasks:
/para
  @@ -96,7 +96,7 @@
/para
para
If this is the case with you or, if you have any 
further comments or suggestions about this document 
  - or JBoss then please join the ulink 
url=/business/lists.htmlJBoss mailing list/ulink. You will 
  + or JBoss then please join the ulink 
url=/lists.jspJBoss mailing list/ulink. You will 
then be able to contribute to the production of this 
document and the development of JBoss.
/para
/section
  
  
  
  1.5   +4 -4  manual/src/docs/howtojetty.xml
  
  Index: howtojetty.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/howtojetty.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- howtojetty.xml2001/05/17 20:00:03 1.4
  +++ howtojetty.xml2001/06/16 12:32:24 1.5
  @@ -61,7 +61,7 @@
Not so fast comrades. You need to obtain a copy of the 
integrated JBoss-Jetty distribution from 
the ulink url=http://www.jboss.org/;JBoss 

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

2001-04-20 Thread starksm

  User: starksm 
  Date: 01/04/19 21:19:06

  Modified:src/docs jbossintro.xml
  Log:
  Clean up the tutorial as it was rather rambling
  
  Revision  ChangesPath
  1.12  +603 -755  manual/src/docs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- jbossintro.xml2001/04/12 12:17:59 1.11
  +++ jbossintro.xml2001/04/20 04:19:06 1.12
  @@ -1,755 +1,603 @@
  -chapter
  - titleFirst steps/title
  - paraAuthor:
  - author
  - firstnameKevin/firstname
  - surnameBoone/surname
  - /author
  - email[EMAIL PROTECTED]/email
  - author
  - firstnameTobias/firstname
  - surnameFrech/surname
  - /author
  - /para
  - section
  - titleIntroduction/title
  - section
  - titleWhat this section is about/title
  - para
  -This section presents a step-by-step tutorial on how to set up `JBoss', the 
  -free Enterprise JavaBean (EJB) server, and create your first
  -Enterprise JavaBean and client. It doesn't explain what Enterprise JavaBeans 
  -are, or how they are used; there are a number of good
  -introductory articles on Sun's JavaSoft Web site. Although the description is 
  -based on the use of a Linux server, most of the issues discussed in
  -this article will also apply to other platforms. If you are using a Windows 
  -platform you will need to pay attention to the directory names, which
  -will be different from the one's I've assumed. 
  -/para
  - /section
  - section
  - titleAbout JBoss/title
  - para
  -JBoss 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 is much more single-minded than 
  -J2EE. JBoss provides only an EJB server; it does not include
  -support for JSP, SSL, and all the other protocols that the Sun product can 
  -handle. This means that it is smaller in memory and in disk space.
  -JBoss will run very effectively on a machine with 64 megabytes of RAM, and 
  -requires only some megabytes of disk (including source code!). Sun's
  -J2EE requires a minimum of 128 megabytes of RAM, and 31 megabytes of disk 
  -space. That's not to criticise the Sun product; it is a
  -heavyweight offering providing a host of services. Because of its small memory 
  -footprint, JBoss starts up about 10 times faster than J2EE.
  -There is a built-in SQL database server for handling persistent beans, and 
  -this starts up automatically with the server (J2EE ships with the
  -CloudScape SQL server, which has to be started separately). 
  -/para
  - para
  -   One 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 J2EE makes us go through... 
  -JBoss is distributed under the GNU public licence, which means that
  -it's free, even for commercial work, and is likely to remain that way. You get 
  -no support, of course. 
  -/para
  - para
  -   The main weakness of JBoss is its documentation. There is, essentially, 
  -none. There is a mailing list, and you will almost certainly need
  -recourse to it at some point. This article hopes to remedy this deficiency, to 
  -a small degree, by describing step-by-step how a simple EJB can
  -be created, deployed and tested on the JBoss server. 
  -/para
  - /section
  - section
  - titlePre-requisites/title
  - para
  -JBoss is written entirely in Java, and requires a Java system compatible with 
  -JDK 1.3. This is essential, not optional. Trust me on this; I've tried
  -it with JDK 1.2.2 and the `hot' deployment facility simply doesn't work. Since 
  -it is now possible to get Linux JDKs directly from Sun, there's
  -little reason not to upgrade if you're using an earlier version. /para
  - para
  -I will assume that you are basically familiar with EJBs (and roughly know, for 
  -example, what a `home interface' is) and know how to compile Java
  -classes. 
  -/para
  - /section
  - /section
  - section
  - titleInstalling JBoss/title
  - paraBefore installing and running the server, you should check that 
your JDK 
  -installation is working. You 

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

2001-04-20 Thread Tobias Frech

Hi!
May I suggest not to set direct links to the files area of the
documentation. Instead use a verbal reference to the documentation files
section on www.jboss.org. This was discussed on jboss-docs.

I will only repeat the resoning very short here, for details check the
archives of jboss-docs:

From time to time the website structure changes. The files are "linked"
to the website and not to the documentation. That's why the "pointer" to
the files should be on the webiste, not in the docu. This will help
avoiding broken links the next time the website changes.

Ciao,
Tobias

[EMAIL PROTECTED] wrote:
 
   User: starksm
   Date: 01/04/19 21:23:36
 
   Modified:src/docs jbossintro.xml
   Log:
   Fix ulink tag
 
   Revision  ChangesPath
   1.13  +1 -1  manual/src/docs/jbossintro.xml
 
   Index: jbossintro.xml
   ===
   RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
   retrieving revision 1.12
   retrieving revision 1.13
   diff -u -r1.12 -r1.13
   --- jbossintro.xml2001/04/20 04:19:06 1.12
   +++ jbossintro.xml2001/04/20 04:23:36 1.13
   @@ -139,7 +139,7 @@
 paraIn this step we will write and compile a simple Enterprise 
JavaBean.
You can download the source code for this example in either zip(interestEJB.zip) 
or
tar/gzip( interestEJB.tar.gz) format from the file section of the documentation 
section
   -on ulink url="http://www.jboss.org/documentation/files/"www.jboss.orgulink.
   +on ulink url="http://www.jboss.org/documentation/files/"www.jboss.org/ulink.
You will need to unpack the archive into an empty directory./para
 paraThe example, which is called 'Interest', is a simple stateless 
session EJB.
Its job is to calculate the amount of compound interest payable on a sum
 
 
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-development

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



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

2001-04-19 Thread starksm

  User: starksm 
  Date: 01/04/19 21:23:36

  Modified:src/docs jbossintro.xml
  Log:
  Fix ulink tag
  
  Revision  ChangesPath
  1.13  +1 -1  manual/src/docs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- jbossintro.xml2001/04/20 04:19:06 1.12
  +++ jbossintro.xml2001/04/20 04:23:36 1.13
  @@ -139,7 +139,7 @@
paraIn this step we will write and compile a simple Enterprise 
JavaBean.
   You can download the source code for this example in either zip(interestEJB.zip) or
   tar/gzip( interestEJB.tar.gz) format from the file section of the documentation 
section
  -on ulink url="http://www.jboss.org/documentation/files/"www.jboss.orgulink.
  +on ulink url="http://www.jboss.org/documentation/files/"www.jboss.org/ulink.
   You will need to unpack the archive into an empty directory./para
paraThe example, which is called 'Interest', is a simple stateless 
session EJB.
   Its job is to calculate the amount of compound interest payable on a sum
  
  
  

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



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

2001-04-10 Thread gropi

  User: gropi   
  Date: 01/04/10 02:46:41

  Modified:src/docs jbossintro.xml
  Log:
  title cosmetics
  
  Revision  ChangesPath
  1.9   +2 -2  manual/src/docs/jbossintro.xml
  
  Index: jbossintro.xml
  ===
  RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- jbossintro.xml2001/04/02 23:34:27 1.8
  +++ jbossintro.xml2001/04/10 09:46:41 1.9
  @@ -561,7 +561,7 @@
   of its methods, just to prove that it's working./para
/section
section
  - titleCoding the test client/title
  + titleCoding and compiling the test client/title
paraAn EJB on its own is no use; we will need at least a simple 
client to 
   use its services. A user of EJBs may be another EJB, and ordinary JavaBean, a 
   JSP page, an applet, or a stand-alone application. In this example, for 
  @@ -695,7 +695,7 @@
paraThis generates InterestClient.class in the current directory. 
/para
/section
section
  - titleCompiling and running test client/title
  + titleRunning the test client/title
paraWe're now ready to run the test client, but first a word of 
   explanation./para
paraIn reality the client and the server are likely to be on 
different 
  
  
  

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