March 2008


Productive Day Today

Implemented a workaround today to fix what was stopping my retrieved form fields from being populated. The problem was that their destinations had not been created yet, so I created a temporary variable for each field to be stored in the meanwhile.

After that I started working on the PDF creating servlet, the results of which can be seen in the previous post. Just more fields and “chrome” to be added to that.

A link to the first pdf i’ve created in the webapp.

A bit to go to decorate it more and add the rest of the fields, but the name fields are generated dynamically!

Policy PDF

Continuing with acegi session integration

Have been carrying on working with the acegi integration, a logged on user will now have their quote associated with their user id, while an unregistered user will be registered.

Spent most of today working on a form field handler, to persist and retrieve saved form entries per user.

The persisting is working on both sides, while currently the retrieval is just working server side. Just need to get flex to populate the fields from the returned xml/jsp.

Meeting with Howard 25th March

We met with Howard yesterday, mainly discussing progress on the two components wespent most of last week on, the acegi session integration on my part, and the document up/down-loading on Kevin’s.

Apache Cactus: http://jakarta.apache.org/cactus/

Good page on acegi:

http://www.tfo-eservices.eu/wb_tutorials/media/SpringAcegiTutorial/HTML/SpringAcegiTutorial-1_1-html.html

Request More Info Handler

Today I created the request more info pages for Lump Sum, Regular Savings and Pensions, as well as a handler that can deal with each of them generically.

I implemented this by using a field sent by flex called SpecificFormFields which specifies the number of specific fields that the current form submission contains, as well as a corresponding number of SpecFormTag and SpecFormText fields, each specifying the label and form field associated with that specific form entry.

The handler then iterates through each one in a for loop, counting up until n = SpecificFormFields and gettig SpecFormTagn and SpecFormTextn.

Session problems

We came across session problems again today, when Kevin was trying to implement the Download function in the Customer Document Repository, again the problem is between sharing of sessions between flex and the browser, this will have to carry forward to Friday, as the solutions we’ve tried so far have all failed. I’m wondering if there’s a complementing fileDownload component to flex’s fileUploading one? If so hopefully we could use our workaround from Monday.

Installed the Metrics plug in for eclipse, we’re looking good, see below:

metrics.jpg

Busy St Patricks day

Spent today creating product pages for all of our products, text will need to be replaced with original text by Dermot.

Most of the day was taken up with both of us trying to fix what seems to be a big problem with flex/flash. Kevin was working on his file upload component, which was failing because fo authentication issues, apparently it creates a new session thus losing all of the previous authentication.

After a lot of trial and error we worked a way to embed the session id into the request to the upload service, which tomcat interprets and passes on to the servlets.

With full text on all of the product pages the shop front is starting to look nice, so with a bit more ‘chrome’ and more comprehensive subcomponents it should provide quite an extensive service.

Plans for the week ahead

We’re meeting with Dermot to give a release next Friday, here are my plans between now and then:

Create templates and editable text for the offline products
Add in login functionality

Validation of form fields

Email component

Server side validation

Form field persistence – a handler that fires on quote Generate? or quote Generate and copletePurchase handler passing request to FormFieldPersister, FormFieldDAO.

Similarly, a requestHandler for form field value requester.

Online purchase shaping up

Only one more step to add to the online purchase process.
At present it works as follows,

A customer registers as a site user, this gives them a site user id.
This is associated with any quotes or purchases.
I they make a purchase, they become a client and so a row is created for them in the climas table, and a corresponding foreign key is set in their site user row. Emails are sent to the customer and to the DM Office, sample below

Quote 104 has been generated and purchased by customer 224.

David Gibbon, 09/03/1970 purchased Hibernian Life Cover Only at EUR631.63 (Annual).

The customer’s contact details are as follows:
Telephone: 085146xxxx
Email: Link to david@xxxxxxx.com
Address:
200 The Street,
Nice town,
Dublin

Customer’s client key is 224.

Customer accepted execution only disclaimer at time of purchase (11/03/08 21:49)

All that needs to be integrated now is the login functionality, which will retrieve a site user id from the backend, to stop multiple clients being created

for one customer.

My plan of action for the rest of the week is to implement this last piece of functionality, and then try to get all of the products (both on / offline) finished on the shop front side.

I’ve sent Dermot another email asking for furhter information and feedback on some of these products.

Got the external quote requests going through dcu proxy in the labs late last night, so that’s that out of the way. Emails are a little problematic as the DCU mailserver does allow relaying. Perhaps I’ll direct my local mailserver through the dcu proxy, or just use dcu addresses while in dcu.

The Assignments have now all come in, and there really isn’t a moment to spare, so we’re just focussig on getting each assignment out of the way as quickly as possible, hopefully leaving the last few weeks free for a full final sprint on this.

Next Page »