Export of JMS queue having reference to error queue

[gregoan]

Hello,

If a queue is referenced as error queue by another queue, the generated model file is not correct

config.xml

=> cat gregoan_jmsmodule-jms.xml
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
  <queue name="Sysper2JMSNDPArchivingRequestError">
    <sub-deployment-name>gregoan_JmsSubDeployment</sub-deployment-name>
    <jndi-name>Sysper2JMSNDPArchivingRequestError</jndi-name>
  </queue>
  <queue name="Sysper2JMSNDPArchivingRequestQueue">
    <sub-deployment-name>gregoan_JmsSubDeployment</sub-deployment-name>
    <delivery-failure-params>
      <error-destination>Sysper2JMSNDPArchivingRequestError</error-destination>
      <redelivery-limit>5</redelivery-limit>
      <expiration-policy>Redirect</expiration-policy>
    </delivery-failure-params>
    <jndi-name>Sysper2JMSNDPArchivingRequestQueue</jndi-name>
  </queue>
</weblogic-jms>

---> See Sysper2JMSNDPArchivingRequestQueue having link to Sysper2JMSNDPArchivingRequestError (cf error-destination tag)

Generated Model file

gregoan_JmsModule:
	Target: XXX-SGLW12213_TSTwls11
	SubDeployment:
		gregoan_JmsSubDeployment:
			Target: gregoan_JmsServer
	JmsResource:
		Queue:
			Sysper2JMSNDPArchivingRequestError:
				JNDIName: Sysper2JMSNDPArchivingRequestError
				SubDeploymentName: gregoan_JmsSubDeployment
 			Sysper2JMSNDPArchivingRequestQueue:
 				JNDIName: Sysper2JMSNDPArchivingRequestQueue
 				SubDeploymentName: gregoan_JmsSubDeployment
 				DeliveryFailureParams:
 					ExpirationPolicy: Redirect
 					RedeliveryLimit: 5
 				DeliveryParamsOverrides:
 					RedeliveryDelay: 300000

[jshum2479]

I reproduced with online discovery/offline works as expected. fix will be in the next release

[gregoan]

Sorry Johnny but I had problem to access GitHub until now..
Yes we are using online mode (sorry to have missed this important point)