Re: JBuilder Enterprise
Bruce, Do you compile your code with JB? The reason why I ask... If you have a library in your JB project, it will automatically put that on the classpath when you launch your main class for the project. Hopefully this states the problem simply... Problem... Put struts.jar in my project so I can compile in JB. When Tomcat's main (Catalina for me I'm using Tomcat 4.0) is called the struts.jar is added to the classpath. Solution... use ant to build my code and don't include struts.jar in my project. Did you find another solution to the problem? After about 8 emails on inprise newsgroup they had a couple of suggestions. I just wanted to see what your experience was. Thanks in advance, Steve Bruce McCleave wrote: Hotspot is what causes debugging to be so slow. We have found that passing "-classic" as a VM Parameter, which disables HotSpot, will dramatically increase performance. In my case I went from a 2 minute startup time to about 5 seconds, it actually makes the debugger usable. That was with JBuilder Professional 4.0. ~Bruce -Original Message- From: Deping Chian [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 06, 2001 9:09 AM To: [EMAIL PROTECTED] Subject: Re: JBuilder Enterprise Lind Jrgen wrote: Hi, after the discussion on using JBuilder for Web Development, I decided to try the Enterprise Edition... While my stuff worked fine with the Foundation version (and an "external" Tomcat), I cannot get it running within the JBuilder Environment. After I managed to tell the internal Tomcat where to find the struts TLDs, Tomcat complains about some missing attribute: javax.servlet.ServletException: Missing resources attribute org.apache.struts.action.MESSAGE Discard JB4's internal Tomcat (older version). Download tomcat 3.2.1, and new struts nightly build. create a new library set (call it tomcat3.2.1 if you want), add all jar files in tomcat-3.2.1/lib directory. I do database apps with interclient, so I put my interclient.jar there. Also I used GenericDataSource class of struts, so I put jdbc2_0-stdext.jar there (download from Sun). I have been using these for one of my projects for a while. Debugging is ok in Linux even for struts calls. Debugging can be slow in windows unless you include a -class VM parameters. If you updrade to another version of JBuilder or struts, you should delete all the work files. Otherwise, it is very likely to have problems. Deping at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:386) at www.p_00025blic_0005fhtml.webapps.odin_0002dtracer.jsp._0002fwww_0002fpublic _0005fhtml_0002fwebapps_0002fodin_0002dtracer_0002fjsp_0002flogon_0002ejsplo gon_jsp_0._jspService(_0002fwww_0002fpublic_0005fhtml_0002fwebapps_0002fodin _0002dtracer_0002fjsp_0002flogon_0002ejsplogon_jsp_0.java:305) Any ideas what this means and how to fix it? Regards, Jrgen -- - Steven D. Wilkinson, [EMAIL PROTECTED]
RE: JBuilder Enterprise
I have set up JBuilder to mimic my tomcat environment. First I set up my
JBuilder project to build my classes in "/WEB-INF/classes" then I changed
the working directory to {tomcat_root}/bin (this is not required).
As for the Jars, I include them in the project so that the build can find
all the jars. In our final build struts.jar is placed in "/WEB-INF/lib"
where tomcat automatically picks up the jars.
Hope that helps,
~Bruce
-Original Message-
From: Steven D. Wilkinson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 7:59 AM
To: [EMAIL PROTECTED]
Subject: Re: JBuilder Enterprise
Bruce,
Do you compile your code with JB? The reason why I ask...
If you have a library in your JB project, it will automatically put that on
the
classpath when you launch your main class for the project. Hopefully this
states the problem simply...
Problem...
Put struts.jar in my project so I can compile in JB.
When Tomcat's main (Catalina for me I'm using Tomcat 4.0) is called the
struts.jar is added to the classpath.
Solution...
use ant to build my code and don't include struts.jar in my project.
Did you find another solution to the problem?
After about 8 emails on inprise newsgroup they had a couple of suggestions.
I
just wanted to see what your experience was.
Thanks in advance,
Steve
Bruce McCleave wrote:
Hotspot is what causes debugging to be so slow. We have found that
passing
"-classic" as a VM Parameter, which disables HotSpot, will dramatically
increase performance. In my case I went from a 2 minute startup time to
about 5 seconds, it actually makes the debugger usable.
That was with JBuilder Professional 4.0.
~Bruce
-Original Message-
From: Deping Chian [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 9:09 AM
To: [EMAIL PROTECTED]
Subject: Re: JBuilder Enterprise
Lind Jrgen wrote:
Hi,
after the discussion on using JBuilder for Web Development, I decided
to try the Enterprise Edition... While my stuff worked fine with the
Foundation version (and an "external" Tomcat), I cannot get it running
within the JBuilder Environment. After I managed to tell the internal
Tomcat where to find the struts TLDs, Tomcat complains about some
missing
attribute:
javax.servlet.ServletException: Missing resources attribute
org.apache.struts.action.MESSAGE
Discard JB4's internal Tomcat (older version). Download tomcat 3.2.1,
and new struts nightly build.
create a new library set (call it tomcat3.2.1 if you want), add all jar
files in tomcat-3.2.1/lib directory. I do database apps with
interclient, so I put my interclient.jar there. Also I used
GenericDataSource class of struts, so I put jdbc2_0-stdext.jar there
(download from Sun).
I have been using these for one of my projects for a while. Debugging is
ok in Linux even for struts calls. Debugging can be slow in windows
unless you include a -class VM parameters.
If you updrade to another version of JBuilder or struts, you should
delete all the work files. Otherwise, it is very likely to have
problems.
Deping
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:386)
at
www.p_00025blic_0005fhtml.webapps.odin_0002dtracer.jsp._0002fwww_0002fpublic
_0005fhtml_0002fwebapps_0002fodin_0002dtracer_0002fjsp_0002flogon_0002ejsplo
gon_jsp_0._jspService(_0002fwww_0002fpublic_0005fhtml_0002fwebapps_0002fodin
_0002dtracer_0002fjsp_0002flogon_0002ejsplogon_jsp_0.java:305)
Any ideas what this means and how to fix it?
Regards,
Jrgen
--
-
Steven D. Wilkinson, [EMAIL PROTECTED]
Re: JBuilder Enterprise
Lind Jrgen wrote: Hi, after the discussion on using JBuilder for Web Development, I decided to try the Enterprise Edition... While my stuff worked fine with the Foundation version (and an "external" Tomcat), I cannot get it running within the JBuilder Environment. After I managed to tell the internal Tomcat where to find the struts TLDs, Tomcat complains about some missing attribute: javax.servlet.ServletException: Missing resources attribute org.apache.struts.action.MESSAGE Discard JB4's internal Tomcat (older version). Download tomcat 3.2.1, and new struts nightly build. create a new library set (call it tomcat3.2.1 if you want), add all jar files in tomcat-3.2.1/lib directory. I do database apps with interclient, so I put my interclient.jar there. Also I used GenericDataSource class of struts, so I put jdbc2_0-stdext.jar there (download from Sun). I have been using these for one of my projects for a while. Debugging is ok in Linux even for struts calls. Debugging can be slow in windows unless you include a -class VM parameters. If you updrade to another version of JBuilder or struts, you should delete all the work files. Otherwise, it is very likely to have problems. Deping at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:386) at www.p_00025blic_0005fhtml.webapps.odin_0002dtracer.jsp._0002fwww_0002fpublic _0005fhtml_0002fwebapps_0002fodin_0002dtracer_0002fjsp_0002flogon_0002ejsplo gon_jsp_0._jspService(_0002fwww_0002fpublic_0005fhtml_0002fwebapps_0002fodin _0002dtracer_0002fjsp_0002flogon_0002ejsplogon_jsp_0.java:305) Any ideas what this means and how to fix it? Regards, Jrgen
AW: JBuilder Enterprise
-Ursprngliche Nachricht- Von: Steven D. Wilkinson [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 6. Februar 2001 17:32 An: [EMAIL PROTECTED] Betreff: Re: JBuilder Enterprise Did you figure out how to debug JSP's in the Enterprise Version? thats what I'm currently working on as I expected a much better performance from that... The first problem I still working on, however, is that it seems to be impossible to tell the Tomcat that comes with JBE which directory to use for configuration info. It always uses the root of the C: drive. As it appears to me right now, I'm no longer sure whether the Enterprise edition is worth the investment as the better debugging support would have been my main point in buying it. Perhaps I'll try to contact Inprise about that topic but I'm not sure whether they are willing to offer support to a not-yet customer... Jrgen
RE: JBuilder Enterprise
Hotspot is what causes debugging to be so slow. We have found that passing "-classic" as a VM Parameter, which disables HotSpot, will dramatically increase performance. In my case I went from a 2 minute startup time to about 5 seconds, it actually makes the debugger usable. That was with JBuilder Professional 4.0. ~Bruce -Original Message- From: Deping Chian [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 06, 2001 9:09 AM To: [EMAIL PROTECTED] Subject: Re: JBuilder Enterprise Lind Jrgen wrote: Hi, after the discussion on using JBuilder for Web Development, I decided to try the Enterprise Edition... While my stuff worked fine with the Foundation version (and an "external" Tomcat), I cannot get it running within the JBuilder Environment. After I managed to tell the internal Tomcat where to find the struts TLDs, Tomcat complains about some missing attribute: javax.servlet.ServletException: Missing resources attribute org.apache.struts.action.MESSAGE Discard JB4's internal Tomcat (older version). Download tomcat 3.2.1, and new struts nightly build. create a new library set (call it tomcat3.2.1 if you want), add all jar files in tomcat-3.2.1/lib directory. I do database apps with interclient, so I put my interclient.jar there. Also I used GenericDataSource class of struts, so I put jdbc2_0-stdext.jar there (download from Sun). I have been using these for one of my projects for a while. Debugging is ok in Linux even for struts calls. Debugging can be slow in windows unless you include a -class VM parameters. If you updrade to another version of JBuilder or struts, you should delete all the work files. Otherwise, it is very likely to have problems. Deping at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:386) at www.p_00025blic_0005fhtml.webapps.odin_0002dtracer.jsp._0002fwww_0002fpublic _0005fhtml_0002fwebapps_0002fodin_0002dtracer_0002fjsp_0002flogon_0002ejsplo gon_jsp_0._jspService(_0002fwww_0002fpublic_0005fhtml_0002fwebapps_0002fodin _0002dtracer_0002fjsp_0002flogon_0002ejsplogon_jsp_0.java:305) Any ideas what this means and how to fix it? Regards, Jrgen
