Hi I've tested wicket before it was in the apache incubator and found
it to be awesome, since then we have adopted it and I have been
migrating all legacy applications for my company for the last 3 years
aprox.
Now I have to build a small app to manage small accounting and
logistics for my wife's """"Business""""
She is opening a small printing shop for small business labels, such
as wine bottle labels, clothing labels, bags, etc.
At work I use wicket with an "ingenious" CORBA server, courtesy of the
legacy applications.
Now I am free to do whatever I want. This is the worst part. :-)
I would like to help out and test maybe wicket 1.5 and some good
database solution.
Can you share some comments or recommendations on what to do?
For Instance, I once read about Active Objects, I pretty much liked
the idea and built some prototypes, but now the site is exactly the
same and found their latest released is from 2008. So that is no so
edgy...
I don't wish to use hibernate, but could be some other "object
relational mapping", even hibernate if you insist... :-)
So, ideas on what to use?
UI = Wicket.
+ 1.4?
+ 1.5?
middle layer?
Persistence?
Thanks in advance,
f(t)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
