[jbossws-dev] WS not resolving xml.xsd locally anymore as of 4.2.3.GA?

[Chris Laprun]

Hi all,

A problem has surfaced with JBoss Portal and its WSRP implementation  
while testing on 4.2.3.GA. If you try to run Portal while being  
offline, you will get the following error:

Caused by: org.jboss.ws.metadata.wsdl.WSDLException:  
javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot  
extract schema definition: java.net.UnknownHostException: www.w3.org
	at  
org 
.jboss 
.ws 
.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java: 
154)
	at  
org 
.jboss 
.ws 
.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java: 
295)
	at  
org 
.jboss 
.ws 
.metadata 
.builder 
.jaxrpc 
.JAXRPCServerMetaDataBuilder 
.buildMetaData(JAXRPCServerMetaDataBuilder.java:97)
	at  
org 
.jboss 
.wsf 
.stack 
.jbws 
.UnifiedMetaDataDeploymentAspect 
.create(UnifiedMetaDataDeploymentAspect.java:56)
	at  
org 
.jboss 
.wsf 
.framework 
.deployment 
.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java: 
118)
	at  
org 
.jboss 
.wsf 
.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java: 
97)
	at  
org 
.jboss 
.wsf 
.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java: 
90)
	at org.jboss.deployment.SubDeployerInterceptorSupport 
$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
	at  
org 
.jboss 
.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java: 
95)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at  
org 
.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java: 
264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy158.start(Unknown Source)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
	... 115 more
Caused by: javax.wsdl.WSDLException: WSDLException:  
faultCode=OTHER_ERROR: Cannot extract schema definition:  
java.net.UnknownHostException: www.w3.org
	at  
org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:394)
	at  
org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:416)
	at  
org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:416)
	at  
org 
.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java: 
178)
	at  
org 
.jboss 
.ws 
.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java: 
128)
	... 129 more
Caused by: java.net.UnknownHostException: www.w3.org
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
	at java.net.Socket.connect(Socket.java:520)
	at java.net.Socket.connect(Socket.java:470)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:387)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:522)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
	at sun.net.www.http.HttpClient.New(HttpClient.java:304)
	at sun.net.www.http.HttpClient.New(HttpClient.java:321)
	at  
sun 
.net 
.www 
.protocol 
.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
	at  
sun 
.net 
.www 
.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java: 
765)
	at  
sun 
.net 
.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
	at  
sun 
.net 
.www 
.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java: 
934)
	at java.net.URL.openStream(URL.java:1007)
	at  
org 
.jboss 
.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:588)
	at  
org 
.jboss 
.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:589)
	at  
org 
.jboss 
.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:560)
	at  
org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:385)
	... 133 more

which I think is caused by the WSDL parser failing to resolve an  
import in the WSDL type definition for WSRP:
<import namespace="http://www.w3.org/XML/1998/namespace"  
schemaLocation="http://www.w3.org/2001/xml.xsd"/>

This scenario (offline running) was properly handled in 4.2.2.GA (and  
previous versions) so this seems as a regression to me.

Any ideas?

Best,
Chris

==
JBoss Portal Developer / WSRP Lead
JBoss, a division of Red Hat
JBoss Portal blog: http://jbossportal.blogspot.com
Personal blog: http://blogs.codepuccino.com/metacosm
"Reality is that which, when you stop believing in it, doesn't go  
away." - Philip K. Dick