It's truly awful that an entity that exists solely to spew spam has "legal recourse" to continue operations when *individuals* have none such. A recent article on salon.com (which, alas, I couldn't find a link to) details how quickly an ISP will yank someone's access, based on unaccountable notices from RIAA-related organizations.
I also felt pain at the lack of (free, open) availability for WebObjects.
I've been working on my own framework, Tapestry, which shares many features with WebObjects, but uses a very different component object model that is much more compatible with Java and J2EE.
(It isn't quite as powerful as WOF, and it makes the developer do a few extra things, but its more open, extensible and scalable and not tied to any particular vendor).
We're using Tapestry internally on a very important application for one of our clients (a multi-billion-dollar bank interest).
Tapestry is LGPL and works quite well; it's also heavily documented (in Word and using JavaDoc), and has tutorials and example code, including a real J2EE application.
I got sick of waiting and developed a component object model for web application development in Java. It's called Tapestry and will be released as open source on SourceForge as soon as I can my damn company to open a port for ssh in our firewall!
We're using it for development of customer web applications already and we like it. Don't have a good Object Relational bridge yet (to do it as right as EOF is very, very, very hard... my first attempt wasn't good enough).
You can find out more at:
http://tapestry.primix.com/tapestry
Off topic? Of course... but this is just one example of how Apple has screwed up; they've let thier best, most marketable technologies languish. They also have a habit of screwing thier supposed partners. Our shop is very, very happy to be able to do WebObjects style development without having to deal with Apple.
Slashdot Mirror
It's truly awful that an entity that exists solely to spew spam has "legal recourse" to continue operations when *individuals* have none such. A recent article on salon.com (which, alas, I couldn't find a link to) details how quickly an ISP will yank someone's access, based on unaccountable notices from RIAA-related organizations.
I've been working on my own framework, Tapestry, which shares many features with WebObjects, but uses a very different component object model that is much more compatible with Java and J2EE.
(It isn't quite as powerful as WOF, and it makes the developer do a few extra things, but its more open, extensible and scalable and not tied to any particular vendor).
We're using Tapestry internally on a very important application for one of our clients (a multi-billion-dollar bank interest).
Tapestry is LGPL and works quite well; it's also heavily documented (in Word and using JavaDoc), and has tutorials and example code, including a real J2EE application.
I got sick of waiting and developed a component object model for web application development in Java. It's called Tapestry and will be released as open source on SourceForge as soon as I can my damn company to open a port for ssh in our firewall!
... my first attempt wasn't good enough).
... but this is just one example of how Apple has screwed up; they've let thier best, most marketable technologies languish. They also have a habit of screwing thier supposed partners. Our shop is very, very happy to be able to do WebObjects style development without having to deal with Apple.
We're using it for development of customer web applications already and we like it. Don't have a good Object Relational bridge yet (to do it as right as EOF is very, very, very hard
You can find out more at:
http://tapestry.primix.com/tapestry
Off topic? Of course