前端之家

  1. 首页
  2. 问答

Helidon MP OpenAPI不会生成更新的openapi端点响应

• 问答

我目前正在遵循Oracle自身的指南和教程，基于Helidon microprofile构建微服务，但是在使用注释时遇到了与“自动OpenAPI规范生成器”相关的问题。

我的POM由一个MP捆绑包和一些集成组成，可以使其与Hibernate提供的JPA一起使用。

即使在我的资源上设置了所有注释之后，它也不会生成更新的规范。

POM 

 <dependencies>
    <dependency>
        <groupId>io.helidon.microprofile.bundles</groupId>
        <artifactId>helidon-microprofile</artifactId>
        <version>1.4.0</version>
    </dependency>

    <dependency>
        <groupId>org.jboss</groupId>
        <artifactId>jandex</artifactId>
        <version>2.1.1.Final</version>
        <scope>runtime</scope>
    </dependency>

    <dependency>
        <groupId>io.helidon.integrations.cdi</groupId>
        <artifactId>helidon-integrations-cdi-datasource-hikaricp</artifactId>
        <version>1.4.0</version>
        <scope>runtime</scope>
    </dependency>

    <dependency>
        <groupId>io.helidon.integrations.cdi</groupId>
        <artifactId>helidon-integrations-cdi-jta-weld</artifactId>
        <version>1.4.0</version>
        <scope>runtime</scope>
    </dependency>

    <dependency>
        <groupId>io.helidon.integrations.cdi</groupId>
        <artifactId>helidon-integrations-cdi-hibernate</artifactId>
        <version>1.4.0</version>
    </dependency>

    <dependency>
        <groupId>javax.transaction</groupId>
        <artifactId>javax.transaction-api</artifactId>
        <version>1.3</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>jakarta.persistence</groupId>
        <artifactId>jakarta.persistence-api</artifactId>
        <version>2.2.3</version>
        <scope>provided</scope>
    </dependency>

    <dependency>
        <groupId>org.mariadb.jdbc</groupId>
        <artifactId>mariadb-java-client</artifactId>
        <version>2.5.2</version>
    </dependency>

    <dependency>
        <groupId>com.googlecode.json-simple</groupId>
        <artifactId>json-simple</artifactId>
        <version>1.1.1</version>
    </dependency>

    <dependency>
        <groupId>org.glassfish.jersey.media</groupId>
        <artifactId>jersey-media-json-jackson</artifactId>
        <version>2.29.1</version>
        <scope>runtime</scope>
    </dependency>

    <dependency>
        <groupId>com.auth0</groupId>
        <artifactId>java-jwt</artifactId>
        <version>3.8.3</version>
    </dependency>

    <dependency>
        <groupId>com.auth0</groupId>
        <artifactId>jwks-rsa</artifactId>
        <version>0.9.0</version>
    </dependency>

    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>test</scope>
    </dependency>

    <dependency>
        <groupId>org.junit.jupiter</groupId>
        <artifactId>junit-jupiter-api</artifactId>
        <version>5.5.2</version>
        <scope>test</scope>
    </dependency>

    <dependency>
        <groupId>org.junit.jupiter</groupId>
        <artifactId>junit-jupiter-engine</artifactId>
        <version>5.5.2</version>
        <scope>test</scope>
    </dependency>
</dependencies>

我仅使用指南中指定的注释和@OpenAPIDefinition来定义标题和许可证之类的内容。

资源 

    @OpenAPIDefinition(
        info = @Info(
                title = "Newsletter microservice",version = "1.0",description = "microservice in charge of handling newsletter",license = @License(name = "Apache 2.0",url = "https://www.apache.org/licenses/LICENSE-2.0"),contact = @Contact(name = "Email",url = "mailto:email")
        ),tags = {
                @Tag(name = "public"),@Tag(name = "private")
        }
)

@Path("/newsletter")
@RequestScoped
public class NewsletterClientResource {

日志 

Connected to the target VM,address: '127.0.0.1:0',transport: 'socket'
Java HotSpot(TM) 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
2019.12.02 20:01:19 INFO org.jboss.weld.Version Thread[main,5,main]: WELD-000900: 3.1.1 (Final)
2019.12.02 20:01:20 INFO org.jboss.weld.Bootstrap Thread[main,main]: WELD-ENV-000020: Using jandex for bean discovery
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file:/C:/Users/Brenno%20Fagundes/.m2/repository/org/jboss/weld/weld-core-impl/3.1.1.Final/weld-core-impl-3.1.1.Final.jar) to method java.lang.ClassLoader.defineclass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2019.12.02 20:01:21 INFO org.jboss.weld.Event Thread[main,main]: WELD-000411: Observer method [BackedAnnotatedMethod] public org.glassfish.jersey.ext.cdi1x.internal.ProcessAllAnnotatedTypes.processAnnotatedType(@Observes ProcessAnnotatedType<?>,Beanmanager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2019.12.02 20:01:21 INFO org.jboss.weld.Event Thread[main,main]: WELD-000411: Observer method [BackedAnnotatedMethod] private io.helidon.microprofile.openapi.IndexBuilder.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2019.12.02 20:01:22 INFO org.jboss.weld.Bootstrap Thread[main,main]: WELD-ENV-002003: Weld SE container 404f642b-892f-4676-960e-8df848aee3a3 initialized
2019.12.02 20:01:22 INFO io.helidon.microprofile.security.SecurityMpService Thread[main,main]: Security extension for microprofile is enabled,yet security configuration is missing from config (requires providers configuration at key security.providers). Security will not have any valid provider.
2019.12.02 20:01:22 INFO io.smallrye.openapi.api.OpenApiDocument Thread[main,main]: OpenAPI document initialized: io.smallrye.openapi.api.models.OpenAPIImpl@7793ad58
2019.12.02 20:01:23 INFO io.helidon.webserver.NettyWebServer Thread[main,main]: Version: 1.4.0
2019.12.02 20:01:24 INFO io.helidon.webserver.NettyWebServer Thread[nioEventLoopGroup-2-1,10,main]: Channel '@default' started: [id: 0x4e1f119b,L:/0:0:0:0:0:0:0:0:7200]
2019.12.02 20:01:24 INFO io.helidon.microprofile.server.ServerImpl Thread[nioEventLoopGroup-2-1,main]: Server initialized on http://localhost:7200 (and all other host addresses) in 5254 milliseconds.

BUMP ，也可以使用自定义过滤器和模型进行生成，Meta-INF中的静态定义也可以使用。当前正在使用JDK 13。

编辑：这是Tim Quinn建议的修改后的我的Application类。

应用类 

@ApplicationScoped
@ApplicationPath("/")
@OpenAPIDefinition(
        info = @Info(
                title = "Newsletter microservice",url = "mailto:john.doe@gmail.com")
        ),@Tag(name = "private")
        }
)
public class NewsletterApplication extends Application {
    @Override
    public Set<Class<?>> getclasses(){
        HashSet<Class<?>> classes = new HashSet<Class<?>>();
        classes.add(NewsletterClientResource.class);
        return classes;
    }
}

生成的文件 

---
openapi: 3.0.1
info:
  title: Generated API
  version: "1.0"
paths: {}
wg85840223 回答：Helidon MP OpenAPI不会生成更新的openapi端点响应

布伦诺，

您没有显示更新的源代码，但是我假设您在快速入门@OpenAPIDefinition类中添加了GreetResource注释，对吗？

该注释的属性描述了整个应用程序，而不是其资源的子集，因此请尝试将注释移至GreetApplication类：

@ApplicationScoped
@ApplicationPath("/")
@OpenAPIDefinition(info = @Info(title = "QuickStart API",version = "1.1"))

public class GreetApplication extends Application {...}

应该可以。我只是在生成的Helidon MP快速入门示例源上进行了尝试，对其进行了重新构建，然后服务器返回了预期的结果。

以下是我所做更改的区别：

diff --git a/examples/quickstarts/helidon-quickstart-mp/src/main/java/io/helidon/examples/quickstart/mp/GreetApplication.java b/examples/quickstarts/helidon-quickstart-mp/src/main/java/io/helidon/examples/quickstart/mp/GreetApplication.java
index fd140738..cca60da2 100644
--- a/examples/quickstarts/helidon-quickstart-mp/src/main/java/io/helidon/examples/quickstart/mp/GreetApplication.java
+++ b/examples/quickstarts/helidon-quickstart-mp/src/main/java/io/helidon/examples/quickstart/mp/GreetApplication.java
@@ -23,12 +23,15 @@ import javax.ws.rs.ApplicationPath;
 import javax.ws.rs.core.Application;

 import io.helidon.common.CollectionsHelper;
+import org.eclipse.microprofile.openapi.annotations.OpenAPIDefinition;
+import org.eclipse.microprofile.openapi.annotations.info.Info;

 /**
  * Simple Application that produces a greeting message.
  */
 @ApplicationScoped
 @ApplicationPath("/")
+@OpenAPIDefinition(info = @Info(title = "QuickStart API",version = "1.1"))
 public class GreetApplication extends Application {

     @Override

这是从服务器返回的更新的OpenAPI文档的开头：

---
openapi: 3.0.1
info:
  title: QuickStart API
  version: "1.1"
paths:

标题和版本已按预期更改。

,

案例 1：您正在使用 jandex，而您的 /openapi 没有得到更新。

如果您正在使用 jandex，您的 jandex.idx 很有可能没有得到更新。您可以通过运行 mvn process-classes

案例 2：您没有使用 jandex，当您点击 /openapi 时，您会得到一些空白响应。

这似乎是 Helidon 的问题。依赖项 helidon-integrations-cdi-jpa,helidon-integrations-cdi-jta,helidon-integrations-cdi-eclipselink etc... 包含 jandex.idx 并且 Helidon 现在认为 jandex 已启用并且它 将仅从那些 jandex 文件中读取，跳过您的资源。所以暂时，你可以包含 jandex 插件来解决这个问题。

helidonjavamicroprofileopenapi
本文链接：https://www.f2er.com/2991265.html

大家都在问