Yes. Its rudimentary but...boy, did it take a while!
I have been working at this for about 10 hrs per week since my last blog post 9 weeks ago.
APPLICATION DESCRIPTION
The application use case scenario is pretty basic. An administrator uses the "Admin Console" screen on the left to select cities to make available to users. On the right, users select cities to view weather status. As the user types a city that they would like to add, the app helpfully provides suggestions. The suggestions are limited to just the cities permitted by the administrator in the Admin Console.
WHY DID IT TAKE SO LONG
Its hard to remember all the challenges but I'll try to list some. I'll probably add more to this list and get into more details on these in future posts.
Java/POJO (Plain Old Java)
Applied new (to me) concepts to handle Exceptions, Collections, XML parsing, and even variable declarations and scope (a missing use of "final" declaration was the source of 10hrs - 20hrs of tedious debugging)
Java/EJB (Enterprise Java Beans)
Challenges with consuming SOAP Web Service from J2EE/EJB which I was able to do just fine using regular Java
Java/JPA (Java Persistence API)
Challenges with Java Persistence API syntax and usage
Google GWT
Spent many hours learning the idioms of GWT framework particularly around user interactions and Client/Server Remote Procedure calls.
Apache Derby
Challenges with starting, configuring Apache Derby database as standalone server outside of Eclipse
IDE.
NEXT STEP...
Heavy sigh and deep breadth...deploy servers and services to the cloud!
No comments:
Post a Comment