| objectus 2004-05-25, 11:33 pm |
| I don't know if there is a comparison somewhere, but I can tell you some of the limitations from experience:
1. The test environment redeploys all of the portlets to a single Debug page every time you start the test server. This means that any pages you have created with portlets on them will not have those portlets after a restart. It also means that as you
add more portlets to a project, that page gets bigger and bigger. It's a bit of a pain because of that.
2. Without some patches from IBM (maybe they're in the last couple of point releases), you can't have a portlet war reference a Java project as a dependency. You can put them in WEB-INF/lib, but this means you'll have to use something like Ant to deploy
them, which is also a pain.
Hm, I'm sure there are others I'm not thinking of right now, but all that being said, it's still a better way of doing development than having to use the full portal server all of the time, just for debugging if nothing else (it's way too painful to debug
in the full portal server--so slow it's not even funny).
A good dose of XmlAccess can also help make the test environment more usable.
--Kevin
http://www.SurgingSystems.com
|