Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) project_key: SOA Data Services Developer Guide draft document is ready for first pass QE review. Available at: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/Data_Services_Developer_Guide/index.html Review Comments go here: https://docspace.corp.redhat.com/docs/DOC-49211
Added comments to: https://docspace.corp.redhat.com/docs/DOC-49211
Assigning back to Darrin after 1st round of QE reviews
This task has to be completed before GA. Marking as blocker for easier tracking.
Labels: Removed: qe-docsreview Added: DS_Developer_Guide qe-docsreview
Writer: Added: Darrin
doc updated & pushed to stage outstanding items emailed for feedback: Section 1.1 Can be a JCA Connector or any other custom connection provider. Teiid recommends and uses JCA as its specification defines how you can write, package, and configure access to EIS system in consistent manner. Open issue – We recommend that customers use the vendor-supplied JCA adapters for using JMS with JCA. Will we do the same for using Teiid with JCA? Section 1.2.1, 1.3.1 For sample Translator code, refer to the Teiid source code athttp://anonsvn.jboss.org/repos/teiid/trunk/connectors/ Where will the Teiid source be available from ? Will it be a standalone ZIP or included with the SOA source? And (assuming it will be available for download as a ZIP) what directory of the repo will be the root of the ZIP ? eg, if the docs refer to http://anonsvn.jboss.org/repos/teiid/trunk/connectors/ how will that be available in the ZIP - noting that the product docs will really be referring to the branch source although the upstream docs generally refer to the trunk. Section 3.1.7. Metadata Override and implement the method getMetadata(), if you want to expose the metadata about the source for use in Dynamic VDBs. This defines the tables, column names, procedures, parameters, etc. for use in the query engine. This method is not yet used by Designer tooling. Open issue: Need to check with the Dev team about “This method is not yet used by Designer tooling.” What are the user impacts of this?
The last edit that I was looking for was to list the source directories in the source.zip - once this is resolved the JIRA can be resolved.
update doc and restaged. Last updated items on the docspace page have DONE in bold to identify them.
Release Notes Docs Status: Added: Not Required
Verified in the doc.