-
1. Re: Notifications
tfennelly Nov 27, 2007 6:39 AM (in response to objectiser)Check out the "LogicalEPR" (don't you just love that name ;-) ). It allows you specify the reply-to based on the Service Category/Name.
-
2. Re: Notifications
marklittle Nov 27, 2007 6:45 AM (in response to objectiser)"tfennelly" wrote:
Check out the "LogicalEPR" (don't you just love that name ;-) ). It allows you specify the reply-to based on the Service Category/Name.
Yeah, thank goodness we didn't give it a name like Smooks, eh ;-)? -
3. Re: Notifications
objectiser Nov 27, 2007 6:47 AM (in response to objectiser)Thanks - from the javadoc I assume I can use it to send the category/name from a client (that does support its own reply service interface) in the replyTo field, and then use it later on to return a notification.
It also looks like I could use a temporary queue based replyTo EPR in the service, to construct a logicalEPR based on the PortReference, to send a notification back to a pure client?
Will try both mechanisms out.
Thanks again,
Gary -
4. Re: Notifications
tfennelly Nov 27, 2007 6:49 AM (in response to objectiser)Yeah, good point.... that would have made even less sense ;-)
-
5. Re: Notifications
marklittle Nov 27, 2007 6:51 AM (in response to objectiser)As Tom said, you could use the LogicalEPR approach. Alternatively you are free to add whatever extensions you want to the ReferenceProperties/ReferenceParameters section of the EPRs in the Message. Since these are available to the service you can implement that to pull those details out.
-
6. Re: Notifications
tfennelly Nov 27, 2007 6:54 AM (in response to objectiser)"objectiser" wrote:
Thanks - from the javadoc I assume I can use it to send the category/name from a client (that does support its own reply service interface) in the replyTo field, and then use it later on to return a notification.
So I think you need to get your client to register it's JMS endpoint in the Registry. You said you didn't want the ESB to make the reply invocation, so whatever it is that's making the reply can use the ServiceInvoker supplied with the Service cat/name captured from the reply-to."objectiser" wrote:
It also looks like I could use a temporary queue based replyTo EPR in the service, to construct a logicalEPR based on the PortReference, to send a notification back to a pure client?
Will try both mechanisms out.
Not sure you'll get that to work, but feel free to experiment :-) -
7. Re: Notifications
objectiser Nov 27, 2007 6:56 AM (in response to objectiser)However that would require both client and server to understand the extensions in the EPR.
Hopefully the LogicalEPR approach will address all my requirements.
Thanks
Gary -
8. Re: Notifications
objectiser Nov 27, 2007 6:57 AM (in response to objectiser)Will let you know Tom........
-
9. Re: Notifications
objectiser Nov 28, 2007 8:45 AM (in response to objectiser)Just started putting together a simple test using the LogicalEPR, by modifying the helloworld example in quickstart, however I get the following compilation problem:
[javac] symbol : class eprs
[javac] location: package org.jboss.soa.esb.addressing
[javac] org.jboss.soa.esb.addressing.eprs.LogicalEPR(message.getHeader().
[javac] ^
[javac] 1 error
Just wondered which jar is it picking up the soa.esb.addressing package from, but not the eprs sub-package?
For some earlier standalone client tests I used the jbossesb-rosetta.jar from deploy/jbossesb.sar/lib folder for the jboss.soa.esb classes, which does have the eprs package.
I will keep digging - but just in case there is a simple explanation, I thought I would ask.
Regards
Gary -
10. Re: Notifications
marklittle Nov 28, 2007 9:03 AM (in response to objectiser)Strange. I build the CP earlier today. Are you running against trunk? Which branch/tag?
-
11. Re: Notifications
tfennelly Nov 28, 2007 9:18 AM (in response to objectiser)All EPR classes are located in jbossesb-rosetta.jar.
Perhaps the native-client is a better example for you to base off?? It has a client component (it's a JSR 181 impl) that uses the ServiceInvoker. All client classpaths etc will be in place for you there. -
12. Re: Notifications
objectiser Nov 28, 2007 9:51 AM (in response to objectiser)Looks like the eprs package is ok - if I change to JMSEpr it compiles fine. So must be some additional dependency on the LogicalEPR class.
-
13. Re: Notifications
objectiser Nov 28, 2007 9:53 AM (in response to objectiser)I'm using version 4.2.1GA. I'll have a look at the native-client to see if it has additional local jars.
Thanks
Gary -
14. Re: Notifications
marklittle Nov 28, 2007 9:58 AM (in response to objectiser)I'll check out the 4.2.1GA branch and check.