I'm not really fond of having a predefined schema for application type xml. reasons: 1) in my opinion is too early to figure out what should be in the schema given that we don't have lot of apptypes (or identified what we will support in future) 2) I like to draw an example from Apache Ant. Correct me if im wrong but they purposely don't have a schema to validate tags in build.xml file. why ? because they if they do they can't introduce any ant tasks/types with out changing the schema. (- it becomes a bottleneck - and brings a lot of backward compatibility issues).
What do you guys think? @Punnadhi: BTW is it possible to have un-Marshal xml if the xml document contains UN-recognized tags? On Mon, Jul 28, 2014 at 8:00 PM, Punnadi Gunarathna <[email protected]> wrote: > Hi All, > > We thought of come-up with an XSD for the apptype.xml and use it to > validate the xml file against the mandatory elements. If apptype.xml is > validated and the result is success then it can be unmarshelled with JAXB. > > > On Mon, Jul 28, 2014 at 5:33 PM, Danushka Fernando <[email protected]> > wrote: > >> Hi All >> >> Problem : App Factory deployers should be able to add application types >> by packaging everything in a file. For example to add foo apptype add >> foo.apptype archive file and putting it in a location. [1] >> >> Solution : Add a new deployer (Apptype Deployer), which will listen to >> the location $CARBON_HOME/repository/deployment/server/apptypes and which >> will do the following set of tasks. >> >> >> 1. >> >> Explode the zip file. >> 2. >> >> This zip file should contain a xml file such as apptype.xml. >> 3. >> >> There are set of tags that should be in this xml (Mandatory Tags) and >> there could be set of properties which is custom to this apptype. >> 4. >> >> Pre check the availability of the class mentioned as the Application >> Type Processor (Which should be a Mandatory Tags). (This application type >> processor is a customization endpoint provided by App Factory) >> 5. >> >> Copy set of resources files to a named locations. >> 6. >> >> Populate a in memory data structure with the data in the apptype.xml. >> >> >> >> [1] https://redmine.wso2.com/issues/2889 >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks and Regards, > > Punnadi Gunarathna > Senior Software Engineer, > WSO2, Inc.; http://wso2.com <http://wso2> > Blog: http://hi-my-world.blogspot.com/ > Tel : 94 11 214 5345 > Fax :94 11 2145300 > > > > <http://lalajisureshika.blogspot.com/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: [email protected] P: +94 777542851
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
