• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 localhost commented Permalink

I'm just finishing Expert One-on-One J2EE Design and Development and think its one of the best tech books I've ever read. Also, I've seen in this and other posts you lean towards not using Struts or JSF in portlets. Do you have some framework code that you've developed on your own? We are currently writing some of our own code to standardize development and wondered if this is how most implementations do it.

2 localhost commented Permalink

I know it comes across that I am against these frameworks, but really I just want folks to understand what they are getting into before they jump in over their heads. My advice is often geared toward first time portal project teams that want to do everything all at once. Folks often get caught up in the hype and forget that the job is to deliver a working portal. I think that all of the available options have a place in portal development.I do not have my own framework outside of using what is available. Although I want to focus on that more this year. Coming up with some ways to help folks use the tools and frameworks in the best possible manner. Some of the areas that I have notice missing are some best practices around logging, handling exceptions, etc., across all of the frameworks. I think what you are doing is great, and mostly what I try and impress upon customers. Building some framework components along with some good development standards is the best way to start.

Add a Comment Add a Comment