|
Chris, I use Eclipse or WDSc as and editor and write no platform specific code. That allows me to build and test applications on my PC before moving the entire package to the iSeries. To make this work, I use CVS and Ant to manage the source and build parts. I use Hibernate to manage persistence so that I can use mysql or postgres on my PC and DB2 on the iSeries without code changes. I use Tomcat and Struts for an application server/framework. Other tools I use quite a bit are jUnit, jMeter, and jProfiler. On the iSeries I recently had the opportunity to try the Performance Trace Data Visualizer, which is the best profiler I have used because it stays out of the way and gives a good picture of what is happening but it is pretty buggy and I couldn't get it to work over more than a 10 seconds of activity. I always use some version of Eclipse because of the run/debug support, which is far to valuable because I write code in pieces and debug as I go. I used to write lots of main type tests, but now I use jUnit for the same type of thing, which makes regression testing very easy. David Morris >>> chrisd@xxxxxxxxxxxxx 9/24/2003 7:23:14 AM >>> I thought it would be interesting to find out how everyone does their development Java development for the iSeries, and to possibly share some tips for your individual tool chain. I'll start out: We've used a few different methods to code Java on the iSeries. For WebSphere projects, we mostly use WebSphere Studio Application Developer (migrating to 5.0 right now). It's a pretty good tool, but often slow. Most of the slowness we get when using it is related to building projects. A lot of our developers have been asking if there is a way to do "background" builds while they go on and work on other tasks in the IDE. I've thought about seeing if Ant inside of WSAD will allow for this. If the project isn't WebSphere related, then we still tend to use WSAD, but I've found that a simple setup of a good PC text editor (TextPad, Notepad, insert your favorite here), and Ant on the iSeries (Ant is a Java based build scripting tool kinda like Make) can work very well for some projects. I then use the iSeries debugger to debug the Java code (JAVA ... OPTION (*DEBUG)) to debug the code from the green screen, and a utility called the BeanShell (http://www.beanshell.org/), which allows you to interactively work with Java objects to either play with or debug Java code. Any thoughts? What is everyone else doing? ---------------------------------------------------------------------- Chris DeLashmutt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.