Mule jdbc connector xml 구문 분석

Question

Mule 프로젝트에 JDBC 끝점을 추가하는 데 문제가 있습니다. 일부 XML 구문 분석 문제로 인해 초기화하는 동안 문제가 있습니다. JDBC 엔드 포인트를 추가 한 후에 문제점이 시작되었습니다.

Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jdbc:inbound-endpoint'. One of '{ 
"http://www.mulesource.org/schema/mule/core/2.2":description, 
"http://www.springframework.org/schema/beans":beans, 
"http://www.springframework.org/schema/beans":bean, 
"http://www.springframework.org/schema/context":property-placeholder, 
"http://www.mulesource.org/schema/mule/core/2.2":global-property, 
"http://www.mulesource.org/schema/mule/core/2.2":configuration, 
"http://www.mulesource.org/schema/mule/core/2.2":notifications, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-extension, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-security-manager, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-transaction-manager, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-connector, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-global-endpoint, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-transformer, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-filter, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-model, 
"http://www.mulesource.org/schema/mule/core/2.2":abstract-interceptor-stack}' 
is expected. 

것은 내가

노새 JDBC 네임 스페이스 http://www.mulesoft.org/documentation/display/MULE2USER/JDBC+Transport#JDBCTransport-ConfigurationReference 내 XML 정의에 추가 된이 가이드에게 다음 왔습니다.

아이디어가 있으십니까?

확인 내 구성 파일의 조각 :

<mule 
xmlns="http://www.mulesource.org/schema/mule/core/2.2" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:jms="http://www.mulesource.org/schema/mule/jms/2.2" 
xmlns:xm="http://www.mulesource.org/schema/mule/xml/2.2" 
xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2" 
xmlns:jdbc="http://www.mulesource.org/schema/mule/jdbc/2.2" 
xmlns:file="http://www.mulesource.org/schema/mule/file/2.2" 
xsi:schemaLocation=" 
    http://www.mulesource.org/schema/mule/jdbc/2.2 http://www.mulesource.org/schema/mule/jdbc/2.2/mule-jdbc.xsd 
    http://www.mulesource.org/schema/mule/core/2.2 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd 
    http://www.mulesource.org/schema/mule/jms/2.2 http://www.mulesource.org/schema/mule/jms/2.2/mule-jms.xsd 
    http://www.mulesource.org/schema/mule/vm/2.2 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd 
    http://www.mulesource.org/schema/mule/file/2.2 http://www.mulesource.org/schema/mule/file/2.2/mule-file.xsd 
    http://www.mulesource.org/schema/mule/xml/2.2 http://www.mulesource.org/schema/mule/xml/2.2/mule-xml.xsd"> 

<!-- Endpoints --> 

<jdbc:inbound-endpoint 
    name="jdbcKapitalCommandIn" 
    connector-ref="jdbcConnector" 
    queryKey="queryKapitalProcessControl" 
    pollingFrequency="10000" synchronous="true"> 
</jdbc:inbound-endpoint> 

<jdbc:outbound-endpoint 
    name="jdbcKapitalCommandOut" 
    connector-ref="jdbcConnector" 
    queryKey="updateKapitalProcessControl" 
    synchronous="true"> 
</jdbc:outbound-endpoint> 

<file:endpoint 
    name="kapitalErrorBackup" 
    path="${APPS_HOME}/lbo-esb/files/kapital/error" 
    outputPattern="#[DATE:yyyy-MM-dd_HH-mm-ss]_error.txt"> 
</file:endpoint> 
<file:endpoint 
    name="kapitalInputBackup" 
    path="${APPS_HOME}/lbo-esb/files/kapital/backup" 
    outputPattern="#[DATE:yyyy-MM-dd_HH-mm-ss]_kapital-command.xml"> 
</file:endpoint> 
<file:endpoint 
    name="kapitalInvalidSchemaBackup" 
    path="${APPS_HOME}/lbo-esb/files/kapital/error" 
    outputPattern="#[DATE:yyyy-MM-dd_HH-mm-ss]_inv_schema.xml"> 
</file:endpoint> 

<!-- Kapital --> 
<vm:endpoint 
    name="kapitalTransactionInput" 
    path="kapital.transaction.input"> 
</vm:endpoint> 
<vm:endpoint 
    name="kapitalError" 
    path="kapital.error.input"> 
</vm:endpoint> 


<model 
    name="KapitalServices"> 

    <default-service-exception-strategy> 
     <outbound-endpoint 
      ref="kapitalError"> 
     </outbound-endpoint> 
    </default-service-exception-strategy> 
    <service 
     name="kapitalService"> 
     <inbound> 
      <inbound-endpoint 
       ref="jdbcKapitalCommandIn"> 
      </inbound-endpoint>    
     </inbound> 
     <echo-component /> 
    <!-- more stuff from here --> 
    </service> 
</model> 

<!-- more stuff from here --> 
</mule> 

Answer 1

당신이 당신의 구성을 도시하지 않는 때문에, 당신을 도울 어렵다.

예외적으로, 내 인상은이 문제가 JDBC와 아무 관련이 없다는 점입니다. 글로벌 엔드 포인트 (인바운드가 아닌 아웃 바운드) 만 선언 할 수있는 장소에서 인바운드 엔드 포인트를 정의하려고 시도하는 것 같습니다. 전역 종점은 서비스에서 선언되고 out/bound는 내부에서 선언됩니다.

내 진단이 잘못 되었다면 설정을 공유하십시오.