August 2008 - jbossws-users - Jboss List Archives

by kosulin

Why there is no source distribution for latest releases available? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171313#4171313 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171313

17 years, 1 month

1
0
0 / 0

[JBossWS] - SimpleDeserializer error on returning complex type

by jaki

Hi, I have exposed a stateless ejb3 bean as a WS and it has a method returning a complex type. Signature: @WebMethod | public MapBean getMap(String test) The class MapBean just has 2 string members along with their getters/setters. I'm using an axis WS client for it (using the Call interface) but invoking the Web service gives me the below error: Caused by: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. | at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145) | at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) | at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) | at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) | at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) | at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) | at org.apache.axis.client.Call.invoke(Call.java:2448) | ... 3 more What's wierd is, it works without the error if I change the binding from document/wrapped to document/BARE but in that case the input arguements take the form '<arg0 xsi:type='xsd:string' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>nabble</arg0>' even inside the webmethod! Kindly help me here. WSDL for response: xs:complexType name="getMapResponse"> | <xs:sequence> | <xs:element minOccurs="0" name="return" type="tns:mapBean"/> | </xs:sequence> | </xs:complexType> | <xs:complexType name="mapBean"> | <xs:sequence> | <xs:element minOccurs="0" name="key" type="xs:string"/> | <xs:element minOccurs="0" name="value" type="xs:string"/> | </xs:sequence> | </xs:complexType> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171275#4171275 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171275

17 years, 1 month

1
0
0 / 0

[JBossWS] - JBossWS throws exception when receiving unbound soap header

by Dennisk

Hello, I hope some one can help me with this problem, it's causing me headaches: I use Jax-ws in my webservice client project deployed on JBoss4.2.2GA (with JBossWs patch) to communicate with a party through soap. When I receive a reply to my request I get the following exception: 2008-08-19 10:37:42,020 ERROR [org.jboss.ws.core.soap.SOAPMessageUnMarshaller] Cannot unmarshall SOAPMessage | javax.xml.soap.SOAPException: Invalid SOAPHeaderElement name: api-version | at org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement(SOAPHeaderImpl.java:64) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.buildSOAPHeader(EnvelopeBuilderDOM.java:174) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:138) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:262) | at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:84) | at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:473) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:305) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183) | at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | at $Proxy389.getDatabases(Unknown Source) | at com.myorganize.services.mail.MailServiceBean.getDatabaseId(MailServiceBean.java:180) | | It looks like the parsing of the unbound soap header element (api-version) causes an exception (I do not need this info anyway). Strangely enough in Eclipse I used the jaxws-rt implementation for testing these calls and there it worked perfectly and caused no exceptions. I looked at the jboss code (org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement) that trows the exception and it seems to throw it when the namespace or prefix is null, but I do not exactly know how or why these could be null. Can anybody give me some info on what the exact problem could be and maybe what the best solution is? Or is there a setting or configuration item that can direct jboss to ignore soap header elements. I already tried to use the jaxws-rt implementation in JBoss (4.2.2.GA) but I could not get a working set because the jbossws core seems to be tightly coupled with the jboss application server, and I keep getting compatibility and classloading issues with implementation classes of jbossws/saaj and jaxws-rt. ps. I cannot change the wsdl and define the header elements because the other party will not change the wsdl. pss. I hope to avoid having to write a raw soap msg handler to remove the element since it is a lot of work and I think it should not be necessary. The return message with the api-version soap header element that causes the problem: | <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> | <soap:Header> | <api-version>1.82</api-version> | </soap:Header> | <soap:Body> | <ns1:getDatabasesResponse xmlns:ns1="http://tservice.services.xxxxxxxx.com/"> | <databaseInfos> | <id>yDK</id> | <name>_Expeditie</name> | <subscriberFields>email</subscriberFields> | ............deleted contents of message.................. | <subscriberFields>naam</subscriberFields> | </databaseInfos> | </ns1:getDatabasesResponse> | </soap:Body> | </soap:Envelope> | Thanks in advance for looking at this problem...regards, Dennis View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171205#4171205 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171205

17 years, 1 month

1
0
0 / 0

[JBossWS] - [UsingAddressing] tag is not added to auto-generated WSDL fo

by karypid

Hi, I used the @EndpointConfig annotation to add WS-Addressing handlers to my SEI implementation as described in the WS-Addressing tutorial. I noticed however that even though JBoss adds the WS-Addressing handlers to the the endpoint, it does not specify it in the WSDL that gets published for the web service. In fact, the WSDL generated and published is identical whether you enable WS-Addressing or not. The WS-Addressing tutorial at http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-Addressing_Tut... uses a "manual" approach to make this information available in the contract: It uses the "wsdlLocation" attribute of the @WebService annotation to refer to a pre-constructed WSDL that has an appropriate service definition: <service name='AddressingService'> | <port binding='tns:ServiceIfaceBinding' name='AddressingServicePort'> | <soap:address location='REPLACE_WITH_ACTUAL_URL'/> |  |  |  | <UsingAddressing xmlns="http://www.w3.org/2006/05/addressing/wsdl"/> | </port> | </service> I would expect JBoss to add the UsingAddressing tag to the generated WSDL contract to "warn" clients that it is required. Is this only possible when using pre-constructed WSDL? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171199#4171199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171199

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: WebServiceException: Unable to load Provider

by gsekar

https://jira.jboss.org/jira/browse/JBPAPP-941 This fixed the same issue I was having. I didnt have to remove or copy any jars View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171156#4171156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171156

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: JBossWS Benefits

by karypid

I suppose "choice" is one advantage. Lots of "non-standardized" web services functionality (for example, WS-ReliableMessaging or WS-Eventing) is accessed via a different API for each of the various stacks (CXF, Metro, etc). Rather than coding to a specific Web Services stack, you can use the JBossWS "wrapper APIs". Then you have the option of switching your web services stack among the supported options (Metro, CXF, Native) without having to change your code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171139#4171139 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171139

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Web Service URL pattern

by skajotde

You can apply annotation @RolesAllowed, eg.: holder for auth roles constant: public class Roles { | private static final XXX = "033"; | | } and in Webservice: @WebMethod | @RolesAllowed(Roles.XXX) | public void youMethod(.... This annotation is same as in EJB and use JAAS to configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170943#4170943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170943

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: mtom on the server

by lfoggy

I am concerned if a client can not process mtom encoded attachments, so I like to make mtom optional on the server. (this is an in-house application, so customers will have control over the server) So when server is not mtom-enabled, attachment is send inline. The javadoc for BindingType annotation states that the annotation may be overriden programmatically. I was thinking maybe I can use that to read mtom configuration from a properties file, but I am not sure how do that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170939#4170939 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170939

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: Error SAP WS-Security client calling JBoss Security WS

by enpasos

Requiring "ValueType to be set" breaks the wsse standard 1.0 and 1.1!!! (tested in jbossws-3.0.1-native-204.GA) Please change. Thanks a lot. See ... http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu... page 22, lines 702 - 708 702 /wsse:SecurityTokenReference/wsse:Reference/@ValueType 703 This optional attribute specifies a URI that is used to identify the type of token being 704 referenced. This specification does not define any processing rules around the usage of 705 this attribute, however, specifications for individual token types MAY define specific 706 processing rules and semantics around the value of the URI and how it SHALL be 707 interpreted. If this attribute is not present, the URI MUST be processed as a normal URI. 708 The usage of ValueType is RECOMMENDED for references with local URIs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170841#4170841 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170841

17 years, 1 month

1
0
0 / 0

[JBossWS] - Re: mtom on the server

by kosulin

Do you mean, for some client you want to use SOAP with attachments, and for others - MTOM? I do not believe you can enable or do this dynamically, because it is part of the service endpoint contract definition. What we do, we have only one XML atttribute defined as @XmlMimeType("application/zip") and at the same time as @XmlElement(..., required=false). As a result, when this attribute is not null, it is sent using MTOM, and when it is null it is absent from response, and there is no MTOM encoding in this response. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170779#4170779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170779

17 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users August 2008