[ http://jira.andromda.org/browse/SPRING-172?page=all ]
Chad Brandon closed SPRING-172:
-------------------------------
Resolution: Won't Fix
How does it break encapsulation? Encapsulation is like "shielding" (i.e. if a
client calls a service interface method, it doesn't care how that service
method goes about things other than the fact the it performs the operation it
expects). The fact that I can "forget" about exceptions is the whole reason
I added it, I don't want to care about an exceptions unless I want to. I'm not
planning on changing the behavior, so you'll need to just merge in your custom
template to have this behavior.
> Eleminate excesive use of throws Exception in base and implementation classes
> -----------------------------------------------------------------------------
>
> Key: SPRING-172
> URL: http://jira.andromda.org/browse/SPRING-172
> Project: Spring Cartridge
> Type: Improvement
> Versions: 3.2-RC1
> Reporter: Patrik Jurica
> Assignee: Chad Brandon
> Priority: Minor
> Attachments: SpringServiceBase.vsl, SpringServiceImpl.vsl
>
> Service base and implementation classes declare always "throws Exception" for
> implementation service methods. This is very unpleasent and really not
> needed. I suggest these declaration should declare the same exceptions as in
> the interface of the service.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
