Julian Coombes wrote:
>
> I'm relatively new to jetspeed, and one of my goals is to understand how
> everything hangs together, so that I can learn and eventually help build the
> thing. The problem is that when I understand something I have to understand
> every minute detail, and with Jetspeed
Cool!
> that's quite difficult for a
> number of reasons, primarily because its still fairly embryonic, there aren't
> stacks of documentation, and getting it working correctly is still something of
> a balancing act.
Well. I keep hearing that. I tried to fix things with Jetspeed 1.1
but haven't received any feedback since then. Point out any areas that
need to be improved so that we can fix them :)
> However, I've been playing around with Jetspeed and Jbuilder35 under Linux. I've
> managed to configure my environment so that I have a java web server and the
> latests Jetspeed builds + source and Turbine + source all running happily under
> the Jbuilder debugger. It's great, it all works and I can set breakpoints
> within Jetspeed or Turbine, single step just about anywhere, learn how
> everything hangs together and track down all those fustrating exceptions in no
> time.
I used JBuilder 3 back in my when I still used Windoze. The major
benefit was that it was soo powerfull yet *very* fast. I tried the 3.5
version a while ago but wasn't that happy. It was a lot slower since it
is now 100% Java and I didn't like the way the license it. You have to
register to download and then you always have to run this stupid license
key! :(
I tried the new version of Forte that was released about 2 weeks ago.
It was really cool. I think I am going to try it again now that I
realized I was running it without a JIT. :(
It acts sort of "wierd". I am not sure if these are Java issues or
small impl bugs in Forte. The cool thing is that SUN is going to OSS
Forte just like Tomcat. The process is moving along similar to the
whole tomcat initial release so don't expect the code too soon.
Currently I used jEdit. jEdit will *always* beat any IDE because it is
really good at cutting through raw code. Also it is OSS (GPL) and the
plugin API is really nice (I have already written 5 plugins for it).
> There are a few little tweaks needed to get things going, these involve
> one line changes to around three files which for some reason aren't able to get
> settings from JetspeedResources.
Which files?
> If anyone else is using Jbuilder, and would like to know how to set up a
> similar environment, let me know and I'll put together a short HOW-TO. Also I'd
> be interested to know how other people debug Jetspeed.
Currently I just use a combination of the Turbine logger. I wouldn't
call what you are doing debugging though. You aren't actually looking
for a bug. Just seeing how everything flows. I used to use JBuilder a
*lot* for this and miss this functionality now that I don't have a nice
debugger with jEdit.
When I am actually looking for bugs I just add some skeleton code to
test for problems and log accordingly. The only reason I really need
breakpoints is for conditional breakpoints but even this I can live
without.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
The house of the unbelievers shall be razed and they shall be
scorched to the earth. Their code will be open until the end of days.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
