Hi Marshall,
Take a look at the RESTful web application on the Resources and Solutions page of the openqm.com web site. This may do what you want though I haven’t looked closely at it.
Martin
--
You received this message because you are subscribed to the Google Groups "OpenQM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openqm+un...@googlegroups.com.
To post to this group, send an email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openqm?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
FWIW, one of my primary projects now is:
- a Grails front-end maintained by another company
- intefacing to a Java middle-tier which I wrote, exposing a BAL to Grails with a MV DAL
- the DAL uses a standard web service client
- that calls to IIS with mv.NET which I use to get into the DBMS
It all works great and the client sponsoring the development has many companies in the pipeline eager to subscribe to their new services.
That topology is versatile enough to use any connectivity tool to get into any web server and any DBMS, MV or otherwise. It does not require the UI people to know anything about the comms or back-end, and in fact we've gone to lengths to ensure they know little to nothing about the encapsulated details specifically because it allows us to make changes which don't affect front-end code at all. The middle-tier and back-end can also be ported to other MV environments to repurpose for whatever reason.
Compare this to hard-coding a UI into MV communications software.
I'll also reiterate that I would really rather than Martin and other database providers spend their time focusing on the database, which no one else can do, while we let thousands of other developers compete for our attention in the communications arena. It's really a shame to keep asking these database companies to do things that are outside of their scope when so many specialized and competent solutions are available elsewhere. Our market doesn't expand when we continue to use platform-specific interfaces - it appears to be smaller because we aren't using mainstream tools. It discourages people on the outside from using the platform because they don't feel like they can use the knowledge they have - and it does MV developers an equal dis-service because they spend their time learning platform-specific tools where the knowledge doesn't translate into something that can be used in the sales cycle against mainstream competition.
There are Lots of reasons Not to keep asking DBMS companies for even more proprietary solutions. Rather, we should be asking them to create more marketing which touts their ability to integrate with anything else out there.
T