Ok, it's not tomcat-related problem - it's eclipse related problem. I used to run project just from eclipse and it was not working. Deploying war on the external server works like a charm. best regards Aleksander
2011/5/20 [email protected] <[email protected]> > Ok, I checked it - thats true, on jetty it's working properly. > So lets me change the question: do You have any idea, why it's not working > on tomcat 6.0.29? > best regards > Aleksander > > > 2011/5/20 Daniel Kulp <[email protected]> > >> On Friday, May 20, 2011 2:57:21 AM [email protected] wrote: >> > In the second wsdl there is only very little part of schema: >> > >> > <xsd:schema attributeFormDefault="unqualified" >> > elementFormDefault="qualified" targetNamespace="http://a/xml";> >> > <xsd:element name="ARequest" nillable="true"/> >> > <xsd:element name="getTopologyResponse" nillable="true"/> >> > </xsd:schema> >> > >> > But I need whole schema to be included in service description (that was >> > XFire behaviour). Am I doing something wrong? >> > Best regards >> > Aleksander >> >> In your project, if I run "mvn jetty:run" and then use a browser to view >> >> http://localhost:8080/a/AWs?wsdl=A.wsdl >> >> I get the entire schema: >> >> ............................ >> <xsd:element name="request" type="ARequest"/> >> <xsd:element name="response" type="AResponse"/> >> >> <xsd:complexType name="ARequest"> >> <xsd:sequence> >> <xsd:element maxOccurs="1" minOccurs="0" name="partitionName" >> type="xsd:string"/> >> <xsd:element maxOccurs="1" minOccurs="0" >> name="pruningConditions" >> type="PruningConditions"/> >> </xsd:sequence> >> </xsd:complexType> >> >> <xsd:complexType name="AResponse"> >> <xsd:sequence> >> <xsd:element minOccurs="0" name="topology1" >> type="t1:Topology"/> >> <xsd:element minOccurs="0" name="topology2" >> type="t2:Topology"/> >> <xsd:element minOccurs="0" name="topology3" >> type="t3:Topology"/> >> <xsd:element name="status" type="Status"/> >> </xsd:sequence> >> </xsd:complexType> >> >> .................. >> >> >> Dan >> >> >> >> > 2011/5/20 Daniel Kulp <[email protected]> >> > >> > > On Friday, May 13, 2011 6:23:07 AM [email protected] wrote: >> > > > Hi, >> > > > Sorry for long gap between mails, but I was on holiday. >> > > > In the attachment you have sample created by me. >> > > > Obviously the real schema is much more complicated, but faces the >> same >> > > > problem: there is neither schema, nor link to schema in wsdl. I >> XFire >> > > > implementation, all schema files were published on the server. >> > > > I know, that this sample may contain some errors and >> misunderstandings >> > > > of CXF philosophy, because its my very beginning in apache CXF. >> > > > Thanks for your help >> > > >> > > The schemas are actually in the wsdl, just in the secondary wsdl that >> the >> > > first wsdl imports. This is due to you not having the >> targetnamespace >> > > attribute on all the @WebService annotations. You need to put it on >> > > both the >> > > interface and the impl and make sure they match. This is per JAX-WS >> > > spec. >> > > >> > > Dan >> > > >> > > > Regards >> > > > Aleksander >> > > > >> > > > 2011/4/29 Daniel Kulp <[email protected]> >> > > > >> > > > > On Friday, April 29, 2011 9:20:14 AM [email protected]: >> > > > > > Hi there, >> > > > > > I'm porting application from XFire to CXF (xmlbeans databinding) >> > > > > > and >> > > >> > > I >> > > >> > > > > see, >> > > > > >> > > > > > that cxf, opposite to xfire, does not includes schemas in wsdl. >> Is >> > > > > > there any way to achieve xsd schema via webservice? Currently i >> get >> > > > > > only namespace. XFire gives me wsdl with port description and >> also >> > > > > > full schma of arguments and response. >> > > > > > Thanks in advance >> > > > > >> > > > > It should provide the full schema and we have a testcase that >> shows >> > > > > it working. Is there anyway you could create a small testcase? >> > > > > >> > > > > >> > > > > -- >> > > > > Daniel Kulp >> > > > > [email protected] >> > > > > http://dankulp.com/blog >> > > > > Talend - http://www.talend.com >> > > >> > > -- >> > > Daniel Kulp >> > > [email protected] >> > > http://dankulp.com/blog >> > > Talend - http://www.talend.com >> >> -- >> Daniel Kulp >> [email protected] >> http://dankulp.com/blog >> Talend - http://www.talend.com >> > >
