Hi Alexander, > are there equivalent concepts in jetspeed for the ActionForm.
I have written entire apps in both Turbine and Struts, so I think I'm qualified to give my opinion ;). You could try using the Turbine Intake service. Unfortunately, it lags somewhat behind ActionForms/Validator in terms of usability and documentation. In Jetspeed 2.0 there is talk of facilitating Struts actions as an alternative strategy for portlet development. However, I don't know the current status on it. AFAIK, 2.0 is in the very early stages development as it is the JSR-168 compliant version of Jetspeed. Lately I have been working on re-factoring a lot of the core portlet action model in Jetspeed 1.4x. If you have any suggestions on how to integrate struts actions into the mix, I would be happy to hear them. -scott > -----Original Message----- > From: Alexander Bibighaus [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2003 6:01 PM > To: 'Jetspeed Users List' > Subject: struts concepts in jetspeed > > okay i did some searching on the archives before sending this and i > couldn't find anything so I'm asking. > > i'm fairly new to jetspeed. i've got quite a bit of experience using > struts. i'm developed a few portlets and figured > out the basic concepts of the events in turbine...at least enough to be > dangerous. > > what i'm wondering is: > > are there equivalent concepts in jetspeed for the ActionForm. More > specifically, the ability to associate a bean with > a form and populate it before calling your "Action". > > also, what about the ActionErrors and <html:errors> concept > > and if you know struts and jetspeed already, i'd appreciate maybe a few > comments about the basic similarities/differences. > > > thanks for any hel
