> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > Hi Mark, > > > Mark Butler wrote: > > > > <snip/> > > > > 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? > > > > This would make the configuration definitly a lot easier. But it > would be great if Deli could use the SourceResolver of Cocoon, so you > could write: > <profileref>cocoon://mieSample.rdf</profile> > > Currently there a two possibilities to get the SourceResolver: > - the easiest (bug ugliest?) is to pass add the source resolver to the > methods of the Deli component interface, so with each invokation it > is passed on to the deli component. > - The Deli component can implement the RequestLifecycleComponent interface > and get the SourceResolver throught this interface, but then Deli can > not be ThreadSafe any longer.
- Or Use URLFactorySourceResolver, and leave Deli Threadsafe. Deli resources are request-independent, so there is no need for resolving via Environment here. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
