October 2006 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Problem using a .NET client with JBOSSWS 1.0.3

by summer.hill

Yep, I get exactly the same thing for the .NET client I am using. In 1.0.3 you have to make sure that no Object parameters contain null properties. I'm rolling back to 1.0.2 as I type. James View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978684#3978684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978684

17 years, 7 months

1
0
0 / 0

[JBossWS] - Problem using a .NET client with JBOSSWS 1.0.3

by king_country2000

We have exposed a web service in JBOSS AS 4.0.4 GA using DOC/LITERAL/WRAPPED. We have a .NET client that accesses this web service. In JBOSSWS 1.0-GA this worked fine. We then upgraded to JBOSSWS 1.0.3-GA and now the same setup produces error messages: anonymous wrote : | | Caused by: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: The prefix "xsi" for attribute "xsi:nil" associated with an element type "userId" is not bound. @ *unknown*[1,579] | | at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:67) | | at org.jboss.ws.jaxrpc.encoding.JAXBDeserializer.deserialize(JAXBDeserializer.java:92) | | ... 30 more | | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: The prefix "xsi" for attribute "xsi:nil" associated with an element type "userId" is not bound. @ *unknown*[1,579] | | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:156) | | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126) | | at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:63) | | ... 31 more | | Caused by: org.xml.sax.SAXException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "userId" is not bound. @ *unknown*[1,579] | | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:332) | | at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) | | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | | at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) | | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) | | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) | | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | | | It looks like the XML Schema Instance namespace is not being provided to the deserializer. Is this a bug. If so could it be fixed in the next release. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978673#3978673 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978673

17 years, 7 months

1
0
0 / 0

[JBossWS] - JWSDP 2.0 with JBoss 4.0.4 ?

by hamptont

When using JBoss 4.0.3SP1 I used JWSDP 2.0 to generate the ties for my webservice. I would like to upgrade to using JBoss 4.0.4. When I deploy this same web service built, using JWSDP to JBoss 4.0.4, I get the following WARNINGS. The web service works, but these warnings concern me. 17:47:27,822 WARN [PortComponentMetaData] <wsdl-port> element in webservices.xml not namespace qualified: MyWSPort | 17:47:29,593 WARN [WSDL11Reader] Encoding style 'http://schemas.xmlsoap.org/soap/encoding/' not supported for: {http://myws.my.com/}getDBList | 17:47:29,594 WARN [WSDL11Reader] Encoding style 'http://schemas.xmlsoap.org/soap/encoding/' not supported for: {http://myws.my.com/}processBlastJob Do I need to stop using JWSDP and use the wstool that comes with JBoss ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978654#3978654 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978654

17 years, 7 months

1
0
0 / 0

[JBossWS] - Re: noice in SOAP reply

by ge0ffrey

I installed a pipeline between the client and server which shows the problem: POST /seems-ejb/SeemsServiceImpl HTTP/1.1 User-Agent: Profile/MIDP-1.0 Configuration/CLDC-1.0 Content-Language: en-US Content-Type: text/xml SOAPAction: " User-Agent: UNTRUSTED/1.0 Content-Length: 325 Host: geoffreydesktop:8081 <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tns="http://seems.kahosl.be/jaws"> <soap:Body> <tns:sayHello> </tns:sayHello> </soap:Body> </soap:Envelope> HTTP/1.1 200 OK Server: Apache-Coyote/1.1 X-Powered-By: Servlet 2.4; JBoss-4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)/Tomcat-5.5 Set-Cookie: JSESSIONID=DAD82CAF9143C49861F34EFD5131AB5F; Path=/ Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Mon, 16 Oct 2006 15:18:24 GMT e2 <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><ns1:sayHelloResponse xmlns:ns1='http://seems.kahosl.be/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><ns1:result>Hello:) d </ns1:result> 17 </ns1:sayHelloResponse> 1a </env:Body></env:Envelope> 0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978571#3978571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978571

17 years, 7 months

1
0
0 / 0

[JBossWS] - Global JAX-RPC handlers

by sujeet.banerjee

I have a JBoss 4.0 instance running, which deploys lots of Webservices (most of them are not written by me; I am just the administrator). Now I am interested in analysing any request that go to any of the deployed services. Is there a standard-way/hack to intercept the SOAP requests going to any of the depolyed services, without having to configure handlers for each of the service-endpoints individually? May be, something like a global handler which could be configured as a part of the JBoss server, and that would intercept any message irrespective of the service-endpoint it is going to? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978335#3978335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978335

17 years, 7 months

1
0
0 / 0

[JBossWS] - Exception when invoking EJB3 webservice from clients/SchemaB

by MmarcoM

hi all, i have exposed an EJB3 as a webservice.... it is deployed fine on jboss, but whenn i try to invoke it from a client i got this bad exception.. | Exception in thread "main" java.rmi.RemoteException: Call invocation failed: Cou | ld not transmit message; nested exception is: | javax.xml.soap.SOAPException: Could not transmit message | at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:718) | at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) | at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) | at $Proxy0.testWebServiceMethod(Unknown Source) | at ws.jboss.org.samples.jsr181ejb.WSFacadeTester.doTest(WSFacadeTester.j | ava:49) | at ws.jboss.org.samples.jsr181ejb.WSFacadeTester.main(WSFacadeTester.jav | a:34) | Caused by: javax.xml.soap.SOAPException: Could not transmit message | at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:204 | ) | at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:687) | ... 5 more | Caused by: java.lang.NoSuchMethodError: org.jboss.xb.binding.sunday.unmarshallin | g.SchemaBinding.setXopMarshaller(Lorg/jboss/xb/binding/sunday/xop/XOPMarshaller; | )V | at org.jboss.ws.jaxb.JBossXBMarshallerImpl.marshal(JBossXBMarshallerImpl | .java:145) | at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer. | java:107) | at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElemen | t.java:157) | at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.j | ava:817) | at org.jboss.ws.soap.SOAPContentElement.handleMTOMTransitions(SOAPConten | tElement.java:1015) | at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:96 | 8) | at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.ja | va:171) | at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.ja | va:184) | at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.ja | va:184) | at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.ja | va:184) | at org.jboss.ws.soap.SAAJElementWriter.printInternal(SAAJElementWriter.j | ava:163) | at org.jboss.ws.soap.SAAJElementWriter.print(SAAJElementWriter.java:142) | | at org.jboss.ws.soap.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:266) | at org.jboss.ws.binding.soap.SOAPMessageMarshaller.write(SOAPMessageMars | haller.java:78) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnect | ion(HTTPClientInvoker.java:164) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPCli | entInvoker.java:81) | at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.jav | a:143) | at org.jboss.remoting.Client.invoke(Client.java:525) | at org.jboss.remoting.Client.invoke(Client.java:488) | at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189 | ) | ... 6 more | in running my client, i am launching application as follows.. | C:\Sw\J2MEJobApp\wsclient>java -cp activation.jar;jbossall-client.jar;jboss-xml- | binding.jar;jbossws-client.jar;mail.jar;serializer.jar;xalan.jar;xercesImpl.jar; | xml-apis.jar;target\wsclient-1.0-SNAPSHOT.jar;. ws.jboss.org.samples.jsr181ejb.WSFacadeTester | i m guessing there's a classpath clash... can anyone help me in fixing the problem? thanks and regards marco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978333#3978333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978333

17 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Pure message style SOAP exchange

by caldron68

If you find out, let me know. I'm trying to do the same thing and have not been successful with JBossWS. Cheers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978149#3978149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978149

17 years, 7 months

1
0
0 / 0

[JBossWS] - Pure message style SOAP exchange

by giusarno

Hi, I would like to have a simple WS where I can send different XML documents (starting with a different root element) using the same SOAP channel. I basically want to implement a simple and generic SOAP XML doc exchange interface. I looked at the documentation and I thought Messaging style did for me. But when I looked at the conf file I noticed that we still need to specify the root element for the incoming message and for the return message. 1 question: Why it is so ? if the either the sender and the responder implements method that do not care about the content ? | <operation name="processElement" return-xml-name="Response"> | <parameter type="javax.xml.soap.SOAPElement" xml-name="Order"/> | </operation> | </service> | | | public interface MessageTestService extends Remote | { | public Element processElement(Element msg) throws RemoteException; | } | 2 question: How can I solve my problem with JbossWS? is it possible ? Can anyone please help on this ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978124#3978124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978124

17 years, 7 months

1
0
0 / 0

[JBossWS] - Re: Default context root of EJB Endpoint in ear

by be324854

I know you can do that, but including the ear name in the context root has some advantages. You may change the name of an ear in 5 seconds and has only to be done in 1 place. Changing the @PortComponent requires access to the source code, recompile and possible changing multiple locations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978105#3978105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978105

17 years, 7 months

1
0
0 / 0

[JBossWS] - JBossWS Plugin for JBossIDE / Eclipse

by omatzura

Hi all, We are happy to announce the first public beta of our JBossWS-plugin for JBossIDE / Eclipse (http://www.soapui.org/jbossws/index.html) which has been release as part of the JBossIDE 2.0.0 beta2 release. The JBossWS Plugin is a specialized Eclipse plugin for working with the JBossWS webservice stack together with JBossIDE or standalone. In addition to previously available webservice-related functionality in our soapui-eclipse-plugin (http://www.soapui.org/eclipse/index.html), the JBossWS Plugin currently has initial functionality for: * Publishing POJO's/EJB's as JBossWS Web Services (walkthrough example: http://www.soapui.org/jbossws/bottomup_example.html) * Consuming an existing Web Service with JBossWS * Implementing an existing WSDL contract with JBossWS (walkthrough example: http://www.soapui.org/jbossws/topdown_example.html) * Adding JSR-181 WebService Annotations to an existing POJOs/EJB3s (walkthrough example: http://www.soapui.org/jbossws/annotations_example.html) The following improvements are planned to be available for the final JBossIDE 2.0.0 release: * Improved support for implementing Web Services from an existing WSDL contract * Improved support for consuming Web Services from en EJB or Servlet * Improved support for adding Web Service annotations on a method level * Wizards for security configurations * Project/File templates for JBossWS projects and related artifacts * Tighter integration with the Eclipse Web Tools Projects Web Service support * Integrated Help We would of course be extremely thankfull for any feedback, bug-reports, suggestions, etc.. Please submit questions and discuss issues here or on the JBoss Eclipse IDE User Forum, and report bugs/requests/etc in JBossIDE JIRA under the "Webservices Plugin" component. Also, please come and talk to us att jbossworld in berlin, our spot is on wednesday; http://www.jbossworld.com/agenda_wednesday_schedule.htm#jbws regards, /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978095#3978095 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978095

17 years, 7 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 October 2006