libxmlplusplus-general — Open discusions about libXML++

Re: [libxml++] parse_stream with auto_ptr

[Christophe de V. <cde...@gm...>]

Hi,

Could you post a little program that reproduce your problem ?

2005/10/12, Tobias Grimm <lis...@e-...>:
> Hi!
>
> I try to use the dom parser in the following way:
>
>     ....
>     auto_ptr<istream> xmlStream(new stringstream("<foo/>"));
>     ....

Can you guarantee that the stream is untouch during the "..." ?

>     parser.parse_stream(*xmlStream);
>     ....
>
> But this always causes a segfault. And I have absolutely no idea why.
> This code works:
>
>     ....
>     auto_ptr<istream> xmlStream(new stringstream("<foo/>"));
>     ....
>     stringstream s;
>     s << (*xmlStream).rdbuf();
>     parser.parse_stream(s);
>     ....
>
> Any idea, why parse_stream() doesn't like the auto_ptr?

nope


Christophe

[libxml++] segmentation fault on solaris 10

[jane J <jan...@ya...>]

Hello,
 I'm a new user of libxml++ and solaris. I do need help for the 
following problem: 
 
 when I use libxml++1.0.1 on solaris 10, it had the sementation fault 
even I only tested the dom_parser example. I've already tried to put the "xmlpp::Document::Init init;" in the main program, but it alway remind me with a compile error of "the Init is 
private".  What shall I do to fix this problem? or if the later version of libxml++ had already fixed the problem?
 
By using gdb, the fault occured (for the dom_parser example) at line:
>  Glib::ustring nodename = node->get_name();
 in the method: 
> void print_node(const xmlpp::Node* node, unsigned int indentation =
0)
 
 Thank you very much!
 
 Jane


		
---------------------------------
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

[libxml++] parse_stream with auto_ptr

[Tobias G. <lis...@e-...>]

Hi!

I try to use the dom parser in the following way:

    ....
    auto_ptr<istream> xmlStream(new stringstream("<foo/>"));
    ....
    parser.parse_stream(*xmlStream);
    ....

But this always causes a segfault. And I have absolutely no idea why.
This code works:

    ....
    auto_ptr<istream> xmlStream(new stringstream("<foo/>"));
    ....
    stringstream s;
    s << (*xmlStream).rdbuf();
    parser.parse_stream(s);
    ....

Any idea, why parse_stream() doesn't like the auto_ptr?

Regards,

Tobias

[libxml++] branch 2.14

[Christophe de V. <cde...@gm...>]

Hi all,

I branched the cvs head to start working on XML schemas. The stable
branch name is gnome-2-14. From now, any fix on this branch should be
commited on the HEAD branch as well.

Regards,

Christophe

Re: [libxml++] XSD validation in SAX and xmlReader mode

[Daniel V. <vei...@re...>]

On Tue, Oct 11, 2005 at 10:16:45PM +0200, Christophe de VIENNE wrote:
> Hi Daniel,
> 
> Just to let you know that your message was not useless :-)
> 
> I hadn't time earlier to work on it, but I'm starting to look at the
> schemas support in libxml2 to add it to libxml++ 2.13.x

  cool, thanks :-)

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
vei...@re...  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

Re: [libxml++] XSD validation in SAX and xmlReader mode

[Christophe de V. <cde...@gm...>]

Hi Daniel,

Just to let you know that your message was not useless :-)

I hadn't time earlier to work on it, but I'm starting to look at the
schemas support in libxml2 to add it to libxml++ 2.13.x

Regards,

Christophe

2005/8/26, Daniel Veillard <vei...@re...>:
>  I'm not sure if any of the developpers looked at this, this was
> added in libxml2-2.6.20 and the possibility to validate with
> XML Schemas at the SAX flow level (or the reader). Streaming
> validation is an important feature for a number of uses.
>
> Daniel
>
> --
> Daniel Veillard      | Red Hat Desktop team http://redhat.com/
> vei...@re...  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
> http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Libxmlplusplus-general mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general
>

Re: [libxml++] ANNOUNCE: libxml++ 1.0.5

[Darko M. <da...@uv...>]

Christophe de VIENNE wrote:
> I'm very sorry I can't find this set in my mail archives. Do you still
> have it ? Can you send it again ?

I'll send you files tommorow. Thanks.

Darko


---
avast! Antivirus: Mensaje saliente limpio.
Base de datos de Virus (VPS): 0539-4, 02/10/2005
Comprobado el: 02/10/2005 04:15:54 p.m.
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com

Re: [libxml++] ANNOUNCE: libxml++ 1.0.5

[Christophe de V. <cde...@gm...>]

Hi Darko,

2005/9/29, Darko Miletic <da...@uv...>:
>
> I can see that set of Borland makefiles I sent you is not included. Is
> there a plan to do so?
>

I'm very sorry I can't find this set in my mail archives. Do you still
have it ? Can you send it again ?

Sorry about that, I'll include it as soon as I receive it.

Thanks,

Christophe

[libxml++] problem returning a node

[Josh T. <jos...@gm...>]

I have a domparser setup and it parses my xml file fine without any error. =
I
can transverse through the doc tree fine with
parser.get_document()->get_root_node()
and iterating using the recursion example provided in the docs.

What i am having trouble with is breaking up different parsing tasks into
functions.
In my function:

const xmlpp::Node* RssData::getElementTag(const xmlpp::Node* node, const
Glib::ustring tagname)
{
std::cout<<"Node loop: get_name()node: "<<node->get_name()<<std::endl;

xmlpp::Node::NodeList nlist =3D node->get_children();
if(!nlist.empty())
{
for(xmlpp::Node::NodeList::const_iterator itr =3D nlist.begin(); itr !=3D
nlist.end(); ++itr)
{
if((*itr)->get_name() =3D=3D tagname)
{
std::cout<<"Title tag found try to return"<<std::endl;
return (*itr);
}
else
getElementTag((*itr), tagname);
}
}
}

The function is able to find a matching node and will return without errors
but it does not return a valid address to a node in the doctree. I get a se=
g
fault after trying to use the node pased from getElementTag (eg
node->get_name() will segfault because it does not point to a valid
address).

the function is passed a const node pointer returned from
parser.get_document()->get_root_node() and a string tagname to match agains=
t
a node. It will transverse the tree till it finds a matching node and try t=
o
return a pointer to that node so it can be use elsewhere.
I'm not sure if nodelist is a copy of node's children and thus when the
function ends they are no longer accessible, but i understand them to be a
list<node*> right?
I am sorry if this is a simple logic error, just trying to get past this.

Re: [libxml++] ANNOUNCE: libxml++ 1.0.5

[Darko M. <da...@uv...>]

Christophe de VIENNE wrote:
> *** libxml++
> 
>   libxml++ is a C++ wrapper for the libxml XML parser library. It has SAX
>   and DOM-like APIs, but does not attempt to conform exactly to the DOM
>   specifications because they are not aimed at C++. Its API is much
>   simpler than the underlying libxml C API.
> 
> *** Changes
> 
> This is a maintenance release
> 
> * Fixed warnings with borland compilers (thanks to Darko Miletic)
> * Fixed issue #161925: "Inefficency in Node::find"
> * Fixed issue #162350: "gcc-3.4 new pedantic behavior"
> * Fixed issue #150082: "Memory Leak in DomParser"

I can see that set of Borland makefiles I sent you is not included. Is 
there a plan to do so?


Darko

[libxml++] ANNOUNCE: libxml++ 1.0.5

[Christophe de V. <cde...@ne...>]

*** libxml++

  libxml++ is a C++ wrapper for the libxml XML parser library. It has SAX
  and DOM-like APIs, but does not attempt to conform exactly to the DOM
  specifications because they are not aimed at C++. Its API is much
  simpler than the underlying libxml C API.

*** Changes

This is a maintenance release

* Fixed warnings with borland compilers (thanks to Darko Miletic)
* Fixed issue #161925: "Inefficency in Node::find"
* Fixed issue #162350: "gcc-3.4 new pedantic behavior"
* Fixed issue #150082: "Memory Leak in DomParser"


*** Download

You can download libxml++ from here:
http://ftp.gnome.org/pub/GNOME/sources/libxml++/1.0/


Christophe de Vienne

[libxml++] libxml++ 2.12.0

[Christophe de V. <cde...@gm...>]

*** libxml++
=20
  libxml++ is a C++ wrapper for the libxml XML parser library. It has SAX
  and DOM-like APIs, but does not attempt to conform exactly to the DOM
  specifications because they are not aimed at C++. Its API is much
  simpler than the underlying libxml C API.
=20
 libxml++ is part of the GNOME Platform Bindings and follows the GNOME=20
 release schedule:
 http://live.gnome.org/ReleasePlanning/TwoPointEleven
=20
=20
 *** Changes

* Added the state "Reading" to xml Reader States list.
=20
 *** Homepage
=20
 http://libxmlplusplus.sourceforge.net/
=20
 *** Download
=20
 You can download libxml++ from here:
 http://ftp.gnome.org/pub/gnome/sources/libxml++/2.12/
=20
=20
=20
 Regards,
=20
 Christophe

[libxml++] 2.12.0 soon

[Christophe de V. <cde...@gm...>]

Hi all,

Before releasing the 2.12.0 version, I'd like to known if some of you
successfully used the 2.11.0, which was released not long ago
(probably not long enough to be sure there is no problem with it, so
I'm asking).

Thanks,

Christophe

RE: [libxml++] Failure Building Libxml++ on FC 3

[Tom B. <tbr...@co...>]

My bad.

After rooting around some more, I found an old libxml-2.0 pkg-config *.pc
file which was messing up configure.

The build works now that the old pc file was removed.

Sorry about the false alarm--I look forward to using the package.

Tom Browder

[libxml++] Failure Building Libxml++ on FC 3

[Tom B. <tbr...@co...>]

I have not been able to successfully build libxml++ on FC 3, although I can
build all the prereqs.

I have a libxml2 snapshot installed, and I get no failures from the
configure step.  But when starting the make, the build fails immediately.

It appears to me that the libxml2 include files are rooted at
/usr/include/libxml2/libxml and the libxml++ build system cannot find them.
I would like to be able to decipher the automake system but get lost in
trying to track the source of variables.

Does anyone have any suggestions?  I have seen a message from an FC
developer that states that the build system is "broken."

Thanks.

Tom Browder

Re: [libxml++] ANNOUNCE: libxml++ 2.11.0

[Christophe de V. <cde...@gm...>]

2005/8/29, Darko Miletic <da...@uv...>:
> Christophe de VIENNE wrote:
> > *** libxml++
>=20
> No updates to libxml++ 1.x branch? What happened to the update for
> Borland compiler I submitted here?
>=20

It's commited in the 1.0.x branch, on which no maintenance release has
been done yet. It should be done shortly though.

Regards,

Christophe

Re: [libxml++] ANNOUNCE: libxml++ 2.11.0

[Darko M. <da...@uv...>]

Christophe de VIENNE wrote:
> *** libxml++

No updates to libxml++ 1.x branch? What happened to the update for 
Borland compiler I submitted here?

Darko

[libxml++] XSD validation in SAX and xmlReader mode

[Daniel V. <vei...@re...>]

 I'm not sure if any of the developpers looked at this, this was
added in libxml2-2.6.20 and the possibility to validate with
XML Schemas at the SAX flow level (or the reader). Streaming 
validation is an important feature for a number of uses.

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
vei...@re...  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

[libxml++] extra enum entry in TextReader.h

[sebastian m. <s....@ro...>]

Didn't want to bugzilla it as it's so minor...


possible minor inclusion for xmlpp::TextReader::xmlReadState in
TextReader.h:

    enum xmlReadState
    {
    /*
     * see xmlreader.h:
     *     XML_TEXTREADER_MODE_INITIAL = 0,
     *     XML_TEXTREADER_MODE_INTERACTIVE = 1,
     *     XML_TEXTREADER_MODE_ERROR = 2,
     *     XML_TEXTREADER_MODE_EOF =3,
     *     XML_TEXTREADER_MODE_CLOSED = 4,
     *     XML_TEXTREADER_MODE_READING = 5
     */

      Reading = 5,	// might want to add this line
      Closed = 4,
      EndOfFile = 3,
      Error = 2,
      Initial = 0,
      Interactive = 1
    };

regards,

seb

Re: [libxml++] "unimplemented block" - xmlreader.c

[Daniel V. <vei...@re...>]

On Thu, Aug 18, 2005 at 11:32:12AM +0930, sebastian moss wrote:
> hi everyone,
> 	i've been using libxml++ 2.10 but am having a problem using
> TextReader::read_inner/outer_xml(); on execution it spits out 
> 
> 	'Unimplemented block at xmlreader.c:1578'
> 
> I've tried rebuilding/reinstalling the libraries (no errors) but to no
> avail. Any pointers??

  Make sure your have a recent libxml2 version.
If you still have it with 2.6.20 try to reproduce it with xmllint --stream
(and possibly other options) and bugzilla it or send it here with the
associated data
    http://xmlsoft.org/bugs.html

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
vei...@re...  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

[libxml++] "unimplemented block" - xmlreader.c

[sebastian m. <s....@ro...>]

hi everyone,
	i've been using libxml++ 2.10 but am having a problem using
TextReader::read_inner/outer_xml(); on execution it spits out 

	'Unimplemented block at xmlreader.c:1578'

I've tried rebuilding/reinstalling the libraries (no errors) but to no
avail. Any pointers??

Sebastian Moss

Re: [libxml++] Using SAX with XPath

[Stefan S. <se...@sy...>]

tikcireviva wrote:
> Hi Everyone,
> 
> After going through a couple examples, I found that the XPath feature is 
> pretty handy. And I wonder why there is XPath example for DOM instead of 
> SAX?

To be able to look up nodes via xpath expressions you need a dom tree to
navigate to match the pattern from the expression. These patterns can
become arbitrarily complex and they typically involve nodes far appart
in the document (or even across multiple documents !), so matching with
a stream-based protocol would be very hard (you would have to reread the
stream over and over again).

Regards,
		Stefan

[libxml++] Using SAX with XPath

[tikcireviva <tik...@ya...>]

Hi Everyone,

After going through a couple examples, I found that the XPath feature is 
pretty handy. And I wonder why there is XPath example for DOM instead of 
SAX? If libxml++ do support this feature, could you mind show me any 
examples or a way to tackle this?

While playing with the XPath example, I have enountered some 
difficulties in order to extract the value from "my-xpath". For 
instance, let's say if I have the following xml-like input.

    <title>A section</title>

And I have this XPath '/title', how can I get the 'A section' value from 
a node? (A node/nodeset should be in this type 'xmlpp::NodeSet' 
according to the example)
I know this is a really dumb question, and I am really hoping that you 
guys could give me a helping hand. Thank you very much.

Best wishes,

-tikcireviva.

Re: [libxml++] Compiling libxml++ example (myparser) in VC6.0

[tikcireviva <tik...@ya...>]

Thanks Darko, that helps either. Thank you very much.

-tikcireviva

Darko Miletic wrote:

> tikcireviva wrote:
>
>> I wonder if version 1.04 do support double-bytes characters or not. 
>> It seems to me that using glibmm is the only solution, am I right? 
>> Anyway, I will try version 1.04. Thank you for your suggestions.
>
>
> Version 1.04 does not support unicode, but it can work fine with utf-8 
> because it can be stored in std::string.
> The question is do you really need utf-16 or utf-32? In 98% percent of 
> cases the answer is no.
>
> Darko
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
> & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Libxmlplusplus-general mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libxmlplusplus-general
>

Re: [libxml++] Compiling libxml++ example (myparser) in VC6.0

[Darko M. <da...@uv...>]

tikcireviva wrote:
> I wonder if version 1.04 do support double-bytes characters or not. It 
> seems to me that using glibmm is the only solution, am I right? Anyway, 
> I will try version 1.04. Thank you for your suggestions.

Version 1.04 does not support unicode, but it can work fine with utf-8 
because it can be stored in std::string.
The question is do you really need utf-16 or utf-32? In 98% percent of 
cases the answer is no.

Darko