blocks|key|1977772|text|断言是在运行时评估的，注释帮助FindBugs在运行前的分析过程中捕获问题。因为这两个检查并不是真的冲突，所以你可以同时保留它们。如果IDE让我删除断言，我会觉得很烦人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1977773|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The assert is evaluated at runtime, the annotation helps FindBugs catch problems during the analysis before runtime. As both checks are not really conflicting you could keep them both. I would find it annoying if my IDE told me to remove the assert.

blocks|key|1971648|text|Netbeans是对的。如果您认为它可以为null:删除注释。如果您知道它不能:删除断言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1971649|如果您的方法有可能被调用为null值，那么@Nonnull注释就不应该存在。|offset|length|style|CODE|1971650|正如您所说，该注释在运行时实际上并不做任何事情:它只由IDE和静态代码分析工具使用。它不能确保事情不是空的。|1971651|entityMap^0|0|L|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Netbeans is right. If you think it can be null: remove the annotation. If you know it can't: remove the assert.

If there's ANY chance that your method could be called with a null value, then <code>@Nonnull</code> annotation shouldn't be there.

Like you said, that annotation doesn't actually do anything at runtime: it is only used by IDEs and static code analysis tools. It doesn't ensure that things aren't null.

blocks|key|2712336|text|因为这是私有方法，所以我们可以确保带注释参数不能为空。我认为您可以删除此断言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2712337|如果NetBeans警告公共方法，我认为它有问题。我建议你把断言。|2712338|如果你仍然觉得私有方法中的断言是必要的，我认为你可以使用字节码注入。例如，这里有一个用于注入null检查的maven插件。抱歉，这是我的个人项目，但它对我很有效。我想它能满足你的需要。https://github.com/KengoTODA/jsr305-maven-plugin|offset|length|2712339|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/KengoTODA/jsr305-maven-plugin^0|0|0|2K|1C|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Since this is private method, we can ensure that annotated parameter cannot be null. I think you can remove this assertion. 

If NetBeans warns to public method, I think it has problem. I recommend you to put assertion.

If you still feel that assertion in private method is necessary, I think you can use bytecode injection.
For instance, here is a maven plugin to inject null check. Sorry this is my personal project, but it works to me. I guess it can suit your need.
<a href="https://github.com/KengoTODA/jsr305-maven-plugin" rel="nofollow">https://github.com/KengoTODA/jsr305-maven-plugin</a>

blocks|key|1977784|text|当我在思考IDE警告时，我找到了一个不同的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1977785|最初，我觉得IDE是错误的。我是一个偏执的程序员，我希望有一个文档的标签&静态分析和运行时检查，以防我从反射中使用它，或者其他JVM语言或其他不能静态分析的东西，所以我认为给我一个警告并告诉我不需要assert(x+!=+null)语句是错误的。|offset|length|style|CODE|1977786|但是后来我想到了如何根据运行时传递给Java的-ea标志的状态来删除断言，而且在某些方面，assert和@Nonnull实际上都是仅限开发的检查。|1977787|事实证明，有一个实际的运行时检查可以插入(Java+7%2B)+Objects.requireNonNull，它将抛出NullPointerException，并且不能通过-ea断言删除。我想比起我的assert(x+!=+null);+use(x);模式，我更喜欢这种模式。|1977788|public+ConstructorForClass(@Nonnull+Type+x)+{
++this.x+=+Objects.requireNonNull(x);
++//...
}|code-block|syntax|javascript|1977789|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.oracle.com/javase/7/docs/api/java/util/Objects.html#requireNonNull%2528T%2529^0|0|2R|H|0|N|3|19|6|1G|8|0|U|M|1L|K|2C|3|2Q|Q|U|M|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@$D|13|E|14|F|G]|$D|15|E|16|F|G]|$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]|$D|1G|E|1H|F|G]]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|L|3|M|5|N|7|1L|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

I found a different solution, as I was thinking about my IDE warnings.

Initially, I felt that the IDE was wrong. I'm a paranoid programmer, and want to have the label for documentation &amp; static analysis AND a runtime check in case I ever use it from reflection, or another JVM language or something that isn't statically analyzable, so I thought it was wrong to give me a warning and tell me the <code>assert(x != null)</code> statement wasn't needed. 

But then I thought about how asserts can be removed depending on the status of the <code>-ea</code> flag passed to Java at Runtime, and that in some ways <code>assert</code> and <code>@Nonnull</code> are really both development-only checks.

Turns out, there's an actual runtime check that can be inserted (Java 7+) <a href="http://docs.oracle.com/javase/7/docs/api/java/util/Objects.html#requireNonNull%28T%29" rel="nofollow"><code>Objects.requireNonNull</code></a> which will throw a <code>NullPointerException</code> and cannot be removed with an <code>-ea</code> assertion. I think I'm going to prefer this to my <code>assert(x != null); use(x);</code> pattern.

<pre><code>public ConstructorForClass(@Nonnull Type x) {
 this.x = Objects.requireNonNull(x);
 //...
}
</code></pre>

I'm using Findbugs and javax.annotation.Nonnull on method parameters.

On private methods I usually add an assert line to check for nullness like

<pre><code>private void myMethod(@Nonnull String str) {
 assert str != null
 ....
</code></pre>

Latest Netbeans version (7.3rc2) is reporting that the assert check is not necessary (because of the Nonnull annotation). I'm not fully sure this is a Netbeans bug or not.

Can the assert line be removed because I specified the @Nonnull annotation ?

As far as I understand, the annotation is used only during static analysis while assert is, when enabled, active during execution so the twos are not alternative.

javax.annotation.Nonnull vs assert

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在方法参数上使用了Findbugs和javax.annotation.Nonnull。在私有方法中，我通常添加一个断言行来检查空性，如下所示private void myMethod(@Nonnull String str) {    assert str != null    ....最新的Netbeans版本(7.3rc2)报告断言检查不是必需的(因为Nonnull注释)。我不能完全确定这是

问javax.annotation.Nonnull vs assert
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问javax.annotation.Nonnull vs assertEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问javax.annotation.Nonnull vs assert
EN