About route expression in Dynamic route to service

Question

Hi all,
in the "Dynamic route to service" action:
<route xmlns="http://www.bea.com/wli/sb/context">
<service isProxy="true">{ $proxyToBeInvoked }</service>
</route>
I use a variable named 'proxyToBeInvoked' to build dynamically what service shoud be called.
Here an example of ''proxyToBeInvoked" variable assignment:
fn:concat('EventBus-', $eventType, '/providers/', $provider, '/resource/', $providerEventType, '-', $provider, '-TransformIntoIPEvent')
I've noticed that if ''proxyToBeInvoked" points to non-existent proxy no error is raised by ALSB and I can realize that something goes wrong only having a look at log files!
Do you know a way to test if variable ''proxyToBeInvoked" points to existent service or a way to add to the <route> expression some extra flag in order to enforce that the related service exists ?
Best regards
ferp

Answer 1

Hello,
I'm surprised you're having trouble with this one. In ALSB 2.5 and 2.6, I get back a fault when this occurs. My proxy that contains dynamic routing does not have an error handler on the route node, only on the proxy level.
I'm using exactly the same xml syntax as you posted, so it doesn't appear to be a difference in flag settings.
This is the fault that I get back:
<fault xmlns="http://www.bea.com/wli/sb/context">
<errorCode>BEA-382000</errorCode>
<reason>Error preparing message for dispatch</reason>
<location>
<node>ProxyName RouteNodeName</node>
<path>request-pipeline</path>
</location>
</fault>
Hope that helps,
Meghan