What version of CXF? How configured?

On Thu, Mar 12, 2009 at 5:48 AM, Cecchi Sandrone
<[email protected]> wrote:
>
> Hi all,
> I have a very strange problem. I've been using CXF to expose my beans for
> months, also collections and arrays. Now I can't get this code to work and I
> don't know why:
>
> public class UserServiceException extends Exception {
>
>        private static final long serialVersionUID = 1L;
>
>        private String messageKey;
>
>        private String[] params;
>
>        public UserServiceException() {}
>
>        public UserServiceException(String message,String messageKey) {
>                super(message);
>                this.setMessageKey(messageKey);
>                this.setParams(null);
>        }
>
>        public UserServiceException(String message,String messageKey,String[]
> params) {
>                super(message);
>                this.setMessageKey(messageKey);
>                this.setParams(params);
>        }
>
>        public void setMessageKey(String messageKey) {
>                this.messageKey = messageKey;
>        }
>
>        public String getMessageKey() {
>                return messageKey;
>        }
>
>        public void setParams(String[] params) {
>                this.params = params;
>        }
>
>        public String[] getParams() {
>                return params;
>        }
>
> So I have this exception that has two field, a String and a String[], but
> the wsdl generated is:
>
> <xs:complexType name="UserServiceException">
> <xs:sequence>
> <xs:element name="messageKey" nillable="true" type="xs:string"/>
> </xs:sequence>
> </xs:complexType>
>
> It seems that the String[] is ignored and in fact the client object
> generated doesn't include this field. It's very strange because I have other
> complex object with arrays and collections fields that I use with success.
>
> Please give me an help,
> Thanks.
> --
> View this message in context: 
> http://www.nabble.com/CXF-not-exposing-arrays-collection-tp22471469p22471469.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>

Reply via email to