Re: Disadvantages of Struts?
Yes, we should be passing an API context object instead of tucking things away here and there in the various contexts. We started work on one during the 1.1 march, but it was sidetracked by the module initiative. At this point, it will probably be slated for Stuts 2.0. The other questions speak to whether you want to take a declarative approach to writing a web application. If you are writing a small application, the strategy of using XML configurations to deploy object graphs can be more trouble than it's worth. But if you are writing a larger application, most developers believe it is much better than the alternatives. (Been there, done that.) Of course, your mileage may vary. There are several other web application frameworks available, most of which are tracked by the wafer project. Choosing a framework is like choosing shoes. You really need to try them on for yourself to be sure. Like most software products, Struts is far from perfect. But, like Java itself, for complex enterprise applications, many developers find it's the best alternative available today. Neither Struts nor Java is the best choice for all applications and all teams, but most people do find that it is a good choice for larger applications that need to be maintained and improved over time. If there is a disadvantage to using Struts, it's that the underlying design is so darn useful that people try to use it as an application framework rather than a WEB application framework. Many teams invest *way* too much business logic in ActionForms and Actions. Why? Because most large application do need to utilize the Context and Command patterns. But because they don't have a distinct business framework, people usurp the Struts classes. The Chain of Responsibility package in the Commons Sandbox is a first step toward creating a business layer framework. Webwork is doing something similiar with their xwork package. -Ted. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
BDY.RTF Description: RTF file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
Thanks, Ted. I agree that Struts is the best option available today. Like you said, there are areas that Struts can, and probably should, improve. I am delighted to hear that some of them will be addressed in 2.0. - Robert. - Original Message - From: Ted Husted [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 4:40 AM Subject: Re: Disadvantages of Struts? Yes, we should be passing an API context object instead of tucking things away here and there in the various contexts. We started work on one during the 1.1 march, but it was sidetracked by the module initiative. At this point, it will probably be slated for Stuts 2.0. The other questions speak to whether you want to take a declarative approach to writing a web application. If you are writing a small application, the strategy of using XML configurations to deploy object graphs can be more trouble than it's worth. But if you are writing a larger application, most developers believe it is much better than the alternatives. (Been there, done that.) Of course, your mileage may vary. There are several other web application frameworks available, most of which are tracked by the wafer project. Choosing a framework is like choosing shoes. You really need to try them on for yourself to be sure. Like most software products, Struts is far from perfect. But, like Java itself, for complex enterprise applications, many developers find it's the best alternative available today. Neither Struts nor Java is the best choice for all applications and all teams, but most people do find that it is a good choice for larger applications that need to be maintained and improved over time. If there is a disadvantage to using Struts, it's that the underlying design is so darn useful that people try to use it as an application framework rather than a WEB application framework. Many teams invest *way* too much business logic in ActionForms and Actions. Why? Because most large application do need to utilize the Context and Command patterns. But because they don't have a distinct business framework, people usurp the Struts classes. The Chain of Responsibility package in the Commons Sandbox is a first step toward creating a business layer framework. Webwork is doing something similiar with their xwork package. -Ted. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
Robert Tran, you were griping about config files and the need to go between code (your Actions) and the xml config files. Other developers have scratched that itch already. Check out XDoclet: http://xdoclet.sourceforge.net/ This piece of software will generate your configuration files for you via an ant task. You can keep everything relative to an Action in one place, inside your Action class itself. You use JavaDoc-like tags to define your config files. The following is an example from a real application I maintain: /** * @struts:action name=GetMessageAction * path=/GetMessage * @struts:action-forward name=editMessage * path=/EditMessage.jsp */ The Action associated with the above JavaDocs is responsible for retrieving a bean, putting it in request scope, and forwarding to the proper page for editing. Having everything in a single file (the Action) is useful and is easy for me to keep in my head. When the WebDoclet Ant task executes, it will parse those tags and generate Struts-config.xml for you. It can generate ActionForms, Validator xml files, and more. It can also be extended to generate other code of your choosing. It works very well and there only a slight learning curve. something to look at and think about, perhaps. mark Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2003 1:45 PM To: Struts Users Mailing List Subject: Re: Disadvantages of Struts? Thanks, Ted. I agree that Struts is the best option available today. Like you said, there are areas that Struts can, and probably should, improve. I am delighted to hear that some of them will be addressed in 2.0. - Robert. - Original Message - From: Ted Husted [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 4:40 AM Subject: Re: Disadvantages of Struts? Yes, we should be passing an API context object instead of tucking things away here and there in the various contexts. We started work on one during the 1.1 march, but it was sidetracked by the module initiative. At this point, it will probably be slated for Stuts 2.0. The other questions speak to whether you want to take a declarative approach to writing a web application. If you are writing a small application, the strategy of using XML configurations to deploy object graphs can be more trouble than it's worth. But if you are writing a larger application, most developers believe it is much better than the alternatives. (Been there, done that.) Of course, your mileage may vary. There are several other web application frameworks available, most of which are tracked by the wafer project. Choosing a framework is like choosing shoes. You really need to try them on for yourself to be sure. Like most software products, Struts is far from perfect. But, like Java itself, for complex enterprise applications, many developers find it's the best alternative available today. Neither Struts nor Java is the best choice for all applications and all teams, but most people do find that it is a good choice for larger applications that need to be maintained and improved over time. If there is a disadvantage to using Struts, it's that the underlying design is so darn useful that people try to use it as an application framework rather than a WEB application framework. Many teams invest *way* too much business logic in ActionForms and Actions. Why? Because most large application do need to utilize the Context and Command patterns. But because they don't have a distinct business framework, people usurp the Struts classes. The Chain of Responsibility package in the Commons Sandbox is a first step toward creating a business layer framework. Webwork is doing something similiar with their xwork package. -Ted. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When
Re: Disadvantages of Struts?
I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 6:55 AM Subject: RE: Disadvantages of Struts? I have to disagree with you on the first point. I find that there is just a small amount of necessary configuration required to build an Action class (most of my Action configurations have about a half dozen lines, even less if there is no associated ActionForm). I'm not really sure what you mean by paddle back and forth between the code and the configuration, could you explain? Thanks. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
I think XDoclet is very nice. Thanks, Mark. - Robert. - Original Message - From: Turansky, Mark [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 10:56 AM Subject: RE: Disadvantages of Struts? Robert Tran, you were griping about config files and the need to go between code (your Actions) and the xml config files. Other developers have scratched that itch already. Check out XDoclet: http://xdoclet.sourceforge.net/ This piece of software will generate your configuration files for you via an ant task. You can keep everything relative to an Action in one place, inside your Action class itself. You use JavaDoc-like tags to define your config files. The following is an example from a real application I maintain: /** * @struts:action name=GetMessageAction * path=/GetMessage * @struts:action-forward name=editMessage * path=/EditMessage.jsp */ The Action associated with the above JavaDocs is responsible for retrieving a bean, putting it in request scope, and forwarding to the proper page for editing. Having everything in a single file (the Action) is useful and is easy for me to keep in my head. When the WebDoclet Ant task executes, it will parse those tags and generate Struts-config.xml for you. It can generate ActionForms, Validator xml files, and more. It can also be extended to generate other code of your choosing. It works very well and there only a slight learning curve. something to look at and think about, perhaps. mark Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2003 1:45 PM To: Struts Users Mailing List Subject: Re: Disadvantages of Struts? Thanks, Ted. I agree that Struts is the best option available today. Like you said, there are areas that Struts can, and probably should, improve. I am delighted to hear that some of them will be addressed in 2.0. - Robert. - Original Message - From: Ted Husted [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 4:40 AM Subject: Re: Disadvantages of Struts? Yes, we should be passing an API context object instead of tucking things away here and there in the various contexts. We started work on one during the 1.1 march, but it was sidetracked by the module initiative. At this point, it will probably be slated for Stuts 2.0. The other questions speak to whether you want to take a declarative approach to writing a web application. If you are writing a small application, the strategy of using XML configurations to deploy object graphs can be more trouble than it's worth. But if you are writing a larger application, most developers believe it is much better than the alternatives. (Been there, done that.) Of course, your mileage may vary. There are several other web application frameworks available, most of which are tracked by the wafer project. Choosing a framework is like choosing shoes. You really need to try them on for yourself to be sure. Like most software products, Struts is far from perfect. But, like Java itself, for complex enterprise applications, many developers find it's the best alternative available today. Neither Struts nor Java is the best choice for all applications and all teams, but most people do find that it is a good choice for larger applications that need to be maintained and improved over time. If there is a disadvantage to using Struts, it's that the underlying design is so darn useful that people try to use it as an application framework rather than a WEB application framework. Many teams invest *way* too much business logic in ActionForms and Actions. Why? Because most large application do need to utilize the Context and Command patterns. But because they don't have a distinct business framework, people usurp the Struts classes. The Chain of Responsibility package in the Commons Sandbox is a first step toward creating a business layer framework. Webwork is doing something similiar with their xwork package. -Ted. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each
Re: Disadvantages of Struts?
Robert H. Tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. I disagree with this almost completely. If actions are written properly, you should be able to reconfigure the application, to some extent at least, by changing the config alone and not touching the Java code. This is immensely useful when an app needs to be customised after the fact, and when the source code is not available (e.g. by a customer, in their own environment). -- Martin Cooper Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 6:55 AM Subject: RE: Disadvantages of Struts? I have to disagree with you on the first point. I find that there is just a small amount of necessary configuration required to build an Action class (most of my Action configurations have about a half dozen lines, even less if there is no associated ActionForm). I'm not really sure what you mean by paddle back and forth between the code and the configuration, could you explain? Thanks. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
My point was not against configuration altogether, but rather against the current rigid and centralized configuration. There should be options. If there is configurations in a component, it should be self-contained by the component. It is no framework's business. If there is an api in Struts, this can be done nice and easy, as I said with Eclipse. - Robert. - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 11:51 AM Subject: Re: Disadvantages of Struts? Robert H. Tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. I disagree with this almost completely. If actions are written properly, you should be able to reconfigure the application, to some extent at least, by changing the config alone and not touching the Java code. This is immensely useful when an app needs to be customised after the fact, and when the source code is not available (e.g. by a customer, in their own environment). -- Martin Cooper Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 6:55 AM Subject: RE: Disadvantages of Struts? I have to disagree with you on the first point. I find that there is just a small amount of necessary configuration required to build an Action class (most of my Action configurations have about a half dozen lines, even less if there is no associated ActionForm). I'm not really sure what you mean by paddle back and forth between the code and the configuration, could you explain? Thanks. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
I disagree with you as well Robert. Having a confgiration nudges you toward design and separation, and everyone on the team know where to find things. In fact, when not doing Web apps, I use HiveMind, just so that I can have the structure. Anyway, there a lot of MVC compeitoris. .V Robert H. Tran wrote: My point was not against configuration altogether, but rather against the current rigid and centralized configuration. There should be options. If there is configurations in a component, it should be self-contained by the component. It is no framework's business. If there is an api in Struts, this can be done nice and easy, as I said with Eclipse. - Robert. - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 11:51 AM Subject: Re: Disadvantages of Struts? Robert H. Tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. I disagree with this almost completely. If actions are written properly, you should be able to reconfigure the application, to some extent at least, by changing the config alone and not touching the Java code. This is immensely useful when an app needs to be customised after the fact, and when the source code is not available (e.g. by a customer, in their own environment). -- Martin Cooper Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 6:55 AM Subject: RE: Disadvantages of Struts? I have to disagree with you on the first point. I find that there is just a small amount of necessary configuration required to build an Action class (most of my Action configurations have about a half dozen lines, even less if there is no associated ActionForm). I'm not really sure what you mean by paddle back and forth between the code and the configuration, could you explain? Thanks. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can be generated after the fact as in a debugging view. When the application is finished, configurations become static. But since configurations are required, they will be like loose ends of the application. Another issue: how can one componentize his code and deploy it in a self-contained plug-in, as with Eclipse? Please forgive my novice. - Robert. - Original Message - From: Rick Hightower [EMAIL PROTECTED] To: 'Struts Developers List' [EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 6:24 PM Subject: RE: Disadvantages of Struts? Don't be silly. Struts is perfect. -Original Message- From: Robert H. Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 2:10 PM To: Struts Developers List Subject: Disadvantages of Struts? I just wonder if Struts comes with any significant drawback. I mean not in terms of when to use Struts and when not to use it necessarily, but more in the line of anyone's wishes that it had been better. Any advice is very appreciated. -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
Robert, I've gone to the opposite extreme as you. I don't want the action to be responsible for where it goes, only for telling users which forward states it supports. I've removed the forward from both the Action and the struts-config.xml file. The action still returns the forward, but the forward is dynamically created based on what the page has passed to the action. In my situation I resorted to this because I was using a single action to handle multiple applications on the same site. This meant that my path would not be the same between each application. Resorting to multiple mappings in the configuration file would rapidly get out of control for me as some of these applications can be created and removed rather quickly. I do have separate pages per application and this is why the page drives the actions result. I know this bends the MVC pattern, but it allows me to concentrate on developing actions, form beans, and all the back end business logic, while letting the Creative Designers develop pages and GUI workflow. Is anyone else doing something similar? I posted my DynaAction class that I use to do this with a couple of weeks ago. It really surprises me that there hasn't been a greater need for something like this in the community. I'd be curious to hear how others have solved this problem. Brian McClung Senior Programmer Belo Interactive 214-977-4083 -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2003 2:18 PM To: [EMAIL PROTECTED] Subject: Re: Disadvantages of Struts? I disagree with you as well Robert. Having a confgiration nudges you toward design and separation, and everyone on the team know where to find things. In fact, when not doing Web apps, I use HiveMind, just so that I can have the structure. Anyway, there a lot of MVC compeitoris. .V Robert H. Tran wrote: My point was not against configuration altogether, but rather against the current rigid and centralized configuration. There should be options. If there is configurations in a component, it should be self-contained by the component. It is no framework's business. If there is an api in Struts, this can be done nice and easy, as I said with Eclipse. - Robert. - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 11:51 AM Subject: Re: Disadvantages of Struts? Robert H. Tran [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. I disagree with this almost completely. If actions are written properly, you should be able to reconfigure the application, to some extent at least, by changing the config alone and not touching the Java code. This is immensely useful when an app needs to be customised after the fact, and when the source code is not available (e.g. by a customer, in their own environment). -- Martin Cooper Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 6:55 AM Subject: RE: Disadvantages of Struts? I have to disagree with you on the first point. I find that there is just a small amount of necessary configuration required to build an Action class (most of my Action configurations have about a half dozen lines, even less if there is no associated ActionForm). I'm not really sure what you mean by paddle back and forth between the code and the configuration, could you explain? Thanks. Robert H. Tran wrote: I am not sure that is true. Struts seems to lack of an API. IMO, there are more required configurations than necessary. Take Action for example, to write an Action, one has to paddle back and forth between the code and the configuration. It is like an executable having to configure each of its dlls. The visibility of the mappings is nice to have but the mappings can
Re: Disadvantages of Struts
Hi, Has anyone compared the configuration of JSF vs Struts ? Struts has a good mechanism to specify the forwards for each Action. JSF has a different approach. In faces-config.xml, you can specify navigation rules. You can specify something a navigation rules like.. navigation-rule from-tree-id/demo/login.jsp/from-tree-id navigation-case from-outcomefail/from-outcome to-tree-id/demo/error.jsp/to-tree-id /navigation-case navigation-case from-outcomesuccess/from-outcome to-tree-id/demo/welcome.jsp/to-tree-id /navigation-case /navigation-rule I find this better, because you can specify both the FROM webpage and the TO webpage in the navigation rule. Also event-handling is nice in JSF. For example, you can implement a web-screen as one Java class and specify event-handling methods to each submit button. So far, I have really liked JSF. Ajay I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts
Well, I'm thinking of looking into WebWork, to try a Pull MVC, rather than the Push MVC of Struts. I'm also looking for a simplicity of taglibs and close integration with JSTL (I know, I could use Struts-EL). Struts works and is being adopted widely but I'm still up for performing a comparison with another MVC framework. Nick Faiz -Original Message- From: Ajay Patil [mailto:[EMAIL PROTECTED] Sent: Friday, 5 December 2003 1:28 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Disadvantages of Struts Hi, Has anyone compared the configuration of JSF vs Struts ? Struts has a good mechanism to specify the forwards for each Action. JSF has a different approach. In faces-config.xml, you can specify navigation rules. You can specify something a navigation rules like.. navigation-rule from-tree-id/demo/login.jsp/from-tree-id navigation-case from-outcomefail/from-outcome to-tree-id/demo/error.jsp/to-tree-id /navigation-case navigation-case from-outcomesuccess/from-outcome to-tree-id/demo/welcome.jsp/to-tree-id /navigation-case /navigation-rule I find this better, because you can specify both the FROM webpage and the TO webpage in the navigation rule. Also event-handling is nice in JSF. For example, you can implement a web-screen as one Java class and specify event-handling methods to each submit button. So far, I have really liked JSF. Ajay I think an action's mapping is a decision by the action itself. Like I said earlier, when an application development finishes, that decision will become static. At that point, when an Action's mapping changes, its code will have to change too (unless the new mapping is kind of a synonym to the old mapping, which doesn't bear any shift in the semantics). As such, there is almost no point in keeping the decision and the code separate (i.e. making the decision's configuration a loose end of the code). Or at least, configuration shouldn't be the only way to add or modify an Action. Even though each Action's configuration may be small, the configurations for all the Actions need to be kept track of and maintained (for integrity). That may be a significant but unnecessary side work. To view the mappings, there can be a tool to traverse the structure by api calls and display it. That can be done after the fact and doesn't have to be before it. In addition to that, when the decision (or configuration if any) goes where the code lives, modularity increases. IMHO, - Robert. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts
You can see a spreadsheet comparison of some mvc2 frameworks at mvc2frameworks.org. Its was last updated for J1 and will need to be updated again but should give a decent idea. snip I'm still up for performing a comparison with another MVC framework. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts
Thanks Sandra, Good to see that such information exists. Nick -Original Message- From: Sandra Cann [mailto:[EMAIL PROTECTED] Sent: Friday, 5 December 2003 3:59 PM To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts You can see a spreadsheet comparison of some mvc2 frameworks at mvc2frameworks.org. Its was last updated for J1 and will need to be updated again but should give a decent idea. snip I'm still up for performing a comparison with another MVC framework. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
[Originally posted on struts-dev, answering on struts-user] I just wonder if Struts comes with any significant drawback. The main problem I'm always running up against is the lack of a go back where you came from mechanism in the framework. Everything goes forward, with the exception of Validation, but in that case, you never really left the page you were on. An example is the sort of lookup I have to do to populate fields on my form. The user puts in a free-form name. I have to display a list of possible matches (a separate form with a bunch of radio buttons) the user picks one, and he must then be taken back to the original form he was working on, with the name he picked inserted into the form and another blank text box now available for his next name choice. Think of a database of people, and you're adding [keys to] children to a parent record. I've resorted to putting a 'returnTo' attribute in the session, and using that to construct an ActionForward, but it's not very pretty. Several people have posted extensions and workarounds, I think there was one that keeps a page stack, and is able to push and pop pages so that the user can always be sent back one step (or more). -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
I had to do something similar where I keep a Map in the session and allow the actionmappings/request specify a source, it's then up to the action code to specify what key to store it under. Then I can later look up the source as a forward. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 4:21 PM To: Struts Users Mailing List Cc: Robert H. Tran Subject: RE: Disadvantages of Struts? [Originally posted on struts-dev, answering on struts-user] I just wonder if Struts comes with any significant drawback. The main problem I'm always running up against is the lack of a go back where you came from mechanism in the framework. Everything goes forward, with the exception of Validation, but in that case, you never really left the page you were on. An example is the sort of lookup I have to do to populate fields on my form. The user puts in a free-form name. I have to display a list of possible matches (a separate form with a bunch of radio buttons) the user picks one, and he must then be taken back to the original form he was working on, with the name he picked inserted into the form and another blank text box now available for his next name choice. Think of a database of people, and you're adding [keys to] children to a parent record. I've resorted to putting a 'returnTo' attribute in the session, and using that to construct an ActionForward, but it's not very pretty. Several people have posted extensions and workarounds, I think there was one that keeps a page stack, and is able to push and pop pages so that the user can always be sent back one step (or more). -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
I had to do something similar where I keep a Map in the session and allow the actionmappings/request specify a source, it's then up to the action code to specify what key to store it under. Then I can later look up the source as a forward. Care to elaborate? Do you have a Map of String-String name/value pairs, or are you putting ActionForwards in the Map? What do you mean by 'allow the actionmappings/request specify a source'? I'm not happy with the way I'm doing the and am looking for something better. However I tend to get lost in the details and can't step back and design the whole solution. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
Wendy Smoak wrote: [Originally posted on struts-dev, answering on struts-user] I just wonder if Struts comes with any significant drawback. The main problem I'm always running up against is the lack of a go back where you came from mechanism in the framework. Everything goes forward, with the exception of Validation, but in that case, you never really left the page you were on. Just a thought: In case you are ok with Validation than you can as well use mapping.getInputForward in Action to go back ...in case you are in same action mapping. But, I agree you actually mean some other problem. There is request-header referrer-to which will tell you the original source of page from where request came BUT this request-header is not implemented by all browsers. An example is the sort of lookup I have to do to populate fields on my form. The user puts in a free-form name. I have to display a list of possible matches (a separate form with a bunch of radio buttons) the user picks one, and he must then be taken back to the original form he was working on, with the name he picked inserted into the form and another blank text box now available for his next name choice. Think of a database of people, and you're adding [keys to] children to a parent record. I've resorted to putting a 'returnTo' attribute in the session, and using that to construct an ActionForward, but it's not very pretty. Several people have posted extensions and workarounds, I think there was one that keeps a page stack, and is able to push and pop pages so that the user can always be sent back one step (or more). -- Thanks Manish Singla x73166 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts?
Hello all! That's my first intercourse on the list Does anyone use different languages? I've setup all the JSP with html:html locale=true and created the bla.properties, bla_en.properties and bla_pt.properties. So, when I access in my browser, independent of the selected language and order, I always see just one language. Can anyone help me? Thanks, Renan Viegas Dynamic Systems - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Disadvantages of Struts?
What I have for the foundation of our Struts app: --- SmoAction +-void setSource(SmoActionMapping, HttpServletRequest, String key) +-ActionForward getSource(SmoActionMapping, String key) SmoActionMapping +-String getSource() --- Step 1: Setting the Source On SmoAction, I lazy load a Map into the user's session if: +-Request has a source parameter +-else SmoActionMapping.getSource() != null Then I use the passed String key to set the String value from either the request or the mapping. End Method. --- Step 2: Getting the Source On SmoAction, I call getSource() with the SmoActionMapping for reference and the String key for lookup. The reason for not storing the ActionForward itself is that I would rather have the ActionForward relative to the current Action being executed, instead of the one that originally set the source (this is debatable, but it meets our needs). +- If there is a map in the session to look against +- use the passed key to find a forward name +- if not null, then use the passed ActionMapping to findForward --- Notes: Variations on this could include allowing a stack to be created for each key. So when I call getSource() I get the last value that was set for that key. Some of the issues we ran into were storing parameters and resubmitting forms. Because we use SessionBeans to preserve state on our crutial areas, re-requesting an Action would be able to restore the view based on a session bean and not on parameters. Jacob Hookom Senior Analyst/Programmer McKesson Medical-Surgical Golden Valley, Minnesota http://www.mckesson.com -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 4:49 PM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts? I had to do something similar where I keep a Map in the session and allow the actionmappings/request specify a source, it's then up to the action code to specify what key to store it under. Then I can later look up the source as a forward. Care to elaborate? Do you have a Map of String-String name/value pairs, or are you putting ActionForwards in the Map? What do you mean by 'allow the actionmappings/request specify a source'? I'm not happy with the way I'm doing the and am looking for something better. However I tend to get lost in the details and can't step back and design the whole solution. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disadvantages of Struts
Michael Lee wrote: No real world examples and no good documentation describing those examples. This email list helps that. I'm also going to see if I can release some of my code here open source when I'm done for an example for just such a reason. This is an example of how the community can help out where they see a problem. Mike (*) Does not solve all your problems. Concentrate solely on the web front-end user interface (which is actually a good thing ). (*) It is not the silver bullet ( it is built on a set of compatible technologies JSP / Servlets / JavaBeans / Custom Tag libs / JAXP ). This means it can be very confusing for the very new user. I remember my own Java beginnings: What is JavaBean? What is virtual machine? etc. It will time to teach a complete Java novice for him or her to be proficient in this aspect of server side java. Struts, then, is aimed at medium to advance level to enterprise level web applications. Hence some people like `WebMacro' and `Velocity' and other templating web applications. (*) Does not provide data access (*) Base Jakarta Struts does not provide instant security, your log-in or authorisation ( but you write your own or use other integrated libaries and frameworks ) (*) No work flow solution in base Jakarta struts On the otherhand it is written in pure Java, therefore should work with any application server or web server that implements the Java Servlet , JSP standards. It is also open source and in active development. -- Peter Pilgrim +-\ +-+++++ Java Technologist | | | ||||| 'n' Shine | O | | || --+| ---+ /\| ._ / | | \ \ || / \ | | \ \ | |+-- || ---+ A new day /_ _\ Up| | | | | ||||| is coming ||+-+ +-+ +-+++++ home page=http://www.xenonsoft.demon.co.uk/; / -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
I don't consider this as disadvantage because it adds more security to your site so that people cannot figure out what page you are actually using. Thanks, Lee From: Dan Cancro [EMAIL PROTECTED] Subject: Disadvantages of Struts Date: Thu, 12 Sep 2002 11:05:24 -0700 Content-Type: text/plain This problem isn't unique to Struts, but it's one tradeoff with using Struts and a few other frameworks instead of plain old jsp. Since all requests go through an action, and all strings are stored in resource files, when debugging, it's hard to locate the source file location corresponding to what you see when you click View Source in the browser. This is also a problem any time you use jsp includes. You can get around this by having the server put hidden html comments in the output. Dan __ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
One disadvantage of Struts is that it strives to maintain compatibility with the Servlet 2.2 specification. While some may consider this a strength, it does preclude the Struts framework using newer Servlet 2.3 features like Filters. The Servlet 2.3 features can greatly simplify implementations. I wonder whether Struts would be the same if it was designed today with the Servlet 2.3 API as a basis (instead of Servlet 2.2). Just a thought, Oliver -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Hi Raghu, in my opinion, for developing, struts is a huge help. The disadvantages are only in the administrative/costum-related parts (mainly if you want to support a long-lifing application). Martina Jesse Alexander (KADA 11) [EMAIL PROTECTED] schrieb: Disadvantages of Struts: ... thinking ... == - you have to read through a HUGE number of mails if you subscribe to the official mailing list ... (== this one) - every now and then people will aks you why you use Struts (espescially by those who have financial interests to get XYZ-framework to be used...) - you have not too many excuses for being late in the office (cannot say: had to develop lots of framework-components) - you cannot make huge architectoral mistakes - every now and then you get smacked with a smelly trout - you have to explain to your managers why that framework costs nothing... about what comes to my mind thinking it... Alexander -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 12. September 2002 08:23 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Having to put up with me on this list? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
You left out Flash -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 2:23 AM Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Did you see the Flash frontend to Petstore yet? http://www.macromedia.com/desdev/mx/blueprint/ -Original Message- From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:01 To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts You left out Flash -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 2:23 AM Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Hmm. Looks like mark isnt the only one who doesnt like Flash! snip Trend SMEX Content Filter has detected sensitive content. Place = Struts Users Mailing List; ; ; Struts Users Mailing List Sender = Andrew Hill Subject = RE: Disadvantages of Struts Delivery Time = September 12, 2002 (Thursday) 08:07:02 Policy = Blocking09042002b Action on this mail = Quarantine message Warning message from administrator: Content filter has detected a sensitive e-mail. /snip -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:14 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Did you see the Flash frontend to Petstore yet? http://www.macromedia.com/desdev/mx/blueprint/ -Original Message- From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:01 To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts You left out Flash -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 2:23 AM Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [BEER]Disadvantages of Struts
Do we really need to expose the skeletons? Especially when they have been imbibing (RE:BEER) Jim Berg [EMAIL PROTECTED] Galbreath, Mark [EMAIL PROTECTED] 12-Sep-2002 07:48 Please respond to Struts Users Mailing List [EMAIL PROTECTED] To: 'Struts Users Mailing List' cc: Subject:RE: Disadvantages of Struts Having to put up with me on this list? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Yeah - pretty slick POC. I fooled around with Flash 4.0 and 5.0 but never got any good at it. I love a good Flash site, though (notice cnn.com used Flash for the 9/11 stories?). Now that I have my home server set up with Tomcat and Struts (because I'm walking through James' book), I think I'll give Flash another shot and see for myself what the integration issues are. That should produce enough knowledge to start a really gd flame war here. ;-) Mark the Instigator, er, Investigator -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 8:14 AM Did you see the Flash frontend to Petstore yet? http://www.macromedia.com/desdev/mx/blueprint/ -Original Message- From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:01 To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts You left out Flash -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 2:23 AM Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
In the 30s they burned books; now they burn electrons. What's the difference? -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 8:22 AM Hmm. Looks like mark isnt the only one who doesnt like Flash! snip Trend SMEX Content Filter has detected sensitive content. Place = Struts Users Mailing List; ; ; Struts Users Mailing List Sender = Andrew Hill Subject = RE: Disadvantages of Struts Delivery Time = September 12, 2002 (Thursday) 08:07:02 Policy = Blocking09042002b Action on this mail = Quarantine message Warning message from administrator: Content filter has detected a sensitive e-mail. /snip -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:14 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Did you see the Flash frontend to Petstore yet? http://www.macromedia.com/desdev/mx/blueprint/ -Original Message- From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 20:01 To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts You left out Flash -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 2:23 AM Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Disadvantages of Struts
It's way too productive for my taste... raghuramudu.v@pol aris.co.in 09/11/2002 11:20 PMTo: struts help [EMAIL PROTECTED] Please respond to cc: Struts Users Mailing List Subject:Disadvantages of Struts Caterpillar: Confidential Green Retain Until: 10/11/2002 Retention Category: G90 - Information and Reports Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu (See attached file: InterScan_Disclaimer.txt)-- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] InterScan_Disclaimer.txt Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Here are some examples with source code I've seen mentioned on the list http://www.scioworks.com/jpetstore/jpetstore-camino.html http://www.keyboardmonkey.com/downloads/index.jsp http://sourceforge.net/projects/struts http://www.rollerweblogger.org/ Dan -Original Message- From: Michael Lee [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 7:47 AM To: Struts Users Mailing List Subject: Re: Disadvantages of Struts No real world examples and no good documentation describing those examples. This email list helps that. I'm also going to see if I can release some of my code here open source when I'm done for an example for just such a reason. This is an example of how the community can help out where they see a problem. Mike - Original Message - From: Martina Weise [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Thursday, September 12, 2002 5:19 AM Subject: RE: Disadvantages of Struts Hi Raghu, in my opinion, for developing, struts is a huge help. The disadvantages are only in the administrative/costum-related parts (mainly if you want to support a long-lifing application). Martina Jesse Alexander (KADA 11) [EMAIL PROTECTED] schrieb: Disadvantages of Struts: ... thinking ... == - you have to read through a HUGE number of mails if you subscribe to the official mailing list ... (== this one) - every now and then people will aks you why you use Struts (espescially by those who have financial interests to get XYZ-framework to be used...) - you have not too many excuses for being late in the office (cannot say: had to develop lots of framework-components) - you cannot make huge architectoral mistakes - every now and then you get smacked with a smelly trout - you have to explain to your managers why that framework costs nothing... about what comes to my mind thinking it... Alexander -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 12. September 2002 08:23 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
This problem isn't unique to Struts, but it's one tradeoff with using Struts and a few other frameworks instead of plain old jsp. Since all requests go through an action, and all strings are stored in resource files, when debugging, it's hard to locate the source file location corresponding to what you see when you click View Source in the browser. This is also a problem any time you use jsp includes. You can get around this by having the server put hidden html comments in the output. Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 9:21 PM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
One disadvantage of Struts is that there are no high-level tools for modeling, viewing/creating workflows, etc. There are also not any good productivity tools for generating skeleton code/actionMappings and the like. Yes, I know about struts console and several IDE plug-ins, but none of them do what I'm envisaging. Another disadvantage is that there is not compile-time checking of property references, since everything is done by reflection. These are not problems with the framework per se, rather things that would be nice to have. my .02 -Original Message- From: Dan Cancro [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 9:57 AM To: 'Struts Users Mailing List' Subject: RE: Disadvantages of Struts Here are some examples with source code I've seen mentioned on the list http://www.scioworks.com/jpetstore/jpetstore-camino.html http://www.keyboardmonkey.com/downloads/index.jsp http://sourceforge.net/projects/struts http://www.rollerweblogger.org/ Dan -Original Message- From: Michael Lee [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 7:47 AM To: Struts Users Mailing List Subject: Re: Disadvantages of Struts No real world examples and no good documentation describing those examples. This email list helps that. I'm also going to see if I can release some of my code here open source when I'm done for an example for just such a reason. This is an example of how the community can help out where they see a problem. Mike - Original Message - From: Martina Weise [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Thursday, September 12, 2002 5:19 AM Subject: RE: Disadvantages of Struts Hi Raghu, in my opinion, for developing, struts is a huge help. The disadvantages are only in the administrative/costum-related parts (mainly if you want to support a long-lifing application). Martina Jesse Alexander (KADA 11) [EMAIL PROTECTED] schrieb: Disadvantages of Struts: ... thinking ... == - you have to read through a HUGE number of mails if you subscribe to the official mailing list ... (== this one) - every now and then people will aks you why you use Struts (espescially by those who have financial interests to get XYZ-framework to be used...) - you have not too many excuses for being late in the office (cannot say: had to develop lots of framework-components) - you cannot make huge architectoral mistakes - every now and then you get smacked with a smelly trout - you have to explain to your managers why that framework costs nothing... about what comes to my mind thinking it... Alexander -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 12. September 2002 08:23 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Ok. Good point. Now, from what perspective? Disadvantages compared to what? ASP? ASPX? PHP? Cold Fusion? CGI (Perl/C/C++)? or do we play in our own ballpark? JSP? (Model 1) Servlet? Servlet w/JSP? Servlet w/XML/XSL? Other similar frameworks? James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:45 AM To: Struts Users Mailing List Subject: RE: Disadvantages of Struts Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto
Disadvantages of Struts
Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu Polaris Software Lab Ltd., MAIL DISCLAIMER :This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited. Visit Us at http://www.polaris.co.in -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Disadvantages of Struts
Oh come on. Who best to get the bad points from than the users and developers themselves? Having a good critical look to identify weaknesses and problems will help to make the framework stronger, as once identified these points can be addressed in future enhancements. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 13:38 To: Struts Users Mailing List Subject: RE: Disadvantages of Struts You won't find it on this list. James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the Open Minded Developer Network http://www.open-tools.org/struts-atlanta -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:21 AM To: struts help Subject: Disadvantages of Struts Hi All, Can any one tell me what are the disadvantages of Struts?. Your help is appreciated thanks and regards Raghu -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
