Hi Carsten > I see currently two (minor) problems with Deli: > - the legacyDevice.xml contains profile references which are URIs. > As these URIs are served by Cocoon, they currently contain > the server name > and the server port (assuming localhost and 8080 is correct). > This is a bad dependency. It would be creat to have this > configuration > independent of the servlet context.
Some possible solutions - comments please? 1. Make profiles available as web resources: I can copy the legacy profiles to http://www-uk.hpl.hp.com/people/marbut/legacyProfiles Then we can update legacyDevices.xml to point to these profiles, keeping the old file (legacyDeviceFallback.xml ?) for folks behind firewalls / not connected to the internet? Possible issues here: I can't guarantee these profiles will be permanent web resources e.g. if HP web pages changes etc. Perhaps my web page is not the most appropriate place to site them but placing them somewhere else will be more difficult. 2. Alter the format of the legacydevice file: Is the real problem that the legacydevice file has to use repeated instances of the host name / port number? For example would a format that abstracted this information as a "profile repository" be better? E.G. <devices> <repository> <name>local</name> <host>http://localhost</host> <port>8080</port> <path>cocoon/legacyProfiles</path> <legacyDevice> <useragentstring>MSIE</useragentstring> <profileref>mieSample.rdf</profileref> </legacyDevice> <legacyDevice> <useragentstring>mozilla</useragentstring> <profileref>mozSample.rdf</profileref> </legacyDevice> </repository> </devices> Here, although localhost and port number are hard-coded, there is only one instance to alter? > - The "use-deli" configuration on the Deli component seems a > little bit > too much configuration possibilities. I think either > configuration Deli > as a component (or not) is enough. So you mean just get TraxTransformer to check if DELI is running and if so uses it? This is possible, assuming the code that looks up whether the DELI component is being managed now works e.g. if (this.manager.hasComponent(Deli.ROLE)) I asked Berin if I this was due to DELI or Avalon - I don't think I got a reply? I need to look at this in the current C2 CVS - I'm sorry I've been spending time on DELI rather than C2 end of last week - and see what the current situation is. The good news is though the new version of DELI has a number of improvements - (for folks who are interesed I enclose some details below) - so next step will be to integrate this with C2. Version 0.40 25/01/2002 - DELI can now read UAProf schemas and extract vocabulary descriptions from them. - DELI now uses Jena 1.3.0. - DELI now includes legacy profiles for Opera, Netscape and Amaya. - Made changes to TestCCPPClient so that it can send HTTP requests with a UAProf profile header but no UAProf profiles overrides. Version 0.31 22/01/2002 - Fixed problem with deliServletConfig.xml file. Version 0.30 21/01/2002 - DELI can now infer components from the attribute name / vocabulary description if the profile does not use <rdf:type> to identify components. This change was necessary to cope with the Ericsson T68 and T39 profiles. - DELI can be configured to deal with multiple vocabularies where each vocabulary corresponds to a different namespace URI. This allows it to deal with WAP 1.2 and WAP 2.0 profiles. - DELI no longer crashes if it encounters a profile attribute it does not recognises. best regards Mark H. Butler, PhD Research Scientist HP Labs Bristol --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
