hi, just joined the list, and i have a newbie question about struts design.
this is where i am at. i have looked at struts about a year back, and rolled my own version of mvc web architecture, stealing several basic ideas from struts. at the time, it appeared that many features of struts were not apparently applicable to the project, so the overhead of configuring struts didn't seem justifiable. now the need for many of the struts features has become pretty concrete, and so i am in process of incorporating struts rather than re-inventing the wheels (and axels and cupholders, etc). while adapting the code base to use struts, i get the sense that: these are the classes/packages; for many, you can configure/adapt it to your needs via config files; in other aspects, you may want/need to subclass and override some of the classes to fit your needs. for the later category of adaptation (subclassing/overriding), the best way seems to be to look into the source to ascertain the default behavior and to ensure the overriding implementation is proper. to put it simply, struts' interface doesn't seem to be clearly defined. by "clearly defined" interface, i mean programming/usage could/should be via/against the interface without delving into implementation details. if not, pointer(s) to the authoritative interface defnitions would be much appreciated (i told you i'm a newbie). but if so, is this deliberate? and the reasoning behind? some obvious (generic) arguments i could see are: 1. it's advantageous in order to provide greater flexibility, struts being a development framework 2. struts (and web app requirements) are progressing rapidly, so loose interface may serve the purpose better are there more specific reasons other than these? or perhaps it is simply a documentation issue? thanx for any insight/info, dasa ps: i am sending this to both the user and dev lists, thinking the subject is of interest to both. perhaps you'll correct me. again, a newbie here. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
