Just a note on this subject
You know that you can get absolutely sweet decoupling from everything
struts for your data model with the use of nesting objects?... And no
messy property copying!
I wanted to get a simple persistence mechanism running for my form
object, so I placed a little
Hello Arron,
Tuesday, November 27, 2001, 11:53:25 AM, you wrote:
AB Just a note on this subject
AB You know that you can get absolutely sweet decoupling from everything
AB struts for your data model with the use of nesting objects?... And no
AB messy property copying!
AB I wanted to get
The one thing to watch with nested objects is that they don't expose
anything that should not be exposed.
One thing we plugged in the imminent 1.01 release candidate is nesting
ActionServlet on the ActionForm. This let you do silly things like set
the temporary directory for uploads from a
It's all here... the original nesting extension and the saving model I
just mentioned.
http://www.keyboardmonkey.com/downloads/struts/index.html
The main part of the action simply gets the data that held in a
hierarchy of objects from one method and serializes the result. It's in
the example
See intermixed.
On Fri, 23 Nov 2001, Donnie Hale wrote:
Date: Fri, 23 Nov 2001 11:25:15 -0500
From: Donnie Hale [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: RE: Struts extensibility, multiple servlets, etc.
That was kind of an ignorant comment. I don't know why you people
resisting it so much.
There is no danger in nesting objects at all.
It is possible (however truly ugly) to do the same thing in out of the
box struts. It's all about getting the JSP's to elegantly manage data
structures you're
People reading this thread should also look at the last few in...
Re: Fwd: Re: Extensibility of struts...
It's touching the same topic.
I think that the most important things is what was just raised. The
marshaling of strings into more valid objects. One implementation I'm
working with has
Craig R. McClanahan wrote:
I disagree with what I think you are saying.
Struts follows the J2EE convention that data sources are configured on a
per-webapp basis. The details of exactly what database is being accessed
(and the database username/password being used) can be easily made
Is there anything wrong with having a given ActionServlet save itself in
the request at process() time and then have all attributes that are
currently accessed through application scope can instead be accessed
through the servlet that has been saved in the request? That way all
components are
I haven't studied the source from this perspective, but it certainly
seems feasible.
I don't know if we want to expose the ActionServlet in the request as
much as the resources associated with it. So I'd think about an
interface for a JavaBean that encapsulated the Mappings and the Messages
and
I didn't code it, but I have to use it. The chaps here did it before I
hit the scene. But I have to say that it's quite elegant.
You won't find it in the code I've written for nesting extension. I
didn't write this, so it's out of my hands to submit it (and I think
that their client paid too
Ted, I appreciate the feedback, thx.
The public interface of ActionServlet is already used by ActionForm,
ActionMapping and Action so it seems natural for it to be used by the
taglibs and get it to them through the request like everything else. In
fact, FormTag itself actually caches the
We just changed the ActionForm to use a wrapper object, rather than the
original, since exposing the ActionServlet this way can be exploited.
I'm just thinking that many of the components that we use may have wider
user, and we should avoid binding things to the ActionServlet class.
Avoding
http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=813
So, someone could also call
getServlet().setTempDir(whatever)
with
http://whatever.com/do/someAction?servlet.tempdir=whatever
Hmmm.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
--
Yes, yes. Point made.
That series of emails makes for some good bedside reading.
I think that the solution that was arrived at is fine for protecting the
struts system objects themselves.
Is there anything happening to allow the developer to protect their own
properties from this kind of
Personally, I have the feeling that it's better to encourage people to
define a proxy object, or wrapper, as was done with the ActionServlet,
than invent a special class for people to learn.
I actually believe that this is the approach that should have been used
in the first place, and in other
Hi,
We used to use PetStore architecture to develop our web application which is
used in hospital. Now we are considering to change the architect to Structs
in order to reduce the re-coding time. I got the following questions
regarding to it:
1. Compare to PetStore architect, what are the
17 matches
Mail list logo
