 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | Can you suggest a suitable pattern? | Can you suggest a suitable pattern? 2006-03-28 - By Soms S
Back
Hi Jin,
Sorry for the delayed response.
Thanks a lot for providing new perspective. I think I can solve the
problem with the outside-in approach you specified.
Thanks for your help.
Thanks, Soms.
__ ____ ____ ____ ____ ____ ____
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTERNS-INTEREST@(protected)] On Behalf Of Jin Chun
Sent: Wednesday, March 22, 2006 6:26 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: Can you suggest a suitable pattern?
I think you need to simplify the problem. If the config item map
directly to your domain, then it may be simpler. Alternatively, you can
go inside out or outside in, in both cases you need the context that
includes all items. For example, if you bind directly from the GUI
widgets to domain objects, inside out would mean using something like a
chain of command to allow all config items to try and validate
internally whether or not they are in a valid state. Personally, I think
outside in is better and more manageable, ie having a Validation class
that receives the context and exposes a method that can validate against
the configuration, all of them, then return back a validation result as
in commons validation that you can then use. We've done something
similar w a swing based trading app, and we use error codes and the
context to then localize the display of error messages back. In general,
I would worry about the structure first, then bind how you present it to
the use later.
Thanks,
Jin
__ ____ ____ ____ ____ ____ ____
-- -- Original Message -- --
From: An interest list for Sun Java Center J2EE Pattern
Cat====================================================================
Companion Site: http://www.corej2eepatterns.com J2EE BluePrints:
http://java.sun.com/blueprints/corej2eepatterns List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft
-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http:
//www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@(protected)
{font-family:Tahoma;
panose-1 (See http://ose-1.ora-code.com):2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@(protected) Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Hi Jin,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Sorry for the delayed response. <o:p></o:p
></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks a lot for providing new
perspective. I think I can solve the problem with the outside-in approach you
specified.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for your help.<o:p></o:p></span><
/font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, Soms.<o:p></o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> An interest list
for Sun Java Center J2EE Pattern Catalog [mailto:J2EEPATTERNS-INTEREST@(protected)
.COM]
<b><span style='font-weight:bold'>On Behalf Of </span></b>Jin Chun<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, March 22, 2006
6:26 PM<br>
<b><span style='font-weight:bold'>To:</span></b>
J2EEPATTERNS-INTEREST@(protected)<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: Can you suggest a
suitable pattern?</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I think you need to simplify the problem. If the config item map
directly to your domain, then it may be simpler. Alternatively, you can go
inside out or outside in, in both cases you need the context that includes all
items. For example, if you bind directly from the GUI widgets to domain
objects, inside out would mean using something like a chain of command to allow
all config items to try and validate internally whether or not they are in a
valid state. Personally, I think outside in is better and more manageable, ie
having a Validation class that receives the context and exposes a method that
can validate against the configuration, all of them, then return back a
validation result as in commons validation that you can then use. We've done
something similar w a swing based trading app, and we use error codes and the
context to then localize the display of error messages back. In general, I
would worry about the structure first, then bind how you present it to the use
later.<br>
<br>
Thanks,<br>
<br>
Jin<o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'> -- -- Original Message -- --<br>
<b><span style='font-weight:bold'> From: </span></b>An interest list for
Sun Java Center J2EE Pattern
Cat====================================================================
Companion Site: http://www.corej2eepatterns.com J2EE BluePrints:
http://java.sun.com/blueprints/corej2eepatterns List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing:
email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected) <o:p><
/o:p></span></font></p>
</div>
</body>
</html>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
