For my project, I'm working with the JMS connector. The PDF on connectors is clear enough and everything works, but I notice one small flaw: lack of abstraction.
In an ideal XA-world, I would not have to know where my BizDocument is on the server and how it is called there. I would like to have some kind of discovery (web)service that I could query if certain transformation are available.

For example:
I would like to transform AA-XML to BB-xml. With the current implementation, I have execute contextpath/AAtoBBxml.xbd. With the service I would call (maybe with the possibility to specify the source and target format as parameters)

http://xawareserver:8090/xaware/discovery

The return value would be a list with implementations. Something like:

1. AAtoBB.xbd
2. newversion/AAtoBB.xbd
3. Beta/AAtoBB.xbd
etc.

This would allow for a next step in abstraction of the connector code which would improve consistency of the code throughout newer features/versions.

What you are talking about is a good feature to add. Please put in a feature request on the Forge site.

Or if you would like I can do it for you but I think it would be better to have your name on the request so when the design discussions are held you would be involved.

One thing that might alleviate the pain in the mean time is to use our aliasing mechanism.

The alias mechanism allows you to use a generic term for your BizDocument and the ResourceLoader will lookup the alias in a map to find which BizDocument that term refers to.

The feature has been posted. Cheers.

Thanks for posting the feature request ... we talked about that this morning and will be trying to work it into our development plan for the Engine.

We also decided to point out one thing you may not know about. At design time, specifically in the Designer, the Component Catalog provides a simple component registry to facility identification and reuse of BizView files. You can use it to locate matches for relevant components in other BizView files listed in the catalog.

I recognize you are looking for an implementation or production discovery capability, and we'll work on that, but we did want to point out the design-time feature as well just in case you didn't know about it.

Thanks!

Virginia