-
15. Re: Problems with delivering the request message sysnchronou
claudio_br Jun 8, 2007 8:23 AM (in response to andre1001)Hi Kevin,
Did you test my example?
This problem seems with the first problem related.
Thanks, -
16. Re: Problems with delivering the request message sysnchronou
kconner Jun 8, 2007 8:49 AM (in response to andre1001)Hiya Claudio.
Tom is looking at the webservice quickstarts as we speak. Once he has finished I will be able to look at your problem.
Apologies for the delay. -
17. Re: Problems with delivering the request message sysnchronou
claudio_br Jun 13, 2007 9:03 AM (in response to andre1001)Hi Kevin,
I am doing some tests and this problem is blocking me.
Would you have a expectation to solve this problem?
Thanks -
18. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 9:10 AM (in response to andre1001)I believe Tom has finished with the webservice quickstarts so I'll look at it now.
-
19. Re: Problems with delivering the request message sysnchronou
tfennelly Jun 13, 2007 10:17 AM (in response to andre1001)I haven't actually looked at that quickstart yet.
Anyway, this quickstart is not really a "Webservice" quickstart. It's just a message-aware client (running completely outside any ESB instance), sending a message to a ESB based Service using the MessageDeliveryAdapter. This client app just so happens to be a 181 impl, but it could just as well be a regular Java client app for all the ESB cares.
Might better be named the "MessageDeliveryAdapter" quickstart. -
20. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 10:56 AM (in response to andre1001)No problem, I'm looking at it now.
I already have our version up and running within AS 4.2.0. -
21. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 11:11 AM (in response to andre1001)Actually, having looked at the jboss-esb.xml I think I can see where the issue lies.
I'll be offline for the next hour or so but will have it sorted. -
22. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 11:12 AM (in response to andre1001)BTW I mean Claudio's jboss-esb.xml and not ours
-
23. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 1:40 PM (in response to andre1001)Claudio.
There is a bug in the StaticRouter which is causing your problem. I have raised a JIRA issue to check all the actions we currently support, http://jira.jboss.com/jira/browse/JBESB-624
The issue with StaticRouter is that it returns a message at the end of it's process method. This method is then returned to the caller which is why you are seeing the original message as a respone. The router should really be returning null to terminate further processing.
You can workaround this by putting an extra action at the end of that actionlist. This action should just return null from it's process method.
I'll get this fixed first thing tomorrow. -
24. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 1:59 PM (in response to andre1001)Claudio.
There is a second JIRA issue that you should be aware of, this will prevent the workaround from working correctly. I'll get these fixed in HEAD tomorrow.
http://jira.jboss.com/jira/browse/JBESB-625 -
25. Re: Problems with delivering the request message sysnchronou
kconner Jun 13, 2007 2:05 PM (in response to andre1001)JBESB-625 is already fixed in HEAD.
-
26. Re: Problems with delivering the request message sysnchronou
claudio_br Jun 13, 2007 2:14 PM (in response to andre1001)Hi Kevin,
This same problem occur in routing with Rules.
Thanks. -
27. Re: Problems with delivering the request message sysnchronou
tfennelly Jun 14, 2007 5:19 AM (in response to andre1001)Can we explain (in more detail) why this is a problem i.e. the StaticRouter process method returning the input message unmodified?
Isn't it possible for the StaticRouter to be used in any of the following ways:
1) In the middle of an action pipeline (to route out midstream) and be followed by other actions which process the message further (and possibly return the message).
2) As described above (if I read it correctly)... message routed onto the action processing pipeline, some processing done on it, processed message routed off to some other interested Service (using the StaticRouter) and then processed message routed via the message ReplyTo settings.
Can any fix be made configurable such that it can be used in a number of ways? -
28. Re: Problems with delivering the request message sysnchronou
kconner Jun 14, 2007 6:15 AM (in response to andre1001)"tfennelly" wrote:
Can we explain (in more detail) why this is a problem i.e. the StaticRouter process method returning the input message unmodified?
The issue occurs when the action class is the last action of a pipeline as the message returned from the process method is then used as a response to the originator.
When StaticRouter was added there was no support for ReplyTo processing for actions, unless it was explicitly handled by those actions, so the intent of StaticRouter was never to return a response to the originator. It could, however, have returned the message for further processing by the action pipeline."tfennelly" wrote:
Isn't it possible for the StaticRouter to be used in any of the following ways:
1) In the middle of an action pipeline (to route out midstream) and be followed by other actions which process the message further (and possibly return the message).
2) As described above (if I read it correctly)... message routed onto the action processing pipeline, some processing done on it, processed message routed off to some other interested Service (using the StaticRouter) and then processed message routed via the message ReplyTo settings.
While these are both ways in which the StaticRouter can be used I would argue that it is not the intention of that class. It's intention has always been to route the message to one or more services. What you are describing sounds more like a wiretap than routing."tfennelly" wrote:
Can any fix be made configurable such that it can be used in a number of ways?
My preference would be to keep the StaticRouter simple, i.e. always route and terminate the pipeline. In this way everyone knows what to expect when using the action.
To handle the wiretap functionality we can do one of the following
- introduce a wiretap action to route the message and then return it
- specify that the action processing should be handled by a second service
My preference would be for the first but either can be done. -
29. Re: Problems with delivering the request message sysnchronou
tfennelly Jun 14, 2007 6:32 AM (in response to andre1001)okidoki, wiretap sounds good to me there Kev :-)