首页 文章

无法在AEM中使用GraphQL

提问于
浏览
1

我将GraphQL添加到AEM中的捆绑包中,导致捆绑启动失败 .

  • 我有一个捆绑项目,它在AEM中工作正常 . Bundle start命令:mvn clean install -PautoInstallBundle

<profile>

<ID> autoInstallBundle </ ID>
<活化>
<activeByDefault>假</ activeByDefault>
</激活>
< Build >
<pluginManagement>
<插件>
<插件>
<的groupId> org.apache.sling </的groupId>
<artifactId的>行家-吊带插件</ artifactId的>
<处决>
<执行>
<ID>安装束</ ID>
<目标>
<目标>安装</目标>
</目标>
</执行>
</处决>
</插件>
</插件>
</ pluginManagement>
</建造>
</简档>

  • 我将下面的配置添加到pom.xml然后重新安装捆绑包和捆绑仍然可以正常工作 .

<依赖>
<的groupId> com.graphql-java的</的groupId>
<artifactId的> graphql-java的</ artifactId的>
<版本> 3.0.0 </版本>
</依赖性>

12.07.2018 14:55:17.223错误[qtp1398311933-54244] org.apache.felix.http.jetty%bundles.pluginTitle:无法启动(org.osgi.framework.BundleException:无法解析com.mb.graphql.mb -graphql.core [528](R 528.27):缺少要求[com.mb.graphql.mb-graphql.core [528](R 528.27)] osgi.wiring.package;(osgi.wiring.package = graphql)未解决要求:[[com.mb.graphql.mb-graphql.core [528](R 528.27)] osgi.wiring.package;(osgi.wiring.package = graphql)])org.osgi.framework.BundleException:无法解决com.mb.graphql.mb-graphql.core [528](R 528.27):缺少要求[com.mb.graphql.mb-graphql.core [528](R 528.27)] osgi.wiring.package; (osgi.wiring.package = graphql)未解决的要求:[[com.mb.graphql.mb-graphql.core [528](R 528.27)] osgi.wiring.package; (osgi.wiring.package = graphql)] org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4112)org.apache.felix.framework.Felix.startBundle(Felix.java:2118)at org .apache.felix.framework.BundleImpl.start(BundleImpl.java:998)org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)org.apache.felix.webconsole.internal.core.BundlesServlet .doPost(BundlesServlet.java:364)位于org.apache.felix的javax.servlet.http.HttpServlet.service(HttpServlet.java:644)javax.servlet.http.HttpServlet.service(HttpServlet.java:725) . webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:563)atg.apache.felix.webconsole.internal.servlet.OsgiManager $ 3.run(OsgiManager.java:465)at java.security.AccessController.doPrivileged(Native方法)org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:461)at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:85)在org.apache.felix.http.base.internal.dispatch.In vocationChain.doFilter(InvocationChain.java:79)org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:138)org.apache.felix.http.base.internal.handler.FilterHandler.handle( FilterHandler.java:135)org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)at org.apache.sling.security.impl.ReferrerFilter.doFilter(ReferrerFilter.java: 295)org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java: 74)在org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)的com.adobe.granite.license.impl.LicenseCheckFilter.doFilter(LicenseCheckFilter.java:308)位于org.apache的org.apache.felix.http.sslfilter.internal.SslFilter.doFilter(SslFilter.java:96)的.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74) .felix.http.base.internal.handler.FilterHa ndler.handle(FilterHandler.java:135)位于org.apache.felix.http.base.internal.dispatch的org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74) . Dispatcher.dispatch(Dispatcher.java:128)位于org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49)的javax.servlet.http.HttpServlet.service(HttpServlet.java: 725)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)org.eclipse.jetty.server.session位于org.eclipse.jetty.servlet.servlet.ServletHandler.doScope的Org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)的.SessionHandler.doHandle(SessionHandler.java:221)(ServletHandler.java:515 )org.eclipse.jetty上的org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.hand.ContextHandler.doScope(ContextHandler.java:1061) . server.handler.Scoped Handler.handle(ScopedHandler.java:141)atOrg.eclipse.jetty.handle(HandlerWrapper.java:97)org.eclipse.jetty.server上的org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) . Server.handle(Server.java:499)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)atg.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)org .eclipse.jetty.io.AbstractConnection $ 2.run(AbstractConnection.java:544)位于org.eclipse.jetty.util.thread的org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) . QueuedThreadPool $ 3.run(QueuedThreadPool.java:555)at java.lang.Thread.run(Unknown Source)

有人面临同样的问题,知道如何解决它吗?

谢谢

1 回答

  • 1

    我找到了解决问题的方法 . 将以下配置添加到maven-bundle-plugin .

    <Export-Package> graphql . * </ Export-Package>

相关问题