J2EE in a nutshell

J2EE specifies Enterprise Java Beans for handling data, where the data and the client accessing it may or may not be on the same system. Entity beans are used to encapsulate the data in the database—instead of accessing the database directly, you create an entity bean to do it for you. That way the client can use the entity bean and not need to know about SQL. However, the person writing the entity bean doesn’t really want to have to know about SQL either.

Learning J2EE, continued

I’ve just successfully written an EJB, deployed it, and called it from a servlet and some JSP. Right now, it looks like the EJB specification has the highest complexity-to-benefit ratio I’ve ever encountered in a programming API. Sure, I’m a beginner to J2EE, but I’m an experienced software developer, and over the years I’ve developed an intuitive ability to recognize a pile of steaming crap when I see one.

Up and limping with J2EE

Today I decided that writing my own application deployment descriptors was unnecessary drudgery, so I tried out xdoclet. It doesn’t work, I get various stupid error messages that I see (from the mailing list) have been reported by other people too. I strongly suspect crapulence on xdoclet’s part, since its API changed between release 1.1 and 1.2, and will change again completely for 2.0, which is a complete rewrite. (A lot of Java projects are like this.

J2EE is teh suck

21:32:26,041 ERROR [Server] start failed org.jboss.deployment.DeploymentException: Could not create deployment: file:/opt/jboss-3.0.6_tomcat-4.1.18/server/default/conf/jboss-service.xml; – nested throwable: (java.lang.AbstractMethodError: org/jboss/deployment/scanner/AbstractDeploymentScanner.scan) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:835) […etc etc…] Stock JBoss/tomcat downloaded 10 minutes ago, stock RedHat 8, Java 1.4.0. You know, J2EE really sucks dog balls. Every J2EE environment I’ve tried to get working has had some massive brokenness about it. Does anyone have any suggestions?

J2EE battles

After about three days of more-or-less solid effort, I have almost got a WebSphere development environment running. WebSphere is running, the HTTP server is running, SSL is working, and DB2 is running… however, the HTTP server doesn’t map the /servlet/ URLs to WebSphere when I connect to it via SSL. I’m assuming the problem is somewhere in the httpd.conf file, which is huge and ugly. I’ll have to sit down with the documentation tomorrow morning and hope for an “Aha!