[teiid-dev] [teiid-designer-dev] Proposed Schema for "ConfigurationInfo.def" file

[Ramesh Reddy]

Now comes to the question what we name the XML file inside the VDB
artifact. 

some suggestions

teiid-vdb-deployer.xml
teiid-vdb-configuration.xml

any more?

Let me know quick, we are ready to merge..

Thanks

Ramesh..

On Tue, 2010-03-02 at 17:43 -0600, Ramesh Reddy wrote:
> Based discussions from another thread here is the another revision of
> the schema. Let me if this works..
> 
> Ramesh..
> 
> On Mon, 2010-03-01 at 10:41 -0600, Ramesh Reddy wrote:
> > Here is another revision to this schema file. I removed the "data-role"
> > and modified couple names to fit what they mean.
> > 
> > Ramesh..
> > 
> > 
> > On Wed, 2010-02-24 at 17:27 -0600, Ramesh Reddy wrote:
> > > Taking second look at the vdb-manifest, Teiid runtime only looks at
> > > 
> > > 1) type - required (for making sure the binding is associated)
> > > 2) uri
> > > 3) visibility - (required by runtime, but if not available it is assumed
> > > "PUBLIC")
> > > 4) path
> > > 
> > > Another thing the runtime looks for is any problem "markers" with
> > > severity = "error", which avoids VDB from deploying. 
> > > 
> > > I added above to the "model" element as attributes. Also added a new
> > > optional element called "problem-marker" to include the errors. See
> > > attached.
> > > 
> > > Since there were no oppositions, I will go ahead with the required
> > > changes in Teiid runtime. Let me know if you if want me tweak the schema
> > > any differently.
> > > 
> > > Ramesh..
> > > 
> > > 
> > > On Fri, 2010-02-19 at 15:37 -0600, Ramesh Reddy wrote:
> > > > Is there any interest from the Tooling to merge "vdb-manifest.xmi" that
> > > > is in every VDB file into this file. Based on this schema, we can make
> > > > it work with single file. Since we already making changes to current
> > > > format, I thought I will put this as question.
> > > > 
> > > > Currently there are two different files, and Teiid at deployment time
> > > > reconciles these two into single entity. The "vdb-manifest.xmi" has
> > > > properties such as "model-type", "model-uri", "visibily" etc. It would
> > > > be *nice* to have single file.
> > > > 
> > > > I see this same file is being used for defining the "dynamic-vdb" too,
> > > > so this will fill in gap between the differences between two versions in
> > > > defining some of the same properties.
> > > > 
> > > > Ramesh..
> > > > 
> > > > On Thu, 2010-02-18 at 12:26 -0600, Ramesh Reddy wrote:
> > > > > Attached find updated schema for the configuration file that includes
> > > > > the changes for including "data-roles". Please take look an let me know
> > > > > if I need to change anything.
> > > > > 
> > > > > I also attached image of the schema and a sample xml file (generated).
> > > > > 
> > > > > Thanks
> > > > > 
> > > > > Ramesh..
> > > > > 
> > > > > On Mon, 2010-02-01 at 13:51 -0600, Ramesh Reddy wrote:
> > > > > > Attached is schema diagram for easier viewing.
> > > > > > 
> > > > > > On Mon, 2010-02-01 at 13:45 -0600, Ramesh Reddy wrote:
> > > > > > > Based on the JCA changes to the VDB artifact and its configuration the
> > > > > > > current "ConfigurationInfo.def" file needs to be modified.
> > > > > > > 
> > > > > > > I have attached the XML schema and a sample XML file showing the new
> > > > > > > format of this file. This format closely resembles the old format with
> > > > > > > few additions to lot of removal of other elements.
> > > > > > > 
> > > > > > > This same XML file will serve as 
> > > > > > > 1) Configuration for the VDB 
> > > > > > > 2) Configuration to define a "Dynamic VDB"
> > > > > > > 3) Will serve as the persisted format in the container, when a user
> > > > > > > modifies the associated connector bindings to a model using any
> > > > > > > administrative tools.
> > > > > > > 
> > > > > > > Please take look at this and let me know if there are any suggestions to
> > > > > > > improve upon.
> > > > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > teiid-designer-dev mailing list
> > > > > teiid-designer-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
> > > > 
> > > > _______________________________________________
> > > > teiid-designer-dev mailing list
> > > > teiid-designer-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
> > > _______________________________________________
> > > teiid-dev mailing list
> > > teiid-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/teiid-dev
> > _______________________________________________
> > teiid-dev mailing list
> > teiid-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/teiid-dev
> _______________________________________________
> teiid-dev mailing list
> teiid-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/teiid-dev