Juan Alvarado wrote:
That is the underlying concept of a tool like xdoclet. It allows you
to edit/generate the struts config file from your action classes instead of the file itself. It's also that way for EJBs, JDO etc...etc... It basically comes down to the preference of the developer.
For EJBs etc it's great because it generates classes etc that you'd have to code yourself. It's just for Struts that I don't like it - mostly because one of the benefits of Struts is having a central config file where you can change things. For example, what if you decided you wanted to forward to a different page in an action mapping. All it takes is to change a forward name in the config file and restart. Using xdoclet you have to go in and find the java class it's defined in then change it there and then recompile the class probably even redploy a war. Same thing if you want to change the scope of a form. But you are right, comes down to preference (Tim used it in NAM application that I'm still stuck with:). I just think for Struts it makes the application more fragmented and more difficult to maintain. XDoclet is great for a lot of other stuff though (I like it for writing custom tags).
Ok I'm out of here. Won't be back 'til Tuesday. Hope I don't blow off the Sunshine Skyway Bridge tonight:)
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
