© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This release notes file contains late-breaking information about limitations and known problems and workarounds that pertain to one of the following tools:
- A component that does not have a release notes file of its own
- The entire WebSphere® Integration Developer product
The XML catalog is primarily used as a cache for performance improvement by avoiding unecessary Web access for internet-located schemas. Therefore, for all Web-based XSD imports, where the schemaLocation attribute points to a Web address, the XML catalog is always used first to resolve the import. If no entry is in the catalog, then it is accessed from the Web. For file-relative imports, where the schemaLocation attribute points to a file, the schema location is used to resolve the import.
The XML catalog can also be used to store system-specific schemas that are referred to in many schemas. An example of this is the BusinessGraph.xsd. In these cases, if an XSD import schemaLocation attribute points to a file that is not found in the file system, but the schema is in the catalog, then the catalog version is used.
As a result, when you share XSDs that use system schemas that are registered in the XML catalog, you should either include the system schema with the shared XSDs, or share the contents of the XML catalog.
You might receive errors indicating that a WSDL object or business object (XSD type) cannot be found, yet you cannot see any reason for the error because the file that contains the object resides in a dependent project. Usually, these errors are displayed in the Problems view. You might also encounter them in the workbench log file or in a message dialog box.
You might have received this error if you dragged an object from a Java project onto one of the WebSphere Integration Developer editors, creating a reference to that artifact in the file you are editing.
Ensure that the file is in a WebSphere Integration Developer module or a WebSphere Integration Developer library. The object might not be found if its file resides in a Java project, even if that project is a dependent project.
To work around the problem, move the file to a WebSphere Integration Developer library or a WebSphere Integration Developer module. If several WebSphere Integration Developer modules must share the object, move the file to a WebSphere Integration Developer library.
With business-driven development, you can model a solution, implement the solution, deploy it to a runtime server, and monitor the solution on the server.
The business analyst models a business process in WebSphere Business Modeler that the integration developer implements in WebSphere Integration Developer and deploys to the runtime server. During the integration process, the solution can be annotated to capture business performance information, which you can monitor using WebSphere Business Monitor.
For guidelines and tips to achieve a smooth business-driven development experience, read "Business-driven development considerations", which is available on the following Web site: http://www.ibm.com/support/docview.wss?rs=2308&context=SSQQFK&uid=swg27008813.