March 2009 - jbossws-users - Jboss List Archives

[JBossWS] - Re: abstract operation - wsconsume error

by scottmh

Anyone? Pretty please? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222153#4222153 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222153

15 years, 8 months

1
0
0 / 0

[JBossWS] - Maven WSConsume

by john.pfeifer＠billmelater.com

We haven encountered several issues with the lack of platform independence using the maven exec plugin to invoke the wsconsume.sh script. I was hoping that there was a single jar (i.e. wsconsume.jar) or an existing maven plugin that we could use to generate our services from a WSDL. This along with the lack of spring support may lead us to a new WS Stack. Any help would be greatly appreciated. Thanks, John View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222147#4222147 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222147

15 years, 8 months

1
0
0 / 0

[JBossWS] - Call.setReturnType gives NPE

by p_repetti

Hello I am using JBossWS inside JBoss AS 4.2.2GA. I guess the WS version is 2.0.1GA. I get a NullPointer calling setReturnType(null) on an instance of Call. The Java EE doc for setReturnType javax.xml.rpc.Call says that "Invoking setReturnType(null) removes the return type for this Call object." and so does the JBoss implementation, org.jboss.ws.core.jaxrpc.client.CallImpl. The jboss stack trace is Caused by: java.lang.NullPointerException at org.jboss.ws.core.binding.TypeMappingImpl$IQName.(TypeMappingImpl.java:702) at org.jboss.ws.core.binding.TypeMappingImpl.getJavaType(TypeMappingImpl .java:214) at org.jboss.ws.core.jaxrpc.client.CallImpl.setReturnType(CallImpl.java: 239) I downloaded the sources and followed the stack trace. It looks to me that the NPE is justified, since the IQName constructor does not check the passed qname against null: public IQName(QName name) { namespace = name.getNamespaceURI() != null ? name.getNamespaceURI().intern() : "".intern(); localPart = name.getLocalPart() != null ? name.getLocalPart().intern() : "".intern(); prefix = name.getPrefix() != null ? name.getPrefix().intern() : "".intern(); hash = name.hashCode(); } Has anyone had the same problem ? Is it necessary to open a bug ? -- Pierangelo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221957#4221957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221957

15 years, 8 months

1
0
0 / 0

[JBossWS] - How to get rid of namespace information ?

by dimar1975

Hi all, I have a Webservice which returns an ArrayList of Objects to the client. Since the methods takes quite a bit to return I have taken a dump of the SOAP packet which is returned: The method is getAllViews and this is a small piece of it: <ns1:getAllViewsResponse xmlns:ns2="http://oneoffice/tasklist" xmlns:ns1="http://oneoffice/filter"><return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">view2</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">view1</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">item18</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">item1</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">item7</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">item3</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">ff</return> | <return xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">item3</return></ns1:getAllViewsResponse> As you can see there's a lot of information in the xmlns and xsi elements which bloat the SOAP package. How can I get rid of it so that I slim the SOAP packet ? I've tried with both @SOAPBinding(style = SOAPBinding.Style.RPC) and @SOAPBinding(style = SOAPBinding.Style.DOCUMENT) but the SOAP packet stays the same..... any idea ? thanks Marco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221864#4221864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221864

15 years, 9 months

1
0
0 / 0

[JBossWS] - Re: No Content-type in the header

by gurkanerdogdu

Thanks for answer. I have following jars in the endorsed library. jbossws-native-jaxrpc.jar,-jaxws.jar, -jaxws-ext.jar, -saaj.jar, Exception is : Exception in Thread main javax.xml.ws.WebServiceException : No Content-type in the header at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java 163:) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java ) at com.sun.xml.ws.api.pipe.Fiber.__doRun et.c.... I run the client in standalone mode in Eclipse. Actually, I am putting all the JBoss Client jars in to the class path. Exactly, which jars that I have to setup in the client classpath to call webservice correctly? Thanks a lot; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221831#4221831 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221831

15 years, 9 months

1
0
0 / 0

[JBossWS] - Re: java.lang.LinkageError: loader constraint violation:(In

by GajananM

thanks for the reply. i am running same application through simple java project and it is working fine but when i created webclient that time i am getting this error. if it is a library problem then it should not work in java project also bec lib are same. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221813#4221813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221813

15 years, 9 months

1
0
0 / 0

[JBossWS] - WebServiceException: Undefined port type

by abcd1234

I am new to Web Services with JBoss. A client is connecting to an EJB3 based Web Service With JBoss AS 5 and JDK 6 using JAX-WS. I am stuck with the following exception. Some jars might be missing in the classpath for the client. If it is the case , which ones ? I have verified that Jboss has correctly deployed the Web Service. | Exception in thread "main" javax.xml.ws.WebServiceException:Undefined port type: {http://webservice.samples/}HelloRemoteat com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:300)at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:306)at javax.xml.ws.Service.getPort(Service.java:161)at samples.client.BeanWSClient.getPort(BeanWSClient.java:44)at samples.client.BeanWSClient.main(BeanWSClient.java:35) BeanWSClient.java (client is a different project than EJB3 WS): package samples.client; | import java.net.MalformedURLException; | import java.net.URL; | import javax.xml.namespace.QName; | import javax.xml.ws.Service; | import samples.webservice.HelloRemote; | | public class BeanWSClient { | | /** | * @param args | */ | public static void main(String[] args) throws Exception{ | // TODO Auto-generated method stub | | | String endpointURI ="http://127.0.0.1:8080/SampleWSEJBProject/HelloWorld?wsdl"; | String helloWorld = "Hello world!"; | | Object retObj = getPort(endpointURI).echo(helloWorld); | System.out.println(retObj); | } | private static HelloRemote getPort(String endpointURI) throws MalformedURLException { | QName serviceName = new QName("http://www.openuri.org/2004/04/HelloWorld", "HelloWorldService"); | URL wsdlURL = new URL(endpointURI); | | | Service service = Service.create(wsdlURL, serviceName); | return service.getPort(HelloRemote.class); | } | | | } | HelloRemote.java: package samples.webservice; | import javax.jws.WebService; | @WebService | public interface HelloRemote { public String echo(String input);} HelloWorld.java: package samples.webservice; | import javax.ejb.Remote; | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebService; | import javax.jws.soap.SOAPBinding; | /** * Session Bean implementation class MyBean */ | @WebService(name = "EndpointInterface", targetNamespace = "http://www.openuri.org/2004/04/HelloWorld", serviceName = "HelloWorldService")@SOAPBinding(style = SOAPBinding.Style.RPC)(a)Remote(HelloRemote.class) | @Stateless | public class HelloWorld implements HelloRemote { | /** * @see Object#Object() */ | @WebMethod | public String echo(String input) { return input; }} View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221782#4221782 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221782

15 years, 9 months

1
0
0 / 0

[JBossWS] - Re: SOAP not working with Jboss 5

by alessio.soldano＠jboss.com

If you can see the wsdl from the console and can call the service for instance with SoapUI, this is definitely a .NET issue. Please provide a java exception you get on server side if any. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221664#4221664 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221664

15 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Specify WS-Security Handler using JEE standards

by alessio.soldano＠jboss.com

"vdurbha" wrote : But the server side endpoint still does not work if I use @HandlerChain annotation instead of @EndpointConfig to set the security handler. After digging into the source code of JBossWS and the log files for a few hours, I understood that for the WS-Security handler to work correctly, it has to be configured as a POST Handler type. When I used @HandlerChain annotation, it is configured as ENDPOINT Handler type. I was not able to find anyway to specify the type of handler in a standard way. You're right, you can't configure POST handlers using the standard descriptor. This is a limitation of the native stack; in the case of ws-addresing configuration you can use the standard @Addressing annotation, but there's no similar standard annotation for ws-security. Do you have multiple handlers? Never tried, but I though ws-addresing native impl could work even with ENDPOINT handlers if they're in the right position in the chain and there aren't other handlers in POST (decryption needs to happen first, encryption needs to happen last) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221662#4221662 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221662

15 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Generating WSDL from request/response

by alessio.soldano＠jboss.com

You need the schema, soap request/response are not enough to generate the wsdl. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221661#4221661 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221661

15 years, 9 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 March 2009