Hello, > Stefano Mazzocchi wrote: > > > Now, how can this be handled? should we reverse the Source > interface and > > come up with a "Destination" (sort of InputStream/OutputStream > > parallel)? > > > > If this XML contained data, we could come up with an automatic > > relational mapping between the arriving XML and the SQL > update query on > > a RDBMS. It could be pretty straightforward. > > > > At the same time, how would you do such a thing on an > article stored on > > a native XML DB? > > > > As Jeremy pointed out, XUpdate is a choice. I must tell you > that I don't > > like XUpdate that much, but I admit it's a choice. > > > I badly need here someone to enlighten me. I was unable to > come up with > a use case where XSLT could not be used instead of XUpdate. > Admitedly, > XUpdate is easier, but I see no real advantage in using it > other than as > a more comfrotable way to express updates. Actually, when I was > proposing XUpdate I was scared by the fact that the one and only > implementation (Lexus) seemed to be dead, and I was thinking about > rewriting the XUpdate engine around on the fly XSLT generation and > Transformer APIs...
Just for information, as long i know the Lexus project donated the XUpdate implmentation to the XML:DB project. Thus the Lexus and XML:DB is under same roof. Max --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
