rebelutionary
Mike Cannon-Brookes on Java, J2EE, OSX, Open Source, Australia, Atlassian, Bug Tracking, JIRA and more...

Friday, 14 June 2002

Shooting crap: "Symbolically translated, where P = probability: P(Aunt Mary comes through) + P(Grandma's first poodle comes through) + P(Jen's ex-brother-in-law comes through) + P(a person who will eventually die comes through prematurely) + P(an unknown ancestor comes through) + P(Edward can talk himself out of anything) = Damn close to 100 percent." 4:31:02 PM  comment []      Danger CEO: "I've seen a lot of companies start in the consumer (market) and fail and say, 'OK, refocus; it's enterprise because that's where the deep pockets are.' And those are the guys that really get burned in an economy like this where enterprises aren't spending any money." [evhead] The other amusing thing is the phrase "hiptop" which I'm guessing is between a palmtop and a laptop? 10:20:50 AM  comment []      SAAJ. JAXM has been refactored into JAXM 1.1 and SAAJ 1.1. (SOAP with Attachments API for Java). This is good as it allows the SAAJ API to be used with multiple transports, such as JMS. I think the reference implementation of SAAJ still uses dom4j, bless those Sun guys :-) [james strachan's musings] After yesterday's rant on naming SAAJ isn't that bad - it's nice to have an acronym without an X in it, and that can be pronounced (kinda ). 10:18:43 AM  comment []      changing my software development mindset. Two thumbs up! [rc3.org] 10:08:21 AM  comment []      Amazon's unfeasibly high handling charges - this is a funny 'glitch' [The Register] 10:05:57 AM  comment []      Dion Almer has written an interesting article on enhance collection performance using Trove. I like the performance gains, and the fact you can use primitives in collections. However I don't think I'll use this much for the sheer fact it requires another library - and different coding techniques to achieve huge performance benefits. Would you use it? 10:03:55 AM  comment []      I'm sad that O'Reilly has started publishing stuff like "J2EE Form-based Authentication". The author completely waves away the difficulties of the J2EE security model, and his view (and code I think) needs heavy customisation to work on other containers than Tomcat. (No, providing a link to the BEA docs doesn't count as portability in my book) Phrases like: This allows Web applications to take advantage of container authorization support, and to implement application-specific authorization. annoy me very much. What he's really saying is "you will need to recode or change this for every server you want to deploy on". This sucks. Again, so much for J2EE portability. OSUser helps somewhat, but it will be a long while before this problem is fixed. From talking to other developers at JavaOne, they all agreed it was a huge problem. From talking to Sun at JavaOne, they didn't see it as a problem at all - rather an area for the different containers to provide "points of differentiation"! I don't want differentiated containers, I want a usable ones. </rant> 9:56:15 AM  comment []