Multi Component Fixes
by Darran Lofthouse
I am currently looking for some advice for the following issue: -
http://jira.jboss.com/jira/browse/JBWS-981
As the deployment code has moved back to the AS codebase it is dependent
on the APIs made available by JBossWS.
This fix is first going to require an addition to the SPI to expose the
virtual hosts information.
I will then need to update the framework code to populate this value.
And then the jbossas trunk and Branch_4_2 will need to be updated to
utilise the new values on the SPI.
To be able to update the code in AS it would need to use snapshot
releases for JBossWS and we would need to be sure a JBossWS release was
coming before the next AS release (JBoss AS 4.2.3.GA and 5.0.0.CR2).
Or is the process to get the SPI and Framework updated first and then
wait until the AS branches have the WS version increased to implement
the final fix there?
Regards,
Darran Lofthouse.
18 years
- 3
- 24
[Design of JBoss Web Services] - Re: swaref.xsd: connection time out during deployment
by lall2
Hi,
I am getting a similar error with JBoss 4.2.2 and JBossws-native-3.0.1
Is this the same problem like in
http://jira.jboss.org/jira/browse/JBWS-2252 or is it already fixed in another release?
| [wsconsume] java.net.ConnectException: Connection timed out: connect
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:213)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:88)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.Processor.runModeler(Processor.java:82)
| [wsconsume] at org.jboss.com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:543)
| [wsconsume] at org.jboss.com.sun.tools.ws.util.ToolBase.run(ToolBase.java:57)
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl$1.run(WSContractConsumerImpl.java:163)
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl.consume(WSContractConsumerImpl.java:166)
| [wsconsume] at org.jboss.ws.tools.jaxws.api.WSContractConsumer.consume(WSContractConsumer.java:176)
| [wsconsume] at org.jboss.ws.tools.jaxws.ant.wsconsume.executeNonForked(wsconsume.java:196)
| [wsconsume] at org.jboss.ws.tools.jaxws.ant.wsconsume.execute(wsconsume.java:217)
| [wsconsume] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
| [wsconsume] at org.apache.tools.ant.Task.perform(Task.java:364)
| [wsconsume] at org.apache.tools.ant.Target.execute(Target.java:341)
| [wsconsume] at org.apache.tools.ant.Target.performTasks(Target.java:369)
| [wsconsume] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
| [wsconsume] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
| [wsconsume] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
| [wsconsume] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
| [wsconsume] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
| [wsconsume] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
| [wsconsume] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
| [wsconsume] Caused by: java.net.ConnectException: Connection timed out: connect
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:128)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2207)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:224)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:181)
| [wsconsume] ... 20 more
| [wsconsume] Caused by: java.net.ConnectException: Connection timed out: connect
| [wsconsume] at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:90)
| [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:402)
| [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:301)
| [wsconsume] at com.sun.tools.xjc.reader.internalizer.AbstractReferenceFinderImpl.startElement(AbstractReferenceFinderImpl.java:95)
| [wsconsume] at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527)
| [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:240)
| [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:277)
| [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:246)
| [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.scan(DOMScanner.java:123)
| [wsconsume] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.parseSchema(SchemaCompilerImpl.java:135)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.internalBuildJAXBModel(JAXBModelBuilder.java:91)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.<init>(JAXBModelBuilder.java:70)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2190)
| [wsconsume] ... 22 more
| [wsconsume] Caused by: java.net.ConnectException: Connection timed out: connect
| [wsconsume] at java.net.PlainSocketImpl.socketConnect(Native Method)
| [wsconsume] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| [wsconsume] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| [wsconsume] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| [wsconsume] at java.net.Socket.connect(Socket.java:519)
| [wsconsume] at java.net.Socket.connect(Socket.java:469)
| [wsconsume] at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
| [wsconsume] at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
| [wsconsume] at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
| [wsconsume] at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
| [wsconsume] at sun.net.www.http.HttpClient.New(HttpClient.java:304)
| [wsconsume] at sun.net.www.http.HttpClient.New(HttpClient.java:316)
| [wsconsume] at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:817)
| [wsconsume] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:769)
| [wsconsume] at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:694)
| [wsconsume] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:938)
| [wsconsume] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
| [wsconsume] at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
| [wsconsume] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| [wsconsume] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| [wsconsume] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| [wsconsume] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| [wsconsume] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:394)
| [wsconsume] ... 33 more
| [wsconsume] error: java.net.ConnectException: Connection timed out: connect
|
wsdl:
| <?xml version="1.0" encoding="UTF-8"?>
| <definitions name='SwAService' targetNamespace='http://std.spg.com/ws/swa' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://std.spg.com/ws/swa' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
| <types>
| <xs:schema targetNamespace='http://std.spg.com/ws/swa' version='1.0' xmlns:swaRef='http://ws-i.org/profiles/basic/1.1/xsd' xmlns:tns='http://std.spg.com/ws/swa' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
| <xs:import namespace='http://ws-i.org/profiles/basic/1.1/xsd' schemaLocation='http://ws-i.org/profiles/basic/1.1/swaref.xsd'/>
| <xs:element name='documentDT' type='tns:documentDT'/>
| <xs:element name='findDocument' type='tns:findDocument'/>
| <xs:element name='findDocumentResponse' type='tns:findDocumentResponse'/>
| <xs:element name='sendDocument' type='tns:sendDocument'/>
| <xs:complexType name='sendDocument'>
| <xs:sequence>
| <xs:element form='qualified' minOccurs='0' name='document' type='tns:documentDT'/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name='documentDT'>
| <xs:sequence>
| <xs:element minOccurs='0' name='correlationid' type='xs:string'/>
| <xs:element minOccurs='0' name='creationdate' type='xs:dateTime'/>
| <xs:element minOccurs='0' name='documentdescription' type='xs:string'/>
| <xs:element minOccurs='0' name='filename' type='xs:string'/>
| <xs:element minOccurs='0' name='document' type='swaRef:swaRef'/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name='findDocument'>
| <xs:sequence>
| <xs:element form='qualified' minOccurs='0' name='filename' type='xs:string'/>
| <xs:element form='qualified' minOccurs='0' name='correlationid' type='xs:string'/>
| </xs:sequence>
| </xs:complexType>
| <xs:complexType name='findDocumentResponse'>
| <xs:sequence>
| <xs:element form='qualified' minOccurs='0' name='document' type='tns:documentDT'/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </types>
| <message name='SwAWS_findDocument'>
| <part element='tns:findDocument' name='findDocument'/>
| </message>
| <message name='SwAWS_findDocumentResponse'>
| <part element='tns:findDocumentResponse' name='findDocumentResponse'/>
| </message>
| <message name='SwAWS_sendDocument'>
| <part element='tns:sendDocument' name='sendDocument'/>
| </message>
| <portType name='SwAWS'>
| <operation name='findDocument' parameterOrder='findDocument'>
| <input message='tns:SwAWS_findDocument'/>
| <output message='tns:SwAWS_findDocumentResponse'/>
| </operation>
| <operation name='sendDocument'>
| <input message='tns:SwAWS_sendDocument'/>
| </operation>
| </portType>
| <binding name='SwAWSBinding' type='tns:SwAWS'>
| <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
| <operation name='findDocument'>
| <soap:operation soapAction='http://std.spg.com/ws/swa/findDocument'/>
| <input>
| <soap:body use='literal'/>
| </input>
| <output>
| <soap:body use='literal'/>
| </output>
| </operation>
| <operation name='sendDocument'>
| <soap:operation soapAction='http://std.spg.com/ws/swa/sendDocument'/>
| <input>
| <soap:body use='literal'/>
| </input>
| </operation>
| </binding>
| <service name='SwAService'>
| <port binding='tns:SwAWSBinding' name='SwAWSPort'>
| <soap:address location='REPLACE_WITH_ACTUAL_URL'/>
| </port>
| </service>
| </definitions>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164234#4164234
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164234
18 years
- 1
- 0
[Design of JBoss Web Services] - swaref.xsd: connection time out during deployment
by Aigor1966
Hi,
we are using JBoss 4.0.5.GA Ejb3 enabled with JBossws-native-2.0.3.GA.
We use swaref to manage attachment too.
During the deploy of our application we see that we receive an error of "connetion time out" probably because the application try to reach the address http://ws-i.org/profiles/basic/1.1/swaref.xsd.
Actually the server is not connected to internet and we must take it disconnected. If we try on a server with internet connection enabled deployment works well.
We have seen that this bug was fixed with version 2.0.0 of jbossws, but we still have the problem.
Someone can help me?
Thank you very much.
Bye
Gianni
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162908#4162908
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162908
18 years
- 1
- 0
Running Framework Tests
by Darran Lofthouse
I am currently working on the following Jira issue: -
http://jira.jboss.com/jira/browse/JBWS-2185
As this is related to JAX-WS I believe this needs to be added to the
framwork project and not the native project.
I have checked out the following: -
https://svn.jboss.org/repos/jbossws/framework/trunk
Is there any information on how to build the testsuit and run either one
or all of the tests using the most up to date native libraries?
Regards,
Darran Lofthouse.
18 years
- 2
- 2