On Tue, Jun 28, 2011 at 7:20 AM, Nirmal Fernando <[email protected]> wrote: > On Tue, Jun 28, 2011 at 8:26 AM, Jean-Sebastien Delfino > <[email protected]> wrote: ... >> t) a command line tool that takes the text of a composite on standard >> input and prints the corresponding HTML + SVG on standard output; > > Do you mind explaining what you meant by "corresponding HTML output"? >
I meant this: <html> <head> ... some CSS, Javascript etc, meta tags etc </head> <body> ... whatever you want here, a h1 tag with the name of the composite, or an href link to the composite XML for example <svg> ... your SVG composite diagram </svg> </body> </html> Most SVGs you can find on the Web are included in HTML like that as it's easier to include help, additional text, href links, meta tags, dynamic behavior with javascript etc around the SVG diagram. ... >> z) all of the above should work with buggy, unresolved, and incomplete >> composites or they won't be really useful to a developer or >> administrator... just think of a Java editor that couldn't load a Java >> source with bugs in it... it wouldn't be so useful :) > > So, I think still I can use Tuscany runtime to load the composite XML, am I > right? Maybe, but I'm not sure, as the runtime is not supposed to proceed with incorrect composites. Last time I checked, but that was about a year ago, I was getting exceptions preventing me to proceed and get the composite model. The error handling may have been improved since then. Better check with the other Tuscany folks working on that. > (assuming that the validation part is done separately) > I'd recommend to double check without assuming :) ... -- Jean-Sebastien
