Mnesia schema/XMPP-RPC Generator

Technical Pursuit, Inc. has XForm screens already running for an example database application with a lot of data entry forms, search criteria screens, search result screens, etc. It is running in the browser using the TIBET(tm) client-side middleware "AJAX" library.

We're tempted to set up a server using Ruby on Rails (ignoring its GUI stuff and most of its MVC stuff since we're doing the GUI and middleware with TIBET XForms) using its model specification language.

Is there any model specification language for Mnesia/J-EAI that would generate a Mnesia database with XMPP-RPC service interface so we can just hook in our screens to the RPC calls and start entering data?

(TIBET supports XMPP.)

Is there any model

Is there any model specification language for Mnesia/J-EAI that would generate a Mnesia database with XMPP-RPC service interface so we can just hook in our screens to the RPC calls and start entering data?

I don't understand the question. Do you want ejabberd to listen RPC calls and accept commands to: create new database, remove, add elements, remove, search, get...?

Maybe a slightly different approach is best

Sorry for the delay but we had to discuss more what would be best here and we thought maybe the strategy should be different from what Rails supplies (modeling language drives database schema with scaffold-generated forms). The problem with the Rails approach to rapid prototyping is that it doesn't start with modeling the data -- it starts with workflow specification and forms design. Modeling the data follows from that.

What we have: a bunch of XForms. We can generate associated descriptions such as WSDL, as well as other descriptions of the fields.

What we need: an easy way to generate:

1) A prototype Mnesia store (table) for each XForm to handle just the fields for that XForm. No factoring or communication between XForms is required for the prototype. Refinement of the prototype requires factoring and inter-XForm-communications/dataflow but it can be put off till the prototype looks reasonable.

2) Simple CRUD services for each XForm's store.

We are focused on supporting XMPP via HTTP polling but straight REST-HTTP would suffice since this is a browser based programming.

Clarification

When I said "it doesn't start with modeling the data" I was referring to rapid prototyping rather than Rails.

Syndicate content