Source Code Management
open source java project/portal thingey.
Biztalk.org is closing
Almost two years ago at XMLOne in San Jose, I publicly predicted that schema repositories were going to fail. Now I get to say, "I told you so." Microsoft's BizTalk is closing its doors one week from today. Elliote Rusty Harold, Cafe au Lait - July 12, 2002
Poor Obfuscation Implementation.
Open source Java persistence frameworks.
Anarchy & Infrastructure
This parrot is no more!
Don's romantic evening with J#
I have to admit that when I heard about J#, I was massively skeptical. After spending an evening with it, I have to admit that it appeals pretty deeply to the subversive in me. The thought of running Ant, Xerces, or Tomcat under the CLR is pretty interesting. Don BoxHow is Don going to run Ant, Xerces, and Tomcat under the CLR? All of those things require Java 2, but Microsoft's Java VM is still stuck on JDK 1.1.4 - isn't it? I think he has his beer goggles on. And another thing: did he "probe every corner and alcove" of Stephanie or Visual J#.Net? That article is really creeping me out!
XDoclet moving to Velocity
As Jeff has correctly pointed out, XDoclet will start on a major refactoring to Velocity after the next release (in a month or so we hope). XDoclet 1.1.2 has 17000 downloads and many contributors. vDoclet is the third tool in its category (EJBGen, XDoclet and vDoclet). My question is: Do we need another one? Aslak Hellesoy from the Velocity mail listAslak is encouraging the VDoclet team (a team of 1?) to join forces with the XDoclet team. XDoclet is preparing to drop the weird XML templates and adopt Velocity as it's templating language. That is great news. Those XML templates are butt ugly.
Roller 0.9.4.1 source release
% tar xzvf roller-src-0.9.4.1.tgz % tar xzvf roller-tools-0.9.4.1.tgz % cd roller % build all
Motivational chatter
The machismo of this kind of U.S. business prose trickles through from the rhetoric of the sports field. The CEOs are the multimillion-dollar sports stars, the employees are encouraged to think of themselves as part of a winning team, and sales and marketing departments are heavy with the motivational chatter of sports. Playing the game, Red HerringI hate that motivation chatter but the fact that it is based on sports cliches is what really makes it unbearable.
The 101 Dumbest Moments in Business
Actions part of Controller or Model?
[Struts] developers have a differing opinion on whether the Action class is part of the controller or the model. The argument for it being part of the controller is that it isnt part of the real business logic. If Struts were replaced with an alternative framework, chances are the Action class would be replaced with something else. Therefore, it really isnt part of the model domain, but rather tightly coupled to the Struts controller. It doesnt make sense to put business logic into the Action, since other types of clients cant easily reuse it. From Chapter 3 in the Server Side's Jakarta Struts Book Review ProjectIn the alternative framework WebWork, the action classes could be considered to be part of the model because they include no presentation specific code (i.e. no Servlet API calls). Some would argue that this is better and allows re-use of actions, but I think it is just different. For Roller, the WebWork approach really does not buy me much - my 'business logic' is already re-usable and encapsulated in my model interfaces and classes.
Awesome!
Hypothetical question
WebGain followup
On Tuesday, the parking lot at WebGain's Santa Clara, Calif., headquarters was empty and the entrance to the building was locked.
More on WebWork
Not tied to the web - WebWork (despite it's unfortunate name!) is not tied to the web at all. As I said, we use it as a general purpose command framework within our application. There is also a ClientAction which allows you to run any action over RMI. There is a project to tie SOAP into WebWork at a very low level.
Yet Another MVC Framework
WebWork - WebWork is a web application framework for J2EE. It is based on a concept called "Pull HMVC" (Pull Hierarchical Model View Controller). The basic idea is to separate the site programmers' and site designers' tasks.If you've got pointers to WebWorks articles, postings, threads, etc. please send me a couple.It has a small API and easy to use tag library in order to make it as easy to use as possible. It supports the notion of actions that are just JavaBeans. This means that they have setX() methods for incoming parameters, an execute() method to perform the action, and getX() methods to retrieve the result data. This ensures that all actions only contain the code that is required to perform the logic.
The tag library has also adopted this philosophy. They only provide tags to extract and iterate over the result data so that formatting the output as HTML, WAP, or what ever is as straight forward as possible.
« Previous page of month (Jul 2002) | Main | Next page of month (Jul 2002) »