[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
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 - This has compiled the EJB classes and created the ejb-jar for deployment. The contents of the + This 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: ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
User: vharcq Date: 01/06/25 14:39:02 Modified:src/docs jbossintro.xml Log: cosmetics Revision ChangesPath 1.18 +3 -3 manual/src/docs/jbossintro.xml Index: jbossintro.xml === RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- jbossintro.xml2001/06/25 07:30:52 1.17 +++ jbossintro.xml2001/06/25 21:39:01 1.18 @@ -79,7 +79,7 @@ settings as well. You need Ant version 1.3 or latter. You can download the 1.3 binaries for Ant from http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/";>HERE. If you have problems finding binaries at that location try the Ant home page which is located http://jakarta.apache.org/ant/index.html";>HERE. Once 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/inidex.html file and browse through its +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 the examples in the JBoss documentation. All we care about at this point is that you have Ant installed and availble in your executation path such that you can run ant from the command line. To do this you need the path to the jakarta-ant-1.3/bin @@ -87,7 +87,7 @@ in /usr/local/Java/Ant/jakarta-ant-1.3 and my PATH contains /usr/local/Java/Ant/jakarta-ant-1.3/bin. On a win32 platform with Ant installed in G:/tmp/jakarta-ant-1.3 you would need G:/tmp/jakarta-ant-1.3/bin in your PATH. Setup your PATH now. - You also need the bin directory of a 1.3 JDK(Java development kit) in your path as well for access to the + You need the bin directory of a 1.3 JDK(Java development kit) in your path as well for access to the java interpreter and java compiler. You also typically need to set the JAVA_HOME environment variable to point to the location of a JDK 1.3 installation so that Ant can find the javac compiler. Your Ant installation may have been configured such that this is not necessary and you can try the following installation test without this set at first. @@ -258,7 +258,7 @@ Downloading the Documentation Example Source The source code for all examples in the JBoss documentation are available as a single archive which can be downloaded documentation-example.zip or documentation-example.tar.gz -from files section on: http://www.jboss.org/doco_files//";>www.jboss.org. You should +from files section on: http://www.jboss.org/doco_files/";>www.jboss.org. You should download the archive format of your choice and unpack the archive into an empty directory. This will create a directory structure like that shown in ___ 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
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 @@ In 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 http://www.jboss.org/documentation/files/";>www.jboss.org. +on www.jboss.org. You will need to unpack the archive into an empty directory. The 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 @@ Questions about the J2EE deployer and the integration should be posted to - http://www.jboss.org/business/lists.html";>our lists (JBoss) + http://www.jboss.org/lists.jsp";>our lists (JBoss) Distribution and CVS - JBoss Tomcat is shipped as part of the http://www.jboss.org/business/binary.html";>standard JBoss/Server + JBoss Tomcat is shipped as part of the http://www.jboss.org/binary.jsp";>standard JBoss/Server 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. 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 http://www.jboss.org/";>JBoss website. 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 JBoss FAQ or on + JBoss for yourself can be found in the JBoss FAQ or on the http://www.jboss.org/";>JBoss website. The rest of this document covers the following tasks: @@ -96,7 +96,7 @@ 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 JBoss mailing list. You will + or JBoss then please join the JBoss mailing list. You will then be able to contribute to the production of this document and the development of JBoss. 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 http://www.jboss.org/";>JBoss website. General information about all JBoss products as well as instructions on how to get a copy of JBoss-Jetty for yourself can be found in - the JBoss FAQ or on the + the JBoss FAQ or on the h
[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
User: gropi
Date: 01/04/24 08:17:17
Modified:src/docs jbossintro.xml
Log:
A code snippet in the manual was out of sync with the archives which
included the example sources. Thanks to Jason Yip for the correction.
Revision ChangesPath
1.14 +13 -12manual/src/docs/jbossintro.xml
Index: jbossintro.xml
===
RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- jbossintro.xml2001/04/20 04:23:36 1.13
+++ jbossintro.xml2001/04/24 15:17:17 1.14
@@ -455,7 +455,8 @@
Here is the test client:
Test client, file name InterestClient.java
- import java.util.Properties;
+
+import java.util.Properties;
import javax.rmi.PortableRemoteObject;
import javax.naming.*;
@@ -481,7 +482,7 @@
{
// Set up the naming provider; this may not always be necessary, depending
// on how your Java system is configured.
- Hashtable env = new Hashtable();
+ Properties env = new Properties();
env.setProperty("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
env.setProperty("java.naming.provider.url", "localhost:1099");
env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
@@ -492,17 +493,17 @@
try
{
// Get a naming context
-InitialContext jndiContext = new InitialContext(env);
+ InitialContext jndiContext = new InitialContext(env);
System.out.println("Got context");
-
- // Get a reference to the Interest Bean
- Object ref = jndiContext.lookup("interest/Interest");
- System.out.println("Got reference");
-
- // Get a reference from this to the Bean's Home interface
- InterestHome home = (InterestHome)
-PortableRemoteObject.narrow (ref, InterestHome.class);
-
+
+ // Get a reference to the Interest Bean
+ Object ref = jndiContext.lookup("interest/Interest");
+ System.out.println("Got reference");
+
+ // Get a reference from this to the Bean's Home interface
+ InterestHome home = (InterestHome)
+ PortableRemoteObject.narrow (ref, InterestHome.class);
+
// Create an Interest object from the Home interface
Interest interest = home.create();
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: manual/src/docs jbossintro.xml
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 @@ > In 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 http://www.jboss.org/documentation/files/">www.jboss.org. > +on http://www.jboss.org/documentation/files/">www.jboss.org. >You will need to unpack the archive into an empty directory. > The 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
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 @@ - - First steps - Author: - - Kevin - Boone - - [EMAIL PROTECTED] - - Tobias - Frech - - - - Introduction - - What this section is about - -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. - - - - About JBoss - -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). - - - 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. - - - 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. - - - - Pre-requisites - -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. - -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. - - - - - Installing JBoss - Before installing and running the server, you should check that your JDK -installation is working. You will -need the JDK binaries directory in your PATH (this is essential: see below) -not just for the user account which is doing the installation, but also for -the user account that will run the server. If you are running the server as -root, you should check that the JDK binaries are in the PATH eve
[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
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 @@ In 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 http://www.jboss.org/documentation/files/">www.jboss.org. +on http://www.jboss.org/documentation/files/">www.jboss.org. You will need to unpack the archive into an empty directory. The 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 cmp.xml
User: gropi Date: 01/04/12 05:17:59 Modified:src/docs jbossintro.xml cmp.xml Log: corrected classpath contents of java command to run clients. Revision ChangesPath 1.11 +3 -8 manual/src/docs/jbossintro.xml Index: jbossintro.xml === RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- jbossintro.xml2001/04/11 09:27:44 1.10 +++ jbossintro.xml2001/04/12 12:17:59 1.11 @@ -718,17 +718,12 @@ directory and the server will generate a ClassLoader for it. If the client program is at the top of the directory hierarchy, with the Bean classes below it, then we can run it like this: - - -java -classpath $CLASSPATH:\ -/usr/local/jboss/client/jboss-client.jar:\ -/usr/local/jboss/client/jbosssx-client.jar \ -InterestClient + +java -classpath /usr/local/jboss/client/jboss-client.jar:/usr/local/jboss/client/jbosssx-client.jar:/usr/local/jboss/client/jnp-client.jar:. InterestClient Once again, this needs to go in a shell script or a Makefile; you won't want to type it more than once. - Note the long CLASSPATH; it needs to include the JBoss client classes -and the EJB classes as well as the standard classpath (if any). + Note the long CLASSPATH; it needs to include various JBoss client classes. These classes implement the EJB interfaces with container provider specific code, here JBoss. This is why we now no longer need to include the ejb.jar. If all is well, the test client produces the following output: 1.8 +1 -1 manual/src/docs/cmp.xml Index: cmp.xml === RCS file: /cvsroot/jboss/manual/src/docs/cmp.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- cmp.xml 2001/04/11 09:27:44 1.7 +++ cmp.xml 2001/04/12 12:17:59 1.8 @@ -641,7 +641,7 @@ JBoss client libraries, so the command line will be at least like this: java -classpath -$CLASSPATH:/usr/lib/jboss/client/jboss-client.jar:/usr/lib/jboss/client/jbosssx-client.jar com.web_tomorrow.cd.List; +$CLASSPATH:/usr/lib/jboss/client/jboss-client.jar:/usr/lib/jboss/client/jbosssx-client.jar:/usr/lib/jboss/client/jnp-client.jar com.web_tomorrow.cd.List; If all is well, you will get a list of CDs.So we've created an entity EJB, and a client ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
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. - Coding the test client + Coding and compiling the test client An 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 @@ This generates InterestClient.class in the current directory. - Compiling and running test client + Running the test client We're now ready to run the test client, but first a word of explanation. In 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
[JBoss-dev] CVS update: manual/src/docs jbossintro.xml
User: starksm Date: 01/04/02 16:34:27 Modified:src/docs jbossintro.xml Log: Change the java -jar run.jar to run.sh in the linux section Revision ChangesPath 1.8 +1 -1 manual/src/docs/jbossintro.xml Index: jbossintro.xml === RCS file: /cvsroot/jboss/manual/src/docs/jbossintro.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jbossintro.xml2001/03/21 08:30:20 1.7 +++ jbossintro.xml2001/04/02 23:34:27 1.8 @@ -147,7 +147,7 @@ run the program like this: cd bin -java -jar run.jar +run.sh In a proper installation, the server should start without any error messages or exceptions being thrown. It will produce several pages of ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
