April 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: JSR-109Client, Mapping problem and trying to connect to

by darran.lofthouse＠jboss.com

There is no requirement for two code generators to generate identicle code as the JAX-RPC mapping file is used to describe how the schema was mapped to Java. If you have a reproducable scenario where invalid code is being generated please raise a bug in Jira with the required files to reproduce it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037876#4037876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037876

18 years, 11 months

1
0
0 / 0

[JBossWS] - Re: JSR-109Client, Mapping problem and trying to connect to

by d_pavel

Once again the root cause of the problems are the JBossWS tools used to generate the required artifacts. For comparison I used XFire (=open source Java SOAP framework). I got a total of X artifacts generated using JBossWS wbservices stack and related tools. In comparison I got a total of (X+10) artifacts generated using XFire (from these other 10 artifacts 7 are array type classes and the reminder of 3 are just simple object type classes...). So in conclusion I used both and here is my opinion: Not only that (different nr of artifacts), but there are discrepancies between the structure of the generated artifacts using JBossWS versus XFire even if the core of them should be in sync because I run against same WSDL. Please correct me if I'm wrong related with my last assumption. Even the methods in the generated Service Endpoint Interface had different method signatures (well 2 of them but still !!!). Now everything is working for me without issues (sorry no offence) but I was wondering about the different result from the tools in the 2 cases mentioned above.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037774#4037774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037774

18 years, 12 months

1
0
0 / 0

[JBossWS] - Problem with JBossAS 4.0.5 and JBossWS 1.2.0?

by chui

Hi, I've been searching for a way to send String[] type through SOAP, but it seems impossible when using WSDL generation for JSR-181. I found http://jira.jboss.org/jira/browse/JBWS-1101 and decided to try JBossWS1.2.0 with my JBoss4.0.5-GA::ejb3config (I was using JBossWS1.0.4). I installed JBossWS1.2.0 using anonymous wrote : | ant deploy-jboss40 and then some errors appeared when using my workspace: the annotations WebService, Stateless, etc... were not found. I use JDK1.5.0_upd.11. Did I do something wrong? =/ Thank you... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037706#4037706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037706

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Generated WSDL has default port 8080 even if server runs

by RomeuFigueira

Apparently it should have been fixed by now: http://jira.jboss.org/jira/browse/JBWS-1007 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037651#4037651 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037651

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Schema Validation in JBOSS-WS

by jthalliley

We were counting on the JBoss WS stack to validate incoming data against our schemas :-( Guess I'm putting in my vote to increase the priority of this item. Thanks, Tom View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037619#4037619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037619

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Element or attribute do not match QName production: QNam

by oskar.carlstedt

It seems like using a StreamSource instead of the DOMSource will work to get around this problem. But I can't understand why. //Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037614#4037614 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037614

18 years, 12 months

1
0
0 / 0

[JBossWS] - How to provide soapAction from dispatch call?

by oskar.carlstedt

Hello! I've tried a to fix this for some hours know. Maybe I'm doing something completely wrong here. I have a web service client that that is using the dispatch technique. I will use the dispatch because I'm using xmlbeans to bind my data. Here is a little code snippet of what I'm trying to do: | // names | String targetNamespace = "http://test/test-service"; | QName serviceQName = new QName(targetNamespace, "TestService"); | QName portQName = new QName(targetNamespace, "TestServiceSoap11Port"); | URL wsdlURL = new URL("http://lpt-osca:8080/service-testservice-jaxws-web?wsdl"); | | // create service | Service service = Service.create(serviceQName); | service.addPort(portQName, SOAPBinding.SOAP11HTTP_BINDING, wsdlURL.toExternalForm()); | Dispatch<StreamSource> dispatch = service.createDispatch(portQName, StreamSource.class, Mode.PAYLOAD); | | // set SOAPAction | dispatch.getRequestContext().put(BindingProvider.SOAPACTION_USE_PROPERTY, true); | dispatch.getRequestContext().put(BindingProvider.SOAPACTION_URI_PROPERTY, "uri:placeBuyOrder"); | | // create xml options for pretty print | XmlOptions xmlOptions = new XmlOptions(); | xmlOptions.setSavePrettyPrint(); | | // create request | TestRequestDocument testRequestDocument = TestRequestDocument.Factory.newInstance(); | ... | | | // print request | System.out.println("REQUEST"); | testRequestDocument.save(System.out, xmlOptions); | System.out.println(); | | // save request in a stream | ByteArrayOutputStream requestByteArrayOutputStream = new ByteArrayOutputStream(); | testRequestDocument.save(requestByteArrayOutputStream); | | // create a new stream source | StreamSource requestStreamSource = new StreamSource(new ByteArrayInputStream(requestByteArrayOutputStream.toByteArray())); | | // invoke | StreamSource responseSource = dispatch.invoke(requestStreamSource); | | // parse result | XmlObject xmlObject = XmlObject.Factory.parse(responseSource.getInputStream()); | | // print response | System.out.println("RESPONSE"); | xmlObject.save(System.out, xmlOptions); | When doing this. it seems like the soap action attribute is not sent to the server, at least not in the http headers. So, my question is: Is the soapAction sent to the sever? If so, where can I find it in the messageContext? My service is a web service endpoint provider implementation like | @Stateless | @WebServiceProvider( | serviceName = "TestService", | portName = "TestServiceSoap11Port", | targetNamespace = "http://test/test-service", | wsdlLocation = "WEB-INF/wsdl/test-service.wsdl") | @ServiceMode(value = Service.Mode.PAYLOAD) | public class FundOrderEndpointProvider implements Provider<Source> { | | ... | | } | | I will look for the soap action http header to decide what method to invoke in another stateless session bean. Can anyone help me we this? Best Regards Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037613#4037613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037613

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Generated WSDL has default port 8080 even if server runs

by anescu

Great, Thanks for the info. I searched everywhere for the 8080 string, but I guess the search treated jbossws.beans as a binary file, not as an archive. Why is it jboss-beans.xml pachaged inside a jbossws.beans archive? Why not put directly the file under the META-INF dir as the other 3 XML files? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037590#4037590 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037590

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Generated WSDL has default port 8080 even if server runs

by RomeuFigueira

Until 1.0.4 you need to change also this line: <property name="webServicePort">8080</property> which is located in deploy\jbossws.sar\jbossws.beans\META-INF\jboss-beans.xml You will need to expload jbossws.sar and jbossws.beans to get access to that particular xml file. Once changed, both your tomcat an jbossws ports to the same one, you should have no problem regarding this issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037565#4037565 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037565

18 years, 12 months

1
0
0 / 0

[JBossWS] - Re: Element or attribute do not match QName production: QNam

by oskar.carlstedt

... one more thing ... I'm running JBoss in isolated mode. All xmlbeans jar file are bundled in the EAR file. //Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037474#4037474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037474

18 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users April 2007