You can't ignore validation errors.

If you can't provide this WSDL, you'll have to make one that comes up with
the same error, or I probably can't help you.

Included types should be fine.

Or, of course, you could join up and debug for yourself:-)

On Thu, Oct 8, 2009 at 7:59 PM, noosy <[email protected]>wrote:

>
> Hmmm, I'm unable to provide the WSDL but I can provide some more details if
> it helps. I have used this WSDL before to create JAW-WS Web Service client
> in Netbeans and that worked fine so I dont' think there is anything wrong
> with the WSDL so to speak.
>
> One thing I was wondering, the types that don't appear to be generated by
> wsdl2js are from a schema which is included by the WSDL.
>
> E.g.
>
> <xsd:include
> schemaLocation="http://myMachine:myPort/blah/myService?WSDL/myTypes.xsd";>
>
> Should this be OK? Do I need to do anything extra for the code generator to
> locate these types?
>
> The other thing, when I use the -validate option, I get the following
> output:
>
> cvc-complex-type.2.4.a: Invalid content was found starting with element
> 's3:part' One of '{part}' is expected.
>
> Does this cause the code generator to fall over or can it be ignored?
>
> I can still put up a JIRA if you think it is worthwhile (without a WSDL).
> Please let me know, I appreciate any assistance provided.
>
>
>
>
> bimargulies wrote:
> >
> > Please post a JIRA and attach the WSDL.
> >
> > On Thu, Oct 8, 2009 at 2:41 AM, noosy
> > <[email protected]>wrote:
> >
> >>
> >> I am trying to consume a web service (third party WS) from javascript. I
> >> supplied the URL for the Web Service wsdl to wsdl2js and out popped a
> .js
> >> file. When I go to use this .js file I get errors in Firebug
> >> "...myType_serialize is not defined".
> >>
> >> Looking inside the .js file I have noticed references to
> >> ...myType_serialize
> >> and ...myType_deserialize inside the service code constructor. Yet no
> >> where
> >> else are they mentioned let alone defined.
> >>
> >> E.g.
> >>
> >> function myServicePort()
> >> {
> >>     this.jsutils = new CxfApacheOrgUtil();
> >>     this.jsutils.interfaceObject = this;
> >>     this.synchronous = false;
> >>     this.url = null;
> >>     this.client = null;
> >>     this.response = null;
> >>     this.globalElementSerializers = [];
> >>     this.globalElementDeserializers = [];
> >>     this.globalElementSerializers['{...}myType'] = ...myType_serialize;
> >>     this.globalElementDeserializers['{...}myType'] =
> >> ...myType_deserialize;
> >>     ...
> >> }
> >>
> >> Does this indicate a problem generating the schema code/types from my
> >> WSDL?
> >>
> >> I hope someone can help! For more info just ask :)
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Please-help---wsdl2js---generated-schema-code-types-missing-from-output.js--tp25799168p25799168.html
> >> Sent from the cxf-user mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Please-help---wsdl2js---generated-schema-code-types-missing-from-output.js--tp25799168p25813623.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>

Reply via email to