thanks for the info I was having the same trouble myself.
Shawn Harris
----- Original Message -----
From: "Mark Phelps" <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Monday, March 26, 2001 12:52 PM
Subject: RE: Using the jbuilder IDE with JRUN
> We use JBuilder with JRun successfully. JBuilder does not have a tight
> integration with JRun but you can get by with some manual configuration.
> The steps that need to be taken will vary depending on the type of
component
> you are building, (i.e. servlets, JSPs, or EJBs). We are creating a web
> based system made up of JSPs and EJBs. We have one JBuilder project that
> holds the JSPs and support classes, and another project that includes the
> EJBs.
>
> For the EJB project we did the following:
>
> 1. Create a project to hold the EJBs using FILE | NEW PROJECT.
>
> 2. Define a JBuilder library to hold all of the JAR files that come with
> JRun. JBuilder libraries are simply user-specified lists of JAR files
which
> can be placed on the project's classpath all at once. To do this, go to
> TOOLS | CONFIGURE LIBRARIES. Click the "New" button. Give the library a
> name, such as "JRun 3.0". Leave the "Location" control set to "User
Home".
> Click the "Add" button and select all JAR files in the JRun\lib and
> JRun\lib\ext directories. You don't need all of these but it is easier
not
> to worry about the extra ones. Click OK three times to get back to the
main
> JBuilder window.
>
> 3. In PROJECT | PROJECT PROPERTIES go to the "Enterprise" tab and select
> EJB1.1 as your application server. This tells JBuilder not to build
> anything into the project that is app server specific. The JBuilder
> documentation will tell you that you should flag home interface files to
> have their IIOP stubs generated. You do not need to do this.
>
> 4. On the "Run" tab of the project properties dialog click "Application"
on
> the subdialog. Do this even though your application contains JSPs or EJBs.
> We will be executing JRun rather than your components.
>
> Set the main class to "JRun". Note that class JRun does not belong to a
> package. It is just "JRun".
>
> Set the VM Parameters to:
>
> -Dejipt.classServer.host=127.0.0.1 -Dejipt.classServer.port=2323 -Dejipt.h
om
>
ePort=2333 -Djava.security.policy=c:\progra~1\allaire\jrun\lib\jrun.policy -
>
Dejipt.home=c:/progra~1/allaire/jrun -Dejipt.ejbDirectory=c:/progra~1/allair
> e/jrun/servers/default
>
> Set the Application Parameters to:
>
> -start c:/progra~1/allaire/jrun/servers/default
> jrun.rootDir=c:/progra~1/allaire/jrun
>
> The previous settings assume that you have installed JRun in c:\program
> files\allaire\jrun on your local machine for development. If this is not
> the case, then modify the settings appropriately. In our team each
> developer has a developer licensed version of JRun installed on his/her
> local machine. They code/build/deploy/test locally until everything is
> working and then they check the source into our source code control
system.
> From there it is deployed to the main app server.
>
> 5. Go to the "Paths" tab of the Project Properties dialog. Click on
> "Required Libraries" on the sub dialog. Click "Add". Select your JRun
3.0
> library (Created in step 2) and click OK. Click OK again to get back to
the
> main JBuilder window.
>
> 6. Save your project settings.
>
> 7. Create a new EJB group using FILE | NEW | Empty EJB Group on the
> "Enterprise" tab.
>
> 8. Add new EJBs to the group as desired. The EJBs will be built and
stored
> in a .jar file automatically.
>
> When you are ready to test the EJBs you must first deploy them to JRun.
We
> run a batch file to do this. See the batch file below. Before this batch
> file will work you must put the following line in your
> c:\progra~1\allaire\jrun\servers\default\deploy\deploy.properties file.
>
> ejipt.ejbJars= <the name of your EJB jar file>
>
> If you don't want user security on your EJB methods then you should also
add
> the next line to your deploy.properties file:
>
> ejb.allowedIdentities=all
>
> BATCH FILE TO DEPLOY EJBs IN A JAR FILE:
> c:
> cd \progra~1\allaire\jrun\
> copy <pathname of your EJB jar file>
> c:\progra~1\allaire\jrun\servers\default\deploy
>
java -Dejipt.home=C:\progra~1\allaire\jrun -Dejipt.ejbDirectory=C:\progra~1\
> allaire\jrun\servers\default -Djava.security.policy=jrun.policy -classpath
>
c:\progra~1\allaire\jrun\lib\ejipt_tools.jar;c:\progra~1\allaire\jrun\lib\ex
>
t\jta.jar;c:\progra~1\allaire\jrun\lib\ext\parser.jar;c:\progra~1\allaire\jr
> un\lib\ext\jaxp.jar;c:\progra~1\allaire\jrun\lib\ext\ejb.jar
> allaire.ejipt.tools.Deploy
>
> Once this is all setup your development cycle will be like this:
>
> 1. Make changes to code
> 2. Rebuild the project
> 3. Run your deploy batch file
> 4. Set your breakpoints for debugging
> 5. Run Jrun from within JBuilder by choosing RUN | RUN PROJECT
> 6. Debug normally
>
> If you are building JSPs and Servlets then the same basic setup applies.
> Your deploy batch file will be different because it will need to build the
> web application .war file and call a different deploy class. See the
batch
> file below for a sample.
>
> BATCH FILE TO DEPLOY JSP/SERVLET PROJECT AS A WEB APPLICATION
> c:
> cd <The base directory of your JSP/Servlet project>
> jar -cf <project name>.war *.*
> java -classpath c:\progra~1\allaire\jrun\lib\jrun.jar
> allaire.jrun.tools.WarDeploy -remove -config=warremove.properties
> java -classpath c:\progra~1\allaire\jrun\lib\jrun.jar
> allaire.jrun.tools.WarDeploy -deploy -config=wardeploy.properties
>
> This batch file removes all JSPs and Servlets which may have been deployed
> previously and redeploys the current versions. There are two files
> "warremove.properties" and "wardeploy.properties" which this batch file
> refers to. These files sit in the base directory of your JSP project.
> Their contents are shown below.
>
> warremove.properties:
> deploy.server.name=default
> deploy.webapp.name=default
> deploy.jrun.rootdir=c:\\progra~1\\allaire\\jrun
>
> wardeploy.properties:
> deploy.war.path=<pathname of the .war file>
> deploy.server.name=default
> deploy.webapp.name=default
> deploy.context.path=/
>
deploy.webapp.rootdir=c:\\progra~1\\allaire\\jrun\\servers\\default\\default
> -app
> deploy.jrun.rootdir=c:\\progra~1\\allaire\\jrun
>
> Once these files are built the cycle will be the same as shown above for
the
> EJBs.
>
> GOTCHAS:
>
> There are a couple of things we have learned about JBuilder and JRun. If
> you run your JSPs under tomcat from within JBuilder they will not be able
to
> connect to EJBs which are running in JRun. At least we never succeeded in
> getting them to. I'm sure it can be done somehow. We found that it
worked
> wonderfully when the JSPs and the EJBs were both running under JRun.
>
> I hope this is helpful. Sorry it is so verbose. There may be easier ways
> to do some of this but I know these methods work. Let me know if you have
> specific questions.
>
> Good luck.
>
>
> -----Original Message-----
> From: Hobbet, Linda [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 26, 2001 11:25 AM
> To: JRun-Talk
> Subject: Using the jbuilder IDE with JRUN
>
>
> Does anyone know if the IDE in JBuilder can be configured to work with
JRUN
> as the application server? And if so, how to do it, or where to find
> instructions?
>
> Thanks,
> Linda
>
> Linda Lee Hobbet
> ProBusiness R&D/Internet
> Room NC 189 Eagles Way,
> Pleasanton, CA
> (925) 737-7072
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
