These sound like very useful tools. What about for the C++ side? What about making the modules something like sca/tools/c++ and sca/tools/java?
Brady -----Original Message----- From: Venkata Krishnan [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 11:13 AM To: tuscany-dev@ws.apache.org Subject: Re: SCA Toys? This would be good to get users one step forward with respect to using SCA. A good tool to have would be one that validates a composite assembly - against the xsds and then for overall consistency. I know we do quite a bit of the latter as part of the artifact processing but wonder if it would go an extra mile if abstracted as a tool. I also liked the transformers that we have in the databinding modules today. It would be good to have them as individual tools as well. I'd go for java/tools, atleast to start with. - Venkat On 6/21/07, Simon Laws <[EMAIL PROTECTED]> wrote: > > I've collected a couple of utilites that have helped me during > debugging some problems ( > > http://svn.apache.org/repos/asf/incubator/tuscany/sandbox/slaws/sample > -sca-toys/ > ). > For example this is the code I drop at the end of a test to print out > the model hierarchy that was built: > > // inspect the model > Field domainCompositeField = scaDomain.getClass > ().getDeclaredField("domainComposite"); > domainCompositeField.setAccessible(true); > Composite domainComposite = (Composite) > domainCompositeField.get(scaDomain); > > OutputStream os = new ByteArrayOutputStream(); > PrintUtil printUtil = new PrintUtil(os); > printUtil.print(domainComposite); > System.out.println("Assembly \n " + os.toString()); > > I'm sure people have much smarter utils than I that they use to make > their lives easier. If you have tools are you prepared to share them? > > How about we create a module: > > java/sca/devtools > > or even > > java/devtools > > Simon > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
