WishList

Moved blog

2009-02-16T13:33:00.002Z

Moved blog to sourceforge where the project is.

View new blog (with old posts imported) at this url: http://apps.sourceforge.net/wordpress/wishlist

wish-4.0-beta-1

2008-08-18T15:54:00.002+01:00

First beta of wish version 4.0 has been tagged!

In features it is basic compared to 3.1, as only the core add, view, edit and remove for wish lists and items has been implemented.

But is a complete rewrite, with new architecture, testing modules, admin modules, application server modules etc.

Since this is a beta, from now on no new features will be added to the 4.0 version. Some bugs and UI tweaks will be done before a release candidate will be made. A full release might not be done, as it is a featureless release, and this project is a bit perpetually beta (googleish).

With this tagged, a 4.0.x branch will be made from the tag, and the trunk will move to version 4.1 so new features can be added. (A slight cleanup of the svn structure will also be done)

For a confirmed feature plan visit the roadmap, or possible features look at the plans page.

Version 4 to trunk

2008-07-25T11:33:00.003+01:00

After the tagging of milestone 3, the 4th version/rewrite is now mature enough to move to trunk.

Not all usability features from version 3 are implemented, but will be soon. Check roadmap.

New architectures are mentioned in previous post, but basically, split across many sub modules:
Server modules: web services, business logic, domain objects, xsd schemas, oxm marshallers.
Client ones, with a tools module to connect to servers, web reference app, facebook app, flex based app and mobile app.
Admin modules, server and client.
Testing modules, fitnesse and fixtures, soap and jmeter.
Ear moduels, for deploying a whole stack.

New(old) technologies:
Spring web servcies.
Spring security on client, reusing gold Acegi.
Spring security on server for ws-security.
JAXB marshaller for easy xml conversion, but not required as duck typing is encouraged.
Spring mvc.
Struts tiles.
Hibernate/JPA 3.
HSQLDB.
Jetty for easy development and deployment if needed.
Maven 2 for building.
Subversion for VCS ( hopefully mercurial/bazaar soon)

Version4

2008-06-17T18:24:00.002+01:00

Guess what.

Version 3 has been released and deployed, had minor fix to it, and is nearly finished, so guess what?

Im starting version4 from scratch...
Typical one man project. constant changes and rewrites... :)

~/app/branches/dev/flurdy/version4 is now the currently developed branch. When nearing stability it will move to trunk.

New features of this version is even more modularity, seperate admin applications and newer architecture, but still basically the same, i.e. seperate server and client applications, spring web services, jetty server, hibernate, hsql db, spring mvc, facebook application, flex client etc.

version 3 to trunk

2007-11-29T11:26:00.000Z

Right, decided that the 3rd revision of the wishlist application is ready to go to the trunk.

So this branch
https://wishlist.svn.sourceforge.net/svnroot/wishlist/app/branches/dev/flurdy/version3
will now be available here
https://wishlist.svn.sourceforge.net/svnroot/wishlist/app/trunk

This new version has split client(web) from the application(server).
It has also been split into seperate modules. Ie.:

jpa entity and dao module wishDate.

wishWish for all wishlist specific logic.(and eventuall shop, gift etc).

wishServices for web services.

wishWeb for a reference web client.

wishFlex for a possible flex interface.

wishFacebook for a possible facebook application.

Of course this is all very alpha. It utilises maven, jetty, jpa/hibernate, hsql, spring-ws, acegi.

Major items still to do is:

Security - authentication, authorisation and encryption between client and web services. Currently the web client has acegi login but that does not talk with the web services, so is not properly linked.

Message bus. Going to integrate Mule, so maybe utilise its security options.

Also does not have all the functionality of previous versions.
Major missing items:

Wish reservations

Shopping link

Wish details

Version 3

2007-10-01T13:24:00.000+01:00

As im still the only developer on this project, it is still suffers from me testing fad techs.

Version 3 is now being developed, but earlier versions was never finished..

Now it includes spring web services, and thinking off integrating Mule between clients and back end application.

Current development branch is
http://wishlist.svn.sourceforge.net/viewvc/wishlist/app/branches/dev/flurdy/version3/

Maven

2007-01-07T22:04:00.000Z

Using Maven a lot at work, so may switch WishList to using Maven.

It does more than just build the app, and i find a great assistance. However some times people waste a lot of time on it. But I think the benefits are good.

Might also split the project up into sub projects, eg ejb, web service, web app.
Yes, using maven has pushed this idea through.

Reserve a Wish

2007-01-07T21:58:00.000Z

0.4 αlpha version is now out, which got some basic wish reservation features.

Reimplemented the features of the 0.1,0.2 versions during 0.3.

Still need of some very drastic user interface make overs, but functionality first eh?

Christmas has once again passed, so inspiration might suffer though...

New fork is now trunk version

2006-12-13T08:40:00.000Z

Moved my wishpoker fork of 0.3 to the trunk so it is now the main development version.

Switched from Velocity layoutservlet templating to Struts Tiles with Spring MVC.

Sourceforge forbidden

2006-12-04T10:18:00.000Z

Got further down the line with my new fork.
Version 0.3a-1.1 and 1.2 have now been done.

But I came across an odd sourceforge problem with subversion.

For some reason I couldnt create any more tags, branches or refactor any names.

Seems sourceforge have a problem with the svn copy command, I was getting 403 forbidden all the time.

Searched around, got nowhere, but then I found a well hidden report on sf that they were switching to a new svn implementation. And that all users should switch / relocate their svn repositories. Did that and it solved all the tagging / copying problems.

So the 1.2 tag is not quite after iteration 2 but half way to 3....

Forking

2006-12-01T10:49:00.000Z

Right, dropped my JPA/EJB3 fork. JPA doent seem mature enough yet. Easy to use, but I'll wait another 6 months before I use it in any projects again.

Created another fork instead... Doing the 0.3 onwards branch from this fork.

Reworked the web site, and laid out a release plan for the new fork.

It uses Hibernate with HSQLDB. Security is with Acegi. Templating no longer uses Velocity, but Struts Tiles instead.

Also defined 3 areas of the project, Wish, Shop and Gift. Gift is a record of what you receive, so you know whom to thank for what. Wish is as before, Shop is a shopping list, not always linked to wishes.

EJB 3 & Spring 2

2006-08-30T14:02:00.000+01:00

Going to branch of another development direction. I am experimenting with JPA (ejb 3 persistance) and will try to upgrade to Spring 2 at the same time.

May have to make two structures for domain objects, ie if people use j2se or j2ee containers.

SVN branches

2006-08-30T14:00:00.000+01:00

Ive created some more branches. There is now a dev folder, where indivual developers can spring their own branches.

I got one which I should merge back into the trunk as I was experimenting with something that worked.

Creative Commons

2006-06-06T00:31:00.000+01:00

Trying to find out the implications of moving project to creative commons by-sa license.
Or rather my own respect license on top of it.

Project is already LGPL.

May just move it to cc-gpl. Howeverr I like the ethical issues with flurdy's license of respect

Subversion

2006-05-23T17:31:00.000+01:00

Although I was already using subversion, I was hosting the repository myself.

The project has now switched to using SF's subversion servers.

Also the web site is now in subversion.

The base is http://svn.sourceforge.net/viewcvs.cgi/wishlist/

Inside the app folder is the java application, the app-lib is the libraries, while www is the website.

Task and Bugs

2006-05-23T17:28:00.000+01:00

Currently still using sf's task facility.

Would like to switch to Jira, but need stable release and certain amount of deployments before you can apply for the open source license version of it.

Also basecamp cost money, while the free version is not flexible enough,

Velocity

2006-05-23T17:26:00.000+01:00

The templating engine which was planned to be java server faces will now be velocity.

I have used it many times, and the simplicity of it is what wins me over.

Once we got a stable release i may be tempted to try jsf for certain modules again.

Wish List

2006-05-20T14:06:00.000+01:00

This is the blog to be used with the wish list project on sourceforge.net.

wishlist.sourceforge.net