The nice thing about the way JDBC was implemented is that there is a common abstraction layer regardless of the source. The thing I am thinking about writing would implement the common interfaces and methods, regardless of the jdbc driver, thus allowing the use of any data source where a jdbc driver was available. Whether this included a fs based jdbc driver, a mysql driver, an ldap driver, or whatever it happens to be, on component would be capable of serving all those types of requests, so long as the driver was available in the classpath.
Axton Grams On 9/9/07, Carey Matthew Black <[EMAIL PROTECTED]> wrote: > Axton, > > And after a bit of thought.... I think an ARDBC that reads Server side > menu files would be a good tool to have too. > > I think one might be able to: > Read data from the file (Set Field actions) > add/remove records from the file > ( or maybe re-build the whole file from an ARS form's data) > > > The main advantage I see to this would be to be able to allow multiple > (more than 5) levels of grouping for the menu objects that is still > based on ARS data that can be controlled by work flow from creation to > deletion. It would also allow for a "path forward" for the older > server file menus as a whole. > > And if the ARS data to File Menu part of this is general enough then, > then even the JDBC plugin could be used as a source of data for an ARS > menu. :) > > But maybe it is just me stuck with server side menus that would find > such a features set to be helpful? > > -- > Carey Matthew Black > Remedy Skilled Professional (RSP) > ARS = Action Request System(Remedy) > > Love, then teach > Solution = People + Process + Tools > Fast, Accurate, Cheap.... Pick two. > > > > On 9/8/07, Carey Matthew Black <[EMAIL PROTECTED]> wrote: > > Axton, > > > > I think it is a great idea. And the sample ARDBC Java plugin looks > > fairly good at first blush. :) > > > > From > > (...\Api\javaplugins\samplesrc.jar!\java\com\bmc\arsys\plugin\sample\ARDBCSample.java) > > > > > > /** > > * A sample ARDBC plugin implementation as an example of how to use the sdk. > > * > > * This plugin extends ARDBCPlugin object. Alternatively, one could > > implement the interface ARDBCPluggable. > > * > > * This implementation fetches the jdbc connection information as > > config items using the plugin context. > > * Uses that information to establish a jdbc connection to a SQL > > Server database. Provides a way of creating > > * vendor forms using tables in the underlying database. > > */ > > > > > > But I have not tested it out yet either. > > > > And there is also AREASample.java, and FilterAPISample.java too. > > > > -- > > Carey Matthew Black > > Remedy Skilled Professional (RSP) > > ARS = Action Request System(Remedy) > > > > Love, then teach > > Solution = People + Process + Tools > > Fast, Accurate, Cheap.... Pick two. > > > > > > On 9/8/07, Axton <[EMAIL PROTECTED]> wrote: > > > With the new java based plugin server introduced in 7.1, can I get a > > > show of hands in who would the interested in a jdbc driver implemented > > > as an ARDBC plugin? > > > > > > Seems that a generic implementation would allow access to any remote > > > db that provides a jdbc driver (Oracle, MSSQL, MySQL, LDAP, MS Access, > > > SQLLite, PostgreSQL, Domino, DB2, etc.). > > > > > > Seems the targets could be almost endless. > > > > > > Axton Grams > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
