Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: cvc-complex-type.2.4.c issue with RC1

  1. #1
    Join Date
    Apr 2009
    Posts
    6

    Default cvc-complex-type.2.4.c issue with RC1

    Hi there,

    I have just replaced the org.springframework.flex-1.0.0.M2.jar for org.springframework.flex-1.0.0.RC1.jar, and I'm getting that cvc-complex-type.2.4.c issue. Didn't change anything in my xml config file:

    Code:
    <beans xmlns="http://www.springframework.org/schema/beans"
    	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    	xmlns:flex="http://www.springframework.org/schema/flex"
    	xsi:schemaLocation="
     		http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
     		http://www.springframework.org/schema/flex http://www.springframework.org/schema/flex/spring-flex-1.0.xsd">
    I'm getting this error:

    Code:
    Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'flex:remote-service'.
    	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
    	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131)
    	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384)
    	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:1898)
    	at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.emptyElement(XMLSchemaValidator.java:705)
    	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:377)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2740)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:645)
    	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
    	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508)
    	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
    	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
    	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
    	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
    	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
    	at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
    	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
    	... 28 more
    I'm using Eclipse Europa, with WTP plugin for J2EE. I'm sensing that, for some reason, the application isn't finding the jar file in the classpath. I don't understand why the other jar file works ok.

    Any thoughts?

  2. #2
    Join Date
    Apr 2006
    Posts
    7

    Default

    You are probably still using the xsd locally in eclipse from the m2 version.

    Remove that xsd from eclipse and use the xsd online (it is now online)..

    That should help fix the problem, because the remoting-service is renamed to flex:remoting-destination.

    gr
    marcel

  3. #3
    Join Date
    Apr 2009
    Posts
    6

    Default

    Thanks, that's right.

    Good to know that it has changed

  4. #4

    Default

    I get this same error when I am not connected to the internet. How can I fix it when I am offline?

    Code:
    Multiple annotations found at this line:
    	- Unable to locate Spring NamespaceHandler for element 'flex:remoting-destination' of schema namespace 'http://www.springframework.org/schema/flex'
    	- cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'flex:remoting-destination'.
    	- schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/flex/spring-flex-1.0.xsd', because 1) could not find the document; 2) the document could not be 
    	 read; 3) the root element of the document is not <xsd:schema>.

  5. #5
    Join Date
    Apr 2005
    Location
    San Francisco, CA
    Posts
    1,224

    Default

    I assume this is just something you're seeing in STS rather than an error at runtime? STS does not yet bundle the Spring BlazeDS XSD, so you will get this warning when offline, but it should not prevent the application from running.

    Please do vote on this STS issue if you'd like to see it given increased priority by the team.
    https://issuetracker.springsource.com/browse/STS-173

    Note that you can manually configure a local copy of the XSD in your Eclipse XML Catalog and it will get rid of the warning.
    Jeremy Grelle

    Staff Engineer, Web Products Team
    SpringSource

  6. #6

    Default

    Thanks, I just voted on it.

    It does compile and run with the errors or even the warnings, they are just annoying. I did try pointing to the schema but it didn't fix anything. So I am just ignoring them for now.

    Thanks again,
    Joshua

  7. #7
    Join Date
    Jul 2008
    Posts
    11

    Default

    Quote Originally Posted by marcelpanse View Post
    Remove that xsd from eclipse and use the xsd online (it is now online)..
    Hi,
    I'm having the same issue,
    what do you mean by "Remove that xsd from eclipse" ?
    where is it exactly ?

    thanks
    D

  8. #8

    Default same issue

    I also have the same issue. I don't know how can I removed xsd from local and point the online version. Can some one please let me know.

    Thanks

  9. #9
    Join Date
    Apr 2005
    Location
    San Francisco, CA
    Posts
    1,224

    Default

    When you say you're having the same issue, do you mean this one (http://forum.springsource.org/showpo...43&postcount=1) or this one (http://forum.springsource.org/showpo...43&postcount=4), because they are two different things. If you're referring to the latter, meaning just the error in Eclipse rather than a runtime error on application startup, I would suggest using the latest STS 2.3 which has built-in support for the flex schema.
    Jeremy Grelle

    Staff Engineer, Web Products Team
    SpringSource

  10. #10
    Join Date
    Jan 2010
    Posts
    9

    Default

    Quote Originally Posted by dekely View Post
    Hi,
    I'm having the same issue,
    what do you mean by "Remove that xsd from eclipse" ?
    where is it exactly ?

    thanks
    D
    How do you resolve the above?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •