February 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: JBossWS 1.2.0CR2 with JEMS 1.2 (and JBoss 4.0.5) fails

by Juergen.Zimmermann

I'm using an EJB3 stateless session bean annotated with: @WebService(name="KundenverwaltungSEI", serviceName="KundenverwaltungService") | @SOAPBinding(style=RPC) | @Stateless(name="KundenverwaltungService") | @Remote(KundenverwaltungService.class) | @RolesAllowed(ROLLE_MITARBEITER) | @PortComponent(contextRoot="/hska/KundenverwaltungService", urlPattern="/*", authMethod="BASIC", transportGuarantee="NONE") | @SecurityDomain(LOGIN_DOMAIN_HSKA) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011082#4011082 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011082

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: SchemaTypeCreator.introspectJavaProperties Exception w/

by aschmidt1978

Adding a "serializable" child element to the "globalBindings" xjc annotation in the schema seemed to resolve the problem. For compatibility with .NET apps, I also added the following annotation to element collections throughout the schema, as generic collections didn't seem to be picked up when adding a web reference to a project. <jxb:property collectionType="indexed"/> Given that I found a workaround, I haven't taken the opportunity to see if this issue is resolved without the workaround in jbossws 1.2, but I would hope that it's been resolved either inherently or as a bugfix. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011053#4011053 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011053

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: WS Eventing client - basics question

by heiko.braun＠jboss.com

Yes, tell us what you have come up with when it's working... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010973#4010973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010973

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: JBossWS 1.2.0CR2 with JEMS 1.2 (and JBoss 4.0.5) fails

by heiko.braun＠jboss.com

Sorry, i think that was complete BS. What mode are you using? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010972#4010972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010972

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: JBossWS 1.2.0CR2 with JEMS 1.2 (and JBoss 4.0.5) fails

by heiko.braun＠jboss.com

This looks to me as if the client uses default names for wrapped parameters but the service impl uses named ones. It it a doclit/wrapped service? How did you create the client artefacts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010971#4010971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010971

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Web services and stateful session

by heiko.braun＠jboss.com

Dwin is right. WS-Addressing is the right way to build conversational web services. Take a look at the user guide and the corresponding samples. It contains an example for a staful service. It's already supported for quiet some time now: http://labs.jboss.com/portal/jbossws/user-guide/en/html/wsaddressing.html IMO passing the serialized handle around is not a good idea. I could picture a SLSB facade instead that keeps a UUID->Handle registry and delegates to the SFSB beans behind the scenes. You could hand out the UUID using WS-Adressing and internally rely on the ejb handle. You could even offer a simple API for clients to resign from their sessions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010969#4010969 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010969

19 years, 2 months

1
0
0 / 0

[JBossWS] - EJB 3.0 to WebService

by aerosteak2

Hello, Let say I just deployed a EJB3.0 POJO with the @Service annotation. Now I would like to make this same POJO available as a WebService (WSDL, SOAP). How would I do that with the JBoss infrastructure? Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010937#4010937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010937

19 years, 2 months

1
0
0 / 0

[JBossWS] - Mapping file generation & parameter unwrapping issues

by sbivol

We have a .NET sample Web Service (see wsdl at the very bottom), and we?re trying to invoke it from an SLSB in jboss 4.0.5.GA. We tried to get it working with jboss 1.0.3, 1.0.4, and 1.2.0, but did not succeed. With 1.0.3, we could generate the mapping file, but then when invoking the service it would fail finding operation metadata, similar to http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91101, we upgraded to 1.0.4, where this issue doesn't seem to come up. With 1.0.4, using the artifacts generated with 1.0.3, when invoking the service, it would fail as described in http://jira.jboss.org/jira/browse/JBWS-1260 (Scenarios E, F, I, and L). Any attempts to generate the mapping file with 1.0.4 would result in same error during generation of the file. Then I pulled down jbossws 1.2.0.CR2 source, where the above jira issue is supposed to be fixed, but it still cannot generate the mapping file, getting a different error now (see exception stack below). So, am I doing something wrong? Can anyone try generating the artifacts based on wsdl further down, or suggest a workaround? Appreciate your help. Regards Sergiu ------------------------------------- The error i'm getting with 1.2.0.CR2 is: | Exception in thread "main" org.jboss.ws.WSException: String passed is null | at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:453) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:137) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113) | at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:716) | at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:709) | at org.jboss.ws.tools.WSDLToJava.unwrapRequest(WSDLToJava.java:285) | at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:494) | at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:394) | at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:570) | at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:602) | at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:187) | at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:304) | at org.jboss.ws.tools.WSTools.process(WSTools.java:138) | at org.jboss.ws.tools.WSTools.generate(WSTools.java:120) | at org.jboss.ws.tools.WSTools.main(WSTools.java:61) | ----------------------------------------- The .NET Web Service WSDL file: | <?xml version="1.0" encoding="utf-8"?> | <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" | xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" | xmlns:tns="http://tempuri.org/TitanWebServices/TitanService" xmlns:s="http://www.w3.org/2001/XMLSchema" | xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" | targetNamespace="http://tempuri.org/TitanWebServices/TitanService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> | <wsdl:types> | <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/TitanWebServices/TitanService"> | <s:element name="TitanRunNavision"> | <s:complexType> | <s:sequence> | <s:element minOccurs="0" maxOccurs="1" name="FunctionName" type="s:string" /> | <s:element minOccurs="0" maxOccurs="1" name="ParameterList" type="s:string" /> | </s:sequence> | </s:complexType> | </s:element> | <s:element name="TitanRunNavisionResponse"> | <s:complexType> | <s:sequence> | <s:element minOccurs="0" maxOccurs="1" name="TitanRunNavisionResult"> | <s:complexType> | <s:sequence> | <s:any /> | </s:sequence> | </s:complexType> | </s:element> | </s:sequence> | </s:complexType> | </s:element> | </s:schema> | </wsdl:types> | <wsdl:message name="TitanRunNavisionSoapIn"> | <wsdl:part name="parameters" element="tns:TitanRunNavision" /> | </wsdl:message> | <wsdl:message name="TitanRunNavisionSoapOut"> | <wsdl:part name="parameters" element="tns:TitanRunNavisionResponse" /> | </wsdl:message> | <wsdl:portType name="TitanServiceSoap"> | <wsdl:operation name="TitanRunNavision"> | <wsdl:input message="tns:TitanRunNavisionSoapIn" /> | <wsdl:output message="tns:TitanRunNavisionSoapOut" /> | </wsdl:operation> | </wsdl:portType> | <wsdl:binding name="TitanServiceSoap" type="tns:TitanServiceSoap"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http" /> | <wsdl:operation name="TitanRunNavision"> | <soap:operation soapAction="http://tempuri.org/TitanWebServices/TitanService/TitanRunNavision" style="document" /> | <wsdl:input> | <soap:body use="literal" /> | </wsdl:input> | <wsdl:output> | <soap:body use="literal" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:binding name="TitanServiceSoap12" type="tns:TitanServiceSoap"> | <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" /> | <wsdl:operation name="TitanRunNavision"> | <soap12:operation soapAction="http://tempuri.org/TitanWebServices/TitanService/TitanRunNavision" style="document" /> | <wsdl:input> | <soap12:body use="literal" /> | </wsdl:input> | <wsdl:output> | <soap12:body use="literal" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:service name="TitanService"> | <wsdl:port name="TitanServiceSoap" binding="tns:TitanServiceSoap"> | <soap:address location="http://dev4/titanwebservices/service.asmx" /> | </wsdl:port> | <wsdl:port name="TitanServiceSoap12" binding="tns:TitanServiceSoap12"> | <soap12:address location="http://dev4/titanwebservices/service.asmx" /> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010262#4010262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010262

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Web services and stateful session

by dwin

hey Andrea as of JAX-WS 2.0, there is no supprt for stateful sessions. In JAX-WS 2.1, there is a concept of stateful webservices which is done through ws-addressing. I would not recommend serializing the Handle object, if need be make a representation (or key) of the handle and pass that to the WS client. Each time that key is returned, you can used that to look up the handle. In fact, I don't even think its possible. You can mimick a session by defining the lifecycle of a session (starts at login, ends at logout). Of course, you would have to persist/maintain state on the server side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010251#4010251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010251

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: Error consuption web service

by Rikr2

My team discovered this: If JBOSS use a JDK version with JAI component installed then this problem is risen when you try to consume a web service, if you are in this case you should have 2 JDK installed one with JAI component and the another one without it, and start JBOSS with the second one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010185#4010185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010185

19 years, 2 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 February 2007