First, you have a very nice solution here. A few comments and questions:
A nice feature would be to move the shipping address info under each orderline so a user can select, edit or add a new shipping address to each product. From the demo site, it seems you can add as many addresses as you want but you can't assign different ship-tos to the orderlines. A user should be allowed to do this. For example, orderline 1 ships to Phoenix, and orderline 2 ships to New York. I will look at an nice way to do this for you if it isn't already implemented. Perhaps this is just a UI issue ( I haven't jumped into the source yet).
Any plans on a Spring/Hibernate migration ?
Last quick question after quick database scan, why no foreign key constraint on order table back to customer to prevent order deletion? I can't think of any situation where I would want to delete an order, regardless of status.
A nice feature would be to move the shipping address info under each orderline so a user can select, edit or add a new shipping address to each product. From the demo site, it seems you can add as many addresses as you want but you can't assign different ship-tos to the orderlines. A user should be allowed to do this. For example, orderline 1 ships to Phoenix, and orderline 2 ships to New York. I will look at an nice way to do this for you if it isn't already implemented. Perhaps this is just a UI issue ( I haven't jumped into the source yet).
Any plans on a Spring/Hibernate migration ?
Last quick question after quick database scan, why no foreign key constraint on order table back to customer to prevent order deletion? I can't think of any situation where I would want to delete an order, regardless of status.