Tim,
I think things look pretty good so far.
Right now Customer is a domain object representing a customer.
CustomerDAO is a DAO respsonible for mapping the Customer to its
relational counterpart(s). CustomerService collaborates with CustomerDAO
to manage the persistence and data access of a
Tim,
What you are describing is actually very close to how I build struts
apps with iBATIS.
Starting with your example of a Customer maintenance application, here
are the components I would create:
Customer.java - a typed bean that describes the properties of a customer
CustomerDao.java - the
IMO, no.
That should be done in the action as needed. The reasoning for that is
that if you want to reuse the action form for multiple actions (like
with a DispatchAction), no matter what you do, you are rebuilding the
lists which will lead to performance degradation.
If you are using the action
Couldn't disagree more. ;-)
IMO, adding hungarian notation like that to a Java project is
pointless. What's next? sCustomerName? iCusomerId?
Nonsense. Leave that for C coders. :-D
Larry
On Sat, 26 Feb 2005 13:58:41 +0100, Leon Rosenberg
[EMAIL PROTECTED] wrote:
leon
2cents
The
Hmm, i thought it's more or less standart for interfaces in the advanced
java community...
But you can of course drop any points to the kind of the class like
Service Factory DAO, Action, Bean and the poor Abstract and I
this will sure make it more readable...
And it's not hungarian since
Hmm, i thought it's more or less standart for interfaces in the advanced
java community...
But you can of course drop any points to the kind of the class like
Service Factory DAO, Action, Bean and the poor Abstract and I
this will sure make it more readable...
And it's not hungarian since
On Sat, 26 Feb 2005 14:13:59 +0100, [EMAIL PROTECTED] wrote:
Hmm, i thought it's more or less standart for interfaces in the advanced
java community...
Baloney.
HttpServletRequest? HttpServletResponse? ResultSet? List?
No leading I on any of those.
I am unaware of any interfaces in the
Can you tell me the exact difference between a leading I and a leading
Abstract ?
AbstractButton, AbstractModel, AbstractAction...
I am unaware of any interfaces in the JDK that are ISomething.
There was almost none of those in jdks 1.0, 1.1.x and so on, till swing /
1.2.
Wait till 1.6 :-)
Can you tell me the exact difference between a leading I and a leading
Abstract ?
AbstractButton, AbstractModel, AbstractAction...
I am unaware of any interfaces in the JDK that are ISomething.
There was almost none of those in jdks 1.0, 1.1.x and so on, till swing /
1.2.
Wait till 1.6 :-)
I am unaware of any interfaces in the JDK that are ISomething.
I-terator?
:-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
HAHAHAH
On Sat, 26 Feb 2005 14:32:22 +0100, Leon Rosenberg
[EMAIL PROTECTED] wrote:
I am unaware of any interfaces in the JDK that are ISomething.
I-terator?
:-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Sat, 26 Feb 2005 14:30:18 +0100, [EMAIL PROTECTED] wrote:
Can you tell me the exact difference between a leading I and a leading
Abstract ?
AbstractButton, AbstractModel, AbstractAction...
Abstract describes the behavior (the class is an abstract or partial
implementation), where I is
Hmm,
Abstract describes the behavior (the class is an abstract
or partial implementation), where I is just a name
mangler...I suppose you
*could* argue that it describes the *lack of* behavior, but
that still seems like nonsense. ;-)
I just googled a bit :-)
Interface. When necessary
Hmm,
Abstract describes the behavior (the class is an abstract
or partial implementation), where I is just a name
mangler...I suppose you
*could* argue that it describes the *lack of* behavior, but
that still seems like nonsense. ;-)
I just googled a bit :-)
Interface. When necessary
On Sat, 26 Feb 2005 15:30:12 +0100, [EMAIL PROTECTED] wrote:
I just googled a bit :-)
Interface. When necessary to distinguish from similarly named classes:
InterfaceNameEndsWithIfc.
Class. When necessary to distinguish from similarly named interfaces:
ClassNameEndsWithImpl OR
But that is irrelevant, it is NOT necessary to distinguish
from similarly named classes because of the package structure
and/or class naming.
6.2.1 Naming Interfaces
The Java convention is to name interfaces using mixed case with the first
letter of each word capitalized. The
preferred Java
But that is irrelevant, it is NOT necessary to distinguish
from similarly named classes because of the package structure
and/or class naming.
6.2.1 Naming Interfaces
The Java convention is to name interfaces using mixed case with the first
letter of each word capitalized. The
preferred Java
Hey all,
i've wrote a little framework, that handles it's own definition.
So I have wrote my own definition Factory.
But know there are some cases where I want to use the standard
DefinitionFactory.
Is there a way to overwrite an DefinitionFactory?
I don't understand that
I put a nested Customer object in my action form, and deal with type
conversions from the web layer there (i.e., dates, numbers, etc) so
that by the time my action gets involved, it can get the customer from
the form and pass it to the service layer without worrying too much
about that stuff.
Hi Lee
Set your form property type to String. you could use date validation in
validation.xml. Whenever it's needed the type converting from String to Date
could be performed.
Nafise
-
Do you Yahoo!?
Yahoo! Mail - now with 250MB free
On Sat, 26 Feb 2005 06:24:06 -0700, Larry Meadors
[EMAIL PROTECTED] wrote:
On Sat, 26 Feb 2005 14:13:59 +0100, [EMAIL PROTECTED] wrote:
Hmm, i thought it's more or less standart for interfaces in the advanced
java community...
Baloney.
HttpServletRequest? HttpServletResponse?
Robert Taylor wrote:
Tim,
I think things look pretty good so far.
Right now Customer is a domain object representing a customer.
CustomerDAO is a DAO respsonible for mapping the Customer to its
relational counterpart(s). CustomerService collaborates with
CustomerDAO to manage the persistence
I call them API ex:
http://www.sandrasf.com/other/sandra/javadoc/index.html?org/sandra/api/package-summary.html
and Impl.
.V
Larry Meadors wrote:
At any rate, it boils down to personal preference. As the tech lead
where I work, I would publicly flog anyone who committed a
ICustomerDao class to my
Personally, I find the leading I on an interface rule to
hurt readability, but worse is that it also tempts you to an
insidious practice of naming an interface with the I, and
then an implementation class the same way without the I.
Consider the two names:
* IThisIsAVeryLongName
Personally, I find the leading I on an interface rule to
hurt readability, but worse is that it also tempts you to an
insidious practice of naming an interface with the I, and
then an implementation class the same way without the I.
Consider the two names:
* IThisIsAVeryLongName
I'm trying to experiment with declarative exceptions. When I add a
global handler that deals with java.lang.Exception, I get redirected
to my global error page as I expect. However, when I add an action
specific handler, I still get directed to the global page instead of
to the action specific
I use Frames in my application and in my jsp
don't work simple
c:out value='${...}' escapeXml=false /
html:select
html:options collection
/html:select
Could you please help?
--
regards,
Sergey mailto:[EMAIL PROTECTED]
So, this additional layer, in a Struts application, resides between the
Struts classes (Actions) and your managerial facade? The Action
instantiates/looks up a CustomerApplicationServiceImpl, which does CRUD
via the CustomerService component but also manages (possibly by itself,
possibly by
Thanks a lot.
Erik
Robert Taylor wrote:
So, this additional layer, in a Struts application, resides between the
Struts classes (Actions) and your managerial facade? The Action
instantiates/looks up a CustomerApplicationServiceImpl, which does CRUD
via the CustomerService component but also
On Fri, 25 Feb 2005 11:56:02 -0800, Dakota Jack wrote:
Hope this is helpful. If not, please understand it was meant to be
helpful.
Wish lists like this are mildly interesting, but what's helpful is when people
give back to the community by creating new extensions.
A Struts Upload extension
You know what might actually make a wish list more interesting (at least
to me)? What if we had a site we could go to and see a list of all the
pie-in-the-sky kinds of things people wanted, and I as someone who might
want to contribute could say gee, X over here sounds very interesting
to me,
What you describe is pretty much what the Wiki is for
(http://wiki.apache.org/struts). There are no limitations on who can
post to it (other than having to have a valid login), and nothing that
is on topic - i.e. generally related to the development of Struts - is
likely to be frowned on.
Of
Craig, just wanted to mention that Thunderbird thought your message was
junk. You haven't gotten into a fight with anyone on that development
team lately, have you?!? :) (Don't worry, I set it straight regardless!)
Craig McClanahan wrote:
What you describe is pretty much what the Wiki is for
On Sat, 26 Feb 2005 23:35:43 -0500, Frank W. Zammetti
[EMAIL PROTECTED] wrote:
Craig, just wanted to mention that Thunderbird thought your message was
junk. You haven't gotten into a fight with anyone on that development
team lately, have you?!? :) (Don't worry, I set it straight regardless!)
Craig McClanahan wrote:
Talk to the Google folks, since I use Gmail :-).
They seem to be getting into fights with a lot of people these days.
Doesn't seem that do no evil and we're publicly traded now mix very
well for very long :)
I hope you're not missing my main point ... the process by
My app has been quite happy using SecurityFilter.
I've got a new requirement to do something radical...
Like to redirect a logged in user to the TOS Acceptance page based upon a
user record flag. Yeah, like this is the first app to EVER have that
requirement :-)
Implementing this is painfully
My app has been quite happy using SecurityFilter.
I've got a new requirement to do something radical...
Like to redirect a logged in user to the TOS Acceptance page based upon a
user record flag. Yeah, like this is the first app to EVER have that
requirement :-)
Implementing this is painfully
37 matches
Mail list logo
