MQSeries.net :: View topic - Promoted properties across broker schemas

chrisc · Posted: Thu Sep 20, 2007 3:59 pm Post subject:

We have run into a little problem with a v5 broker solution we are building, and I was wondering if anyone had a solution / explanation...

We have one project which contains some common components that are reusable, and these components contain promoted properties (mainly around the data source and ESQL statement reference). These are in a schema, say com.company.common.

Another project actually uses the components and provides the actual ESQL for those promoted bits. This project has all the flows in a different schema, say com.company.

When in the toolkit, it is able to resolve these just fine, and clicking "Show ESQL" finds the procedure OK. However, when trying to add the flows to a BAR file it fails in all cases, saying it is unable to find the ESQL named xyz, i.e. the ESQL procedure for the promoted property.

I've discovered that it seems to be because they are in different schemas. I'm guessing that it is because the common component is actually the bit that uses the promoted code, and since that common component doesn't have a PATH statement for the flows that use the component, it can't resolve the reference. This seems like a reverse dependency to me, with the general needing to have a reference to the specific!

Anyone know if this is really the case, why it happens like this and whether there is a way around it? It doesn't seem right that you would be prevented from using promoted ESQL across schemas...?

Thanks,
Chris