This content has been marked as final. Show 5 replies
I resovled the problems I was having.
I was able to figure out how to change the library linking in eclipse and switched the commons-codec-1.3.jar & commons-httpclient-3.0.1.jar in the place of commons-codec.jar & commons-httpclient.jar libraries previously used with the project (properties:libraries).
I was not able to correct the service cannot be resolved. Everything I did kept crashing and dropping my connection tot he channel. I ended up just switching the code in my java adapter from:
MessageService msgService = (MessageService) service
MessageBroker broker = MessageBroker.getMessageBroker(null);
MessageService msgService = (MessageService) broker.getService("message-service");
This appears to be working as desired for my use of the java adapter for the session management & logging. I am not really certain why the "service" became undefined between FDS2 & LCDS, something must have been depreciated or changed around.
In LCDS 2.5 we had a major clean-up of the messaging component APIs to prepare
for publishing how to programmatically configure the message broker. One
change was to correct the APIs to reflect the in-memory state of the components,
such as how services, destinations and adapters are actually managed. Services
have a list of destinations, and each destination creates its own instance
of an adapter.
If you want to get to a service from a custom adapter, you can either do
what you mention below and start at the top to get the message broker and
then ask it for a service, or alternatively you can call getDestination()
from your adapter and then call getService() from that destination.
Thanks Pete, good info to know.
Looks like the u maine education paid off. Crosby would be so proud of his star pupil. So if you haven't guess it, another u maine alum.
How do I get ahold of you?
Hey Frenchie, haven't talked to you in forever guy. Send me an email and we will catch up: firstname.lastname@example.org