Spring3.2和jboss as 7

时间:2022-06-17 23:05:37

How to resolve this warn? If i use Spring 3.2 i am see this warn:

如何解决这个警告?如果我使用Spring 3.2,我会看到这个警告:

14:24:19,014 WARN [org.jboss.as.ee] (MSC service thread 1-10) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest

(org.jboss.as 14:24:19,014警告。(MSC服务线程1-10)JBAS011006:不安装可选组件org.springframework.web.context.request.async。因为异常:org.jboss.as. deployment. deploymentunitprocessingexception: JBAS011054:无法找到类org.springframework.web.context.request.async.StandardServletAsyncWebRequest的默认构造函数

4 个解决方案

#1


37  

Apparently this is "normal", everything should still work. Likely there's an (anonymous) inner class in StandardServletAsyncWebRequest.

显然这是“正常的”,一切都应该正常。可能在StandardServletAsyncWebRequest有一个(匿名的)内部类。

See also Applicaiton is deployed in JBoss7.0.2 Final (Arc ) but failed to in 7.1.1 Final (Brontes) and metadata-complete="true" not respected. Basically it's just a warning, everything is fine.

参见Applicaiton在JBoss7.0.2 Final (Arc)中部署,但在7.1.1 Final (Brontes)和metada -complete=“true”中失败。基本上这只是一个警告,一切正常。

#2


10  

To expand aloplop85's link, you can ignore this message. You might want to suppress it because it is distracting (in my opinion, a working application should never normally print stack traces in the log). The instructions are here http://middlewaremagic.com/jboss/?p=2421, short version is to add the following text into the config file (e.g.standalone.xml):

要展开aloplop85的链接,您可以忽略此消息。您可能想要禁止它,因为它会分散注意力(在我看来,正常工作的应用程序不应该在日志中打印堆栈跟踪)。指令在这里http://middlewaremagic.com/jboss/?p=2421,短版本是将以下文本添加到配置文件中(例如:standalone.xml):

  <subsystem xmlns="urn:jboss:domain:logging:1.0">
      <console-handler name="CONSOLE">
          <!-- levels, formatters etc. -->
          <filter>
              <not>
                  <match pattern="JBAS011054"/>
              </not>
          </filter>
      </console-handler>
      <!-- and the same for other handlers -->
  </subsystem>

For JBoss 7.2.0, the syntax is a bit different:

对于JBoss 7.2.0,语法有点不同:

  <subsystem xmlns="urn:jboss:domain:logging:1.2">
      <console-handler name="CONSOLE">
         <!-- levels, formatters etc. -->
         <filter value='not(match("JBAS011054"))' />
      </console-handler>
      <!-- and the same for other handlers -->
  </subsystem>

#3


7  

This is how I suppressed it in my jboss-as-7.1.1

这就是我在jbo -as-7.1.1中抑制它的方式

updated configuration/standalone.xml as

更新配置/独立。xml作为

  <subsystem xmlns="urn:jboss:domain:logging:1.1">
      <console-handler name="CONSOLE">
          <filter>
              <not>
                  <match pattern="JBAS011054|JBAS011006"/>
              </not>
          </filter>
      </console-handler>
  </subsystem>

#4


5  

JBoss warns you when can't find no-args constructor for a class. In this case, there is no no-arg constructor for this Spring class. Just this one:

JBoss警告您当无法为类找到无args构造函数时。在本例中,这个Spring类没有无arg构造函数。只是这一个:

public StandardServletAsyncWebRequest(HttpServletRequest request, HttpServletResponse response) { super(request, response); }

public StandardServletAsyncWebRequest(HttpServletRequest request, HttpServletResponse) {super(request, response);}

No problem with that..That will work..

这个模式没有任何的问题。这将工作. .

#1


37  

Apparently this is "normal", everything should still work. Likely there's an (anonymous) inner class in StandardServletAsyncWebRequest.

显然这是“正常的”,一切都应该正常。可能在StandardServletAsyncWebRequest有一个(匿名的)内部类。

See also Applicaiton is deployed in JBoss7.0.2 Final (Arc ) but failed to in 7.1.1 Final (Brontes) and metadata-complete="true" not respected. Basically it's just a warning, everything is fine.

参见Applicaiton在JBoss7.0.2 Final (Arc)中部署,但在7.1.1 Final (Brontes)和metada -complete=“true”中失败。基本上这只是一个警告,一切正常。

#2


10  

To expand aloplop85's link, you can ignore this message. You might want to suppress it because it is distracting (in my opinion, a working application should never normally print stack traces in the log). The instructions are here http://middlewaremagic.com/jboss/?p=2421, short version is to add the following text into the config file (e.g.standalone.xml):

要展开aloplop85的链接,您可以忽略此消息。您可能想要禁止它,因为它会分散注意力(在我看来,正常工作的应用程序不应该在日志中打印堆栈跟踪)。指令在这里http://middlewaremagic.com/jboss/?p=2421,短版本是将以下文本添加到配置文件中(例如:standalone.xml):

  <subsystem xmlns="urn:jboss:domain:logging:1.0">
      <console-handler name="CONSOLE">
          <!-- levels, formatters etc. -->
          <filter>
              <not>
                  <match pattern="JBAS011054"/>
              </not>
          </filter>
      </console-handler>
      <!-- and the same for other handlers -->
  </subsystem>

For JBoss 7.2.0, the syntax is a bit different:

对于JBoss 7.2.0,语法有点不同:

  <subsystem xmlns="urn:jboss:domain:logging:1.2">
      <console-handler name="CONSOLE">
         <!-- levels, formatters etc. -->
         <filter value='not(match("JBAS011054"))' />
      </console-handler>
      <!-- and the same for other handlers -->
  </subsystem>

#3


7  

This is how I suppressed it in my jboss-as-7.1.1

这就是我在jbo -as-7.1.1中抑制它的方式

updated configuration/standalone.xml as

更新配置/独立。xml作为

  <subsystem xmlns="urn:jboss:domain:logging:1.1">
      <console-handler name="CONSOLE">
          <filter>
              <not>
                  <match pattern="JBAS011054|JBAS011006"/>
              </not>
          </filter>
      </console-handler>
  </subsystem>

#4


5  

JBoss warns you when can't find no-args constructor for a class. In this case, there is no no-arg constructor for this Spring class. Just this one:

JBoss警告您当无法为类找到无args构造函数时。在本例中,这个Spring类没有无arg构造函数。只是这一个:

public StandardServletAsyncWebRequest(HttpServletRequest request, HttpServletResponse response) { super(request, response); }

public StandardServletAsyncWebRequest(HttpServletRequest request, HttpServletResponse) {super(request, response);}

No problem with that..That will work..

这个模式没有任何的问题。这将工作. .