JBossDeveloper

Hi Kevin,

Did you test my example?
This problem seems with the first problem related.

Thanks,

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.

Hi Kevin,

I am doing some tests and this problem is blocking me.
Would you have a expectation to solve this problem?
Thanks

I believe Tom has finished with the webservice quickstarts so I'll look at it now.

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.

No problem, I'm looking at it now.

I already have our version up and running within AS 4.2.0.

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.

BTW I mean Claudio's jboss-esb.xml and not ours

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.

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

JBESB-625 is already fixed in HEAD.

Hi Kevin,

This same problem occur in routing with Rules.
Thanks.

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?

"tfennelly" wrote:
Can we explain (in more detail) why this is a problem i.e. the StaticRouter process method returning the input message unmodified?

"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.

"tfennelly" wrote:
Can any fix be made configurable such that it can be used in a number of ways?

okidoki, wiretap sounds good to me there Kev :-)