Thursday, 3 May 2007

Future of Java EE II

Today I wrote a discussion proposal for the JavaOne Camp with the same title. Later I realized that some of the ideas I have already discusses in an earlier blog entry Future of J2EE roughly a year ago. The basic idea is to let a component (another word for EJB) spawn from the server back to the client and so we may be able to ditch the Local interface madness. Currently this is somewhat done in the EJB3 Entities where the data can move to the client and then back to the server. keep on reading here

Posted by schaefera at 11:43 PM in J2EE

Responses (0)

Future of Java EE II

Today I wrote a discussion proposal for the JavaOne Camp with the same title. Later I realized that some of the ideas I have already discusses in an earlier blog entry Future of J2EE roughly a year ago. The basic idea is to let a component (another word for EJB) spawn from the server back to the client and so we may be able to ditch the Local interface madness. Currently this is somewhat done in the EJB3 Entities where the data can move to the client and then back to the server. keep on reading here

Posted by schaefera at 11:43 PM in J2EE

Responses (0)

Tuesday, 2 January 2007

JSP Precompilation Horror With Tomcat 5.5 and Maven

Another day wasted on a little but unknown issue with the JSP Precompilation for Tomcat 5.5 with Maven. Finally I found a hint in a dark corner of the Google Universe. Maven 1.x is such a great build tool but when it goes wrong then it goes terrible wrong. The old, ant based project generated and compiled the JSP pages without a problem but when I converted to Maven it failed from the get-go. Then I found a page on the Maven 1.x website with a Jelly script to precompile JSP pages. I used that as a starting point even though tha keep on reading here

Posted by schaefera at 10:07 PM in J2EE

Responses (2)

JSP Precompilation Horror With Tomcat 5.5 and Maven

Another day wasted on a little but unknown issue with the JSP Precompilation for Tomcat 5.5 with Maven. Finally I found a hint in a dark corner of the Google Universe. Maven 1.x is such a great build tool but when it goes wrong then it goes terrible wrong. The old, ant based project generated and compiled the JSP pages without a problem but when I converted to Maven it failed from the get-go. Then I found a page on the Maven 1.x website with a Jelly script to precompile JSP pages. I used that as a starting point even though tha keep on reading here

Posted by schaefera at 10:07 PM in J2EE

Responses (2)

Friday, 21 April 2006

The Truth about EJB3

O'Reilly's OnJava.com features an article about EJB 3.0 and I was wondering what they say. The first thing that surprised me was the fact that the article was not hosted by OnJava.com but by Bea's Dev2Dev website. Aren't there enough writers out there for O'Reilly to write for OnJava.com? To be honest I was expecting from O'Reilly that the make it more prominent to readers how is hosting the article. Nevertheless I was glancing over the article but to no surprise it is not really worth the time reading it. You c keep on reading here

Posted by schaefera at 1:27 PM in J2EE

Responses (0)

The Truth about EJB3

O'Reilly's OnJava.com features an article about EJB 3.0 and I was wondering what they say. The first thing that surprised me was the fact that the article was not hosted by OnJava.com but by Bea's Dev2Dev website. Aren't there enough writers out there for O'Reilly to write for OnJava.com? To be honest I was expecting from O'Reilly that the make it more prominent to readers how is hosting the article. Nevertheless I was glancing over the article but to no surprise it is not really worth the time reading it. You c keep on reading here

Posted by schaefera at 1:27 PM in J2EE

Responses (0)

Wednesday, 19 April 2006

Future of J2EE

So on Day 2 I already have my first problem and that is what topic. Today I am working from home with one eye on the project, one eye on the kids and another one and a half one the house selling/buying process. Finally we are good to go with the signing the loan docs (probably tomorrow) and the buyer of our house should have signed his loan docs by today. Everything peachy expect that the seller of our house tries to be as much uncooperative as possible and so he did not discontinue his cable service even though he is moving out this weekend and so I cannot order the cable and subsequently keep on reading here

Posted by schaefera at 3:23 PM in J2EE

Responses (0)

Future of J2EE

So on Day 2 I already have my first problem and that is what topic. Today I am working from home with one eye on the project, one eye on the kids and another one and a half one the house selling/buying process. Finally we are good to go with the signing the loan docs (probably tomorrow) and the buyer of our house should have signed his loan docs by today. Everything peachy expect that the seller of our house tries to be as much uncooperative as possible and so he did not discontinue his cable service even though he is moving out this weekend and so I cannot order the cable and subsequently keep on reading here

Posted by schaefera at 3:23 PM in J2EE

Responses (0)

Monday, 30 January 2006

EJB3: Progress or just Marketing? Part 1

First, let us check out one of the new EJB3 features called 'dependency injection' allowing you to use Java annotations to make member variables that contain a reference to an object that is set by the container like EJB references, datasources, JMS objects, EJB contexts and more. Debu Panda wrote in an OnJava article:

This method [JNDI lookups] is not only hard for new Java developers to understand, but also error-prone, and thus, it's blamed keep on reading here

Posted by schaefera at 6:15 PM in J2EE

Responses (0)

EJB3: Progress or just Marketing? Part 1

First, let us check out one of the new EJB3 features called 'dependency injection' allowing you to use Java annotations to make member variables that contain a reference to an object that is set by the container like EJB references, datasources, JMS objects, EJB contexts and more. Debu Panda wrote in an OnJava article: