That's a good point I hadn't considered. I think we should definitely keep these schemas in then, since without them it will probably fail to load. There should be no problem at all to load but ignore.
Thanks -------------------- Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -----Original Message----- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 9:33 AM To: [email protected] Subject: Re: [SCA Native] java implementation and interface schema files loaded but not used Brady Johnson wrote: > Does anyone have any insight into why these files are loaded but never > used in TuscanySCA Native: > > <TuscanySCA Root dir>/xsd/ > sca-implementation-java.xsd > sca-interface-java.xsd > > I created a JIRA for this: > https://issues.apache.org/jira/browse/TUSCANY-1513 > > Their existence in the project is misleading and implies that > TuscanySCA Native supports Java services. > Perhaps these should be removed in M4. > > > -------------------- > Brady Johnson > Lead Software Developer - HydraSCA > Rogue Wave Software - [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > > > Will you be able to load (and ignore without breaking) a composite containing implementation.java and interface.java elements? I'm thinking about scenarios where people share a composite between the two runtimes, with part of it running on the Native runtime and part running on the Java runtime. I guess I'll have the same question for the Java project, we should be able to ignore (or just handle with a warning) implementation.cpp and interface.cpp in the Java runtime. -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
