|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[Issue 945] New - Deployment fails on IBM WebSphere 6.1.0.17https://wsit.dev.java.net/issues/show_bug.cgi?id=945
Issue #|945 Summary|Deployment fails on IBM WebSphere 6.1.0.17 Component|wsit Version|1.3 Platform|Sun OS/Version|Solaris URL| Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P1 Subcomponent|transaction Assigned to|jfialli Reported by|mbogaert ------- Additional comments from mbogaert@... Tue Jul 1 07:52:41 +0000 2008 ------- When deploying a simple example ws, that deploys fine on Tomcat 6.0.16, IBM WebSphere 6.1.0.17 (incl. WS Feature Pack) fails with the following exception: [7/1/08 9:43:24:015 CEST] 00000031 WASAnnotation E WSWS7055E: The WEB-INF/wsdl/wscoor.wsdl Web Services Description Language (WSDL) file specified by annotations in class com.sun.xml.ws.tx.webservice.member.coord.ActivationRequesterPortType cannot be loaded correctly due to the following error: java.lang.RuntimeException: WSWS7035E: The addressing.xsd metadata file could not be found. [7/1/08 9:43:24:025 CEST] 00000031 WASAxis2MetaD E WSWS7045E: The ConfigurationContext for the websvcpoc.war application module cannot be created correctly because of the following error: java.lang.Exception: Configuration data could not be created for the Web service related class com/sun/xml/ws/tx/webservice/member/coord/ActivationRequesterPortType : com.ibm.ws.websvcs.exception.DeploymentException: java.lang.RuntimeException: WSWS7035E: The addressing.xsd metadata file could not be found. [7/1/08 9:43:24:034 CEST] 00000031 WASAxis2Compo E WSWS7007E: The websvcpoc.war application module cannot be loaded correctly because of the following error: java.lang.Exception: Configuration data could not be created for the Web service related class com/sun/xml/ws/tx/webservice/member/coord/ActivationRequesterPortType : com.ibm.ws.websvcs.exception.DeploymentException: java.lang.RuntimeException: WSWS7035E: The addressing.xsd metadata file could not be found. at com.ibm.ws.websvcs.annotations.generator.WASAnnotationInputBuilder.buildInputs(WASAnnotationInputBuilder.java:186) at com.ibm.ws.websvcs.deployment.WASAxis2MetaDataProcessor.buildAnnotationDBCInputs(WASAxis2MetaDataProcessor.java:380) at com.ibm.ws.websvcs.deployment.WASAxis2MetaDataProcessor.processWARMetadata(WASAxis2MetaDataProcessor.java:217) at com.ibm.ws.websvcs.deployment.WASAxis2MetaDataProcessor.processApplicationMetaData(WASAxis2MetaDataProcessor.java:134) at com.ibm.ws.websvcs.component.WASAxis2ComponentImpl.warMetaDataCreated(WASAxis2ComponentImpl.java:705) at com.ibm.ws.websvcs.component.WASAxis2ComponentImpl.metaDataCreated(WASAxis2ComponentImpl.java:563) at com.ibm.ws.runtime.component.MetaDataMgrImpl.fireMetaDataCreated(MetaDataMgrImpl.java:188) at com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.createMetaData(WebMetaDataFactory.java:205) at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:172) at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:306) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:563) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:832) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949) at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1486) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4070) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4168) at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1491) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 945] wscoord.wsdl deployment fails on IBM WebSphere 6.1.0.17https://wsit.dev.java.net/issues/show_bug.cgi?id=945
User haroldcarr changed the following: What |Old value |New value ================================================================================ Summary|Deployment fails on IBM We|wscoord.wsdl deployment fa |bSphere 6.1.0.17 |ils on IBM WebSphere 6.1.0 | |.17 -------------------------------------------------------------------------------- ------- Additional comments from haroldcarr@... Thu Jul 3 14:42:38 +0000 2008 ------- updated description --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
|
|
[Issue 945] wscoord.wsdl deployment fails on IBM WebSphere 6.1.0.17https://wsit.dev.java.net/issues/show_bug.cgi?id=945
User m_potociar changed the following: What |Old value |New value ================================================================================ Status|NEW |RESOLVED -------------------------------------------------------------------------------- Resolution| |WONTFIX -------------------------------------------------------------------------------- ------- Additional comments from m_potociar@... Mon Jul 7 16:45:17 +0000 2008 ------- This exception is raised in some internal implementation class of IBM WebSphere: com.ibm.ws.websvcs.annotations.generator.WASAnnotationInputBuilder.buildInputs(WASAnnotationInputBuilder.java:186) As I don't see how this exception relates to Metro, I am closing the bug as unrelated. In case this bug is actually related to Metro, please, feel free to reopen it and update the issue description with more details on how is the bug related to Metro. --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@... For additional commands, e-mail: issues-help@... |
| Free Forum Powered by Nabble | Forum Help |