tags: Java
, JasperReports
, J2EE
posted: Wednesday, January 25th, 2006
I haven’t tried this yet, as on my current project we are deeply emmersed in Jasper Reports, but this will be interesting to take a look at.
Brian began developing applications for the Internet in 1995, and has continued to architect, design and develop Internet software for the last 11 years, including projects for IHG, IBM, Brighthouse, and Cox Target Media (Valpak).
Here he shares his thoughts and opinions on Internet Software Architecture and Development, chronicles his current projects and areas of research, and give tips and tricks he discovers along the way.
tags: Java
, JasperReports
, J2EE
posted: Wednesday, January 25th, 2006
I haven’t tried this yet, as on my current project we are deeply emmersed in Jasper Reports, but this will be interesting to take a look at.
tags: Java
, Architecture
, IT Management
, PHP
, J2EE
posted: Thursday, October 20th, 2005
While I’ve been working in Java for the past 7 - 8 years, I definitely do not label myself as a Java -loyalist. I’m an Internet Application loyalist, and I want to do whatever it takes to get the apps done right and done fast. I agree with Andreessen’s statement that Java’s complexity has grown by leaps and bounds. The learning curve has become too steep, and many IT departments are finding it difficult to train an employee in all the technologies needed to go in and make a simple change to a module on their web site. When you have to know Spring, Hibernate, Struts, Tiles, SQL/RDBMS, and make edits within all these technologies in order to add one field per the client, it becomes utterly ridiculous.
It may be fun for us developers, and we love all the separation of the various layers of the application, but it’s no good for the client, and that’s who pays us. So we as Architects, Analysts, Designers, and Developers better come up with something that provides for much faster turnaround time.
tags: Java
, JasperReports
, J2EE
posted: Thursday, April 14th, 2005
The report I’m working on now requires a running count for each line item within a group. Fortunately, Jasper has an easy way of doing this, by simply using $V{groupname_COUNT}, where groupname is the name of your group.