[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Why xml for the manifest file ?
- From: Sankar P <sankar.curiosity@xxxxxxxxx>
- Date: Fri, 17 Jul 2009 18:59:29 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=keqpN9x0B8P3kws6YNuJH2FFhY7OA+bcvY0T00iPnB6HEYLDhZZRsN92wa14YPlo3+ eyCwr3MwIkd//3mm+X0tRaPKoncyYxdFB702dZLaJ1X00atM+zrTq0CwiMJ1rHmB+ir4 L3drMm0+85vrLB0kXwwObi4Ss9X3vdQAVN2cM=
On Fri, Jul 17, 2009 at 5:51 PM, Paul
> If you want your question answered, you will need to subscribe to the
> list (or check it regularly,
> I've copied your email on this response so you are aware of the
> etiquette for using this kind of list.
I'll take care. Thanks.
> On Fri, Jul 17, 2009 at 8:10 AM, Sankar P<sankar.curiosity@xxxxxxxxx> wrote:
>> reason that I could think of is, to check for mandatory elements (like
>> say plugin-id) which can be easily compared by checking against a
>> schema etc.
>> So, can someone explain me why XML is chosen and how it is beneficial
>> over a simple text file ?
> You've hit one of the largest reasons, schema. It allows definitions
> and complex data types for each extension point to be published. Now
> you can 1) generate documentation, 2) hand craft the XML necessary, 3)
> provide *extensive* tooling to help building the files. #3 is really
> There are a number of other good reasons.
Okay. I got the reasons now.
I believe some more advantages could be like, to automatically convert
a xml file into an object (with the help of some serializer function)
and use it directly, etc.
Where can I get the schema files for the manifest files that one can
write for eclipse ? google results are favoring pages that talk about
auto-generating the manifest file by using an eclipse extension.
Thanks a lot for your explanation.