avatar
W*n
1
http://stylecop.codeplex.com/
总是犯愁找不到完整的C# code convention的文档,用这个stylecop很方便啊!隆重推
荐。
有意思的是ms自己的Project template也有很多问题 :)
avatar
z*r
2
for stateless EJB, do you handle rollback manually,
or just throw runtimeexception?
avatar
c*t
3
你没有用过visual studio自带的code analysis?

【在 W********n 的大作中提到】
: http://stylecop.codeplex.com/
: 总是犯愁找不到完整的C# code convention的文档,用这个stylecop很方便啊!隆重推
: 荐。
: 有意思的是ms自己的Project template也有很多问题 :)

avatar
g*g
4
I don't do ejb2 any more, but I think if you do cmp, you should just throw
exception and let the framework deals with it.

【在 z**r 的大作中提到】
: for stateless EJB, do you handle rollback manually,
: or just throw runtimeexception?

avatar
s*w
5
That is FxCop, for VS premium and ultmate version, the code analysis use the
same engine as FxCop
StyleCop is mostly for formatting and comments

【在 c**t 的大作中提到】
: 你没有用过visual studio自带的code analysis?
avatar
t*e
6
The rules are the same across the board, no matter what technology you use. Runtime errors (system errors) cause transaction rollback automatically, checked exceptions (app errors) by default do NOT roll back transactions. But you may explicitly call or configure a txn roll back on application errors.
avatar
z*r
7
the tricky part i know is, if you throw a runtimeexception,
the container rolls back for you, and invalidates the bean instance.
when system is under heavy load, those beans would cause GC disater.

【在 g*****g 的大作中提到】
: I don't do ejb2 any more, but I think if you do cmp, you should just throw
: exception and let the framework deals with it.

相关阅读
logo
联系我们隐私协议©2024 redian.news
Redian新闻
Redian.news刊载任何文章,不代表同意其说法或描述,仅为提供更多信息,也不构成任何建议。文章信息的合法性及真实性由其作者负责,与Redian.news及其运营公司无关。欢迎投稿,如发现稿件侵权,或作者不愿在本网发表文章,请版权拥有者通知本网处理。