John, BAO will just implement the code as supplied in the .jars (provided by the person configuring BAO to use JMS) to attempt to connect as a generic pass through - (you can actually Google the errors for the Web Logic .jars that explain this also and point to a Web Logic specific issue, there have been other people with issues using the Web Logic specific .jars). The adapters are designed to support generic functions for the type of adapter using a standard, thus you can implement a number of different Java based connectors e.g. There are a large number of SQL connectors that BAO can use.
As this adapter is a generic JMS adapter and conforms to the JMS standard, there should be no reason a generic JMS connector (standard .jars) cannot be implemented. Unfortunately, BMC only provide examples for the common JMS interfaces and show how to generate the necessary supporting files for connection but do not cover Web Logic. The best bet to resolve this is to work with BMC Support for AO on this - the guys who code BAO are very responsive. Kind Regards, Carl Wilson http://www.missingpiecessoftware.com/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of John Baker Sent: 13 August 2013 20:21 To: [email protected] Subject: Atrium Orchestrator Issue: JMSActorAdapter : Naming look up did not return a static destination!! Carl Maybe I'm missing something but the error isn't being thrown by the WL jars, it's being thrown by the VM which has been asked (by AO) to cast one object as an interface that the object doesn't implement. The WL JMS drivers are required to connect to WL. John ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
