Hi,

I used struts to write a skin to jive (working on it to release as 
sample...). This is not a commercial application, but I first 
modified the standard jsp-skins (awfull html/java mix) then wrote
my own style model-2 version (1 servlet calling several JSP's) to 
end up with a struts rewrite.

Yes, you need some jars and configuration files.
The jars come with the struts download and the config-files are 
quite good commented (so its no problem to clone a sample and then
modified it to your needs).

You can share forms and action-classes, but that will make the 
resulting classes more complex. The only thing that might make 
sense: if you have forms that add new fields to another form,
then you could use the "biggest" form for all actions.

I structured my jive-struts skin as follows:
- some action classes inheriting from my own generalized action-class
  (just to save some code-writing I extracted some methods...)
- some form-objects
- 1 model-object interfacing to jive
- very view data-holding model-objects

What I like in struts, is 
- one job - one class (each class does only one thing)
- I can reuse action elements by chaining them together just by
  defining it in the configuration files.


hope this helps
Alexander Jesse

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 8:03 PM
> To: [EMAIL PROTECTED]
> Subject: Any experienced struts users out there?
> 
> 
> I keep seeing references to using the Struts framework.  I'm 
> curious if
> anyone has used this for a commercial product and can give me some
> feedback.  I'm considering it, but it just seems a little 
> "heavy". I've
> been reading about it a bit and it seems that in order to use this
> software you need jar files, a bunch of tag-libs, some configuration
> files, etc.  Also, when developing with it, you need to generate a
> plethora of application files, one bean for each form, one 
> action class
> for every action, not to mention business logic beans and jsp files.
> Isn't this a little much just to functionally separate out the
> components of your software.  Can someone offer some advice.
> 
> Thanks alot,
> Brett Procek
> 
> 
> -----Original Message-----
> From: Sam Newman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 01, 2001 3:00 AM
> To: [EMAIL PROTECTED]; James Strachan
> Subject: Re: Form validation
> 
> 
> I'm going to check out strust today for this form stuff. Although I've
> not
> fixed it using a simple error substitution tag and using the Input
> taglib, I
> have similar projects coming up I might us it with.
> 
> > > Having just seen the article on form validation on javaworld, I
> would
> like
> > > to of used that instead, but it doen't allow usage in a commerical
> product
> > > :-(
> >
> > Yes. One of these days I'd like to get a simple, lightweight,
> decoupled
> form
> > validator package that is similar to that described in the javaworld
> > article.
> 
> I emailed the guy and he seems to be in the process of writing a
> commerical
> license for the form code. I'll let you know what it looks like
> 
> > I saw that Baracuda contains a form validation package that looks
> > interesting:-
> >
> > http://barracuda.enhydra.org/index.html
> >
> http://barracuda.enhydra.org/cvs_source/Barracuda/docs/forms/f
orms_brief
.gif
>
> though I'm not sure how dependent it is on other stuff (XMLC et al) -
I'd
> rather it be a seperate independent package that could be used
independently
> of the other Baracuda stuff.
>
> James

I've added this to my list of things to look at. All I need now is some
of
this slack time I've been hearing about in project management books....

sam

Reply via email to