[jboss-jira] [JBoss JIRA] Resolved: (JBESB-317) Converting CBR Listener

[Esteban Schifman (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-317?page=all ]

Esteban Schifman resolved JBESB-317.
------------------------------------

       Resolution: Done
    Fix Version/s:     (was: 4.0 CR2)

The EPR serialization/deserialization returns a vanilla EPR.  While a proper solution is being worked in the EPRHelper class, safety net code was added to the TwoWayCourierImpl

> Converting CBR Listener
> -----------------------
>
>                 Key: JBESB-317
>                 URL: http://jira.jboss.com/jira/browse/JBESB-317
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0
>         Environment: any
>            Reporter: Kurt Stam
>         Assigned To: Esteban Schifman
>            Priority: Blocker
>         Attachments: CbrProxyActionUnitTest.java, CbrProxyActionUnitTest.xml
>
>
> A new CbrListener was created to replace the CbrJmsQueueListener. I have tried to use this new class in the CbrJmsQueueListenerTest, by updating the config xml and way the test starts the listeners. When the test CbrProxyActionUnitTest runs it gives me:
>     [junit] 12:02:37,593 DEBUG [SocketManager] Created ObjectOutputStream
>     [junit] 12:02:37,593 DEBUG [CbrListener] Sending message to the Content Based Router.
>     [junit] 12:02:37,593 DEBUG [SocketManager] Created ObjectInputStream
>     [junit] 12:02:37,593 DEBUG [UILClientILService] Starting
>     [junit] 12:02:37,593 INFO  [JBossRulesRouter] Reading ruleSet from file=JBossESBRules.drl
>     [junit] 12:02:37,593 INFO  [JBossRulesRouter] Going to read the rule: JBossESBRules.drl
>     [junit] 12:02:37,609 DEBUG [SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
>     [junit] 12:02:39,500 DEBUG [JBossRulesRouter] Obtained message=org.jboss.internal.soa.esb.message.format.xml.MessageImpl at edbca8 with ruleSet=JBossESBRules.drl
>     [junit] 12:02:39,500 DEBUG [JBossRulesRouter] Obtained message=org.jboss.internal.soa.esb.message.format.xml.MessageImpl at d9205 with ruleSet=JBossESBRules.drl
>     [junit] 12:02:39,515 INFO  [JBossRulesRouter] Fire the JBossRules Engine
>     [junit] 12:02:39,515 INFO  [JBossRulesRouter] Fire the JBossRules Engine
>     [junit] JBoss_XML
>     [junit] JBoss_XML
>     [junit] 12:02:39,515 DEBUG [JBossRulesRouter] Destination Services List: [test_category:JBOSS_XMLDestination]
>     [junit] 12:02:39,515 DEBUG [JBossRulesRouter] Destination Services List: [test_category:JBOSS_XMLDestination]
>     [junit] 12:02:39,515 DEBUG [CbrListener] Replying to caller
>     [junit] 12:02:39,515 INFO  [RegistryException] Going to load org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl
>     [junit] 12:02:39,515 DEBUG [Factory] Using the Context ClassLoader
>     [junit] 12:02:39,515 INFO  [MessageRouter] Looking for EPRs for category=test_category and serviceName=JBOSS_XMLDestination
>     [junit] 12:02:39,515 ERROR [CbrListener] Unable to reply to caller. Deliver courier for EPR not supported yet
>     [junit] org.jboss.soa.esb.couriers.CourierException: Deliver courier for EPR not supported yet
>     [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.getDeliverCourier(TwoWayCourierImpl.java:90)
>     [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.setToEpr(TwoWayCourierImpl.java:64)
>     [junit] at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.<init>(TwoWayCourierImpl.java:55)
>     [junit] at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:78)
>     [junit] at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:52)
>     [junit] at org.jboss.soa.esb.listeners.message.CbrListener.waitForEventAndProcess(CbrListener.java:120)
>     [junit] at org.jboss.soa.esb.listeners.AbstractManagedListener.run(AbstractManagedListener.java:238)
>     [junit] at java.lang.Thread.run(Thread.java:595)
>     [junit] 12:02:39,515 DEBUG [JAXRRegistryImpl] Going to query the registry for name pattern [test_category, JBOSS_XMLDestination]
>     [junit] 12:02:39,531 INFO  [LocalTransport] Calling org.apache.juddi.registry.local.InquiryService#inquire locally
>     [junit] 12:02:39,531 INFO  [Registry] Loading jUDDI configuration.
>     [junit] 12:02:39,531 INFO  [Registry] Resources loaded from: /org/jboss/soa/esb/services/registry/juddi-qatest.properties
>     [junit] 12:02:39,531 INFO  [Registry] Initializing jUDDI components.
>     [junit] 12:02:39,531 INFO  [ConnectionManager] Not using Datasource as juddi.isUseDataSource=false
>     [junit] 12:02:39,531 ERROR [MessageRouter] Could not obtain an EPR from the Registry. Message is not routed. Could not find service with category=test_category and serviceName=JBOSS_XMLDestination
>     [junit] org.jboss.soa.esb.services.registry.RegistryException: Could not find service with category=test_category and serviceName=JBOSS_XMLDestination
>     [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:333)
>     [junit] at org.jboss.soa.esb.services.routing.MessageRouter.deliverMessages(MessageRouter.java:74)
>     [junit] at org.jboss.internal.soa.esb.services.routing.cbr.JBossRulesRouter.route(JBossRulesRouter.java:107)
>     [junit] at org.jboss.soa.esb.listeners.message.CbrListener.waitForEventAndProcess(CbrListener.java:113)
>     [junit] at org.jboss.soa.esb.listeners.AbstractManagedListener.run(AbstractManagedListener.java:238)
>     [junit] at java.lang.Thread.run(Thread.java:595)
>     [junit] Caused by: org.jboss.soa.esb.services.registry.RegistryException: Could not find service with category=test_category and serviceName=JBOSS_XMLDestination
>     [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:319)
>     [junit] ... 5 more
> This should work for 4.0.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira