RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide
John, actually I believe my howto addressed that, actually I am debugging withoug the embedded tomcat, I simply do not specify tomcat as the argument to start the debugger and I also ensured that the conf/default is in the classpath rather than conf/tomcat, I think that should do the trick. Sorry Iam unfamiliar with Catalina. I assume it is some form of web server/jsp engine? John Coffey Pingtel Corp. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John Menke Sent: Monday, May 21, 2001 11:55 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide John, I have JBoss2.2.1 installed with Catalina 4.0 beta 1 working and would like to debug with JBuilder. If I am not using JBoss with embedded tomcat can I still use JBuilder to debug? What changes do you think I will need to make to the setup? john -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John P. Coffey Sent: Wednesday, May 16, 2001 2:35 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide Adam, no I did'nt experience such a problem. 1 question - does the JBoss server start successfully from the console if not you are out of luck, also make sure your versinos are the same as mine and note I ran from windows 2000? If the problem is specific to JBuilder running the console one thing I did (it's probably not teh right way to fix JBuilder problems) was to start afresh by deletinbg the .jbuilder4 directory from my home folder (beware you will need to have your installation keys handy before proceeding down this route) and then follow the steps exactly as I indicated. FYI I had a colleague at the office do this and he gave me feedback before I posted the last note so the instructions are reasonably accurate.\ Don't know if this helps, bug give it a try and hopefully it'll succeed. If per chance you discover an error in the howto please let me know as I was terribly frustrated with gettting this to work successfully. John Coffey Pingtel Corp -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Adam Lipscombe Sent: Wednesday, May 16, 2001 4:08 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide John, Thanks for such good info! I have got a problem though: when trying to run or debug the project, the CPU goes to 100% and stays there for ages. After 10 minutes I gave up waiting and ended the process. Did you experience this? Any work-arounds? I tried without the -classic but the results were the same. Cheers - Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John P. Coffey Sent: Wednesday, May 16, 2001 1:48 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide Well after pulling my hair out for the last couple of days here is how to get JBoss and JBuilder as friends... Instructions for integrating JBuilder 4.0 Foundation or Higher with JBoss for source level debugging - Install the JBoss Server For the purposes of this howto, I installed teh JBossTomcat release version 2.2.1 into d:\JBoss-2.2.1_Tomcat-3.2.1. Download this from http://www.jboss.org and select the binary link from the page. This is a little confusing as it also contains the source (in the best interests of open source of course). - Create a JBuilder 4.0 Project I typically point this to the source for my EJB code. - Create a JBoss-Server library This is the most difficult part of the setup to get right, however once completed it does not need to be changed so you can setup multiple ejb projects and reuse this library (well done Borland) - Project / Project Properties / RequiredLibraries / Add... Add the following library entries to the JBoss-Server classpath (the order is crucual here). Pay specific attention to the log and tmp folders, faulure to put these in the Library class path will cause the classloader to spit out error messages, the most confusing of which is that /log.properties or /tmp.properties files could not be located. This is because the folders containing these files need to be in the classpath and the class loader complains. /$JBOSS_TOMCAT_HOME/jboss/lib/crimson.jar /$JBOSS_TOMCAT_HOME/jboss/bin/run.jar /$JBOSS_TOMCAT_HOME/jboss/bin /$JBOSS_TOMCAT_HOME/jboss/conf /$JBOSS_TOMCAT_HOME/jboss/lib/jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jboss-jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jdbc2_0-stdext.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jmxri.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/parser.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/servlet.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jaxp.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/webserver.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jasper.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/activation.jar
RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide
John, Thanks for such good info! I have got a problem though: when trying to run or debug the project, the CPU goes to 100% and stays there for ages. After 10 minutes I gave up waiting and ended the process. Did you experience this? Any work-arounds? I tried without the -classic but the results were the same. Cheers - Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John P. Coffey Sent: Wednesday, May 16, 2001 1:48 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide Well after pulling my hair out for the last couple of days here is how to get JBoss and JBuilder as friends... Instructions for integrating JBuilder 4.0 Foundation or Higher with JBoss for source level debugging - Install the JBoss Server For the purposes of this howto, I installed teh JBossTomcat release version 2.2.1 into d:\JBoss-2.2.1_Tomcat-3.2.1. Download this from http://www.jboss.org and select the binary link from the page. This is a little confusing as it also contains the source (in the best interests of open source of course). - Create a JBuilder 4.0 Project I typically point this to the source for my EJB code. - Create a JBoss-Server library This is the most difficult part of the setup to get right, however once completed it does not need to be changed so you can setup multiple ejb projects and reuse this library (well done Borland) - Project / Project Properties / RequiredLibraries / Add... Add the following library entries to the JBoss-Server classpath (the order is crucual here). Pay specific attention to the log and tmp folders, faulure to put these in the Library class path will cause the classloader to spit out error messages, the most confusing of which is that /log.properties or /tmp.properties files could not be located. This is because the folders containing these files need to be in the classpath and the class loader complains. /$JBOSS_TOMCAT_HOME/jboss/lib/crimson.jar /$JBOSS_TOMCAT_HOME/jboss/bin/run.jar /$JBOSS_TOMCAT_HOME/jboss/bin /$JBOSS_TOMCAT_HOME/jboss/conf /$JBOSS_TOMCAT_HOME/jboss/lib/jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jboss-jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jdbc2_0-stdext.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jmxri.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/parser.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/servlet.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jaxp.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/webserver.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jasper.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/activation.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/awt.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/dynaserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxeditor.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjaws.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/hsql.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/idb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jetty-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jms.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jmxtools.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jndi.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jnpserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jpl-util-0_5b.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jta-spec1_0_1.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/mail.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/tomcat-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbossmq.jar /$JBOSS_TOMCAT_HOME/jboss/db /$JBOSS_TOMCAT_HOME/jboss/conf/default /$JBOSS_TOMCAT_HOME/jboss/lib/ext/log4j.jar /$JBOSS_TOMCAT_HOME/jboss/log /$JBOSS_TOMCAT_HOME/jboss/tmp /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosssx.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosscx-0.2.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/connector.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/minerva-1_0b3.jar In the source tab for the JBoss-Server library point to /$JBOSS_TOMCAT_HOME/jboss/src. This is how JBuilder resolves where to find the source for stepping through the code. Without this step typically you will be able to step through the code but the Main.java will appear as Main.class. Set the main class to 'org.jboss.Main'. This is the main startup entry for the JBoss server. Also make sure that you set the working directory to $JBOSS_TOMCAT_HOME/jboss/bin cut and paste the following line and place it into the 'vm parameters' entry field (Project/Properties/Run) -classic -Dtomcat.home=D:\$JBOSS_TOMCAT_HOME\tomcat -Duser.dir=D:\$JBOSS_TOM CAT_HOME\jboss\bin -Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.j axp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apac he.crimson.jaxp.DocumentBuilderFactoryImpl The starup argument should be left blank with the above setting. If you want to run with the integrated tomcat you can put tomcat as the argument, howevre beware that you MAY need to replace the /$JBOSS_TOMCAT_HOME/jboss/conf/default with /$JBOSS_TOMCAT_HOME/jboss/conf/tomcat If the above steps have been done
RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide
Adam, no I did'nt experience such a problem. 1 question - does the JBoss server start successfully from the console if not you are out of luck, also make sure your versinos are the same as mine and note I ran from windows 2000? If the problem is specific to JBuilder running the console one thing I did (it's probably not teh right way to fix JBuilder problems) was to start afresh by deletinbg the .jbuilder4 directory from my home folder (beware you will need to have your installation keys handy before proceeding down this route) and then follow the steps exactly as I indicated. FYI I had a colleague at the office do this and he gave me feedback before I posted the last note so the instructions are reasonably accurate.\ Don't know if this helps, bug give it a try and hopefully it'll succeed. If per chance you discover an error in the howto please let me know as I was terribly frustrated with gettting this to work successfully. John Coffey Pingtel Corp -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Adam Lipscombe Sent: Wednesday, May 16, 2001 4:08 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide John, Thanks for such good info! I have got a problem though: when trying to run or debug the project, the CPU goes to 100% and stays there for ages. After 10 minutes I gave up waiting and ended the process. Did you experience this? Any work-arounds? I tried without the -classic but the results were the same. Cheers - Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John P. Coffey Sent: Wednesday, May 16, 2001 1:48 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide Well after pulling my hair out for the last couple of days here is how to get JBoss and JBuilder as friends... Instructions for integrating JBuilder 4.0 Foundation or Higher with JBoss for source level debugging - Install the JBoss Server For the purposes of this howto, I installed teh JBossTomcat release version 2.2.1 into d:\JBoss-2.2.1_Tomcat-3.2.1. Download this from http://www.jboss.org and select the binary link from the page. This is a little confusing as it also contains the source (in the best interests of open source of course). - Create a JBuilder 4.0 Project I typically point this to the source for my EJB code. - Create a JBoss-Server library This is the most difficult part of the setup to get right, however once completed it does not need to be changed so you can setup multiple ejb projects and reuse this library (well done Borland) - Project / Project Properties / RequiredLibraries / Add... Add the following library entries to the JBoss-Server classpath (the order is crucual here). Pay specific attention to the log and tmp folders, faulure to put these in the Library class path will cause the classloader to spit out error messages, the most confusing of which is that /log.properties or /tmp.properties files could not be located. This is because the folders containing these files need to be in the classpath and the class loader complains. /$JBOSS_TOMCAT_HOME/jboss/lib/crimson.jar /$JBOSS_TOMCAT_HOME/jboss/bin/run.jar /$JBOSS_TOMCAT_HOME/jboss/bin /$JBOSS_TOMCAT_HOME/jboss/conf /$JBOSS_TOMCAT_HOME/jboss/lib/jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jboss-jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jdbc2_0-stdext.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jmxri.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/parser.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/servlet.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jaxp.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/webserver.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jasper.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/activation.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/awt.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/dynaserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxeditor.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjaws.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/hsql.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/idb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jetty-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jms.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jmxtools.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jndi.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jnpserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jpl-util-0_5b.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jta-spec1_0_1.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/mail.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/tomcat-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbossmq.jar /$JBOSS_TOMCAT_HOME/jboss/db /$JBOSS_TOMCAT_HOME/jboss/conf/default /$JBOSS_TOMCAT_HOME/jboss/lib/ext/log4j.jar /$JBOSS_TOMCAT_HOME/jboss/log /$JBOSS_TOMCAT_HOME/jboss/tmp /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosssx.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosscx-0.2.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/connector.jar
[JBoss-user] Jbuilder 4.0 Foundation JBoss2.2.1 HowTo Guide
Well after pulling my hair out for the last couple of days here is how to get JBoss and JBuilder as friends... Instructions for integrating JBuilder 4.0 Foundation or Higher with JBoss for source level debugging - Install the JBoss Server For the purposes of this howto, I installed teh JBossTomcat release version 2.2.1 into d:\JBoss-2.2.1_Tomcat-3.2.1. Download this from http://www.jboss.org and select the binary link from the page. This is a little confusing as it also contains the source (in the best interests of open source of course). - Create a JBuilder 4.0 Project I typically point this to the source for my EJB code. - Create a JBoss-Server library This is the most difficult part of the setup to get right, however once completed it does not need to be changed so you can setup multiple ejb projects and reuse this library (well done Borland) - Project / Project Properties / RequiredLibraries / Add... Add the following library entries to the JBoss-Server classpath (the order is crucual here). Pay specific attention to the log and tmp folders, faulure to put these in the Library class path will cause the classloader to spit out error messages, the most confusing of which is that /log.properties or /tmp.properties files could not be located. This is because the folders containing these files need to be in the classpath and the class loader complains. /$JBOSS_TOMCAT_HOME/jboss/lib/crimson.jar /$JBOSS_TOMCAT_HOME/jboss/bin/run.jar /$JBOSS_TOMCAT_HOME/jboss/bin /$JBOSS_TOMCAT_HOME/jboss/conf /$JBOSS_TOMCAT_HOME/jboss/lib/jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jboss-jaas.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jdbc2_0-stdext.jar /$JBOSS_TOMCAT_HOME/jboss/lib/jmxri.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/parser.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/servlet.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jaxp.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/webserver.jar /$JBOSS_TOMCAT_HOME/tomcat/lib/jasper.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/activation.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/awt.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/dynaserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxeditor.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxejb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjaws.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/ejxjboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/hsql.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/idb.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jboss.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jetty-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jms.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jmxtools.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jndi.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jnpserver.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jpl-util-0_5b.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jta-spec1_0_1.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/mail.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/tomcat-service.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbossmq.jar /$JBOSS_TOMCAT_HOME/jboss/db /$JBOSS_TOMCAT_HOME/jboss/conf/default /$JBOSS_TOMCAT_HOME/jboss/lib/ext/log4j.jar /$JBOSS_TOMCAT_HOME/jboss/log /$JBOSS_TOMCAT_HOME/jboss/tmp /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosssx.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/jbosscx-0.2.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/connector.jar /$JBOSS_TOMCAT_HOME/jboss/lib/ext/minerva-1_0b3.jar In the source tab for the JBoss-Server library point to /$JBOSS_TOMCAT_HOME/jboss/src. This is how JBuilder resolves where to find the source for stepping through the code. Without this step typically you will be able to step through the code but the Main.java will appear as Main.class. Set the main class to 'org.jboss.Main'. This is the main startup entry for the JBoss server. Also make sure that you set the working directory to $JBOSS_TOMCAT_HOME/jboss/bin cut and paste the following line and place it into the 'vm parameters' entry field (Project/Properties/Run) -classic -Dtomcat.home=D:\$JBOSS_TOMCAT_HOME\tomcat -Duser.dir=D:\$JBOSS_TOM CAT_HOME\jboss\bin -Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.j axp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apac he.crimson.jaxp.DocumentBuilderFactoryImpl The starup argument should be left blank with the above setting. If you want to run with the integrated tomcat you can put tomcat as the argument, howevre beware that you MAY need to replace the /$JBOSS_TOMCAT_HOME/jboss/conf/default with /$JBOSS_TOMCAT_HOME/jboss/conf/tomcat If the above steps have been done correctly, open up JBoss-Server.library, this is located in the folder you specified when creating the library. Typically this is C:\Documents and Settings\nt_username\.jbuilder4 or home directory on Linux. Do NOT edit this file, I found several problems manually editing this file and I am unsure why but I got several instances of resoce not found exceptions afterwards. If in doubt don't touch it! ?xml version=1.0 encoding=UTF-8? library !--JBuilder Library Definition File-- fullnameJBoss-Server/fullname class
