November 2006 - jbossws-users - Jboss List Archives

[JBossWS] - Using Axis SAAJ Implementation instead of JBossWS

by reinerka

Hi, is there a way to use the Apache AXIS SAAJ implementation on an application level (not as full replacement for JBossWS). We're having so many problems with the JBossWS SAAJ implementation that it renders our application useless. Since we know that the Apache AXIS SAAJ implementation works flawlessly for what we need we would rather switch to that. Any help/pointers? Thanks, Reiner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987425#3987425 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987425

18 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Cannot find ServiceFactory implementation

by fcheng

You need include jbossws-client.jar when you run your remote client. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987421#3987421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987421

18 years, 1 month

1
0
0 / 0

[JBossWS] - Issue with JASS on JBossWS (1.0.3 & 1.0.4)

by reinerka

Hi, I'm receiving a Premature end of File exception with the following Input XML on createMessage (on MessageFactory). I've tried this on JBoss 4.0.5.GA release and again after upgrading to JBossWS-1.0.4.GA. I broke it into seperate lines for easier reading. <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:cwmp="urn:dslforum-org:cwmp-1-0" xmlns="urn:dslforum-org:cwmp-1-0"> | <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" id="_0"> | <cwmp:Inform> | <DeviceId xsi:type="cwmp:DeviceIdStruct"> | <Manufacturer xsi:type="xsd:string">Somebody</Manufacturer> | <OUI xsi:type="xsd:string">9999</OUI> | <ProductClass xsi:type="xsd:string">Somebody</ProductClass> | <SerialNumber xsi:type="xsd:string">1234567890</SerialNumber> | </DeviceId> | <Event xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="cwmp:EventStruct[2]"> | <EventStruct xsi:type="cwmp:EventStruct"> | <EventCode xsi:type="xsd:string">1 BOOT</EventCode> | <CommandKey xsi:type="xsd:string"></CommandKey> | </EventStruct> | <EventStruct xsi:type="cwmp:EventStruct"> | <EventCode xsi:type="xsd:string">4 VALUE CHANGE</EventCode> | <CommandKey xsi:type="xsd:string"></CommandKey> | </EventStruct> | </Event> | <MaxEnvelopes xsi:type="xsd:unsignedInt">1</MaxEnvelopes> | <CurrentTime xsi:type="xsd:dateTime">0000-00-00T00:04:49</CurrentTime> | <RetryCount xsi:type="xsd:unsignedInt">1</RetryCount> | <ParameterList xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="cwmp:ParameterValueStruct[7]"> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.SpecVersion</Name> | <Value xsi:type="xsd:string">1.0</Value> | </ParameterValueStruct> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.HardwareVersion</Name> | <Value xsi:type="xsd:string">1.0002.0</Value> | </ParameterValueStruct> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.SoftwareVersion</Name> | <Value xsi:type="xsd:string">1.01.38</Value> | </ParameterValueStruct><ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.ProvisioningCode</Name> | <Value xsi:type="xsd:string"></Value> | </ParameterValueStruct> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.ManagementServer.ConnectionRequestURL</Name> | <Value xsi:type="xsd:string">http://123.123.123.123:12345/</Value> | </ParameterValueStruct> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.ManagementServer.ParameterKey</Name> | <Value xsi:type="xsd:string">parameterkey</Value> | </ParameterValueStruct> | <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> | <Name xsi:type="xsd:string">InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANPPPConnection.1.ExternalIPAddress</Name> | <Value xsi:type="xsd:string">192.168.0.101</Value> | </ParameterValueStruct> | </ParameterList> | </cwmp:Inform> | </SOAP-ENV:Body> | </SOAP-ENV:Envelope> | | What could cause this issue. It used to work fine using the Apache AXIS implementation. But right it seems that JBossWS is causing a big amount of problems for this application. | | Thanks, | Reiner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987420#3987420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987420

18 years, 1 month

1
0
0 / 0

[JBossWS] - Re: jbossws 1.0.4GA - wstools fail on a webervice

by klease

It looks like this is the same error reported earlier (http://jira.jboss.org/jira/browse/JBWS-1260), but that was only occurring on wsdl-java when the unwrap=true attribute was used. It appears from the new stack trace that wsdl-java is using unwrap even when it is NOT specified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987415#3987415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987415

18 years, 1 month

1
0
0 / 0

[JBossWS] - Exception with JBoss-4.0.5-SP1 and JBossWS-1.0.3-SP1 but not

by lafr

Running the identical code on the current checkout of Branch_4_0 gives me an exception not seen with our current production version JBoss-4.0.4-GA. 2006-11-20 21:46:32,954 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/mbi-ws/mbi2e-lafr-sb2000-ipc/core].[MessageServiceWS]] Servlet.service() for servlet MessageServiceWS threw exception | java.lang.ExceptionInInitializerError | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:164) | at org.jboss.ws.soap.attachment.ContentHandlerRegistry.<clinit>(ContentHandlerRegistry.java:51) | at org.jboss.ws.xop.XOPUnmarshallerImpl.<clinit>(XOPUnmarshallerImpl.java:59) | at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:60) | at org.jboss.ws.jaxrpc.encoding.JAXBDeserializer.deserialize(JAXBDeserializer.java:92) | at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:235) | at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233) | at org.jboss.ws.binding.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:103) | at org.jboss.ws.binding.EndpointInvocation.getRequestPayload(EndpointInvocation.java:117) | at org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvokerJSE.java:94) | at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:115) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.IllegalArgumentException: failed to parse:image/bmp, image/x-bmp, image/x-windows-bmp | at java.awt.datatransfer.DataFlavor.<init>(DataFlavor.java:292) | at javax.activation.ActivationDataFlavor.<init>(ActivationDataFlavor.java:81) | at org.jboss.ws.soap.attachment.ImageDataContentHandler.buildFlavors(ImageDataContentHandler.java:77) | at org.jboss.ws.soap.attachment.ImageDataContentHandler.<clinit>(ImageDataContentHandler.java:63) | But we don't use any attachments. What's wrong here or what did change here? How to avoid this error? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987414#3987414 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987414

18 years, 1 month

1
0
0 / 0

[JBossWS] - Glassfish vs. JBossWS - no JAXWS support in JBossWS?

by swamini2

I have been working with Glassfish and JBossWS and found that Glassfish is better in a few areas. One of them is supporting latest JAXWS out-of-box. Their WSDL compile tool generates JAXWS specific artifacts and also supports backward compatibility with JAXRPC. JBossWS 1.0.x seems to support only JAXPRC. Which version of JBossWS supports JAXWS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987397#3987397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987397

18 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Cannot find ServiceFactory implementation

by stewchicken

Hello Thanks for your pointer to link I guess it is answear for my question 2) Could you give me some hints for Question 1) ? Thanks and Rgds View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987396#3987396 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987396

18 years, 1 month

1
0
0 / 0

[JBossWS] - WSTOOLS: WSException: String passed is null on jbossws 1.0.4

by bocio

Same error on the WSDL below. WSDL is generated by Axis 1.2.1 Given that soap encoding is not supported we tried with document/literal and wrapped but always with the same results... The problem lies in a simple string[] description Our WSDL: anonymous wrote : <?xml version="1.0" encoding="UTF-8" ?> | - <wsdl:definitions targetNamespace="http://127.0.0.1/services/BaseWebAdapterWS" | | xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://127.0.0.1/services/BaseWebAdapterWS" xmlns:intf="http://127.0.0.1/services/BaseWebAdapterWS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> | -  | - <wsdl:types> | - | - | - | - | | | | | | </wsdl:types> | <wsdl:message name="getProcessorInstancesRequest" /> | - <wsdl:message name="getProcessorInstancesResponse"> | <wsdl:part element="impl:getProcessorInstancesReturn" name="getProcessorInstancesReturn" /> | </wsdl:message> | - <wsdl:portType name="BaseWebAdapter"> | - <wsdl:operation name="getProcessorInstances"> | <wsdl:input message="impl:getProcessorInstancesRequest" name="getProcessorInstancesRequest" /> | <wsdl:output message="impl:getProcessorInstancesResponse" name="getProcessorInstancesResponse" /> | </wsdl:operation> | </wsdl:portType> | - <wsdl:binding name="BaseWebAdapterWSSoapBinding" type="impl:BaseWebAdapter"> | <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /> | - <wsdl:operation name="getProcessorInstances"> | <wsdlsoap:operation soapAction="" /> | - <wsdl:input name="getProcessorInstancesRequest"> | <wsdlsoap:body use="literal" /> | </wsdl:input> | - <wsdl:output name="getProcessorInstancesResponse"> | <wsdlsoap:body use="literal" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | - <wsdl:service name="BaseWebAdapterService"> | - <wsdl:port binding="impl:BaseWebAdapterWSSoapBinding" name="BaseWebAdapterWS"> | <wsdlsoap:address location="http://127.0.0.1/services/BaseWebAdapterWS" /> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987393#3987393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987393

18 years, 1 month

1
0
0 / 0

[JBossWS] - wstools bug?

by biroj

Hi, I'm using JBoss AS 4.0.4 GA with the bundled JBossWS and the corresponding wstools. I tried to compile a valid WSDL file (see below) but it failed with the following exception: | Exception in thread "main" java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName | at javax.xml.namespace.QName.<init>(Unknown Source) | at javax.xml.namespace.QName.<init>(Unknown Source) | at org.jboss.ws.tools.XSDTypeToJava.handleAttributes(XSDTypeToJava.java:418) | at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:198) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:153) | at org.jboss.ws.tools.XSDTypeToJava.createVARforXSElementDeclaration(XSDTypeToJava.java:632) | at org.jboss.ws.tools.XSDTypeToJava.createVARsForElements(XSDTypeToJava.java:519) | at org.jboss.ws.tools.XSDTypeToJava.createVARsforXSParticle(XSDTypeToJava.java:446) | at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:248) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:153) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113) | at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:497) | at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:377) | at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:220) | at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:333) | at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:355) | at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:174) | at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:326) | at org.jboss.ws.tools.WSTools.process(WSTools.java:132) | at org.jboss.ws.tools.WSTools.generate(WSTools.java:119) | at org.jboss.ws.tools.WSTools.main(WSTools.java:61) | WSDL | ?xml version="1.0" encoding="UTF-8"?> |  | <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://siemens.com/ws/request" xmlns:tns="http://siemens.com/ws/request/beans" targetNamespace="http://siemens.com/ws/request" name="EMServices"> | <wsdl:types> | <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:tns="http://siemens.com/ws/request/beans" targetNamespace="http://siemens.com/ws/request/beans"> |  | <xs:include schemaLocation="get-em-info-response.xsd"/> | <xs:include schemaLocation="get-em-info.xsd"/> |  |  | <xs:element name="getEMInfo" type="tns:GetEMInfoType"> | <xs:annotation> | <xs:documentation>Get EM info.</xs:documentation> | </xs:annotation> | </xs:element> | <xs:element name="getEMInfoResponse" type="tns:GetEMInfoResponseType"> | <xs:annotation> | <xs:documentation>Get EM info response.</xs:documentation> | </xs:annotation> | </xs:element> | </xs:schema> | </wsdl:types> | <wsdl:message name="getEMInfoIn"> | <wsdl:part name="getEMInfo" element="tns:getEMInfo"/> | </wsdl:message> | <wsdl:message name="getEMInfoOut"> | <wsdl:part name="getEMInfoResponse" element="tns:getEMInfoResponse"/> | </wsdl:message> | <wsdl:portType name="EMServices"> | <wsdl:operation name="getEMInfo"> | <wsdl:input message="ns:getEMInfoIn"/> | <wsdl:output message="ns:getEMInfoOut"/> | </wsdl:operation> | </wsdl:portType> | <wsdl:binding name="EMServicesSOAP" type="ns:EMServices"> | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> | <wsdl:operation name="getEMInfo"> | <wsdl:input> | <soap:body use="literal"/> | </wsdl:input> | <wsdl:output> | <soap:body use="literal"/> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <wsdl:service name="EMServices"> | <wsdl:port name="EMServicesSOAP" binding="ns:EMServicesSOAP"> | <soap:address location="http://localhost:8080/axis2-1.1-SNAPSHOT/services/EMServices"/> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | I can also include the XSDs if it is neccessary. The wstools config file was the simpliest one: | <wsdl-java file="EMServices.wsdl"> | <mapping file="jaxrpc-mapping.xml" /> | </wsdl-java> | Could you help me? Thanks a lot, Bye, Janos View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987388#3987388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987388

18 years, 1 month

1
0
0 / 0

[JBossWS] - Re: jbossws 1.0.4GA - wstools fail on a webervice

by croisfert

same error at Wolfram Research: http://webservices.wolfram.com/services/SearchServices/WolframSearch2.wsdl and (new) other error: Exception in thread "main" org.jboss.ws.metadata.wsdl.WSDLException: WSDLException (at /definitions/binding/operation[1]/input): faultCode=INVALID_WSDL: Element '{http://schemas.xmlsoap.org/wsdl/}input' contained unexpected attributes: 'message': here: http://www.ebob42.com/cgi-bin/Romulan.exe/wsdl/IRoman View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987382#3987382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987382

18 years, 1 month

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 November 2006