GVKun编程网logo

Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”

12

如果您想了解Wildfly24.0.0部署-部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”的相关知识,那么本文是一篇不可错过

如果您想了解Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”的相关知识,那么本文是一篇不可错过的文章,我们将为您提供关于asp.net – 在Azure部署期间(彻底改变)Web.config、c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException、C#WebService 出现No ''Access-Control-Allow-Origin'' header is present on the requested resource、Caused by: java.io.FileNotFoundException: class path resource [../../resources/config/spring.xml]...的有价值的信息。

本文目录一览:

Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”

Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”

如何解决Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”?

我正在尝试升级我们的应用程序以在 Wildfly 24 上运行,但在部署过程中出现此错误。我相信这与 JSF/Primefaces 有关,但我不确定它,我也不知道如何解决它。

有人知道发生了什么吗?

23:02:25,120 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 101) Critical error during deployment: : java.lang.NullPointerException
    at com.sun.faces.el.ELUtils.tryAddCDIELResolver(ELUtils.java:292)
    at com.sun.faces.el.ELUtils.buildFacesResolver(ELUtils.java:218)
    at com.sun.faces.application.ApplicationAssociate.initializeELResolverChains(ApplicationAssociate.java:467)
    at com.sun.faces.application.applicationimpl.ExpressionLanguage.performOneTimeELInitialization(ExpressionLanguage.java:188)
    at com.sun.faces.application.applicationimpl.ExpressionLanguage.getELResolver(ExpressionLanguage.java:122)
    at com.sun.faces.application.ApplicationImpl.getELResolver(ApplicationImpl.java:213)
    at com.sun.faces.config.ConfigureListener.contextinitialized(ConfigureListener.java:227)
    at io.undertow.servlet.core.ApplicationListeners.contextinitialized(ApplicationListeners.java:187)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:219)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:187)
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
    at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:255)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:105)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:87)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at org.jboss.threads.JBossthread.run(JBossthread.java:513)

23:02:25,138 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 101) MSC000001: Failed to start service jboss.deployment.unit."HeWebV4G.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."HeWebV4G.war".undertow-deployment: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:90)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at org.jboss.threads.JBossthread.run(JBossthread.java:513)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:257)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:105)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:87)
    ... 8 more
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
    at com.sun.faces.config.ConfigureListener.contextinitialized(ConfigureListener.java:286)
    at io.undertow.servlet.core.ApplicationListeners.contextinitialized(ApplicationListeners.java:187)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:219)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:187)
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
    at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1535)
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:255)
    ... 10 more
Caused by: java.lang.NullPointerException
    at com.sun.faces.el.ELUtils.tryAddCDIELResolver(ELUtils.java:292)
    at com.sun.faces.el.ELUtils.buildFacesResolver(ELUtils.java:218)
    at com.sun.faces.application.ApplicationAssociate.initializeELResolverChains(ApplicationAssociate.java:467)
    at com.sun.faces.application.applicationimpl.ExpressionLanguage.performOneTimeELInitialization(ExpressionLanguage.java:188)
    at com.sun.faces.application.applicationimpl.ExpressionLanguage.getELResolver(ExpressionLanguage.java:122)
    at com.sun.faces.application.ApplicationImpl.getELResolver(ApplicationImpl.java:213)
    at com.sun.faces.config.ConfigureListener.contextinitialized(ConfigureListener.java:227)
    ... 21 more

解决方法

暂无找到可以解决该程序问题的有效方法,小编努力寻找整理中!

如果你已经找到好的解决方法,欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@)

asp.net – 在Azure部署期间(彻底改变)Web.config

asp.net – 在Azure部署期间(彻底改变)Web.config

部署到Azure后,我不断收到服务器错误 – 应用程序无法运行.所以我在实例中做了一个远程桌面,发现web.config被彻底检修过……发生了什么事?我以为web.config是按原样打包的?相反,整个配置已被替换.当我用原始的,未改变的,正确的配置替换“新”版本时,我的应用程序按预期工作.

首先,这里发生了什么?我究竟做错了什么?通过这种方式,我可以理解并且不会在将来复制它.

其次,我该如何阻止这种行为?我希望部署原始的web.config – 而不是一些任意的冒名顶替者.谢谢!

解决方法

除非您指定了转换(使用普通的内置web.config.debug和.release),否则它不会转换任何用户设置.在某个时间点,它确实转换了machineKey设置,这样您的Web角色就可以在Web场场景中运行(如果没有,那么在负载均衡器后面什么都不会起作用).我确信它仍然会这样做,但它可能现在在machine.config级别执行(仅保留web.config).我有一段时间没有检查过,所以不确定它现在做了什么.

检查将要部署的内容的简单方法是打包cskpkg并将其打开为.zip文件. Inside将是另一个包含Web角色名称的文件.再次打开.zip,您应该看到您的网站全部打包.检查web.config并确保它是您需要的.如果没有,那么回到这里你认为不应该改变.

c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException

c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException

在我的集成测试中,我使用的是我正在测试的Web API项目中构建的相同的SimpleInjector.Container.

但是组合根类中的这一行:

container.RegisterWebApiControllers(GlobalConfiguration.Configuration);

导致异常:

System.TypeInitializationException : The type initializer for 'MyProject.Api.Test.Integration.HttpClientFactory' threw an exception.
---- system.invalidOperationException : This method cannot be called during the application's pre-start initialization phase.
Result StackTrace:  
at MyProject.Api.Test.Integration.HttpClientFactory.Create()
   at MyProject.Api.Test.Integration.Controllers.ProductControllerIntegrationTest.<GetProductBarcode_Should_Return_Status_BadRequest_When_Barcode_Is_Empty>d__0.MoveNext() in d:\Projects\My\MyProject.Api.Test.Integration\Controllers\ProductControllerIntegrationTest.cs:line 26
----- Inner Stack Trace -----
   at System.Web.Compilation.BuildManager.EnsuretopLevelFilesCompiled()
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies()
   at System.Web.Http.WebHost.WebHostAssembliesResolver.System.Web.Http.dispatcher.IAssembliesResolver.GetAssemblies()
   at System.Web.Http.dispatcher.DefaultHttpControllerTypeResolver.GetControllerTypes(IAssembliesResolver assembliesResolver)
   at System.Web.Http.WebHost.WebHostHttpControllerTypeResolver.GetControllerTypes(IAssembliesResolver assembliesResolver)
   at SimpleInjector.SimpleInjectorWebApiExtensions.GetControllerTypesFromConfiguration(HttpConfiguration configuration)
   at SimpleInjector.SimpleInjectorWebApiExtensions.RegisterWebApiControllers(Container container,HttpConfiguration configuration)
   at MyProject.Api.ContainerConfig.RegisterTypes(Container container) in d:\Projects\My\MyProject.Api\App_Start\ContainerConfig.cs:line 128
   at MyProject.Api.ContainerConfig.CreateWebApiContainer() in d:\Projects\My\MyProject.Api\App_Start\ContainerConfig.cs:line 63
   at MyProject.Api.Test.Integration.HttpClientFactory..cctor() in d:\Projects\My\MyProject.Api.Test.Integration\HttpClientFactory.cs:line 17

评论后,一切正常,网络应用程序本身和测试.

所以问题是:

>例外的原因是什么?
>(这种方法真的需要吗?)

这是HttpClientFactory的代码(一个辅助类,用于创建具有适当头的HttpClient,例如api密钥或授权):

internal static class HttpClientFactory
{
    private static readonly Container _container = ContainerConfig.CreateWebApiContainer();

    public static HttpClient Create()
    {
        var client = new HttpClient { BaseAddress = GetUrl() };
        //...
        return client;
    }
}

解决方法

如果我们仔细观察堆栈跟踪,我们可以准确地看到这里发生了什么. RegisterWebApiControllers扩展方法在从HttpConfiguration获取的IHttpControllerTypeResolver实例上调用GetControllerTypes方法,并传递也从配置中检索的IAssembliesResolver.调用GetControllerTypes方法(WebHostHttpControllerTypeResolver)调用DefaultHttpControllerTypeResolver的GetControllerTypes,最终将调用System.Web.Compilation.BuildManager类的GetReferencedAssemblies.

但是,System.Web.Compilation.BuildManager不能在ASP.NET管道的早期调用,也不能在ASP.NET的上下文之外调用.由于您正在进行测试,BuildManage将抛出您遇到的异常.

所以这里的解决方案(或’技巧’)将在单元测试时替换默认的IAssembliesResolver.我认为旋转变压器看起来像这样:

public class TestAssembliesResolver : IAssembliesResolver
{
    public ICollection<Assembly> GetAssemblies()
    {
        return AppDomain.CurrentDomain.GetAssemblies();
    }
}

[TestMethod]
public void TestMethod1()
{
    // Replace the original IAssembliesResolver.
    GlobalConfiguration.Configuration.Services.Replace(typeof(IAssembliesResolver),new TestAssembliesResolver());

    var container = SimpleInjectorWebApiInitializer.BuildContainer();

    container.Verify();
}

你不得不处理这个问题有点不幸,特别是因为Simple Injector的设计是可测试的.我们似乎忽略了这一点,将RegisterWebApiControllers扩展方法与Web API深深地集成在一起.我们必须退后一步,思考如何更轻松地验证单元测试中的Web API配置.

C#WebService 出现No ''Access-Control-Allow-Origin'' header is present on the requested resource

C#WebService 出现No ''Access-Control-Allow-Origin'' header is present on the requested resource

解决方法:

 

 打开Webservice的Web.config文件

<system.webServer>
    <httpProtocol>
      <customHeaders>
        <add name="Access-Control-Allow-Methods" value="OPTIONS,POST,GET"/>
        <add name="Access-Control-Allow-Headers" value="x-requested-with,content-type"/>
        <add name="Access-Control-Allow-Origin" value="*"/>  // “*”表示允许所有的跨域访问,如果要设置只允许一个一个地址的跨域,则需将“*”替换成被允许的地址
      </customHeaders>
    </httpProtocol>
  </system.webServer>

就可以解决跨域问题了

 

Caused by: java.io.FileNotFoundException: class path resource [../../resources/config/spring.xml]...

Caused by: java.io.FileNotFoundException: class path resource [../../resources/config/spring.xml]...

在尝试使用Spring的Test的时候遇到了这个错误

原来的代码: 

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations={"../../../resources/config/spring.xml"})
public class TestFund {

    @Autowired
    private FundService fundService;

    @Test
    public void testFundSelectAll() {
        //System.out.println("所有基金: " + fundService.selectAll());
        System.out.println(fundService);
    }
}

 

原因分析: 

  修改spring的配置文件spring.xml的位置

解决方法: 

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration("classpath:config/spring.xml")
public class TestFund {

    @Autowired
    private FundService fundService;

    @Test
    public void testFundSelectAll() {
        //System.out.println("所有基金: " + fundService.selectAll());
        System.out.println(fundService);
    }
}

问题解决!

关于Wildfly 24.0.0 部署 - 部署期间出现严重错误“javax.enterprise.resource.webcontainer.jsf.config”的介绍已经告一段落,感谢您的耐心阅读,如果想了解更多关于asp.net – 在Azure部署期间(彻底改变)Web.config、c# – container.RegisterWebApiControllers(GlobalConfiguration.Configuration)导致InvalidOperationException、C#WebService 出现No ''Access-Control-Allow-Origin'' header is present on the requested resource、Caused by: java.io.FileNotFoundException: class path resource [../../resources/config/spring.xml]...的相关信息,请在本站寻找。

本文标签: