Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.6.0.RELEASE
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Seeing 2 errors, neither of which should be occuring.

      The first is STS marking an error Unrecognized xbean namespace mapping: http://activemq.apache.org/schema/core
      for the first occurance of <amq:broker .../>
      The schemas are correctly referenced, and grammar is being recognised, server starts fine so the config is valid.

      The second, which I'm not sure if it is related, is seeing cvc-complex-type.2.4.a: Invalid content was found starting with element 'amq:networkConnectors'. One of '

      {WC[##other:"http://activemq.apache.org/schema/core"]}

      ' is expected.

      <amq:networkConnectors>
      <amq:networkConnector name="default" uri="multicast://default"/>
      </amq:networkConnectors>

      In various places, when using config from the activemq website.

        Activity

        Hide
        Brad Murray added a comment -

        Actually, ignore the second error, its caused by the new amq requirement that elements be declared in alphabetical order.

        Show
        Brad Murray added a comment - Actually, ignore the second error, its caused by the new amq requirement that elements be declared in alphabetical order.
        Hide
        Gordon Dickens added a comment -

        Manually configure the Schema via the Preferences > XML Catalog. http://www.martinahrer.at/2010/10/06/register-activemq-spring-namespace-with-eclipse-3-6/

        Show
        Gordon Dickens added a comment - Manually configure the Schema via the Preferences > XML Catalog. http://www.martinahrer.at/2010/10/06/register-activemq-spring-namespace-with-eclipse-3-6/
        Hide
        Daniel Serodio added a comment -

        Shouldn't the xsi:schemaLocation declaration take care of this namespace -> XSD mapping?

        Show
        Daniel Serodio added a comment - Shouldn't the xsi:schemaLocation declaration take care of this namespace -> XSD mapping?

          People

          • Assignee:
            Unassigned
            Reporter:
            Brad Murray
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: