List Info

Thread: Saving information back to original XIncluded xml files
Saving information back to original XIncluded xml files
user name
 2006-12-21 23:10:54 

  


  

    





I posted this question earlier, but my email got bounced
because the server was not updated with my registration.  Hopefully it is
now.



 



Here is my question:  Is there or has there been any
work done on saving potentially changed XIncluded information back to original
files?  I know that URL’s can come from just about anywhere, but I
am only interested in loading and saving whole XIncluded xml files.  We
currently use xml files under Windows and QNX (using libxml2) for configuration
information and we have many different software configurations that could use the
XInclude technology to bring in software/machine specific information. 
Sometimes this information is modified and it needs to be saved back out to the
original XIncluded file.



 



Does anyone have an implementation for this? ; I have
started to code my own implementation by adding functionality to xmlsave, but
it requires that the href is not optional and I know there are limitations to
my implementation where I may or may not be handling the recursive nature of
xi:include and/or xi:fallback.



 



I thought I’d ask before continuing my implementation
to see if there was anyone out there that already had a working implementation.



 



Dean
Wittmann



Litrex
Corporation






  

  
  
   
     
    

  

    Saving information back to original
XIncluded xml files
  


  

     user name

     2006-12-26 12:34:40
  


  

    
On Thu, Dec 21, 2006 at 03:10:54PM -0800, Dean Wittmann
wrote:
> Here is my question:  Is there or has there been any
work done on saving
> potentially changed XIncluded information back to
original files?  I
> know that URL's can come from just about anywhere, but
I am only
> interested in loading and saving whole XIncluded xml
files.  We
> currently use xml files under Windows and QNX (using
libxml2) for
> configuration information and we have many different
software
> configurations that could use the XInclude technology
to bring in
> software/machine specific information.  Sometimes this
information is
> modified and it needs to be saved back out to the
original XIncluded
> file.

  Okay, in general this is not possible, because you can ask
to
include fragment(s) of XML resources.

> Does anyone have an implementation for this? 

  Not really for the reason above. You still have the 
XML_XINCLUDE_START and XML_XINCLUDE_END nodes in the tree
which may be
sufficient to find the boundaries.

> I have started to code my
> own implementation by adding functionality to xmlsave,
but it requires
> that the href is not optional and I know there are
limitations to my
> implementation where I may or may not be handling the
recursive nature
> of xi:include and/or xi:fallback.

  I think the fragmented and recursive nature of XInclude
makes the general
approach impossible, plus if you use remote resources it's
usually not possible
to save back content. So I'm afraid any implementation will
be way too
limited to really push it as a general feature, but having
the patch around
may be useful for others.

> I thought I'd ask before continuing my implementation
to see if there
> was anyone out there that already had a working
implementation.

  That sounds hard in the general case.

Daniel

-- 
Red Hat Virtualization group http://redhat.com/v
irtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillardredhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ |
Rpmfind RPM search engine  http://rpmfind.net/
_______________________________________________
xml mailing list, project page  http://xmlsoft.org/
xmlgnome.org
http://mai
l.gnome.org/mailman/listinfo/xml


  


  

    
  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )