Sean Walker

Ranch Hand
+ Follow
since Feb 04, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Sean Walker

Well, that's really what I'm getting at. What I keep hearing about Spring is that many people are disenchanted with EJBs and Spring offers a lighter weight alternative. So how lightweight is it? Should it only be used when you have light loads and in general you don't have enterprise type non-functional requirements?

Another related question is are EJBs the only way to go when developing enterprise applications in Java?
[ February 24, 2005: Message edited by: Sean Walker ]
Thnak you - these were very informative.
Does anyone advocate using Spring for enterpise applications? That is, does it address the the big 'ilities' such as horizontal scalability, reliability, security, etc?
[ February 23, 2005: Message edited by: Sean Walker ]
The comparison article introduced a number of terms/concepts taht I am unfamiliar with and didn't spend any time explaining them. For example crosscutting and Join points which were defined in terms of crosscuts. Perhaps you could point me to a good (and short) article about aspect oriented programming itself?
Are there any other Java Aspect Oriented frameworks with siginificant momentum?
Not sure if I'm over-stepping your intend question - but there are other open source frameworks that fill the same niche as Struts. For example WebWork, Tapestry and Spring. See:

https://webwork.dev.java.net/
http://jakarta.apache.org/tapestry/
http://www.springframework.org/
I understand that it is generally agreed that developers should avoid retaining a handle to stateless EJBs in the container's session. It seems to me the corollary here is that you should re-acquire a handle each time - but isn't this inefficient?
18 years ago
I don't believe that what motivated the orginal question and subsequent discussion has any similarity to 'worry'. The primary purposes behind patterns are to catalogue best practice solutions to common problems and to generate a consistent nomenclature for these.
In this light, trying to interpret the Struts framework accurately in terms of the MVC pattern is effort well spent, because it helps to motivate an understanding and an effective use of this framework.
18 years ago
Often when you want to expose paging through a list for users you must allow sorting by user selected field. I don't believe your method will work even if this field is fixed because the ROW_NUM sequence isn't generated per query, but is instead fixed for the table.
Correct me if I am wrong.
[ April 30, 2004: Message edited by: Sean Walker ]
18 years ago
Found a bit more from Ted Husted in Struts in Action about the Model not being present in Struts;

I like to say that Struts is a BYOM (Bring Your Own Model) framework. It brings
data up from the HTTP layer and stops. Getting data to the Model and back again
is an exercise that the framework leaves to the developer.

18 years ago
I think they must have dropped the required dependencies on the basic validators in a recent release of the Validator package, because Ted Husted wrote in his book Struts in Action that most of the basic validators are declared dependent on the required validator.

Like most of the other standard validators, the mask validator is declared to be dependent on the required validator. Therefore, if a field depends on both required and mask, then the required validator must complete successfully before the mask validator is applied.


[ April 29, 2004: Message edited by: Sean Walker ]
18 years ago
Thank you Dirk, that was quite helpful until I read Marc's post. At least it clarified what the author meant. However, what Marc said seems to be in conflict with this. Specifically, since most of the basic validators imply the required validator, how can a rule using a basic validator not be required?
Also, as Marc points out, I also understood that unchecked checkboxes are the only field type that are not present in form submissions.
18 years ago
In reading 'Struts in Action' (I just realized that the name is a play on words - aren't I slow...), I came across the following sentence in the section describing the 'required' validator:
Since browsers do not submit empty fields, any field that isn�t required will skip
all validations if the field is null or has a length of zero.

I have read this through many times now, but I'm lost. Could someone please explain what Mr Husted is getting at?
18 years ago
Thank you, I'll have a look.
I'll also have a look at your Strut's Survival Guide - does it come with an enclosed compass pattern and an object oriented Swiss Army knife?
18 years ago
Not that anybody said otherwise really, but not all state is part of the model. For example, if you retain raw state on the session between pages as part of a wizard workflow sequence and a finish action commits the business level transaction, this intermediate state isn�t model data - just as ActionForms are not model data. It�s really just UI session state.
Again, I'm pretty sure that Struts doesn't explicitly model the Model in MVC. It's implied where the model should be accessed -in the Actions- but the only direct provision that's been made for it is in the JDBC data sources - which I don't think can rightly be regarded as a Model package.
Don't get me wrong, I don't think this is a shortcoming in Strut's design. One of the fundamental drivers in building a framework is to capture the invariant (or common) characteristics of a set of solutions. But what is there in the Model part of MVC that is invariant? None of the patterns that Struts is based implies invariant characteristics in the Model. In the View and Controler parts, on the other hand, many people duplicated each other's efforts at creating such patterns as Service to Worker etc. So there was clearly somethign invariant to capture in these areas within a framework.
18 years ago