java 在 Weblogic 12.1.3 上找不到文件 Metro-default.xml
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/26003785/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
File metro-default.xml not found on Weblogic 12.1.3
提问by vkrausser
We're currently running on WebLogic 12.1.2. And in this environment our application runs fine.
我们目前在 WebLogic 12.1.2 上运行。在这种环境中，我们的应用程序运行良好。
What we want now is to homologate our applications to WebLogic 12.1.3 environments. But we are facing a problem with the Web Services we use. In the new version the server throws a exception saying that the "Default configuration file [ metro-default.xml ] was not found".
我们现在想要的是将我们的应用程序与 WebLogic 12.1.3 环境兼容。但是我们正面临着我们使用的 Web 服务的问题。在新版本中，服务器抛出一个异常，指出“未找到默认配置文件 [metro-default.xml]”。
I'm trying to find something on this file but there is nothing.
我试图在这个文件上找到一些东西，但什么也没有。
PS: We do not use Metro, we use the WebLogic default JAX-WS stack. And the application is deployed as a WAR file.
PS：我们不使用 Metro，我们使用 WebLogic 默认的 JAX-WS 堆栈。并且该应用程序被部署为一个 WAR 文件。
Here is the stack of the exception
这是异常的堆栈
java.lang.IllegalStateException: MASM0001: Default configuration file [ metro-default.xml ] was not found
at com.sun.xml.ws.assembler.MetroConfigLoader.init(MetroConfigLoader.java:142)
at com.sun.xml.ws.assembler.MetroConfigLoader.<init>(MetroConfigLoader.java:119)
at com.sun.xml.ws.assembler.TubelineAssemblyController.getTubeCreators(TubelineAssemblyController.java:122)
at com.sun.xml.ws.assembler.MetroTubelineAssembler.createServer(MetroTubelineAssembler.java:173)
at com.sun.xml.ws.server.WSEndpointImpl.<init>(WSEndpointImpl.java:193)
at com.sun.xml.ws.server.EndpointFactory.create(EndpointFactory.java:337)
at com.sun.xml.ws.server.EndpointFactory.create(EndpointFactory.java:332)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:164)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:577)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:560)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:303)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:179)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.parseAdaptersAndCreateDelegate(WSServletContextListener.java:131)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:152)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:678)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.EventsManager.executeContextListener(EventsManager.java:243)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:200)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:185)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1838)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2876)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1661)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:823)
at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)
at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver.next(ModuleStateDriver.java:216)
at weblogic.application.internal.flow.ModuleStateDriver.next(ModuleStateDriver.java:211)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)
采纳答案by Michal
I solved it so that I added jaxws-rt-2.2.8.jar as a dependency to my project and wrote following to the weblogic-application.xml:
我解决了这个问题，因此我将 jaxws-rt-2.2.8.jar 添加为我的项目的依赖项，并将以下内容写入 weblogic-application.xml：
<wls:prefer-application-packages>
<package-name>com.sun.xml.ws.api.wsdl.parser.*</package-name>
</wls:prefer-application-packages>
<wls:prefer-application-resources>
<wls:resource-name>META-INF/services/javax.xml.ws.*</wls:resource-name>
<wls:resource-name>META-INF/services/com.sun.xml.ws.*</wls:resource-name>
<wls:resource-name>META-INF/services/com.sun.tools.ws.*</wls:resource-name>
</wls:prefer-application-resources>
回答by rjdkolb
All credit to Thomas Isaksen
所有功劳都归功于Thomas Isaksen
I placed this metro-default.xml in my maven src/main/resources/META-INF which results in the file being placed WEB-INF/classes/META-INF
我将此 Metro-default.xml 放在我的 maven src/main/resources/META-INF 中，这导致文件被放置在 WEB-INF/classes/META-INF
The defaulthere caused many ClassNotFoundExceptions...
这里的默认值导致了许多 ClassNotFoundExceptions...
(I am using Weblogic 12.2.1.0.0)
（我使用的是 Weblogic 12.2.1.0.0）
<?xml version="1.0" encoding="UTF-8"?>
<metro xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns='http://java.sun.com/xml/ns/metro/config'
version="1.0">
<tubelines default="#default-metro-tubeline">
<tubeline name="default-metro-tubeline">
<client-side>
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TerminalTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.HandlerTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.ValidationTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MustUnderstandTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MonitoringTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.AddressingTubeFactory" />
<tube-factory className="com.sun.xml.ws.rx.rm.runtime.RmTubeFactory" />
<tube-factory className="com.sun.xml.ws.dump.MessageDumpingTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TransportTubeFactory" />
</client-side>
<endpoint-side>
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TransportTubeFactory" />
<tube-factory className="com.sun.xml.ws.dump.MessageDumpingTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.AddressingTubeFactory" />
<tube-factory className="com.sun.xml.ws.rx.rm.runtime.RmTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MonitoringTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MustUnderstandTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.HandlerTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.ValidationTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TerminalTubeFactory" />
</endpoint-side>
</tubeline>
</tubelines>
</metro>
回答by swts
We placed the metro-default.xml in WEB-INF/classes/META-INF to resolve the issue. Contents of the file can be taken from here : https://metro.java.net/guide/ch02.html#dynamic_tube-based_message_logging
我们将 Metro-default.xml 放在 WEB-INF/classes/META-INF 中以解决该问题。该文件的内容可以从这里获取：https: //metro.java.net/guide/ch02.html#dynamic_tube-based_message_logging
As Tube based messaging is introduced , jaxws-ri-2.2.8 jars are required to make any JAX-WS web services work.
由于引入了基于 Tube 的消息传递，因此需要 jaxws-ri-2.2.8 jars 才能使任何 JAX-WS Web 服务工作。
回答by user10302370
create a xml file named metro-default.xml and add the below xml content into it ,then place this metro-default.xml file inside the WEB-INF folder of your project then restart the server it will work.
创建一个名为metro-default.xml 的xml 文件并将以下xml 内容添加到其中，然后将此metro-default.xml 文件放在项目的WEB-INF 文件夹中，然后重新启动服务器，它将起作用。
<?xml version="1.0" encoding="UTF-8"?>
<metro xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns='http://java.sun.com/xml/ns/metro/config'
version="1.0">
<tubelines default="#default-metro-tubeline">
<tubeline name="default-metro-tubeline">
<client-side>
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TerminalTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.HandlerTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.ValidationTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MustUnderstandTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MonitoringTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.AddressingTubeFactory" />
<tube-factory className="com.sun.xml.ws.rx.rm.runtime.RmTubeFactory" />
<tube-factory className="com.sun.xml.ws.dump.MessageDumpingTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TransportTubeFactory" />
</client-side>
<endpoint-side>
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TransportTubeFactory" />
<tube-factory className="com.sun.xml.ws.dump.MessageDumpingTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.AddressingTubeFactory" />
<tube-factory className="com.sun.xml.ws.rx.rm.runtime.RmTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MonitoringTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.MustUnderstandTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.HandlerTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.ValidationTubeFactory" />
<tube-factory className="com.sun.xml.ws.assembler.jaxws.TerminalTubeFactory" />
</endpoint-side>
</tubeline>
</tubelines>
