Should the standalone-teiid.xml be self-documenting and include all known elements/attributes? In carrying forward https://issues.jboss.org/browse/TEIID-1873 the security doc reference elements/attributes that aren't in the file. As we are close to our first alpha any help in updating the docs would be great. Steve _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev

It's not so much that the docs are referencing the config file in expecting it to be documented, rather it's the docs describe editing that file (which is clearly more difficult if all elements/attributes are not present). So what we actually need to do is modify the documentation to not reference standalone-teiid.xml at all, but rather how to make modifications through the CLI, correct? ----- Original Message ----- > Steve, > > It is not possible to self documenting this file, as this gets > overwritten every time there is a configuration change. However, the > configuration elements are forced to have description in the code, > which > can be seen by querying the subsystem using CLI. So, any tools > written > above the CLI api can get access to this information. > > We should remove any references in docs to see this file for > explanations. > > Ramesh.. > > On Tue, 2011-12-20 at 12:50 -0500, Steven Hawkins wrote: > > Should the standalone-teiid.xml be self-documenting and include all > > known elements/attributes? In carrying forward > > https://issues.jboss.org/browse/TEIID-1873 the security doc > > reference elements/attributes that aren't in the file. > > > > As we are close to our first alpha any help in updating the docs > > would be great. > > > > Steve > > > > _______________________________________________ > > teiid-dev mailing list > > teiid-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/teiid-dev > > >

We are still looking at recommending RHQ to start with though, correct? ----- Original Message ----- | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | To: "Steven Hawkins" <shawkins(a)redhat.com&gt; | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt; | Sent: Wednesday, December 21, 2011 9:21:10 AM | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in general | | Yes, using some kind of admin tool is the preferred way. Another | reason | it may not be good to edit manually is when the server is running in | domain mode. Using the admin tools will change the configuration on | all | or defined server groups by the user. However, if the server is not | running, you can edit the standalone-teiid.xml to make changes to | configuration. Some times it easy to edit this file than using the | tools. | | If we use command line then it is Jboss Admin tool (CLI, | jboss-admin.sh), or use the admin-console web app. Right now user can | use the CLI, however for the Web app I just started looking into and | we | are way behind its implementation time line. We need a GWT expert to | move this along much faster. | | Ramesh.. | | On Tue, 2011-12-20 at 20:59 -0500, Steven Hawkins wrote: | > It's not so much that the docs are referencing the config file in | > expecting it to be documented, rather it's the docs describe | > editing that file (which is clearly more difficult if all | > elements/attributes are not present). So what we actually need to | > do is modify the documentation to not reference | > standalone-teiid.xml at all, but rather how to make modifications | > through the CLI, correct? | > | > ----- Original Message ----- | > > Steve, | > > | > > It is not possible to self documenting this file, as this gets | > > overwritten every time there is a configuration change. However, | > > the | > > configuration elements are forced to have description in the | > > code, | > > which | > > can be seen by querying the subsystem using CLI. So, any tools | > > written | > > above the CLI api can get access to this information. | > > | > > We should remove any references in docs to see this file for | > > explanations. | > > | > > Ramesh.. | > > | > > On Tue, 2011-12-20 at 12:50 -0500, Steven Hawkins wrote: | > > > Should the standalone-teiid.xml be self-documenting and include | > > > all | > > > known elements/attributes? In carrying forward | > > > https://issues.jboss.org/browse/TEIID-1873 the security doc | > > > reference elements/attributes that aren't in the file. | > > > | > > > As we are close to our first alpha any help in updating the | > > > docs | > > > would be great. | > > > | > > > Steve | > > > | > > > _______________________________________________ | > > > teiid-dev mailing list | > > > teiid-dev(a)lists.jboss.org | > > > https://lists.jboss.org/mailman/listinfo/teiid-dev | > > | > > | > > | | | _______________________________________________ | teiid-dev mailing list | teiid-dev(a)lists.jboss.org | https://lists.jboss.org/mailman/listinfo/teiid-dev |

IRT the the GWT console, we need the plugable framework to avoid tying us to AS releases, right? Is the development of that framework what requires GWT expertise?

Extending the AS7 plugin for Teiid is a WIP, but I plan on continuing work on it over holiday break and hope to have it solid by mid Jan.

----- Original Message ----- | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | To: "Ted Jones" <tejones(a)redhat.com&gt; | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt;, "Steven Hawkins" <shawkins(a)redhat.com&gt; | Sent: Wednesday, December 21, 2011 10:07:40 AM | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in general | | Currently community AS7 does not bundle any RHQ based console. This | is a | separate bundle, that needs to be downloaded and installed. Seems | like | they moved away from the "Embedded JOPR" and GWT based | "admin-console" | replaced its place. Unfortunately, to be in-line with other projects | we | need Teiid implementations of both. Time will decide which console | will | succeed. | | Yes, RHQ based implementation is very much needed for community and | product aspirations. Do you have any updates to report your progress | on | this front? | | Ramesh.. | | On Wed, 2011-12-21 at 10:42 -0500, Ted Jones wrote: | > We are still looking at recommending RHQ to start with though, | > correct? | > | > ----- Original Message ----- | > | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | > | To: "Steven Hawkins" <shawkins(a)redhat.com&gt; | > | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt; | > | Sent: Wednesday, December 21, 2011 9:21:10 AM | > | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in general | > | | > | Yes, using some kind of admin tool is the preferred way. Another | > | reason | > | it may not be good to edit manually is when the server is running | > | in | > | domain mode. Using the admin tools will change the configuration | > | on | > | all | > | or defined server groups by the user. However, if the server is | > | not | > | running, you can edit the standalone-teiid.xml to make changes to | > | configuration. Some times it easy to edit this file than using | > | the | > | tools. | > | | > | If we use command line then it is Jboss Admin tool (CLI, | > | jboss-admin.sh), or use the admin-console web app. Right now user | > | can | > | use the CLI, however for the Web app I just started looking into | > | and | > | we | > | are way behind its implementation time line. We need a GWT expert | > | to | > | move this along much faster. | > | | > | Ramesh.. | > | | > | On Tue, 2011-12-20 at 20:59 -0500, Steven Hawkins wrote: | > | > It's not so much that the docs are referencing the config file | > | > in | > | > expecting it to be documented, rather it's the docs describe | > | > editing that file (which is clearly more difficult if all | > | > elements/attributes are not present). So what we actually need | > | > to | > | > do is modify the documentation to not reference | > | > standalone-teiid.xml at all, but rather how to make | > | > modifications | > | > through the CLI, correct? | > | > | > | > ----- Original Message ----- | > | > > Steve, | > | > > | > | > > It is not possible to self documenting this file, as this | > | > > gets | > | > > overwritten every time there is a configuration change. | > | > > However, | > | > > the | > | > > configuration elements are forced to have description in the | > | > > code, | > | > > which | > | > > can be seen by querying the subsystem using CLI. So, any | > | > > tools | > | > > written | > | > > above the CLI api can get access to this information. | > | > > | > | > > We should remove any references in docs to see this file for | > | > > explanations. | > | > > | > | > > Ramesh.. | > | > > | > | > > On Tue, 2011-12-20 at 12:50 -0500, Steven Hawkins wrote: | > | > > > Should the standalone-teiid.xml be self-documenting and | > | > > > include | > | > > > all | > | > > > known elements/attributes? In carrying forward | > | > > > https://issues.jboss.org/browse/TEIID-1873 the security doc | > | > > > reference elements/attributes that aren't in the file. | > | > > > | > | > > > As we are close to our first alpha any help in updating the | > | > > > docs | > | > > > would be great. | > | > > > | > | > > > Steve | > | > > > | > | > > > _______________________________________________ | > | > > > teiid-dev mailing list | > | > > > teiid-dev(a)lists.jboss.org | > | > > > https://lists.jboss.org/mailman/listinfo/teiid-dev | > | > > | > | > > | > | > > | > | | > | | > | _______________________________________________ | > | teiid-dev mailing list | > | teiid-dev(a)lists.jboss.org | > | https://lists.jboss.org/mailman/listinfo/teiid-dev | > | | | |

By "If we can develop with what they have currently" do you mean have them write the GUIs into the current AS 7 console, or roll our own using GWT? I thought we scrapped the idea of them doing the GUI since the development timeframe didn't work for us and we didn't want to be dependent on the AS7 release cycle. ----- Original Message ----- | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | To: "Ted Jones" <tejones(a)redhat.com&gt; | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt;, "Steven Hawkins" <shawkins(a)redhat.com&gt; | Sent: Wednesday, December 21, 2011 10:50:31 AM | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in general | | On Wed, 2011-12-21 at 11:20 -0500, Ted Jones wrote: | > IRT the the GWT console, we need the plugable framework to avoid | > tying us to AS releases, right? Is the development of that | > framework what requires GWT expertise? | No, that is not Teiid's concern, it is AS7 console developer's. If we | can develop with what they have currently is the goal, and we will | modify to whatever framework they provide in future. | > | > Extending the AS7 plugin for Teiid is a WIP, but I plan on | > continuing work on it over holiday break and hope to have it solid | > by mid Jan. | Thanks, if we can show some console by second alpha that would be | good. | | Ramesh.. | > | > ----- Original Message ----- | > | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | > | To: "Ted Jones" <tejones(a)redhat.com&gt; | > | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt;, "Steven Hawkins" | > | <shawkins(a)redhat.com&gt; | > | Sent: Wednesday, December 21, 2011 10:07:40 AM | > | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in general | > | | > | Currently community AS7 does not bundle any RHQ based console. | > | This | > | is a | > | separate bundle, that needs to be downloaded and installed. Seems | > | like | > | they moved away from the "Embedded JOPR" and GWT based | > | "admin-console" | > | replaced its place. Unfortunately, to be in-line with other | > | projects | > | we | > | need Teiid implementations of both. Time will decide which | > | console | > | will | > | succeed. | > | | > | Yes, RHQ based implementation is very much needed for community | > | and | > | product aspirations. Do you have any updates to report your | > | progress | > | on | > | this front? | > | | > | Ramesh.. | > | | > | On Wed, 2011-12-21 at 10:42 -0500, Ted Jones wrote: | > | > We are still looking at recommending RHQ to start with though, | > | > correct? | > | > | > | > ----- Original Message ----- | > | > | From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; | > | > | To: "Steven Hawkins" <shawkins(a)redhat.com&gt; | > | > | Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org&gt; | > | > | Sent: Wednesday, December 21, 2011 9:21:10 AM | > | > | Subject: Re: [teiid-dev] standalone-teiid.xml and docs in | > | > | general | > | > | | > | > | Yes, using some kind of admin tool is the preferred way. | > | > | Another | > | > | reason | > | > | it may not be good to edit manually is when the server is | > | > | running | > | > | in | > | > | domain mode. Using the admin tools will change the | > | > | configuration | > | > | on | > | > | all | > | > | or defined server groups by the user. However, if the server | > | > | is | > | > | not | > | > | running, you can edit the standalone-teiid.xml to make | > | > | changes to | > | > | configuration. Some times it easy to edit this file than | > | > | using | > | > | the | > | > | tools. | > | > | | > | > | If we use command line then it is Jboss Admin tool (CLI, | > | > | jboss-admin.sh), or use the admin-console web app. Right now | > | > | user | > | > | can | > | > | use the CLI, however for the Web app I just started looking | > | > | into | > | > | and | > | > | we | > | > | are way behind its implementation time line. We need a GWT | > | > | expert | > | > | to | > | > | move this along much faster. | > | > | | > | > | Ramesh.. | > | > | | > | > | On Tue, 2011-12-20 at 20:59 -0500, Steven Hawkins wrote: | > | > | > It's not so much that the docs are referencing the config | > | > | > file | > | > | > in | > | > | > expecting it to be documented, rather it's the docs | > | > | > describe | > | > | > editing that file (which is clearly more difficult if all | > | > | > elements/attributes are not present). So what we actually | > | > | > need | > | > | > to | > | > | > do is modify the documentation to not reference | > | > | > standalone-teiid.xml at all, but rather how to make | > | > | > modifications | > | > | > through the CLI, correct? | > | > | > | > | > | > ----- Original Message ----- | > | > | > > Steve, | > | > | > > | > | > | > > It is not possible to self documenting this file, as this | > | > | > > gets | > | > | > > overwritten every time there is a configuration change. | > | > | > > However, | > | > | > > the | > | > | > > configuration elements are forced to have description in | > | > | > > the | > | > | > > code, | > | > | > > which | > | > | > > can be seen by querying the subsystem using CLI. So, any | > | > | > > tools | > | > | > > written | > | > | > > above the CLI api can get access to this information. | > | > | > > | > | > | > > We should remove any references in docs to see this file | > | > | > > for | > | > | > > explanations. | > | > | > > | > | > | > > Ramesh.. | > | > | > > | > | > | > > On Tue, 2011-12-20 at 12:50 -0500, Steven Hawkins wrote: | > | > | > > > Should the standalone-teiid.xml be self-documenting and | > | > | > > > include | > | > | > > > all | > | > | > > > known elements/attributes? In carrying forward | > | > | > > > https://issues.jboss.org/browse/TEIID-1873 the security | > | > | > > > doc | > | > | > > > reference elements/attributes that aren't in the file. | > | > | > > > | > | > | > > > As we are close to our first alpha any help in updating | > | > | > > > the | > | > | > > > docs | > | > | > > > would be great. | > | > | > > > | > | > | > > > Steve | > | > | > > > | > | > | > > > _______________________________________________ | > | > | > > > teiid-dev mailing list | > | > | > > > teiid-dev(a)lists.jboss.org | > | > | > > > https://lists.jboss.org/mailman/listinfo/teiid-dev | > | > | > > | > | > | > > | > | > | > > | > | > | | > | > | | > | > | _______________________________________________ | > | > | teiid-dev mailing list | > | > | teiid-dev(a)lists.jboss.org | > | > | https://lists.jboss.org/mailman/listinfo/teiid-dev | > | > | | > | | > | | > | | | |