May 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Are WebService based on JBoss-Net different from JBossWS

by thomas.diesler＠jboss.com

Please use the user forum. The prefered way toi use web services is through the standard API i.e. JAXWS with JBossWS View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049331#4049331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049331

16 years, 11 months

1
0
0 / 0

[Fwd: SAAJ: Food for thought]

by Magesh Kumar Bojan

FYI -- -Magesh skype: mageshbk msn: mageshbk irc: mbojan yahoo: mageshbk phone: +919945699931

16 years, 11 months

2
1
0 / 0

[Design of JBoss Web Services] - Deploying trunk

by thomas.diesler＠jboss.com

| The JBossWS project is organised like this | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ +~~~~+ | Target Container: | AS-5.0 | | AS-4.2 | | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | Container Integration: | jbossws-jboss50 | | jbossws-jboss42 | | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | | | WS SPI: | jbossws-spi | | | | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | WS Stack Integration: | jbossws-native | | jbossws-sunri | | jbossws-xfire | | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | WS Stack: | jbossws-core | | Sun JAXWS | | Codehaus XFire | | | | +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ +~~~~~~~~~~~~~~~~~+ | | | WS-* Extensions: +~+ +~+ +~+ +~+ +~+ +~+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +~+ +~+ +~+ +~+ +~+ +~+ +~~~~+ | JAXWS Testsuite | | | Typically you would build, deploy, test one of the WS stacks against one of the supported target containers. | Here we explain first the manual procedure. Further down you find instruction on how to do this using our | automated Hudson QA environment. | | Working with the Integration layers | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | To run the general JAXWS samples against our native WS stack on JBoss-5.0 you would run the sequence below. | This is also the required sequence before any SVN commit. If one of the tests fails, please complain loudly. | | cd integration/native | ant deploy-jboss50 | ant tests-samples | | To run the collection of provider sample tests, you would run | | ant -Dtest=jaxws/samples/provider test | | To run a single specific test, you would run | | ant -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test | | This can be done in debug mode as well | | ant -Ddebug=true -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test | | Working with JBossWS Core | ~~~~~~~~~~~~~~~~~~~~~~~~~ | | The jbossws-core testssuite is a superset of the general JAXWS testsuite. It tests our native stack, jaxrpc, the tools layer, etc | This shows how to run the full core testsuite against JBoss-5.0 | | cd jbossws-core | ant deploy-jboss50 | ant tests | | Working with the Hudson QA environment | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | The Hudson QA environment helps you to test any supported stack against any supported target container. | To setup Hudson on your local box, you would run | | cd build | ant hudson-setup | ant hudson-start | | When you hit http://localhost:8180/hudson you should be able to | | 1. login | 2. build a target container | 3. run a testsuite against the target container | | Publicly, Hudson is available at http://jbws.dyndns.org:8180/hudson/ | | | Have fun + good luck | The JBossWS Team | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049311#4049311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4049311

16 years, 11 months

1
0
0 / 0

Deploying trunk

by Magesh Kumar Bojan

How do i do a deploy from trunk. "ant deploy-jbossws50" says target does not exists. -- -Magesh skype: mageshbk msn: mageshbk irc: mbojan yahoo: mageshbk phone: +919945699931

16 years, 11 months

2
1
0 / 0

Re: [Fwd: [jbossws-dev] jbossas internal test suite with jbossws 1.2.0_SP1]

by Thomas Diesler

Hi Magesh, I updated build/build.xml http://fisheye.jboss.com/browse/JBossWS/trunk/build/build.xml?r=3267 to contain propper build, deploy, test instructions. cheers -thomas On Thu, 2007-05-24 at 22:17 +0530, Magesh Kumar Bojan wrote: > I did the following now where do i go from here: > > ant hudson-setup > ant hudson-start > > I can hit my local machine "http://localhost:8180/hudson" > > Do i need to build from the web application "hudson" for local QA? > > Or is my understanding wrong that we can never build locally this QA > environment and it will work only online at > "http://jbws.dyndns.org:8180/hudson/" > > I can dig into the scripts and find out if an offline qa build is > possible using this "hudson" thing otherwise this is what i do manually: > > 1. Run branches\jbossws2.0\jbossws-tests against > Branch_4_0\build\output\jboss-4.0.5x-ejb3 > 2. Run branches\jbossws2.0\jbossws-tests against > Branch_4_2\build\output\jboss-4.2.x > 3. Run branches\jbossws2.0\jbossws-tests against > trunk\build\output\jboss-5.x.x > > Is it really possible to run a standalone hudson QA environment in local > machine offline? If so do we have documented steps of how to do the > build? If not then I will follow my regular tests manually. > > Thanks so much for your time. > > Thomas Diesler wrote: > > Well, Hudson is our QA environment. > > > > http://jbws.dyndns.org:8180/hudson/ > > > > The hudson scrips a plain vanilla shell scripts that simply record the > > manual steps that are involved to do QA. > > > > What are your specific problems running the QA? > > > > -thomas > > > > > > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-i schema for swaRef

by heiko.braun＠jboss.com

http://jira.jboss.com/jira/browse/JBWS-1663 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047909#4047909 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047909

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-i schema for swaRef

by heiko.braun＠jboss.com

Could you create a jira for that and add the suggested solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047883#4047883 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047883

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-i schema for swaRef

by noel.rocher＠jboss.com

You forgot to mention the wsconsume issue. It's solved in SUN RI by adding a "catalog" attribute to the wsimport tool. Also, you're saying that this should be fixed for JBossWS 2.0. Is the JBoss WS 1.2.x generated from the JBoss WS 2.0 codebase ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047882#4047882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047882

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-i schema for swaRef

by heiko.braun＠jboss.com

http://jira.jboss.com/jira/browse/JBWS-1660 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047876#4047876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047876

16 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-i schema for swaRef

by noel.rocher＠jboss.com

The problem is solved if I put the swaref.xsd with in jbossws-core.jar and jbossws-client.jar under /schema and modify org.jboss.ws.core.utils.JBossWSEntityResolver adding : | ... | public JBossWSEntityResolver() | { | ... | registerEntity("http://ws-i.org/profiles/basic/1.1/swaref.xsd", "schema/swaref.xsd"); | } | ... | The last problem is with wsconsume that is not using this resolver. I've got : | [wsconsume] java.net.UnknownHostException: ws-i.org | [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.UnknownHostException: ws-i.org | [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.UnknownHostException: ws-i.org | [wsconsume] at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:74) | [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:374) | [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:273) | [wsconsume] at com.sun.tools.xjc.reader.internalizer.AbstractReferenceFinderImpl.startElement(AbstractReferenceFinderImpl.java:78) | [wsconsume] at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) | [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:224) | [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:261) | [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:230) | [wsconsume] at com.sun.xml.bind.unmarshaller.DOMScanner.scan(DOMScanner.java:107) | [wsconsume] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.parseSchema(SchemaCompilerImpl.java:118) | [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.UnknownHostException: ws-i.org | [wsconsume] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) | [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 com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) | [wsconsume] at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) | [wsconsume] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) | [wsconsume] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) | [wsconsume] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) | [wsconsume] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) | [wsconsume] at com.sun.tools.xjc.reader.internalizer.DOMForest.parse(DOMForest.java:366) | [wsconsume] ... 33 more | [wsconsume] error: java.net.UnknownHostException: ws-i.org | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047872#4047872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047872

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev May 2007