I have created another plugin which adds the schema files to XML catalog of Eclipse to help in providing content-assist support for source page of Geronimo Deployment Plan Editors.
I have attached the patch and a screenshot for the same. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-412 The directory structure of new plugin is: *org.apache.geronimo.st.schemas* -----*META-INF* ------------*MANIFEST.MF* -----*v22* (This folder contains the schema files from Geronimo-2.2 Snapshot) -----*.project* -----*about.html* -----*LICENSE.txt* -----*NOTICE.txt* -----*plugin.xml* -----*pom.xml* I have added this plugin to *org.apache.geronimo.feature* also. Do we need to add all the old schemas (v1.0 etc) also? Thanks, On Wed, Jul 2, 2008 at 12:20 PM, Sainath Chowdary <[EMAIL PROTECTED]> wrote: > I like the name very much proposed by Shiva :) > But instead of having version information in the plugins name we could have > org.apache.geronimo.st.schemas. (as schema files generally change with new > Geronimo versions instead of GEP versions) > > Thanks, > > > On Wed, Jul 2, 2008 at 11:10 AM, Shiva Kumar H R <[EMAIL PROTECTED]> > wrote: > >> >> On Wed, Jul 2, 2008 at 8:32 AM, Tim McConnell <[EMAIL PROTECTED]> >> wrote: >> >>> Wow Sainath, that is really a good idea !! The current schema files that >>> we have in the JAXB model are primarily there for reference and convenience. >>> I think your idea of shipping the schema files in a separate plugin is a >>> much better solution and we could then just eliminate those in the JAXB >>> model to prevent duplicates. Thanks much >>> >> >> Alright let's do that then. >> >> Sainath, >> Please create a new plug-in with schemas files along with required >> extensions to XMLCatalogContributions, and attach the patch to >> GERONIMODEVTOOLS-412. I will review and commit it. I will later delete the >> existing schema files in plugins\org.apache.geronimo.jee.v21.jaxbmodel >> >> What should we name the new plug-in as? "org.apache.geronimo.v21.schemas" >> ? >> >> >>> >>> >>> Sainath Chowdary wrote: >>> >>>> Hi, >>>> >>>> I think the source page in our Geronimo Deployment Plan Editors is a >>>> bare bones Text Editor. Instead we should support *Syntax Highlighting *and >>>> *Content-Assist *which helps the developer immensely and also gives a >>>> cleanly formatted view of the content in deployment plan editors. >>>> >>>> We need to use *StructuredTextEditor* instead of *TextEditor* which we >>>> are currently using to implement all these new features without any hicks >>>> by >>>> reusing the code from *Eclipse*. Also we need to add our schema files to >>>> the >>>> *XML catalog* in eclipse for the content-assist to work properly. >>>> >>>> For providing content-assist we have two options, creating a new plugin >>>> with the schema files and shipping it with GEP *or* Using the schema files >>>> that we already have in our JAXB model (i.e >>>> org.apache.geronimo.jee.v21.JAXB), >>>> >>>> We just need to use the extension provided by eclipse to add files into >>>> catalog. Also there are some new schema files introduced in Geronimo-2.2 >>>> (jetty, jetty-config, tomcat, tomcat-config), We need to add those files >>>> into JAXB model and use the extension point *XMLCatalogContributions *to >>>> provide content-assist in source page of Geronimo Deployment Editors. >>>> >>>> But the problem is that we at present don't ship the schema files with >>>> our JAXB model plugin. So we need to export the schema files also which >>>> will >>>> increase the size of GEP by 50KB roughly. >>>> >>>> So can anyone suggest which way to proceed for the schema files i.e use >>>> the schema files already present in JAXB by exporting them with it or ship >>>> another plugin with the schema files (which is better option instead of >>>> merging functionality) >>>> >>>> I have already created a JIRA for this issue and attached a patch that >>>> adds syntax highlighting feature. >>>> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-410 >>>> >>>> Regards, >>>> >>>> -- >>>> Sainath Chowdary >>>> B.Tech III yr, Spring Semester >>>> Electronics & Communication Engg >>>> Indian Institute of Technology Roorkee >>>> >>> >>> -- >>> Thanks, >>> Tim McConnell >>> >> >> >> >> -- >> Thanks, >> Shiva > > > > > -- > Sainath Chowdary > B.Tech III yr, Spring Semester > Electronics & Communication Engg > Indian Institute of Technology Roorkee > -- Sainath Chowdary B.Tech III yr, Spring Semester Electronics & Communication Engg Indian Institute of Technology Roorkee
