Resin 초기화 구성 파일

3304 단어
최근 새로운 프로젝트가 출시되었습니다. 프로젝트는resin 서버를 기반으로 합니다.
시스템이 시작 시간:
 
 org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 16 in XML document from class path resource [MET A-INF/services-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'amq:broker'.
 
그리고 때때로 시작에 성공하는 것이 이상하다. 마지막으로 공식 설명을 통해 프로필 수정 방식을 설명한다.
 
Typically in Apache ActiveMQ we create destinations on demand as clients start to use them. However sometimes users want to be able to configure which destinations are available on startup explicitly in the Xml Configuration.
4.1 FeatureNote this feature is available from 4.1 onwards. If you try this XML on older versions of ActiveMQ you will get an exception about the 'destinations' property not being writable.

Example


The following example shows how you can configure a number of destinations to be available at startup.
<beans
  xmlns="http://www.springframework.org/schema/beans"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
  http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">

  <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />

  <broker xmlns="http://activemq.apache.org/schema/core">
    <destinations>
      <queue physicalName="FOO.BAR" />
      <topic physicalName="SOME.TOPIC" />
    </destinations>

  </broker>

</beans>

이 방식을 통해 시스템이 정상적으로 작동할 수 있도록 했지만 왜 active Mq의 schema 파일만 읽을 수 없다고 생각합니까!!
앞으로 계속 지켜봐 주세요!

좋은 웹페이지 즐겨찾기