I have been working on Spring and learning Spring MVC to build the site on. I've created the Master Page Template. Choosing the colors is fun and also time consuming. Its like my daughter choosing colors for her coloring app on her ipod Touch. Anything goes. You keep choosing colors and changing them trying to make things better.
I finally settled on Green. Chatak Green :) Ha Ha! White, Green and Gray. With a little sprinkling of Yellow, Red and Orange. No Blue! eh!
The next challenge was to reuse the template across pages. Only the central content will change. How do you achieve this? I wondered off on the web. The age old technique is to use jsp: include. It works. I used it a lot about 10 years ago. But its outdated now. One of the programs I run in office uses Wicket(I just sign team leaves and look at weekly reports) and so I tried reading up a bit. I then meandered to Velocity, Tapestry and finally settled on Apache Tiles. For the simple work I'm doing Tiles is just fine. Its a little old. Wicket is popular and good but then I want to use Spring MVC. So Tiles it is.
Started on Tiles and set it up on Friday. Worked on it yesterday. Finally I'm done. Its working to my satisfaction. Hurrah! Learnt a new thing and used it.
Then came the crash. Today morning when I left for the gym, I had left the laptop on. The cleaning lady came and switched off the power. After I returned from gym, I had my bath and then breakfast. It was time now to get cracking on Login Use Case. I settled down at my desk only to find out the battery had drained and the Laptop had switched off. I cursed the maid silently and fired up the laptop only to find an error. Spring was unable to load from the application. Aaagh! I tried refreshing the project, copied spring-mvc in the lib again but nothing. Out of frustration, I uninstalled Tomcat and reinstalled it. That worked. My app came back up.
I worked a bit on the login page and when I tried testing it, the datasource will not be found. When uninstalling Tomcat, the server config files were deleted. Of course I had no backup. Aaagh Again!
I had forgotten how to set up datasource, as I did it way back in december. Anyhow, I spent a good 3 excruciating hours setting up the datasource. Whatever I did the error won't go. After tearing out a few hair, I finally figured out the in the new datasource name I had one alphabet in Caps while JNDI name I was using in my util class it was not!
A throwback to my developer days. Anyhow its solved now. The login usecase main flow is half done. I'll close it before I move on to business use case Accounts Set up.
I finally settled on Green. Chatak Green :) Ha Ha! White, Green and Gray. With a little sprinkling of Yellow, Red and Orange. No Blue! eh!
The next challenge was to reuse the template across pages. Only the central content will change. How do you achieve this? I wondered off on the web. The age old technique is to use jsp: include. It works. I used it a lot about 10 years ago. But its outdated now. One of the programs I run in office uses Wicket(I just sign team leaves and look at weekly reports) and so I tried reading up a bit. I then meandered to Velocity, Tapestry and finally settled on Apache Tiles. For the simple work I'm doing Tiles is just fine. Its a little old. Wicket is popular and good but then I want to use Spring MVC. So Tiles it is.
Started on Tiles and set it up on Friday. Worked on it yesterday. Finally I'm done. Its working to my satisfaction. Hurrah! Learnt a new thing and used it.
Then came the crash. Today morning when I left for the gym, I had left the laptop on. The cleaning lady came and switched off the power. After I returned from gym, I had my bath and then breakfast. It was time now to get cracking on Login Use Case. I settled down at my desk only to find out the battery had drained and the Laptop had switched off. I cursed the maid silently and fired up the laptop only to find an error. Spring was unable to load from the application. Aaagh! I tried refreshing the project, copied spring-mvc in the lib again but nothing. Out of frustration, I uninstalled Tomcat and reinstalled it. That worked. My app came back up.
I worked a bit on the login page and when I tried testing it, the datasource will not be found. When uninstalling Tomcat, the server config files were deleted. Of course I had no backup. Aaagh Again!
I had forgotten how to set up datasource, as I did it way back in december. Anyhow, I spent a good 3 excruciating hours setting up the datasource. Whatever I did the error won't go. After tearing out a few hair, I finally figured out the in the new datasource name I had one alphabet in Caps while JNDI name I was using in my util class it was not!
A throwback to my developer days. Anyhow its solved now. The login usecase main flow is half done. I'll close it before I move on to business use case Accounts Set up.
No comments:
Post a Comment