Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 99573 invoked from network); 13 May 2005 16:27:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 May 2005 16:27:19 -0000 Received: (qmail 47786 invoked by uid 500); 13 May 2005 16:31:16 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 47767 invoked by uid 500); 13 May 2005 16:31:15 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 47746 invoked by uid 99); 13 May 2005 16:31:15 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of balar@cisco.com designates 171.71.176.72 as permitted sender) Received: from sj-iport-3-in.cisco.com (HELO sj-iport-3.cisco.com) (171.71.176.72) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 13 May 2005 09:31:14 -0700 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 13 May 2005 09:25:53 -0700 X-IronPort-AV: i="3.93,107,1115017200"; d="scan'208"; a="264898422:sNHT446478190" Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j4DGPHQA002606; Fri, 13 May 2005 09:25:51 -0700 (PDT) Received: from xmb-sjc-218.amer.cisco.com ([171.70.151.151]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 13 May 2005 09:25:35 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: SAXException - Invalid element error Date: Fri, 13 May 2005 09:25:34 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SAXException - Invalid element error Thread-Index: AcVXxjeaOxG6uRNWRVi8qiAw+fTnEgAEWj5A From: "Bala Ramakrishnan \(balar\)" To: , "Anne Thomas Manes" X-OriginalArrivalTime: 13 May 2005 16:25:35.0459 (UTC) FILETIME=[64247330:01C557D8] X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Unfortunately, I did not run with debug mode or have any monitor, so I do not have the complete SOAP xml packet. This problem has come a few times, and I have not been able to reliably reproduce it. I suspect that depending upon data, this happens. However here is the wsdl, and the piece of Java code that is giving this error. The java code is trying to retrieve an array of DeviceDetail objects, and gets the exception below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D code that is encountering the = exception =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D com.cisco.nm.wlse.xmlapi.inventory.gencode.Device[] wlseAPDevs = =3D null; try { String[] apDeviceTypes =3D APDeviceTypeInfo.getSupportedDeviceTypes(); String[] deviceStates =3D new String[] {"m"}; wlseAPDevs =3D invHandle.getDevicesEx(apDeviceTypes, deviceStates, 0); } catch (java.rmi.RemoteException re) { String errorStr =3D "WLSE " + wd.getAddressableIp() + " is = not responding for getDevicesEx()"; _Mlogger.error(errorStr); throw new WlsessException(WLSE_NOT_RESPONDING, errorStr); } if (wlseAPDevs =3D=3D null || wlseAPDevs.length =3D=3D 0) { _Mlogger.warn("no AP information in the WLSE with IP: " + wd.getAddressableIp()); return; } // get AP details. DeviceDetail[] apDetails =3D null; com.cisco.nm.wlse.xmlapi.DeviceId[] apIDs =3D new com.cisco.nm.wlse.xmlapi.DeviceId[wlseAPDevs.length]; for (int j =3D 0; j < wlseAPDevs.length; j++) { apIDs[j] =3D wlseAPDevs[j].getId(); } try { // get all devices in one shot - // if slow, may have to put this in a loop. apDetails =3D invHandle.getDeviceDetail(apIDs); } catch (java.rmi.RemoteException re) { <---------- here is the exception that is being caught and logged ------------> _Mlogger.error("WLSE " + wd.getAddressableIp() + " is not responding for getDeviceDetail()"); throw new WlsessException(WLSE_NOT_RESPONDING, "No Response from WLSE for Inventory.getDeviceDetail()"); } = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The generated wsdl (inventory.wsdl): =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Thanks for any help. -----Original Message----- From: Anne Thomas Manes [mailto:atmanes@gmail.com]=20 Sent: Friday, May 13, 2005 7:15 AM To: axis-user@ws.apache.org Subject: Re: SAXException - Invalid element error Could you send us your WSDL and SOAP messages? On 5/12/05, Bala Ramakrishnan (balar) wrote: > =20 > This topic seems to have been discussed before, but I could not get a=20 > clear picture. > =20 > I am getting the error below:=20 >=20 > org.xml.sax.SAXException: Invalid element in=20 > com.cisco.nm.wlse.xmlapi.inventory.gencode.DeviceDetail - deviceType > 2005-04-28 10:33:19,828 [_WlseProcessors:Pooled Thread:2] ERROR > com.cisco.nm.mom.util.WlseXmlApiHelper.invoke() - AxisFault > faultCode: > {http://xml.apache.org/axis/}Server.userException > faultString: org.xml.sax.SAXException: Invalid element in=20 > com.cisco.nm.wlse.xmlapi.inventory.gencode.DeviceDetail - deviceType > faultActor: null > faultDetail:=20 > stackTrace: org.xml.sax.SAXException: Invalid element in=20 > com.cisco.nm.wlse.xmlapi.inventory.gencode.DeviceDetail - deviceType =20 > at > org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeseria > lizer.java:252) > at > org.apache.axis.encoding.DeserializationContextImpl.startElement(Deser > ializationContextImpl.java:893) > at > org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.jav > a:200) > at > org.apache.axis.message.MessageElement.publishToHandler(MessageElement > .java:684) > at > org.apache.axis.message.RPCElement.deserialize(RPCElement.java:241) > at > org.apache.axis.message.RPCElement.getParams(RPCElement.java:265) > at org.apache.axis.client.Call.invoke(Call.java:1871) > at org.apache.axis.client.Call.invoke(Call.java:1777) > at org.apache.axis.client.Call.invoke(Call.java:1315) > at > com.cisco.nm.wlse.xmlapi.inventory.gencode.InventorySoapBindingStub.ge > tDeviceDetail(InventorySoapBindingStub.java:471) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > ava:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess > orImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) > at > com.cisco.nm.mom.util.WlseXmlApiHelper.invoke(WlseXmlApiHelper.java:15 > 2) at $Proxy3.getDeviceDetail(Unknown Source) at > com.cisco.nm.mom.wlsess.AccessPoints.updateAPInfo(AccessPoints.java:80 > ) > at > com.cisco.nm.mom.wlsess.WlseDevice.updateWlseInfo(WlseDevice.java:591) > at > com.cisco.nm.mom.wlsess.WlseDevice.updateWlse(WlseDevice.java:443) > at > com.cisco.nm.mom.wlsess.RedundancyProcessor.processDcrAddModPingEvent( > RedundancyProcessor.java:187) > at > com.cisco.nm.mom.wlsess.WlseDCREventProcessor.processUpdateEvent(WlseD > CREventProcessor.java:219) > at > com.cisco.nm.mom.wlsess.WlseDCREventProcessor.run(WlseDCREventProcesso > r.java:123) > at > com.cisco.nm.mom.util.ThreadPool$1.run(ThreadPool.java:89) > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > The class > com.cisco.nm.wlse.xmlapi.inventory.gencode.DeviceDetail is included=20 > below: > =20 > /** > * DeviceDetail.java > * > * This file was auto-generated from WSDL > * by the Apache Axis WSDL2Java emitter. > */ > =20 > package com.cisco.nm.wlse.xmlapi.inventory.gencode; > =20 > public class DeviceDetail implements java.io.Serializable { > private com.cisco.nm.wlse.xmlapi.DeviceId id; > private java.lang.String ipAddress; > private java.lang.String hostname; > private java.lang.String product; > private java.lang.String version; > private java.lang.String deviceType; > private long timeLastDiscovered; > private java.lang.String sysObjectID; > private java.lang.String sysName; > private java.lang.String sysLocation; > private java.lang.String subnet; > private java.lang.String dnsName; > private java.lang.String userDefinedDescr; > private java.lang.String[] SSIDs; > private int[] vlanIDs; > private java.lang.String[] macAddresses; > private java.lang.String[] radioMacAddresses; > private java.lang.String serialNumber; > private int wdsMode; > =20 > } > =20 > =3D=3D=3D=3D=3D > I have seen discussions pertaining to such problems if there are array > or complex types in the class. This code was generated by wsdl2java=20 > utility and the wsdl itself was generated from java2wsdl. > =20 > Axis 1.0 is the version being used. Is this problem fixed in the=20 > latest release Axis 1.2? if not, am I doing something wrong? > =20 > All answers and help are very much appreciated.=20 > Thanks for your time.=20 >=20 >