Joachim what are your thoughts on OWL export of the object model? Where would that be used? I have to admit I am interested in something else, but have made no progress, that of the possible use of Tapestry with OWL. Henry Story has the story (excuse the pun). https://sommer.dev.java.net/sommer.html It seems to me that if you have implemented the export of the object model into OWL that is a step away from consuming OWL within Tapestry perhaps by creating a pipeline? Might this have some benefit? Henry Story discuses ActiveRDF extension to Ruby where using RDF seems as natural as importing a package. I think it would have benefits. Display data according to inferred type and so on. What do you think? Adam
2008/5/7 adasal <[EMAIL PROTECTED]>: > Hi Joachim, > I have looked at your web site and discussed this with colleagues. It seems > like a very interesting development to me. The apparent ease with which MVC > can be split between different machines may be of particular interest to us > due to the scale and further scaling needs of our web site, one of the > largest UK web sites. > We are not actively developing either with Tapestry or anything else at the > moment for reasons too boring to go into here. > But I am actively promoting Tapestry adoption, whether this turns out to be > 4 or 5 will depend on time frames. > Your tool is very welcome and increases the credibility of what is already > a very credible framework. > Adam Saltiel > Java Enterprise Designer > Serco Web Solutions > Serco Plc > > 2008/5/5 Joachim Van der Auwera <[EMAIL PROTECTED]>: > > equanda, a open source project to generate a JEE application based on a >> domain model, has released version 0.9. >> >> equanda generates the EJB3 access objects with possibility for powerful >> declarative constraints and added programmatic constraints. >> equanda also generates a tapestry5 based user interface with powerful >> options for customizations. >> All this (and quite a few other bots and pieces) are generated at compile >> time from a XML description of the data and constraints. The customizations >> remain intact in the generation process. >> >> This is the first useable release of equanda since the project started >> (though the user interface still lacks features). >> >> Notable changes include : >> - initial tapestry5 user interface >> - type handling in field templates now also interprets subtags >> - filter string per table >> - improved form traversal in user interface, which also auto switches to >> the next tab >> - allow templates to define extra key-value pairs, possibly overwritten by >> user >> - fields named "Reference" or "Description" should automatically be marked >> as is-reference or is-description >> - generate UML and OWL from the domain model >> - Improve xml reading/handling in domain model parsing code >> - add selectors on proxies >> - create archetype for empty equanda project >> - tapestry5 accordion component >> - tapestry5 tabs component >> - tapestry5 FormTraversal component >> - add equandaReset() method in proxies to revert the state to the database >> values >> - tapestry5 create "manifest" binding prefix >> - Should allow a table type (in the inheritance tree) to be impossible to >> create >> >> For more information, visit the project web site : http:// equanda.org/ >> >> -- >> Joachim Van der Auwera >> http://blog.progs.be/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
