[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-assembly-comment] .composite extension for composite fileis overly constraining
Anish, If different SCA runtimes use different file extensions for composite files, wouldn't this prevent portability of contributions from one SCA runtime to another? At the moment all SCA runtimes are required to support zip archives containing .composite files. This seems like a valuable portability feature. Simon Jim Marino wrote: > It sounds as if Eclipse is similar to IntelliJ. Also, another > non-tooling benefit of the ".composite" extension is that it allows > people to "eyeball" the filename and know it is a composite from its > name. If composites could end in .xml, they would have to open the file > to determine that. > > Jim > > > > On Jun 24, 2009, at 12:35 PM, Mike Edwards wrote: > >> >> Anish, Jim, >> >> I can offer some information regarding Eclipse and composite files, >> since Eclipse is my development weapon of choice ;-) >> >> It is straightforward to configure Eclipse to recognise .composite >> files as XML files and to choose which editor to use for >> those files. It is also straightforward to configure the Eclipse XML >> facilities to read the SCA XSDs and provide on-the-fly >> validation of the SCDL within the composite files. Dave Booz was most >> recently using this in anger validating the changes >> that were part of some of the Bindings TC issue resolutions. >> >> >> One point that I make in favour of having a separate file extension of >> ".composite" is that it is then easy to ensure that the >> right tooling is used for composite files. For example, if you want >> to use the graphical tools from the Eclipse SOA Tools >> project, it is possible to associate ".composite" with that editor. >> If composite files were called ".xml", this would not be >> easy since then any general XML file would start up in the SOA Tools >> editors. While composite files are XML files, they >> are also specialized XML files with particular features for which >> add-on tooling is very useful. >> >> >> Yours, Mike. >> >> Strategist - Emerging Technologies, SCA & SDO. >> Co Chair OASIS SCA Assembly TC. >> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain. >> Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431 >> Email: mike_edwards@uk.ibm.com <mailto:mike_edwards@uk.ibm.com> >> >> >> From: Jim Marino <jim.marino@gmail.com <mailto:jim.marino@gmail.com>> >> To: sca-assembly-comment@lists.oasis-open.org >> <mailto:sca-assembly-comment@lists.oasis-open.org> >> Date: 24/06/2009 11:09 >> Subject: Re: [sca-assembly-comment] .composite extension for >> composite file is overly constraining >> >> >> ------------------------------------------------------------------------ >> >> >> >> Anish, >> >> One thing you may want to check is associating an XML MIME media type >> with the composite file. My development tool (IDEA IntelliJ) can be >> configured to recognize composite files as XML documents allowing me >> to use its built-in XML refactoring capabilities such as syncing >> referenced Java class names with source code. I'm not sure about other >> tools, but I believe Eclipse should be able to do this too. >> >> Jim >> >> >> On Jun 24, 2009, at 7:09 AM, Anish Karmarkar wrote: >> >> > This is the feedback from our development team: >> > >> > The specification requires that the composite file extension >> > be .composite. This is overly restrictive. Specifically, allowing it >> > to be .xml allows existing tools to deal with it without any >> > modification. >> > >> > -Anish >> > -- >> > >> > >> > -- >> > This publicly archived list offers a means to provide input to the >> > OASIS Service Component Architecture / Assembly (SCA-Assembly) TC. >> > >> > In order to verify user consent to the Feedback License terms and >> > to minimize spam in the list archive, subscription is required >> > before posting. >> > >> > Subscribe: sca-assembly-comment-subscribe@lists.oasis-open.org >> <mailto:sca-assembly-comment-subscribe@lists.oasis-open.org> >> > Unsubscribe: sca-assembly-comment-unsubscribe@lists.oasis-open.org >> <mailto:sca-assembly-comment-unsubscribe@lists.oasis-open.org> >> > List help: sca-assembly-comment-help@lists.oasis-open.org >> <mailto:sca-assembly-comment-help@lists.oasis-open.org> >> > List archive: http://lists.oasis-open.org/archives/sca-assembly-comment/ >> > Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf >> > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php >> > Committee: >> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-assembly >> > Join OASIS: http://www.oasis-open.org/join/ >> > >> >> >> -- >> This publicly archived list offers a means to provide input to the >> OASIS Service Component Architecture / Assembly (SCA-Assembly) TC. >> >> In order to verify user consent to the Feedback License terms and >> to minimize spam in the list archive, subscription is required >> before posting. >> >> Subscribe: sca-assembly-comment-subscribe@lists.oasis-open.org >> <mailto:sca-assembly-comment-subscribe@lists.oasis-open.org> >> Unsubscribe: sca-assembly-comment-unsubscribe@lists.oasis-open.org >> <mailto:sca-assembly-comment-unsubscribe@lists.oasis-open.org> >> List help: sca-assembly-comment-help@lists.oasis-open.org >> <mailto:sca-assembly-comment-help@lists.oasis-open.org> >> List archive: http://lists.oasis-open.org/archives/sca-assembly-comment/ >> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf >> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php >> Committee: >> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-assembly >> Join OASIS: http://www.oasis-open.org/join/ >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> / >> / >> >> /Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 >> 3AU/ >> >> >> >> >> >> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]