can you display both the XSD and the WSDL?
thanks,
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Wed, 28 Oct 2009 17:26:52 -0400
Subject: Any workaround?
From: newax...@gmail.com
To: axis-user@ws.apache.org
Hi all,
I've gotten back to looking at upgrading to Axis2 after a long hiatus. Feel
free to tell me if I've done something stupid.
I tried running
sh $AXIS2_HOME/bin/wsdl2java.sh -uri wsdl/our_wsdl.wsdl -o gensrc -ss -sd
using first Axis2 1.4.1 and then 1.5.1. our_wsdl.wsdl is the file I
successfully used with Axis 1.4 the last time I worked with the services on our
project.
Both times, wsdl2java generated source files but one problem.
The generated code wouldn't compile Cadm.java:
if (reader.isStartElement())
{
object.setDOC_APP_CALDT(org.apache.axiom.om.OMElement.Factory.parse(reader));
reader.next();
} // End of if for expected property start element
and the problem is that OMElement.Factory doesn't exist.
The matching part in the wsdl looks like
<xsd:complexType name="cadmType">
<xsd:sequence>
<xsd:element ref="cadm:DOC_APP_CALDT" minOccurs="0"/>
<xsd:element ref="cadm:ARCH_ID" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
I can make the compilation problem disappear by commenting out DOC_APP_CALDT
which is defined as
<xsd:element name="DOC_APP_CALDT" type="ddms:CombinedDateType"/>
<simpleType name="CombinedDateType">
<union memberTypes="dateTime date gYearMonth gYear"/>
</simpleType>
So ... am I doing something obviously wrong? does this mean that I can't use
the default binding? Is there a workaround? Since it's only 1 file, I wouldn't
mind manually fixing the code if I knew what was supposed to go there.
Thanks for any help.
_________________________________________________________________
Windows 7: It works the way you want. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen2:102009
