Re: Visual Age For Java

2001-01-04 Thread Sheldon Wosnick
Hugh, Sorry once again to inject some information into this thread. I guess I feel justified since you are pointing right at my papers and referencing the tools I developed :-) While I agree with everything you say you are not completely correct. First, the Pro version ALSO supports the JSP and

Re: Visual Age For Java

2001-01-04 Thread Sheldon Wosnick
Duane, Actually, just to add to your correct statements and suggestions for comparing product A and B, I would add the following: The same statements you make are applicable to the Profesional edition as well (which is considerably less expensive) which supports the integrated WebSphere Test Env

Re: Visual Age For Java

2001-01-04 Thread Sheldon Wosnick
der *Professional* ? I think, in fact that VisualAge for Java Professional is quite comparable in price to JBuilder Professional. - Sheldon Wosnick >From: Pete Ehli <[EMAIL PROTECTED]> >Reply-To: A mailing list about Java Server Pages specification and > reference <[EMAIL PROTECT

Re: Please help to test my new jsp website

2000-10-04 Thread Sheldon Wosnick
Admittely, the "security exposure" here is really minimal but do you want to expose this kind of information so easily on a production box??? Is this meant to be a "production" box??? You asked... Sheldon Wosnick Software Developer, IBM Toronto Lab >From: "Karau, Joe"

No-Charge Apache Tomcat Test Environment for VisualAge for Java

2000-08-24 Thread Sheldon Wosnick
The new Apache Tomcat Test Enviroment for VisualAge for Java is now generally available at: http://www.ibm.com/vadd This feature builds on the technologies and concepts distributed in my Apache Tomcat whitepapers: http://www7.software.ibm.com/vad.nsf/Data/Document2390?OpenDocument&p=1 http://

Re: VisualAge for Java - component problem

2000-08-04 Thread Sheldon Wosnick
The WebSphere Tools *are* indeed a part of VisualAge for Java 3.0x Pro. However, there are a number of situations in which you would not see the feature to load and among those reasons, the most common are: 1 - You are running your VA/Java image on Window 95/98. The WebSphere Tools are only supp