当前位置: 首页 > 面试题库 >

Jboss Seam:在WebLogic 10.3.2(11g)上启用调试页面

岳良策
2023-03-14
问题内容

跳过更新3

我想在Weblogic 10.3.2(11g)上启用Seam调试页面。因此,我做了以下工作:

我的ejb和Web Maven项目(都是我的超级项目的模块)中都具有jboss-seam和jboss-seam-
debug罐子作为依存关系,我将此上下文参数放在了web.xml中:

<context-param>
        <param-name>org.jboss.seam.core.init.debug</param-name>
        <param-value>true</param-value>
</context-param>

现在,当我点击应用程序的URL时,我得到了带有此异常的调试页面(文章结尾处的完整堆栈跟踪):

由java.lang.IllegalStateException引起,并带有消息:“没有相位ID绑定到当前线程(请确保您没有安装两个SeamPhaseListener实例)”

从我阅读的帖子中看来,这似乎与类路径中的两个jar包jboss-seam或jboss-seam-
debug有关。我打开了我的耳朵文件,但每个文件中只有一个(耳朵里),而战争本身在WEB-INF / lib中没有库。

我还阅读了使用components.xml初始化调试页面的另一种方法。我还尝试在WEB-INF中包含以下components.xml,但它也不起作用:

<?xml version="1.0" encoding="UTF-8"?>
<components xmlns="http://jboss.com/products/seam/components"
        xmlns:core="http://jboss.com/products/seam/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="
        http://jboss.com/products/seam/core
        http://jboss.com/products/seam/core-2.2.xsd
        http://jboss.com/products/seam/components
        http://jboss.com/products/seam/components-2.2.xsd">
        <core:init debug="true"/>
</components>

关于如何正确启用调试页面的任何建议?

干杯!

完整的堆栈跟踪:

org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:163)
org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:175)
org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext.java:91)
org.jboss.seam.contexts.PageContext.remove(PageContext.java:105)
org.jboss.seam.Component.newInstance(Component.java:2141)
org.jboss.seam.Component.getInstance(Component.java:2021)
org.jboss.seam.Component.getInstance(Component.java:2000)
org.jboss.seam.Component.getInstance(Component.java:1994)
org.jboss.seam.Component.getInstance(Component.java:1967)
org.jboss.seam.Component.getInstance(Component.java:1962)
org.jboss.seam.faces.FacesPage.instance(FacesPage.java:92)
org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId(ConversationPropagation.java:84)
org.jboss.seam.core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:57)
org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:391)
org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:230)
org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:196)
com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175)
com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114)
com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104)
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

更新1:

现在,调试页面根本不会出现。当我请求http://localhost/myapp/debug.xhtml时,我得到一个页面:

myapp / debug.xhtml

与任何不存在的页面相同。我打开了.ear,并且以下jboss jars在其中:

  • jboss-seam-debug-2.2.0.GA.jar
  • jboss-el-1.0_02.CR4.jar
  • jboss-seam-2.2.0.GA.jar

我当前的配置:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org    /2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
              http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5">
<display-name>PRS 6.0</display-name>

<session-config>
    <session-timeout>30</session-timeout>
</session-config>
<!--
    The default behavior of JSF is to map the incoming request for a JSF
    view identifier (view ID for short) to a JSP file with the file
    extension .jsp. To get JSF to look for a Facelets template instead, we
    must register the .xhtml extension as the default suffix for JSF views
-->
<context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.xhtml</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>server</param-value>
</context-param>

<context-param>
    <param-name>javax.faces.CONFIG_FILES</param-name>
    <param-value>
        /WEB-INF/faces-config/application.xml
    </param-value>
</context-param>

<context-param>
    <param-name>facelets.REFRESH_PERIOD</param-name>
    <param-value>2</param-value>
</context-param>
<context-param>
    <param-name>facelets.DEVELOPMENT</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>facelets.SKIP_COMMENTS</param-name>
    <param-value>true</param-value>
</context-param>

<context-param>
    <param-name>com.sun.faces.verifyObjects</param-name>
    <param-value>false</param-value>
</context-param>

<context-param>
    <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
    <param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
<context-param>
    <param-name>org.ajax4jsf.COMPRESS_SCRIPT</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>org.ajax4jsf.COMPRESS_STYLE</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>org.ajax4jsf.xmlparser.ORDER</param-name>
    <param-value>NONE</param-value>
</context-param>
<context-param>
    <param-name>org.richfaces.SKIN</param-name>
    <param-value>blueSky</param-value>
</context-param>
<context-param>
    <param-name>org.richfaces.CONTROL_SKINNING</param-name>
    <param-value>enable</param-value>
</context-param>
<context-param>
    <param-name>org.richfaces.LoadStyleStrategy</param-name>
    <param-value>ALL</param-value>
</context-param>
<context-param>
    <param-name>org.richfaces.LoadScriptStrategy</param-name>
    <param-value>ALL</param-value>
</context-param>


<!-- Seam Filter -->
<!-- (MUST BE FIRST)-->
<filter>
    <filter-name>Seam Filter</filter-name>
    <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>Seam Filter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

<!-- RichFaces filter -->
<filter>
    <display-name>RichFaces Filter</display-name>
    <filter-name>richfaces</filter-name>
    <filter-class>org.ajax4jsf.Filter</filter-class>
    <init-param>
        <description>Set the size limit for uploaded files as attachments in bytes. (max 5MB)</description>
        <param-name>maxRequestSize</param-name>
        <param-value>5242880</param-value>
    </init-param>
</filter>

<filter-mapping>
    <filter-name>richfaces</filter-name>
    <servlet-name>Faces Servlet</servlet-name>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
</filter-mapping>

<listener>
    <listener-class>
        XX.XXXX.XXX.prs.web.listeners.ResourceInitializationListener</listener-class>
</listener>

<listener>
    <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>

<listener>
    <listener-class>XX.XXXX.XXX.prs.web.listeners.EJBInjectionListener</listener-class>
</listener>
<!-- Seam Listener-->
<listener>
    <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
</listener>

<!-- Faces Servlet -->
<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

-> Seam资源Servlet </ servlet-name>-> org.jboss.seam.servlet.SeamResourceServlet </ servlet-class>->->-> Seam Resource Servlet </ servlet-name>\- > / seam / resource / * </ url-pattern>->->

<welcome-file-list>
    <welcome-file>index.xhtml</welcome-file>
</welcome-file-list>

</web-app>

faces.config

<?xml version="1.0" encoding="UTF-8"?>
<faces-config xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-facesconfig_1_2.xsd"
version="1.2">

<application>
    <locale-config>
        <default-locale>en</default-locale>
        <supported-locale>en</supported-locale>
    </locale-config>
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
    <el-resolver>org.jboss.seam.el.SeamELResolver</el-resolver>
    <resource-bundle>
        <base-name>XX.XXXX.XXX.prs.web.messages.messages</base-name>
        <var>msgs</var>
    </resource-bundle>
    <resource-bundle>
        <base-name>XX.XXXX.XXX.prs.web.messages.validation</base-name>
        <var>val</var>
    </resource-bundle>
</application>

<lifecycle>
    <phase-listener>XX.XXXX.XXX.prs.web.listeners.SetFocusListener</phase-listener>
</lifecycle>
<!--    <lifecycle>-->
<!--
    <phase-listener>XX.XXXX.XXX.prs.web.listeners.DebugPhaseListener</phase-listener>
-->

<converter>
    <converter-for-class>XX.XXXX.XXX.prs.model.Applicant</converter-for-class>
    <converter-class>
        XX.XXXX.XXX.prs.web.common.converters.ApplicantConverter</converter-class>
</converter>

<validator>
    <validator-id>EmailValidator</validator-id>
    <validator-class>XX.XXXX.XXX.prs.web.common.validators.EmailValidator</validator-class>
</validator>


</faces-config>

components.xml

<?xml version="1.0" encoding="UTF-8"?>
<components xmlns="http://jboss.com/products/seam/components"
xmlns:core="http://jboss.com/products/seam/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
    http://jboss.com/products/seam/core
    http://jboss.com/products/seam/core-2.2.xsd
    http://jboss.com/products/seam/components
    http://jboss.com/products/seam/components-2.2.xsd">

<core:init debug="true" />

<core:manager concurrent-request-timeout="500"
    conversation-timeout="1200000" conversation-id-parameter="cid"
    parent-conversation-id-parameter="pid" />

更新2:

这些家伙在这里有同样的问题。他们有一个外部EAR项目,其中包含内部WAR项目。他们讨论这可能与jars如何最终出现在项目中有关。

我使用Maven,并已将其设置为创建“ Skinny
Wars”,即从内部WAR项目中排除所有jar依赖项,以使其尺寸较小。它的所有依赖关系都包含在EAR中,并由所有其他模块使用。

我更改了maven-war-plugin的设置,以保留战争专用的Web专用jar(链接中提到的jar,例如RichFaces,jboss-seam-
debug,Facelets等)。

但是,问题已恢复为以前的形式。现在,我得到了调试页面,无论我按了什么链接,除了最初的异常。

由java.lang.IllegalStateException引起,并带有消息:“没有相位ID绑定到当前线程(请确保您没有安装两个SeamPhaseListener实例)”

更新3: 应用程序.ear的结构如下:

application.ear
|--> APP-INF
| |--> classes
|--> lib (all jar dependencies go here, including the WAR dependencies, EJB module dependencies)
|-->META_INF
| |--> application.xml
| |--> data-sources.xml
| |--> MANIFEST.MF
| |--> weblogic.xml
| |--> weblogic-application.xml
|--> jboss-seam-2.2.0.GA.jar
|--> myEjbModule1.jar
|--> myEjbModule2.jar
|--> myEjbModule3.jar
|--> myEjbModule4.jar
|--> myWar.war (NO libraries in WEB-INF/lib, finds everything in EAR/lib)

当在未启用调试的情况下部署.ear应用程序时(在耳朵中不包括jboss-seam-debug.jar),将正确加载该应用程序。

当在EAR(EAR / lib目录)中使用WITH jboss-seam-
debug.jar进行部署时,该应用程序不会出现,但只有出现以下异常的调试页面(最后是stacktrace):

请求处理期间的异常:

由java.lang.IllegalStateException引起,并带有消息:“没有相位ID绑定到当前线程(请确保您没有安装两个SeamPhaseListener实例)”

当对同一EAR进行“ JBoss大小调整”时(删除JBoss提供的休眠jar,并将所有库从EAR /
lib移至EAR根目录),应用程序将正确加载。应用程序和调试页都正确显示。

完整的堆栈跟踪:

org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:163)org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:175)org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext。
java:91)org.jboss.seam.contexts.PageContext.remove(PageContext.java:105)org.jboss.seam.Component.newInstance(Component.java:2141)org.jboss.seam.Component.getInstance(Component。
java:2021)org.jboss.seam.Component.getInstance(Component.java:2000)org.jboss.seam.Component.getInstance(Component.java:1994)org.jboss.seam.Component.getInstance(Component.java:
1967)org.jboss.seam.Component.getInstance(Component.java:1962)org.jboss.seam.faces.FacesPage.instance(FacesPage.java:92)org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId(ConversationPropagation。
java:84)org.jboss.seam。core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:57)org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:391)org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:
jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:196)com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175)com.sun.faces.lifecycle.Phase.doPhase(Phase.java:
114)com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104)com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)javax.faces.webapp.FacesServlet.service(FacesServlet。
java:265)weblogic.servlet.internal.StubSecurityHelper $
ServletServiceAction.run(StubSecurityHelper.java:227)weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:530)weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)org.jboss.seam.servlet.SeamFilter
$ FilterChainImpl.doFilter(SeamFilter.java:
83)org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)org.jboss.seam.servlet.SeamFilter
$
FilterChainImpl.doFilter(SeamFilter.java:69)org.jboss.seam.web.MultipartFilter。
doFilter(MultipartFilter.java:90)org.jboss.seam.servlet.SeamFilter $
FilterChainImpl.doFilter(SeamFilter.java:69)org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)org.jboss。
seam.servlet。SeamFilter $
FilterChainImpl.doFilter(SeamFilter.java:69)org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)org.jboss.seam.servlet.SeamFilter
$ FilterChainImpl.doFilter(SeamFilter.java:69)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)组织。
ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)org.jboss.seam.servlet.SeamFilter
$ FilterChainImpl.doFilter(SeamFilter.java:
69)org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)org.jboss.seam.servlet.SeamFilter
$
FilterChainImpl.doFilter(SeamFilter.java:69)org.jboss.seam.web.HotDeployFilter。
doFilter(HotDeployFilter.java:53)org.jboss.seam.servlet.SeamFilter $
FilterChainImpl.doFilter(SeamFilter.java:69)org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)weblogic.servlet.internal.FilterChainImpl.doFilter(
FilterChainImpl.java:56)weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)weblogic.servlet.internal.WebAppServletContext
$ ServletInvocationAction.run(
WebAppServletContext.java:3592)weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)weblogic.servlet.internal.WebAppServletContext.securedExecute(
WebAppServletContext.java:2202)weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)weblogic.work.ExecuteThread.run(ExecuteThread.java:173)


问题答案:

Seam调试页面未出现的原因令人难以置信(对我而言)。

我将应用程序与Apache Maven打包在一起。传统上,由maven管理的jar文件的文件名也包含版本号。Seam的jar是jboss-seam
-2.2.0.GA
.jar。因为Seam是应用程序中的EJB模块,所以我这样声明了它的依赖性。确实,EAR将其包含为EJB模块(位于EAR的根目录中),并在META-INF
/ application.xml中声明了它。

我不知道该规范是否为EAR中的EJB模块定义了命名限制,但是文件名的版本部分是WebLogic不喜欢的(如果进行了修改,则在JBoss上运行良好)。

我从这里更改了maven-ear-plugin中的设置:

<ejbModule>
    <groupId>org.jboss.seam</groupId>
    <artifactId>jboss-seam</artifactId>
</ejbModule>

对此:

<ejbModule>
    <groupId>org.jboss.seam</groupId>
    <artifactId>jboss-seam</artifactId>
    <bundleFileName>jboss-seam.jar</bundleFileName>
</ejbModule>

现在,我可以同时看到我的应用程序和“调试”页面。



 类似资料:
  • 问题内容: 在Java桌面应用程序上是否有与在命令行上设置类似的内容,在Android上是否有类似设置?我试图通过代码在代码中设置它,但是没有用。 如果没有启用此属性的方法,至少还有另一种方法来调试SSL连接的客户端吗? 编辑: 只是为了澄清,这是指原始SSL套接字(SSLSocket和SSLSocketFactory),而不是Apache库或任何其他网络库。 问题答案: 在这一点上,似乎还没有办

  • 在symfony存储库中打开票据之前,我只想检查是否遗漏了一些明显的内容。 我想启用调试组件(因为有这些漂亮的异常屏幕等等)。 我刚刚使用安装了symfony 出于测试目的,我向WelcomeController添加了一个异常: 我没有显示(旧的)异常屏幕,而是从nginx获得了一个502坏网关。 app_dev.php: 但是,处理PHP错误确实有效: 生成灰色symfony错误屏幕。

  • 我试图解决一个SSLHandshakeExcure,为此,我试图启用SSL调试模式,我尝试设置-Djavax.net.debug=ssl,但它不起作用,记录器只给我有关类的信息,如org.eclipse.util.ssl.SSLContext工厂org.eclipse.util.ssl.X509,这是否意味着Jetty在其核心中不使用JSSE实现? 我试图以这种格式可视化日志:https://do

  • 问题内容: 我是spring的新手,我使用https://start.spring.io/创建了一个新的spring boot项目,没有更多依赖关系,解压缩了zip文件并在IntelliJ IDEA中打开了该项目。我没有做任何进一步的配置。我现在正在尝试使用@PostConstruct方法设置bean-但是,该方法从未被spring调用。 这些是我的课程: SpringTestApplicatio

  • 问题内容: 只是一个简单的问题。对于ANT构建,如果我完全省略该参数,它将使用所有调试信息进行编译吗?还是将其包含在javac任务中会更好?我想启用最大程度的调试。这是一个片段: 问题答案: 简短的回答:是的,你可以离开属性了,只要你设置属性。 从文档中: 调试 指示是否应使用调试信息编译源;默认为关闭。如果设置为off,则-g:none将在支持该功能的编译器的命令行上传递(对于其他编译器,将不使

  • 场景: 我试图在Sabayon Linux下的Visual Studio代码上调试ASP.NET核心项目。当我点击F5时,我得到以下消息: launch.json }