On Tue, 2003-09-09 at 17:02, Geoff Howard wrote: > Bruno Dumon wrote: > > (catching up on block discussions...) > > > > On Fri, 2003-08-29 at 05:53, Geoff Howard wrote: > > <snip/> > > > >>>Implementation Phases > >>>--------------------- > >>> > >>>Phase 1: definition of the contract between the block manager inside > >>>cocoon and the standalone block deployer. These contracts include: > >>> > >>> 1) description of the file system layout (see above for a suggestion) > >>> 2) description of the wiring document schema > >>> 3) description of the block metadata schema > >> > >>Ok, the file system seems fine - how about starting the discussion with > >>the following for the wiring document? (I'm assuming stuff will have to > >>change - just trying to get the ball rolling) > >> > >><?xml version="1.0" encoding="UTF-8"?> > >><blocks version="1.0"> > >> <block uri="cob:mycompany.com/webmail/1.3.43" wire-id="384938958499"> > >> <mount>/mail/</mount> > >> <connections> > >> <connection > >>name="external-skin">cob:yetanothercompany.com/skins/fancy/1.2.2</connection> > >> <connection > >>name="internal-skin">cob:mycompany.com/skins/corporate/34.3.345</connection> > >> <connection > >>name="repository">cob:mycompany.com/repositories/email/exchange/3.2.1</connection> > >> </connections> > >> <configuration> > >> <param name="user">guest</param> > >> <param name="password">sj3u493</param> > >> </configuration> > >> </block> > >> <block uri="cob:mycompany.com/repositories/email/exchange/3.2.1" > >>wire-id="394781274834"> > >> <configuration> > >> <param name="host">mail.blah.org</param> > >> </configuration> > >> </block> > >> <block uri="cob:yetanothercompany.com/skins/fancy/1.2.2" > >>wire-id="947384127832"/> > >> <block uri="cob:mycompany.com/skins/corporate/34.3.345" > >>wire-id="746394782637"/> > >></blocks> > >> > >>Wiki'd here: http://wiki.cocoondev.org/Wiki.jsp?page=BlocksWiring > >> > >>For sake of discussion, I recorded a wire-id instead of the location. > >>Can blocks be in other locations other than WEB-INF/blocks/{$wire-id} ? > >> > >>I also considered recording the wire-id instead of the uri for > >>connections between blocks - what are the arguments for each? > >> > >><connection> was out of the blue using the wiring metaphore. Other > >>options? Free association: connect, attach, solder, wire, use ... > > > > Avalon Phoenix uses the words "assembly" and "provide" instead of > > "wiring" and "connection", which I quite like (I mean the assembly & > > provide). > > I don't quite see where these terms would be used - can you explain a > little more? Maybe a proposed set of changes to the example above? >
Yep. I meant that the connection tag would become provide: <provide name="external-skin">cob:yetanothercompany.com/skins/fancy/1.2.2</provide> And the wiring.xml would be called assembly.xml OTOH, I'm meanwhile becoming accustomed to the wiring and connection terms, so let's leave it as wiring and connection for now. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
