September 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: JBoss wstool generate incorrect WSDL file

by mendaye

Thanks Richard for your answers. It is very helpful. I wanted to make sure I am not running into any interoperablility isse using jaxws stack (2.0.x) with java collecion class. Can someone answer my question below. 1. If I use Java Collections object in my web service that will be JBoss jaxws stack (2.0.x) compliant, am I running to any interoperability issue for .NET consumer. I wanted to make sure these web services can be consumed by .NET client. I am exposing existing Stateless EJB as service end-point and it is not easy to replace Java Collections object. 2. I have requirement - only authorized users can consume these web services. Does JBossWS 2.0.x provide user authentication mechanism to do this? If so how? 3. If #2 (Web service consumer authentication) is possible, can you point me document that has examples on this. Thanks, Surafel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083018#4083018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083018

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: wsconsume schema type reference problem

by Maffewl

R2203 of the Basic Profile standard (http://www.ws-i.org/Profiles/BasicProfile-1.2.html) states: 'An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute' where you say: <wsdl:message name="HelloWorldIn"> | <wsdl:part name="HelloWorld" element="tns:HelloWorld" /> | </wsdl:message> in rpc-literal it should be <wsdl:message name="HelloWorldIn"> | <wsdl:part name="HelloWorld" type="tns:sometype" /> | </wsdl:message> Axis I noticed is lenient on this rule, but JBossWS seems pretty strict about it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083011#4083011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083011

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: When JbossWS Wiki will be online

by richard_opalka

We're looking for the proper machine to be used for our Wiki hostage because old machine is broken. Wait few hours/days and all you want will be up and running again. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082927#4082927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082927

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: When JbossWS Wiki will be online

by DeanoUK

Thats the Wiki contents. What about the FAQ, the tutorials and the mass of links all around JBoss WS that point to the dyndns entry. Not good enough, I'm going back to Apache Axis. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082860#4082860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082860

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: wsconsume - Problems regarding http://www.w3.org/2001/XM

by vashistvishal

Have a look at this... what i have posted http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118062 I have also experienced issues like this when generating stubs for clients. To resolve issues like this even with the newer stack i had to modify wsdl by hand for interoperability. The way i did is first i created a service and client within Jboss and see how it work and what SOAP packet goes on wire... Then do a same sort of thing on .NEt side and capture SOAP packet. Now try to send the SOAP packet what .NET expects, for that you will have to modify your wsdl by hand. Once you know the difference between .NET side generated WSDL and required by Jboss ws client stack you cam modify other WSDLs. Some heavy lifting required to grasp the differences Mos of the issues i have come across is Because JAX-WS is pretty strict where as older stacks were not that strict in some conventions. All SOAP toolkit work fine within same envioronment but when used with other you normally have to fiddle with WSDL to make them work. Interoperability is their but with some modifications not just out of box yet. I hope this helps.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082859#4082859 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082859

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: http://jbws.dyndns.org When is it back up?

by richard_opalka

Guys, next time try to read the forum first and maybe you will find the answers to your questions without posting them ;-) http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082256#4082256 Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082848#4082848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082848

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: How to make a web service with XML input?

by jaboj

Thank you. Then it is possible to deploy JAX-WS style web services to JBoss? Do I need the same deployment descriptors as in the Provider sample or some specific JBoss deployment descriptors? My sample web service signature looks like this: anonymous wrote : | @ServiceMode(value=Service.Mode.PAYLOAD) | @WebServiceProvider(wsdlLocation="WEB-INF/wsdl/ProcessXml.wsdl") | public class ProcessXmlImpl implements Provider { | public Source invoke(Source arg0) { | // do something and return XML Source | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082841#4082841 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082841

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: http://jbws.dyndns.org When is it back up?

by ebonnett

I can't get to it either. I'm just getting started with JBossWS but I can't get to the documentation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082746#4082746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082746

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: EndpointRegistry JMX Bean in 2.0 NOT in 2.0.1

by palin

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

17 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Problem with inheritance and JBossWS

by koganty

Client is using the beans generated from the WSDL. Looks like after some minor changes on the server finally, the SOAP response looks right..but is not being materialized into the right type of object : | <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> | <env:Header/> | <env:Body> | <ns2:getAResponse xmlns:ns2="http://impl.beans.client.server.epicenter.extremenetworks.com/"> | <return | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="aa"> | <a>A</a> | <b>B</b> | </return> | </ns2:getAResponse> | </env:Body> | </env:Envelope> | The object still shows up as of type A and not Aa. The generated beans look like this : | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "a", propOrder = { | "a" | }) | @XmlSeeAlso({ | Aa.class | }) | public class A { | | protected String a; | .. | | | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "aa", propOrder = { | "b" | }) | @XmlSeeAlso({ | Aaa.class | }) | public class Aa | extends A | { | | protected String b; | .... | | | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "aaa", propOrder = { | "c" | }) | public class Aaa | extends Aa | { | | protected String c; | ..... | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082736#4082736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082736

17 years, 3 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-users September 2007