Skip to main content

JavaPosse Episode 161

By tvik
This is a tracklist of a JavaPosse Episode.
Original shownotes and the audible mp3 can be found here.
More tracklists can be found here.

Open JavaME and JavaSE interviews

00:30 Intro : About roundup signups, skiing, next episode (will be a listener feedback session), etc
05:00 About interview at Sun Java Mobile and Embedded Developer Days
06:10 Sun aquiring MySQL
12:52 Oracle acquiring BEA
17:25 Is the Geronimo in trouble?
20:00 Applet of the Week: Sea Level applets
21:05 Project of the week - LoboBrowser

Quick News
23:43 JDK6u4
24:00 CommunityOne 2008 call for participation
24:38 JavaZone 2008 call for presentations
25:17 Jazoon 08
25:50 EclipseCon
26:21 Artifactory, Maven
26:34 Chris Richardson's blog entry
27:04 JSR 323 - Strong Mobility for Java
27:41 Bill Venners has released a new testing tool - ScalaTest ('JUnit for Scala')
28:06 The Developer.com product awards for 2008 have been announced
28:32 JackRabbit 1.4
28:49 Apache Jakarta Commons Pool 1.4
29:10 Neal Gafter: Java is dead
29:32 Posse listeners in Pune, India
30:02 Apache Lenya 2.0 (Content Management System)
30:26 Sun is holding another Second Life virtual meeting
30:36 Sun's JavaFX tools to interop with Adobe

31:38 An easy-going interview with Roger and Terrence at Sun Java Mobile and Embedded Developer day
32:16 Are You gonna have this scene next year?
35:50 Why hasn't there been an event like this already?
42:40 ...Google's Android is a reflection that so many things in the industry went wrong...
43:00 Some announcements
45:15 One of the big goals of the community...
45:45 Vodafone r&d
46:50 Squack (?) virtual machine is open source
49:10 When the Sun spot blend? (?)
56:10 Thanx

56:45 Outro
Labels:

Comments

Post a Comment

Popular posts from this blog

Client's transaction aborted

By tvik
I've met the above error message using a Wicket 1.2 / EJB3 intranet application under Glassfish v2 . Here is the more particular head of the stack trace: javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted at com.sun.ejb.containers.BaseContainer.useClientTx(BaseContainer.java:3394) at com.sun.ejb.containers.BaseContainer.preInvokeTx(BaseContainer.java:3274) at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1244) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195) at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:127) This exception raised on the integration server sometimes, randomly, for simple page fetch operations. After pressing reload on the browser, the operation was usually successful. I couldn't reproduce the failure on the local machine where I regularly restart the app server and...
3 comments
Read more

jxl.log

By tvik
In an intranet production environment we have running a Glassfish v2 appserver with several J2EE applications which all use JexcelApi , a.k.a JXL, which is an open source library for accessing, generating or manipulating Microsoft Excel documents. We use version 2.6.3 of JXL because it's the recent one in the Maven repository which we use, however, at the official JXL site there are newer versions. Additionally we have log4j and Java Commons Logging (JCL), ignoring Glassfish's JSR-47 Java Util Logging (JUL) facility. Application #1 uses purely log4j and gets its log4j.xml config from a custom location. Application #2 runs Java Commons Logging with no explicite configuration file given, so JCL uses the default JUL facility of the appserver. Application #1 had been running for a long time without problems but when we installed #2 we realized that a jxl.log file had been created in the glassfish/domain/domain1/config directory and it's rapidly growing. As it happens, we ...
3 comments
Read more

Standup

By tvik
Recently I was asked if it makes sense to do standups. Is it just a formal waste of time? Wouldn't it be more useful to spend the same amount of time by actual work? This is how our standup looks like, this is how the work would look like without it according to me and this is why I think it's worth doing standups: Standup optionally starts with a half-minute long announcement by the Scrum Master if somebody is missing and when will be this person available again. Without standup:  We could check out this information from a well-prepared shared calendar but unexpected lates or illnesses which are missing from the calendar would require a little bit more communication and irrelevant discussion during the day. It would cause some delay for sure. Then we look at the burn-down chart of the sprint and to the status of the latest nightly build. Is it stable, what about automated tests which were run last night? We make a common standpoint in one minute which is clear a...
Post a Comment
Read more