tag:old.nabble.com,2006:forum-2923Nabble - Web Services2009-12-03T04:49:46ZWeb services are Web based applications that use open, XML-based standards and transport protocols to exchange data with clients.tag:old.nabble.com,2006:post-26625484Re: Issues (Dispatcher Error/FilteringNotSupported)2009-12-03T04:49:46Z2009-12-03T04:49:46ZTill Steinbach-2Hi again,
<br><br>Am 03.12.2009 um 12:42 schrieb Klaus Kaempf:
<br>> * Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26625484&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Dec 03. 2009 03:42]:
<br>>>
<br>>> Klaus, would it be possible to rev up the build for openwsman-2.2.1 after
<br>>> applying this fix?
<br>>
<br>> Committed as svn rev 3318.
<br><br>That fixes my segfault problem. Thanks!
<br><br>But I have still a problem with the subscription via localInterface.
<br><br>The same query that works for the cim-xml interface produces a "wsa:DestinationUnreachable" "lter not found" Message (Well the "Fi" is really missing in the response!).
<br><br>Openwsman says:
<br>create CIM_IndicationFilter() rc=0, msg=(null)
<br>create CIM_IndicationHandlerCIMXML() rc=0, msg=(null)
<br>create CIM_IndicationSubscription() rc=6, msg=Filter not found
<br><br><br>Till
<br><br /> <br />------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26625484&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26625484/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26624697Re: Issues (Dispatcher Error/FilteringNotSupported)2009-12-03T03:42:40Z2009-12-03T03:42:40ZKlaus Kaempf* Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26624697&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Dec 03. 2009 03:42]:
<br>>
<br>> Klaus, would it be possible to rev up the build for openwsman-2.2.1 after
<br>> applying this fix?
<br><br>Committed as svn rev 3318.
<br><br>I'll fix the tarball later today.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26624697&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26620167Re: Issues (Dispatcher Error/FilteringNotSupported)2009-12-02T18:42:19Z2009-12-02T18:42:19ZSuresh Sundriyal-2Sorry about not replying to this earlier, I've not been paying much
<br>attention to my emails over the thanksgiving break.
<br><br>Looks like this was an end result of my stupidity. It seems to be caused
<br>by my fix for Bug 220. I was working off of two svn clients from work and
<br>home and managed to screw up a simple copy paste job, as a result of which
<br>I'm passing in the Body node to ws_xml_get_child(), instead of the
<br>PullResponse node, which returns NULL since Items are a child node of
<br>PullResponse and not the Body node.
<br><br>I'm surprised that nobody else has complained about this yet.
<br><br>I'm attaching a fix for this along with the email.
<br><br>Klaus, would it be possible to rev up the build for openwsman-2.2.1 after
<br>applying this fix?
<br><br>I apologize for the inconvenience.
<br><br>--
<br>Suresh
<br><br><br>-----Original Message-----
<br>From: Till Steinbach [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26620167&i=0" target="_top" rel="nofollow">till.steinbach@...</a>]
<br>Sent: Thursday, November 26, 2009 2:04 AM
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26620167&i=1" target="_top" rel="nofollow">openwsman-devel@...</a>
<br>Subject: Re: [Openwsman-devel] Issues (Dispatcher Error/FilteringNotSupported)
<br><br><br>Am 23.11.2009 um 21:17 schrieb Klaus Kaempf:
<br>>> Seems there is an incomplete message?!? In the wireshark traffic
<br>>> everything looks fine
<br>>
<br>> Please run sfcbd with "-t 512" to catch the indication provider debug.
<br><br>Please see: <a href="http://nopaste.info/289f22082a.html" target="_top" rel="nofollow">http://nopaste.info/289f22082a.html</a><br><br>>
<br>>>
<br>>> Strange thing:
<br>>> I may have a strange repository in sfcb now, because of several subscriptions. When I do an enumerate with "Select * from CIM_IndicationSubscription" my openwsman and my wsmancli die with a segfault after the EnumerationResponse that contains the EnumerationContext!
<br>>
<br>> Uhm, never heard about this before. Anyways, neither tool should just
<br>> crash. Try to get a core dump (might need "ulimit -c unlimited"
<br>> before) and analyze with gdb.
<br><br>This happens only with the local interface. I tried to debug with the coredump, but I'm not yet very familiar with openwsman.
<br><br>The Problem might be in wsenum_pull_direct_stub (wsman-soap.c:1265).
<br><br>ws_xml_get_child returns a NULL-pointer but enumInfo->totalItems is 4 this results later in a segfault in xml_parser_add() at wsman-libxml2-binding.c
<br><br><br><br><br>Till
<br><br /> <br />------------------------------------------------------------------------------
<br>Join us December 9, 2009 for the Red Hat Virtual Experience,
<br>a free event focused on virtualization and cloud computing.
<br>Attend in-depth sessions from your desk. Your couch. Anywhere.
<br><a href="http://p.sf.net/sfu/redhat-sfdev2dev" target="_top" rel="nofollow">http://p.sf.net/sfu/redhat-sfdev2dev</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26620167&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>enum-segfault-fix.diff</strong> (768 bytes) <a href="http://old.nabble.com/attachment/26620167/0/enum-segfault-fix.diff" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26527030Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-26T02:04:03Z2009-11-26T02:04:03ZTill Steinbach-2<br>Am 23.11.2009 um 21:17 schrieb Klaus Kaempf:
<br>>> Seems there is an incomplete message?!? In the wireshark traffic everything looks fine
<br>>
<br>> Please run sfcbd with "-t 512" to catch the indication provider debug.
<br><br>Please see: <a href="http://nopaste.info/289f22082a.html" target="_top" rel="nofollow">http://nopaste.info/289f22082a.html</a><br><br>>
<br>>>
<br>>> Strange thing:
<br>>> I may have a strange repository in sfcb now, because of several subscriptions. When I do an enumerate with "Select * from CIM_IndicationSubscription" my openwsman and my wsmancli die with a segfault after the EnumerationResponse that contains the EnumerationContext!
<br>>
<br>> Uhm, never heard about this before. Anyways, neither tool should just
<br>> crash. Try to get a core dump (might need "ulimit -c unlimited"
<br>> before) and analyze with gdb.
<br><br>This happens only with the local interface. I tried to debug with the coredump, but I'm not yet very familiar with openwsman.
<br><br>The Problem might be in wsenum_pull_direct_stub (wsman-soap.c:1265).
<br><br>ws_xml_get_child returns a NULL-pointer but enumInfo->totalItems is 4 this results later in a segfault in xml_parser_add() at wsman-libxml2-binding.c
<br><br><br><br><br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26527030&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26527030/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26497853Openwsman 2.2.1 is now available !2009-11-24T07:23:28Z2009-11-24T07:23:28ZKlaus KaempfHi,
<br><br>its my pleasure to announce availability of Openwsman 2.2.1 !
<br><br>This release has seen quite some changes and improvements:
<br><br>- Major changes:
<br> - Enumeration timeout fixed, resulting in --enum-idle-timeout option
<br> to openwsmand taking seconds (instead of miliseconds) now
<br> - Client side CRL (certificate revocation list) support (Arun Venkatachalam)
<br> - split off client config as /etc/openwsman/openwsman_client.conf
<br> - Fix upper limit check for threads and their stack usage (Suresh Sundriyal)
<br> (Allowing to confine memory usage in the 10-20MB range!)
<br> Reintroduce max_thread config file parameter and two new parameters
<br> * max_connections_per_thread
<br> * thread_stack_size
<br>- Minor changes:
<br> - require swig 1.3.30 or later (rhel5 users: upgrade !)
<br> - clean up fault generation in CIM backend (Suresh Sundriyal)
<br> - fix various memory leaks (Suresh Sundriyal)
<br> - fix Python bindings build (kkaempf)
<br> - Fix security risk when listing indication subscriptions (Suresh Sundriyal)
<br> - Fix xml namespace for enumeration and subscription filters (kkaempf)
<br> - Fix class names for swig bindings, makes Python bindings operational (kkaempf)
<br> - Use same encoding for faults as in incoming msg (bug305, kkaempf)
<br> - Make WS-Enumeration pull response comply to WS-Enumeration sequence
<br> ordering (Suresh Sundriyal)
<br>
<br>Special thanks to all contributors and testers !!
<br><br>Download it at
<br><a href="http://sourceforge.net/projects/openwsman/files/openwsman/2.2.1/openwsman-2.2.1.tar.bz2/download" target="_top" rel="nofollow">http://sourceforge.net/projects/openwsman/files/openwsman/2.2.1/openwsman-2.2.1.tar.bz2/download</a><br><br>Pre-build packages for the most widely used Linux distributions will be
<br>made available through the openSUSE build service at
<br><a href="https://build.opensuse.org/package/show?package=openwsman&project=systemsmanagement%3Awbem" target="_top" rel="nofollow">https://build.opensuse.org/package/show?package=openwsman&project=systemsmanagement%3Awbem</a><br><br>Enjoy !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26497853&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26485113Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T12:17:49Z2009-11-23T12:17:49ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26485113&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 15:01]:
<br><br>> Pleas see the output here: <a href="http://nopaste.info/c5a2103bcd.html" target="_top" rel="nofollow">http://nopaste.info/c5a2103bcd.html</a><br><br>Looks fine to me.
<br><br>> Seems there is an incomplete message?!? In the wireshark traffic everything looks fine
<br><br>Please run sfcbd with "-t 512" to catch the indication provider debug.
<br><br>>
<br>> Strange thing:
<br>> I may have a strange repository in sfcb now, because of several subscriptions. When I do an enumerate with "Select * from CIM_IndicationSubscription" my openwsman and my wsmancli die with a segfault after the EnumerationResponse that contains the EnumerationContext!
<br><br>Uhm, never heard about this before. Anyways, neither tool should just
<br>crash. Try to get a core dump (might need "ulimit -c unlimited"
<br>before) and analyze with gdb.
<br><br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26485113&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26478566Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T06:01:04Z2009-11-23T06:01:04ZTill Steinbach-2<br>Am 23.11.2009 um 13:08 schrieb Klaus Kaempf:
<br>> * Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26478566&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 12:26]:
<br>>>
<br>>>>
<br>>>> Also try to run sfcbd with "-t 0x0001000" (dumps incoming xml) or
<br>>>> "-t 0x0021000" (logs xml processing).
<br>>> Well, there is no output since the local interface does not rely on xml. Right?
<br>>> Do you mean the output when I try the (working) config via CIM-XML?
<br>>
<br>> Right. I still assume some string escaping bug.
<br><br>Pleas see the output here: <a href="http://nopaste.info/c5a2103bcd.html" target="_top" rel="nofollow">http://nopaste.info/c5a2103bcd.html</a><br>Seems there is an incomplete message?!? In the wireshark traffic everything looks fine
<br><br>Strange thing:
<br>I may have a strange repository in sfcb now, because of several subscriptions. When I do an enumerate with "Select * from CIM_IndicationSubscription" my openwsman and my wsmancli die with a segfault after the EnumerationResponse that contains the EnumerationContext!
<br><br><br>Very weird here!
<br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26478566&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26478566/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26477949Feature Request: indication_baseclass_namespace2009-11-23T05:21:32Z2009-11-23T05:21:32ZTill Steinbach-2Problem:
<br>With the current openwsman config-options it is impossible to configure a situation with multiple indication source namespaces.
<br>The namespace that is passed via wsman is used to tell sfcb the location of the Indication Hander/Filter/Subscription classes. Since the wsman client is in most cases unaware of the namespace that should be used in the present config, the default namespace must be set to this namespace. In general this is the root/interop namespace. That situation makes the usage inconvenient for standard queries for example to classes in root/cimv2.
<br><br>Here is my proposal:
<br><br>When the config contains an indication_baseclass_namespace option (to be added) the Hander/Filter/Subscription classes are taken from that namespace. The namespace that is passed in the wsman request is used to specify the indication source namespace (the default indication source namespace can still be configured via the indication_source_namespace option). When no namespace is passed in the request the indication source namespace is assumed to be the default namespace.
<br><br>When there is no indication_baseclass_namespace option openwsman behaves in the way of the current release.
<br><br>Comments, hints, enhancement are desired!
<br><br>Regards
<br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26477949&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26477949/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26476939Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T04:08:46Z2009-11-23T04:08:46ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476939&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 12:26]:
<br>>
<br>> >
<br>> > Also try to run sfcbd with "-t 0x0001000" (dumps incoming xml) or
<br>> > "-t 0x0021000" (logs xml processing).
<br>> Well, there is no output since the local interface does not rely on xml. Right?
<br>> Do you mean the output when I try the (working) config via CIM-XML?
<br><br>Right. I still assume some string escaping bug.
<br><br>>
<br>> Is it interesting to see the providers debug output?
<br>> There is no debug option for local interface. right?
<br><br>There is one for indication providers, run sfcbd with "-t 512" and
<br>watch for "interopProvider.c" messages
<br><br>>
<br>>
<br>> > I just tried to reproduce this problem and failed.
<br>> Hmmm, hope it's not my bad vibrations ;)
<br><br>:-)
<br><br>>
<br>> > Which version of sfcb are you running ?
<br>> sfcb 1.3.5
<br>Also recent, good.
<br><br>> > Which providers have you installed ?
<br>> sblime base providers with Indication support (1.6.0)
<br><br>These I don't have, yet.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476939&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26476297Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T03:26:11Z2009-11-23T03:26:11ZTill Steinbach-2<br>Am 23.11.2009 um 12:04 schrieb Klaus Kaempf:
<br>> My suspicion is wrong escaping in processing the xml message. This
<br>> would explain difference in behaviour of cimxml vs. sfcblocal.
<br>>
<br>> Add "-R" (resp. "--print-request") to the wsman command line to have
<br>> it dump the request.
<br>Here is the Request:
<br><br><?xml version="1.0"?>
<br><s:Envelope xmlns:s="<a href="http://www.w3.org/2003/05/soap-envelope" target="_top" rel="nofollow">http://www.w3.org/2003/05/soap-envelope</a>"
<br>xmlns:wsa="<a href="http://schemas.xmlsoap.org/ws/2004/08/addressing" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing</a>"
<br>xmlns:wsman="<a href="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd</a>"
<br>xmlns:wse="<a href="http://schemas.xmlsoap.org/ws/2004/08/eventing" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/eventing</a>">
<br> <s:Header>
<br> <wsa:Action
<br>s:mustUnderstand="true"><a href="http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe</a></wsa:Action>
<br> <wsa:To s:mustUnderstand="true"><a href="http://localhost:5985/wsman" target="_top" rel="nofollow">http://localhost:5985/wsman</a></wsa:To>
<br> <wsman:ResourceURI
<br>s:mustUnderstand="true"><a href="http://schemas.dmtf.org/wbem/wscim/1/*" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wscim/1/*</a></wsman:ResourceURI>
<br> <wsa:MessageID
<br>s:mustUnderstand="true">uuid:c16ff727-7907-1907-8002-d60a06290c00</wsa:MessageID>
<br> <wsa:ReplyTo>
<br> <wsa:Address><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a></wsa:Address>
<br><br> </wsa:ReplyTo>
<br> <wsman:SelectorSet>
<br> <wsman:Selector Name="__cimnamespace">root/interop</wsman:Selector>
<br> </wsman:SelectorSet>
<br> </s:Header>
<br> <s:Body>
<br> <wse:Subscribe>
<br> <wse:Delivery Mode="<a href="http://schemas.dmtf.org/wbem/wsman/1/wsman/Pull" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/wsman/Pull</a>">
<br> <wse:NotifyTo>
<br> <wsa:Address><a href="http://test.de/" target="_top" rel="nofollow">http://test.de/</a></wsa:Address>
<br> </wse:NotifyTo>
<br> </wse:Delivery>
<br> <wse:Expires>PT600.000000S</wse:Expires>
<br> <wsman:Filter
<br>Dialect="<a href="http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf</a>">SELECT * FROM
<br>CIM_ProcessIndication</wsman:Filter>
<br> </wse:Subscribe>
<br> </s:Body>
<br></s:Envelope>
<br><br><br>>
<br>> Also try to run sfcbd with "-t 0x0001000" (dumps incoming xml) or
<br>> "-t 0x0021000" (logs xml processing).
<br>Well, there is no output since the local interface does not rely on xml. Right?
<br>Do you mean the output when I try the (working) config via CIM-XML?
<br><br>Is it interesting to see the providers debug output?
<br>There is no debug option for local interface. right?
<br><br><br>> I just tried to reproduce this problem and failed.
<br>Hmmm, hope it's not my bad vibrations ;)
<br><br>> Which version of sfcb are you running ?
<br>sfcb 1.3.5
<br>> Which providers have you installed ?
<br>sblime base providers with Indication support (1.6.0)
<br><br><br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476297&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26476297/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26476208Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T03:17:38Z2009-11-23T03:17:38ZKlaus Kaempf* Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476208&i=0" target="_top" rel="nofollow">kkaempf@...</a>> [Nov 23. 2009 12:05]:
<div class='shrinkable-quote'><br>> * Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476208&i=1" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 11:50]:
<br>> >
<br>> > Am 23.11.2009 um 10:42 schrieb Klaus Kaempf:
<br>> > >> Is this issue openwsman or sfcb related?
<br>> > >
<br>> > > Neither ;-) It looks more like a sfcc problem.
<br>> > > Which version of sfcc are you using ?
<br>> > sfcc 2.2.1
<br>>
<br>> Good, thats a recent version.
<br>>
<br>> > <s:Fault>
<br>> > <s:Code>
<br>> > <s:Value>s:Sender</s:Value>
<br>> > <s:Subcode>
<br>> > <s:Value>wsa:DestinationUnreachable</s:Value>
<br>> > </s:Subcode>
<br>> > </s:Code>
<br>> > <s:Reason>
<br>> > <s:Text xml:lang="en">Filter not found</s:Text>
<br>> ^^^^^^^^^^^^^^^^
<br>>
<br>> This points to sfcb, namely 'interopProvider.c'
<br>>
<br>> My suspicion is wrong escaping in processing the xml message. This
<br>> would explain difference in behaviour of cimxml vs. sfcblocal.
</div><br>I just tried to reproduce this problem and failed.
<br><br>Which version of sfcb are you running ?
<br>Which providers have you installed ?
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476208&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26476033Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T03:04:45Z2009-11-23T03:04:45ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476033&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 11:50]:
<br>>
<br>> Am 23.11.2009 um 10:42 schrieb Klaus Kaempf:
<br>> >> Is this issue openwsman or sfcb related?
<br>> >
<br>> > Neither ;-) It looks more like a sfcc problem.
<br>> > Which version of sfcc are you using ?
<br>> sfcc 2.2.1
<br><br>Good, thats a recent version.
<br><br>> <s:Fault>
<br>> <s:Code>
<br>> <s:Value>s:Sender</s:Value>
<br>> <s:Subcode>
<br>> <s:Value>wsa:DestinationUnreachable</s:Value>
<br>> </s:Subcode>
<br>> </s:Code>
<br>> <s:Reason>
<br>> <s:Text xml:lang="en">Filter not found</s:Text>
<br> ^^^^^^^^^^^^^^^^
<br><br>This points to sfcb, namely 'interopProvider.c'
<br><br>My suspicion is wrong escaping in processing the xml message. This
<br>would explain difference in behaviour of cimxml vs. sfcblocal.
<br><br>Add "-R" (resp. "--print-request") to the wsman command line to have
<br>it dump the request.
<br><br>Also try to run sfcbd with "-t 0x0001000" (dumps incoming xml) or
<br>"-t 0x0021000" (logs xml processing).
<br><br>Hth,
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26476033&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26475862Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T02:49:13Z2009-11-23T02:49:13ZTill Steinbach-2<br>Am 23.11.2009 um 10:42 schrieb Klaus Kaempf:
<br>>> Is this issue openwsman or sfcb related?
<br>>
<br>> Neither ;-) It looks more like a sfcc problem.
<br>> Which version of sfcc are you using ?
<br>sfcc 2.2.1
<br>>> How can I contribute to solve the issue?
<br><br>> Provide a full, reproducible test case.
<br>Here is the Situation where the problem appears:
<br><br>My wsman test query:
<br>wsman -P 5985 -u abc -p abc123 subscribe <a href="http://schemas.dmtf.org/wbem/wscim/1/*" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wscim/1/*</a> -x "SELECT * FROM CIM_ProcessIndication" -D "<a href="http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf</a>"
<br>-N root/interop -Z <a href="http://test.de/" target="_top" rel="nofollow">http://test.de/</a> -G pull -r 600
<br><br>My openwsman config:
<br>#--------------------------------------------------------------------------------------
<br>[server]
<br>port = 5985
<br>ssl_cert_file = /etc/openwsman/servercert.pem
<br>ssl_key_file = /etc/openwsman/serverkey.pem
<br>basic_password_file = /usr/local/etc/openwsman/simple_auth.passwd
<br>min_threads = 4
<br>max_threads = 10
<br><br>[client]
<br>port = 5985
<br>agent = openwsman 2.2.0
<br><br>[cim]
<br>default_cim_namespace = root/interop
<br><br># can also be SfcbLocal for local connection with sfcb CIMOM running on
<br>same system
<br>#cim_client_frontend = XML
<br>cim_client_frontend = SfcbLocal
<br><br>vendor_namespaces = ABC=<a href="http://schema.abc.com/wbem/wscim/1/cim-schema/2" target="_top" rel="nofollow">http://schema.abc.com/wbem/wscim/1/cim-schema/2</a>,
<br>Linux=<a href="http://sblim.sf.net/wbem/wscim/1/cim-schema/2" target="_top" rel="nofollow">http://sblim.sf.net/wbem/wscim/1/cim-schema/2</a><br>#--------------------------------------------------------------------------------------
<br>The response:
<br><?xml version="1.0" encoding="UTF-8"?>
<br><s:Envelope xmlns:s="<a href="http://www.w3.org/2003/05/soap-envelope" target="_top" rel="nofollow">http://www.w3.org/2003/05/soap-envelope</a>"
<br>xmlns:wsa="<a href="http://schemas.xmlsoap.org/ws/2004/08/addressing" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing</a>">
<br> <s:Header>
<br> <wsa:To><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a></wsa:To>
<br> <wsa:Action><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/fault" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</a></wsa:Action>
<br> <wsa:RelatesTo>uuid:5ebbcf52-7906-1906-8002-d60a06290c00</wsa:RelatesTo>
<br> <wsa:MessageID>uuid:5ecb96cf-7906-1906-8012-d60a06290c00</wsa:MessageID>
<br> </s:Header>
<br> <s:Body>
<br> <s:Fault>
<br> <s:Code>
<br> <s:Value>s:Sender</s:Value>
<br> <s:Subcode>
<br> <s:Value>wsa:DestinationUnreachable</s:Value>
<br> </s:Subcode>
<br> </s:Code>
<br> <s:Reason>
<br> <s:Text xml:lang="en">Filter not found</s:Text>
<br> </s:Reason>
<br> </s:Fault>
<br> </s:Body>
<br></s:Envelope>
<br><br>When you change the lines:
<br><br>#cim_client_frontend = XML
<br>cim_client_frontend = SfcbLocal
<br><br>of the config to
<br><br>cim_client_frontend = XML
<br>#cim_client_frontend = SfcbLocal
<br><br>The subscription is being created.
<br><br><br><br>Till
<br><br><br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475862&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26475862/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26475052Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T01:42:53Z2009-11-23T01:42:53ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475052&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 23. 2009 10:35]:
<br>> Hi together,
<br>>
<br>> I tested with rev 3286 via CimXML, now I changed to the local-interface and have again a filter issue: (DestinationUnreachable, Filter not found)
<br>>
<br>> Is this issue openwsman or sfcb related?
<br><br>Neither ;-) It looks more like a sfcc problem.
<br>Which version of sfcc are you using ?
<br><br>> How can I contribute to solve the issue?
<br><br>Provide a full, reproducible test case.
<br><br>> I thought sfcc local and cimxml interface differ only in transport, so
<br>> I thought the behavior should be the same!
<br><br>Right, it should be identical.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26475052&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26474958Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-23T01:34:49Z2009-11-23T01:34:49ZTill Steinbach-2Hi together,
<br><br>I tested with rev 3286 via CimXML, now I changed to the local-interface and have again a filter issue: (DestinationUnreachable, Filter not found)
<br><br>Is this issue openwsman or sfcb related? How can I contribute to solve the issue? I thought sfcc local and cimxml interface differ only in transport, so I thought the behavior should be the same!
<br><br>Regards
<br>Till
<br><br><br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26474958&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26474958/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26425538Re: FW: Bug 220.2009-11-19T04:40:42Z2009-11-19T04:40:42ZKlaus Kaempf* Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26425538&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Nov 19. 2009 11:07]:
<br>> Forgot to send it to the development list. I apologize for the duplicate messages, Klaus. :)
<br><br>;-)
<br><div class='shrinkable-quote'><br>>
<br>> --
<br>> Suresh
<br>> ________________________________________
<br>> From: Suresh Sundriyal
<br>> Sent: Thursday, November 19, 2009 2:03 AM
<br>> To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26425538&i=1" target="_top" rel="nofollow">kkaempf@...</a>
<br>> Subject: Bug 220.
<br>>
<br>> Hi Klaus,
<br>>
<br>> I see that you closed bug number 220.
</div><br>Actually, I closed all bugs either because they were fixed already or
<br>no one followed up.
<br><br>I'd rather have one 'channel' for bug reports, namely openwsman-devel.
<br><br>[...]
<br>>
<br>> According to the XML schema specifications, the items inside xs:sequence should
<br>> be in strict order. Which implies that in a PullResponse the "EnumerationContext"
<br>> should be placed before "Items". If you look at the PullResponses sent by
<br>> Openwsman, it seems that Openwsman places the "Items" before "EnumerationContext"
<br>> and I believe this is what is making the OpenTestMan tests fail.
<br><br>Wonderful analysis, thanks for the fix !
<br><br>Will be applied for 2.2.1.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26425538&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26423659FW: Bug 220.2009-11-19T02:06:11Z2009-11-19T02:06:11ZSuresh Sundriyal-2Forgot to send it to the development list. I apologize for the duplicate messages, Klaus. :)
<br><br>--
<br>Suresh
<br>________________________________________
<br>From: Suresh Sundriyal
<br>Sent: Thursday, November 19, 2009 2:03 AM
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26423659&i=0" target="_top" rel="nofollow">kkaempf@...</a>
<br>Subject: Bug 220.
<br><br>Hi Klaus,
<br><br>I see that you closed bug number 220. It complains about Openwsman not returning
<br>the PullResponse in the sequence as per the schema. It was closed since the
<br>original poster never provided any information about reproducing the bug.
<br><br>However, I think I can see what the problem is. The ws-enumeration schema
<br>(<a href="http://www.w3.org/Submission/WS-Enumeration/#Appendix_I__E2_80_93_XML_Schema" target="_top" rel="nofollow">http://www.w3.org/Submission/WS-Enumeration/#Appendix_I__E2_80_93_XML_Schema</a>)
<br>describes the PullResponse sequence as follows:
<br><br> <!-- Pull response -->
<br> <xs:element name="PullResponse">
<br> <xs:complexType>
<br> <xs:sequence>
<br> <xs:element name="EnumerationContext"
<br> type="tns:EnumerationContextType"
<br> minOccurs="0" />
<br> <xs:element name="Items" type="tns:ItemListType"
<br> minOccurs="0" />
<br> <xs:element name="EndOfSequence" minOccurs="0" />
<br> </xs:sequence>
<br> <xs:anyAttribute namespace="##other" processContents="lax" />
<br> </xs:complexType>
<br> </xs:element>
<br><br><br>According to the XML schema specifications, the items inside xs:sequence should
<br>be in strict order. Which implies that in a PullResponse the "EnumerationContext"
<br>should be placed before "Items". If you look at the PullResponses sent by
<br>Openwsman, it seems that Openwsman places the "Items" before "EnumerationContext"
<br>and I believe this is what is making the OpenTestMan tests fail. Here's an example
<br>of a PullResponse returned by Openwsman:
<br><br><wsen:PullResponse>
<br> <wsen:Items>
<br> <n1:OMC_HardwareSubSystem>
<br> <n1:Caption>System Board 7:1</n1:Caption>
<br> <n1:CommunicationStatus xsi:nil="true"/>
<br> <n1:CreationClassName>OMC_HardwareSubSystem</n1:CreationClassName>
<br> <n1:Dedicated>2</n1:Dedicated>
<br> <n1:Description>System Board 7:1</n1:Description>
<br> <n1:DetailedStatus xsi:nil="true"/>
<br> <n1:ElementName>System Board 7:1</n1:ElementName>
<br> <n1:EnabledDefault>2</n1:EnabledDefault>
<br> <n1:EnabledState>0</n1:EnabledState>
<br> <n1:Generation xsi:nil="true"/>
<br> <n1:HealthState>0</n1:HealthState>
<br> <n1:InstallDate xsi:nil="true"/>
<br> <n1:InstanceID xsi:nil="true"/>
<br> <n1:Name>7.1</n1:Name>
<br> <n1:NameFormat>Other</n1:NameFormat>
<br> <n1:OperatingStatus xsi:nil="true"/>
<br> <n1:OperationalStatus>0</n1:OperationalStatus>
<br> <n1:OtherDedicatedDescriptions>System Board</n1:OtherDedicatedDescriptions>
<br> <n1:OtherEnabledState xsi:nil="true"/>
<br> <n1:PrimaryOwnerContact xsi:nil="true"/>
<br> <n1:PrimaryOwnerName xsi:nil="true"/>
<br> <n1:PrimaryStatus xsi:nil="true"/>
<br> <n1:RequestedState>12</n1:RequestedState>
<br> <n1:ResetCapability xsi:nil="true"/>
<br> <n1:Status xsi:nil="true"/>
<br> <n1:TimeOfLastStateChange xsi:nil="true"/>
<br> <n1:TransitioningToState>12</n1:TransitioningToState>
<br> </n1:OMC_HardwareSubSystem>
<br> </wsen:Items>
<br> <wsen:EnumerationContext>e30bcff0-5fdd-1fdd-8717-1ebe4f565000</wsen:EnumerationContext>
<br></wsen:PullResponse>
<br><br><br>It seems like a valid bug to me. Attached is a fix to the problem. The fix is simple enough. In wsenum_pull_stubs
<br>I change the order in which the nodes are added, although I am not sure when this method is actually used. In
<br>wsenum_pull_direct (this is the method that is called for pull operations), I had to add another method to add
<br>enumeration context in the correct place.
<br><br>--
<br>Suresh
<br><br /><tt>[pullresponse.diff]</tt><br /><hr align="left" width="300" /><tt>Index: src/lib/wsman-xml.c
<br>===================================================================
<br>--- src/lib/wsman-xml.c (revision 3304)
<br>+++ src/lib/wsman-xml.c (working copy)
<br>@@ -984,7 +984,24 @@
<br> return newNode;
<br> }
<br>
<br>+/**
<br>+ *** Add a previous sibling to an XML node
<br>+ *** @param node XML node
<br>+ *** @param nsUri Namespace URI
<br>+ *** @param localName local name
<br>+ *** @param val Value of the node
<br>+ *** @return New XML node
<br>+ ***/
<br> WsXmlNodeH
<br>+ws_xml_add_prev_sibling(WsXmlNodeH node,
<br>+ const char *nsUri, const char *localName, const char *val)
<br>+{
<br>+ WsXmlNodeH newNode = xml_parser_node_add(node, XML_ELEMENT_PREV, nsUri,
<br>+ localName, val, 0);
<br>+ return newNode;
<br>+}
<br>+
<br>+WsXmlNodeH
<br> ws_xml_add_child_sort(WsXmlNodeH node,
<br> const char *nsUri, const char *localName, const char *val, int xmlescape)
<br> {
<br>Index: src/lib/wsman-soap.c
<br>===================================================================
<br>--- src/lib/wsman-soap.c (revision 3304)
<br>+++ src/lib/wsman-soap.c (working copy)
<br>@@ -1162,14 +1162,14 @@
<br> goto DONE;
<br> }
<br> if (enumInfo->pullResultPtr) {
<br>+ if (enumId) {
<br>+ ws_serialize_str(soapCntx->serializercntx, node, enumId,
<br>+ XML_NS_ENUMERATION, WSENUM_ENUMERATION_CONTEXT, 0);
<br>+ }
<br> WsXmlNodeH itemsNode = ws_xml_add_child(node,
<br> XML_NS_ENUMERATION, WSENUM_ITEMS, NULL);
<br> ws_serialize(soapCntx->serializercntx, itemsNode, enumInfo->pullResultPtr,
<br> typeInfo, ep->respName, (char *) ep->data, NULL, 1);
<br>- if (enumId) {
<br>- ws_serialize_str(soapCntx->serializercntx, node, enumId,
<br>- XML_NS_ENUMERATION, WSENUM_ENUMERATION_CONTEXT, 0);
<br>- }
<br> ws_serializer_free_mem(soapCntx->serializercntx,
<br> enumInfo->pullResultPtr, typeInfo);
<br> } else {
<br>@@ -1240,13 +1240,15 @@
<br> enumInfo->index++;
<br> if (enumInfo->pullResultPtr) {
<br> WsXmlNodeH body;
<br>- WsXmlNodeH response;
<br>+ WsXmlNodeH response, items;
<br> doc = enumInfo->pullResultPtr;
<br> wsman_set_estimated_total(_doc, doc, enumInfo);
<br>
<br> body = ws_xml_get_soap_body(doc);
<br> response = ws_xml_get_child(body, 0,
<br> XML_NS_ENUMERATION, WSENUM_PULL_RESP);
<br>+ items = ws_xml_get_child(body, 0,
<br>+ XML_NS_ENUMERATION, WSENUM_ITEMS);
<br>
<br> if (enumInfo->totalItems == 0 || enumInfo->index == enumInfo->totalItems) {
<br> /*
<br>@@ -1259,8 +1261,8 @@
<br> locked = 0;
<br> destroy_enuminfo(enumInfo);
<br> } else {
<br>- ws_serialize_str(soapCntx->serializercntx, response, enumInfo->enumId,
<br>- XML_NS_ENUMERATION, WSENUM_ENUMERATION_CONTEXT, 0);
<br>+ ws_xml_add_prev_sibling(items, XML_NS_ENUMERATION,
<br>+ WSENUM_ENUMERATION_CONTEXT, enumInfo->enumId);
<br> }
<br> }
<br> }
<br>Index: include/wsman-xml-api.h
<br>===================================================================
<br>--- include/wsman-xml-api.h (revision 3304)
<br>+++ include/wsman-xml-api.h (working copy)
<br>@@ -140,6 +140,8 @@
<br>
<br> WsXmlNodeH ws_xml_add_child(WsXmlNodeH node, const char *ns,
<br> const char *localName, const char *val);
<br>+WsXmlNodeH ws_xml_add_prev_sibling(WsXmlNodeH node, const char *ns,
<br>+ const char *localName, const char *val);
<br> WsXmlNodeH ws_xml_add_child_sort(WsXmlNodeH node, const char *ns,
<br> const char *localName, const char *val, int xmlescape);
<br>
<br></tt><hr align="left" width="300" /><br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26423659&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26398136Openwsman 2.2.1pre-release available !2009-11-17T13:32:03Z2009-11-17T13:32:03ZKlaus KaempfHi,
<br><br>a pre-release of Openwsman 2.2.1 is now available at
<br><a href="https://sourceforge.net/projects/openwsman/files/openwsman/2.2.1pre/openwsman-2.2.1pre.tar.bz2/download" target="_top" rel="nofollow">https://sourceforge.net/projects/openwsman/files/openwsman/2.2.1pre/openwsman-2.2.1pre.tar.bz2/download</a><br><br>It is identical with svn rev 3301 from the openwsman svn repository.
<br><br>This release includes all patches received since the 2.2.0 release
<br>early September.
<br><br>A big thanks to all contributors, testers, and users !
<br><br>Please test and give feedback !
<br><br>I hope to release this as 2.2.1 by end of week.
<br><br>Klaus
<br><br>---
<br><br>The changes applied since 2.2.0 are as follows:
<br><br>- Major changes:
<br> - Enumeration timeout fixed, resulting in --enum-idle-timeout option
<br> to openwsmand taking seconds (instead of miliseconds) now
<br> - Client side CRL (certificate revocation list) support
<br> (Arun Venkatachalam)
<br> - split off client config as /etc/openwsman/openwsman_client.conf
<br> - Fix upper limit check for threads and their stack usage (Suresh Sundriyal)
<br> (Allowing to confine memory usage in the 10-20MB range!)
<br> Reintroduce max_thread config file parameter and two new parameters
<br> * max_connections_per_thread
<br> * thread_stack_size
<br>- Minor changes:
<br> - clean up fault generation in CIM backend (Suresh Sundriyal)
<br> - fix various memory leaks (Suresh Sundriyal)
<br> - fix Python bindings build (kkaempf)
<br> - Fix security risk when listing indication subscriptions (Suresh Sundriyal)
<br> - Fix xml namespace for enumeration and subscription filters (kkaempf)
<br> - Fix class names for swig bindings, makes Python bindings
<br> operational (kkaempf)
<br>
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26398136&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26397396Re: Changeset 3174.2009-11-17T12:54:39Z2009-11-17T12:54:39ZKlaus Kaempf* Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26397396&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Nov 13. 2009 07:51]:
<br>> I have mentioned this problem in one of my earlier emails. Changeset 3174 was
<br>> introduced into the codebase to return fault messages from CIMOM to the
<br>> client. The fix essentially uncommented a previously commented out code which
<br>> strdup'ed strings however these duplicated strings are not free'd anywhere
<br>> resulting in memory leaks. To make matters worse, the fix is incomplete since
<br>> it will only return faults for the invokeMethod calls and not the rest of the
<br>> intrinsic methods and as such is incomplete in its current form.
<br>>
<br>> The included patch contains the complete fix.
<br><br>Thanks, applied as svn rev 3300 !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26397396&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26396929Re: output of enumerateClassNames2009-11-17T12:24:21Z2009-11-17T12:24:21ZKlaus Kaempf* Prashanth Venky <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26396929&i=0" target="_top" rel="nofollow">prashanth.venky@...</a>> [Oct 01. 2009 11:01]:
<div class='shrinkable-quote'><br>> On Thu, Oct 1, 2009 at 1:26 PM, Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26396929&i=1" target="_top" rel="nofollow">kkaempf@...</a>> wrote:
<br>> >
<br>> > I see three options to implement this in openwsman
<br>> >
<br>> > 1. pass it as 'flags' in the client_opt_t structure. This is easy to
<br>> > implement but would rule out the 'wsman' cli tool as it doesn't
<br>> > support setting the client options (afaik).
<br>> >
<br>> > 2. pass it via the 'selectors' array. This is how e.g. the cim
<br>> > namespace (setting the '__cimnamespace' selector) is set.
<br>> > Selector are appended to the resource URI.
<br>> >
<br>> > 3. pass it via the 'properties' array. Properties are method
<br>> > arguments and look like a 'natural' way to pass flags to
<br>> > EnumerateClassNames.
<br>> > Properties are passed as --prop=<key=val> to wsman.
<br>> >
</div><br>> I think option 3 would be a good way as it would be compatible with both the
<br>> wsman client and the api.
<br>> -Prash
<br>>
<br><br>Looking more closely at the code, option 2 evolves as the most natural
<br>way to pass cim namespace information to the enumerateClassNames calls.
<br><br>Passing it via selectors (adding it to the resource URI) is supported
<br>in a generic way and should work out-of-the-box for all CIM operations.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26396929&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26396576Re: More fixes and testing results.2009-11-17T12:01:38Z2009-11-17T12:01:38ZKlaus KaempfHi Suresh,
<br><br>* Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26396576&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Sep 21. 2009 08:14]:
<br>>
<br>> The patch reintroduces the max_thread config file parameter and introduces
<br>> two new parameters:
<br>>
<br>> * max_connections_per_thread
<br>> * thread_stack_size
<br><br>finally I found some time again to work on the 2.2.2 release of
<br>openwsman. I just applied your patch as svn rev 3296 and added your
<br>explanation as svn rev 3297.
<br><br>Thanks again for your work !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26396576&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26387459Re: Association using openwsman lib2009-11-17T02:23:51Z2009-11-17T02:23:51ZKlaus Kaempf* Anmol Rastogi <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26387459&i=0" target="_top" rel="nofollow">Anmol.Rastogi@...</a>> [Nov 17. 2009 10:15]:
<br>> Thanks for your reply. Here it is what you have asked for:
<br><br>Thanks.
<br><br>The error reply reports wsman:InvalidParameter as the fault code and
<br>MissingValues as the fault detail.
<br>Within openwsman, only the sfcc-interface reports this combination.
<br><br>It is triggered if the CIMOM reports CMPI_RC_ERR_INVALID_PARAMETER.
<br><br>>
<br>> Do let me know what I have missed??
<br>>
<br><br>Try to generate the association enumeration directly on the CIMOM
<br>level, e.g. by using 'wbemcli'.
<br>I'd assume that you're passing the wrong key attributes.
<br><br>Hth,
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26387459&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26386591Re: Association using openwsman lib2009-11-17T01:12:55Z2009-11-17T01:12:55Zarasto02Thanks for your reply. Here it is what you have asked for:
<br><br><?xml version="1.0"?>
<br><s:Envelope xmlns:s="<a href="http://www.w3.org/2003/05/soap-envelope" target="_top" rel="nofollow">http://www.w3.org/2003/05/soap-envelope</a>" xmlns:wsa="http://
<br>schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="<a href="http://schemas.dmtf.org/" target="_top" rel="nofollow">http://schemas.dmtf.org/</a><br>wbem/wsman/1/wsman.xsd" xmlns:wsen="<a href="http://schemas.xmlsoap.org/ws/2004/09/enumer" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/09/enumer</a><br>ation" xmlns:wsmb="<a href="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd</a>">
<br> <s:Header>
<br> <wsa:Action s:mustUnderstand="true"><a href="http://schemas.xmlsoap.org/ws/2004/09/en" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/09/en</a><br>umeration/Enumerate</wsa:Action>
<br> <wsa:To s:mustUnderstand="true"><a href="http://10.99.123.90:8889/wsman" target="_top" rel="nofollow">http://10.99.123.90:8889/wsman</a></wsa:To>
<br> <wsman:ResourceURI s:mustUnderstand="true"><a href="http://schemas.dmtf.org/wbem/wsci" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsci</a><br>m/1/*</wsman:ResourceURI>
<br> <wsa:MessageID s:mustUnderstand="true">uuid:4a1824a7-86b3-4dc8-a695-04449d65
<br>a365</wsa:MessageID>
<br> <wsa:ReplyTo>
<br> <wsa:Address><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymo" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymo</a><br>us</wsa:Address>
<br> </wsa:ReplyTo>
<br> </s:Header>
<br> <s:Body>
<br> <wsen:Enumerate>
<br> <wsman:Filter Dialect="<a href="http://schemas.dmtf.org/wbem/wsman/1/cimbinding/ass" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/cimbinding/ass</a><br>ociationFilter">
<br> <wsmb:AssociationInstances>
<br> <wsmb:Object>
<br> <wsa:Address><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/role/a" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/a</a><br>nonymous</wsa:Address>
<br> <wsa:ReferenceParameters>
<br> <wsman:ResourceURI><a href="http://schemas.dmtf.org/wbem/wscim/1/cim-schema" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wscim/1/cim-schema</a><br>/2/CIM_ComputerSystem</wsman:ResourceURI>
<br> <wsman:SelectorSet>
<br> <wsman:Selector Name="CSCreationClassName">CIM_ComputerSystem</w
<br>sman:Selector>
<br> <wsman:Selector Name="CreationClassName">CIM_ComputerSystem</wsm
<br>an:Selector>
<br> <wsman:Selector Name="__cimnamespace">root/cimv2</wsman:Selector
<br>>
<br> </wsman:SelectorSet>
<br> </wsa:ReferenceParameters>
<br> </wsmb:Object>
<br> </wsmb:AssociationInstances>
<br> </wsman:Filter>
<br> </wsen:Enumerate>
<br> </s:Body>
<br></s:Envelope>
<br><br><br>Do let me know what I have missed??
<br><br>Regards,
<br>Anmol Rastogi
<br><br>-----Original Message-----
<br>From: Klaus Kaempf [mailto:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386591&i=0" target="_top" rel="nofollow">kkaempf@...</a>]
<br>Sent: Tuesday, November 17, 2009 2:36 PM
<br>To: Anmol Rastogi
<br>Cc: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386591&i=1" target="_top" rel="nofollow">openwsman-devel@...</a>
<br>Subject: Re: [Openwsman-devel] Association using openwsman lib
<br><br>* arasto02 <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386591&i=2" target="_top" rel="nofollow">anmol.rastogi@...</a>> [Nov 17. 2009 08:28]:
<br>>
<br>> Hi,
<br>>
<br>> I am build an test application to know the asscoation for
<br>> CIM_ComputerSystem. Below is code snippet for this:
<br>[...]
<br>>
<br>> wsmc_set_action_option(options, FLAG_DUMP_REQUEST);
<br><br>You're setting the dump request flag here, which should output the
<br>SOAP request.
<br>However, I cannot find this request in your mail.
<br><br>Please share the SOAP request with us, this should reveal the missing
<br>parameter.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br>"This email and any files transmitted with it contain confidential, proprietary,
<br>privileged information of Symphony Services Corp (India) Pvt. Ltd. and are intended
<br>solely for the use of the recipient/s to whom it is addressed. Any unauthorized
<br>notifying, copying or distributing of this e-mail, directly or indirectly, and the
<br>contents therein in full or part is prohibited by any entity who is not a recipient.
<br>Any email received inadvertently or by mistake should be deleted by the entity who
<br>is not a recipient thereof. You may be pleased to notify the sender immediately by
<br>email and the email should be deleted from your system".
<br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386591&i=3" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26386474Re: Association using openwsman lib2009-11-17T01:06:03Z2009-11-17T01:06:03ZKlaus Kaempf* arasto02 <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386474&i=0" target="_top" rel="nofollow">anmol.rastogi@...</a>> [Nov 17. 2009 08:28]:
<br>>
<br>> Hi,
<br>>
<br>> I am build an test application to know the asscoation for
<br>> CIM_ComputerSystem. Below is code snippet for this:
<br>[...]
<br>>
<br>> wsmc_set_action_option(options, FLAG_DUMP_REQUEST);
<br><br>You're setting the dump request flag here, which should output the
<br>SOAP request.
<br>However, I cannot find this request in your mail.
<br><br>Please share the SOAP request with us, this should reveal the missing
<br>parameter.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26386474&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26385464Association using openwsman lib2009-11-16T23:28:16Z2009-11-16T23:28:16Zarasto02Hi,
<br><br>I am build an test application to know the asscoation for CIM_ComputerSystem. Below is code snippet for this:
<br>#include <stdio.h>
<br>#include <stdlib.h>
<br>#include <string.h>
<br>//#include <unistd.h>
<br>#include <errno.h>
<br>#include <time.h>
<br><br>#include "u/libu.h"
<br>#include "wsman-client-api.h"
<br>#include "wsman-client-transport.h"
<br>#include "wsman-epr.h"
<br>#include "wsman-filter.h"
<br><br><br>//int facility = LOG_DAEMON;
<br>int errors = 0;
<br><br>typedef struct {
<br> const char *server;
<br> int port;
<br> const char *path;
<br> const char *scheme;
<br> const char *username;
<br> const char *password;
<br>} ServerData;
<br><br>typedef struct {
<br> /* Explanation of what you should see */
<br> const char *explanation;
<br><br> /* Namespace containing the class */
<br> const char *namespc;
<br><br> /* Resource UR to test against */
<br> const char *resource_uri;
<br><br> char *filter;
<br><br> const char* xpath_expression;
<br> char* expected_value;
<br><br> /* What the final status code should be. */
<br> unsigned int final_status;
<br><br> unsigned int auth_data;
<br><br>} TestData;
<br><br>TestData test = {
<br> "Test Associators.",
<br> "root/cimv2",
<br> "<a href="http://schemas.dmtf.org/wbem/wscim/1/*" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wscim/1/*</a>",
<br> "<a href="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem?CreationClassName=" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem?CreationClassName=</a>\"CIM_ComputerSystem\"&CSCreationClassName=\"CIM_ComputerSystem\"",
<br> "/s:Envelope/s:Body/s:Fault/s:Code/s:Subcode/s:Value",
<br> NULL,
<br> 500,
<br> 0
<br>};
<br><br>ServerData sd[] = {
<br> {"server", 8889, "/wsman", "http", "user", "password"}
<br>};
<br><br>static void wsman_output(WsXmlDocH doc)
<br>{
<br> ws_xml_dump_node_tree(stdout, ws_xml_get_doc_root(doc));
<br> return;
<br>}
<br><br>int main(int argc, char** argv)
<br>{
<br> WsManClient *cl;
<br> WsXmlDocH assoc_resp = NULL, doc = NULL;
<br> client_opt_t *options;
<br> char *enumContext = NULL;
<br><br> cl = wsmc_create(sd[0].server, sd[0].port, sd[0].path, sd[0].scheme, sd[0].username, sd[0].password);
<br> wsmc_transport_init(cl, NULL);
<br><br> options = wsmc_options_init();
<br> epr_t *epr = epr_from_string(test.filter);
<br> if(test.namespc)
<br> epr_add_selector_text(epr, CIM_NAMESPACE_SELECTOR, test.namespc);
<br> filter_t *filter = filter_create_assoc(epr, 1, NULL, NULL, NULL, NULL, NULL, 0 );
<br><br> wsmc_set_action_option(options, FLAG_DUMP_REQUEST);
<br> assoc_resp = wsmc_action_enumerate(cl, (char *)test.resource_uri, options, filter);
<br><br> if(!assoc_resp) {
<br> printf("\t\t\033[22;31mUNRESOLVED\033[m\n");
<br> exit(0);
<br> }
<br> wsman_output(assoc_resp);
<br><br><br> /* Pull for the response */
<br> enumContext = wsmc_get_enum_context(assoc_resp);
<br> ws_xml_destroy_doc(assoc_resp);
<br><br> while(enumContext != NULL) {
<br> doc = wsmc_action_pull(cl, (char *)test.resource_uri, options, NULL, enumContext);
<br> if (!doc) {
<br> printf("\t\t\033[22;31mUNRESOLVED\033[m\n");
<br> wsmc_options_destroy(options);
<br> wsmc_release(cl);
<br> return -1;
<br> }
<br> wsman_output(doc);
<br> enumContext = wsmc_get_enum_context(doc);
<br> }
<br> if (doc)
<br> ws_xml_destroy_doc(doc);
<br> wsmc_options_destroy(options);
<br> wsmc_release(cl);
<br> epr_destroy(epr);
<br> filter_destroy(filter);
<br> return 0;
<br>}
<br><br>But when i execute this program i am alwasy getting the error in XML as below:
<br><?xml version="1.0" encoding="UTF-8"?>
<br><s:Envelope xmlns:s="<a href="http://www.w3.org/2003/05/soap-envelope" target="_top" rel="nofollow">http://www.w3.org/2003/05/soap-envelope</a>" xmlns:wsa="http://
<br>schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="<a href="http://schemas.dmtf.org/" target="_top" rel="nofollow">http://schemas.dmtf.org/</a><br>wbem/wsman/1/wsman.xsd">
<br> <s:Header>
<br> <wsa:To><a href="http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous" target="_top" rel="nofollow">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a></wsa
<br>:To>
<br> <wsa:Action><a href="http://schemas.dmtf.org/wbem/wsman/1/wsman/fault" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/wsman/fault</a></wsa:Action>
<br> <wsa:RelatesTo>uuid:c66a8fda-7117-489a-9fc6-480c39646cdc</wsa:RelatesTo>
<br> <wsa:MessageID>uuid:bce4e97a-788b-188b-81e7-2a9f42565000</wsa:MessageID>
<br> </s:Header>
<br> <s:Body>
<br> <s:Fault>
<br> <s:Code>
<br> <s:Value>s:Sender</s:Value>
<br> <s:Subcode>
<br> <s:Value>wsman:InvalidParameter</s:Value>
<br> </s:Subcode>
<br> </s:Code>
<br> <s:Reason>
<br> <s:Text xml:lang="en">An operation parameter is not valid.</s:Text>
<br> </s:Reason>
<br> <s:Detail>
<br> <wsman:FaultDetail><a href="http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetai" target="_top" rel="nofollow">http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetai</a><br>l/MissingValues</wsman:FaultDetail>
<br> </s:Detail>
<br> </s:Fault>
<br> </s:Body>
<br></s:Envelope>
<br><br>as you can see in above XML that reason for this "An operation parameter is not valid." Could somebody please help me here that what parameter i am passing wrong??
<br><br>Thanks in advance!
<br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26379039Re: Security hole.2009-11-16T12:36:33Z2009-11-16T12:36:33ZKlaus Kaempf* Suresh Sundriyal <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26379039&i=0" target="_top" rel="nofollow">ssundriy@...</a>> [Oct 13. 2009 10:33]:
<br>> While subscribing for indications, Openwsman sets the Destination property in the indicationHandler
<br>> with the username/password. If someone were to enumerate the CIMIndicationHandlerCIMXML class
<br>> he will be presented with the password for all the users subscribed for indications.
<br><br>[...]
<br>>
<br>> Seems like this should be changed to:
<br>>
<br>> snprintf(serverpath, 128, "<a href="http://localhost:%s%s" target="_top" rel="nofollow">http://localhost:%s%s</a>", get_server_port(), servicepath);
<br><br>Applied as svn rev 3293.
<br><br>Thanks for the fix !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26379039&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26372513Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-16T06:08:41Z2009-11-16T06:08:41ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372513&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 16. 2009 15:03]:
<br>> >
<br>> > So following the 'be liberate in what you consume, be strict in what
<br>> > you generate', rev 3286 now accepts either Filter namespace for
<br>> > incoming requests.
<br>>
<br>> I have not seen the source yet, (busy monday) do you reject messages with Filter tags in both namespaces?
<br><br>rev 3286 follows DPS0226 recommendation and rejects duplicate Filter
<br>tags. (reports as wse:InvalidMessage)
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372513&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26372417Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-16T06:02:36Z2009-11-16T06:02:36ZTill Steinbach-2Am 16.11.2009 um 14:39 schrieb Klaus Kaempf:
<br>> After re-reading DSP0226 (WS-Management) again, we have to fix rev
<br>> 3279 once more.
<br>> While wsman:Filter is correct for Enumeration, either wsman:Filter or
<br>> wse:Filter (WS-Eventing) can be used for event subscription.
<br>>
<br>> However, section 10.2.2 of DSP0226 clearly says that wsman:Filter is
<br>> correct for WS-Managment subscription.
<br><br>You are right. I did not realize that DSP0226 would be the right source for that issue to find a specification.
<br><br>>
<br>> So following the 'be liberate in what you consume, be strict in what
<br>> you generate', rev 3286 now accepts either Filter namespace for
<br>> incoming requests.
<br><br>I have not seen the source yet, (busy monday) do you reject messages with Filter tags in both namespaces?
<br><br>>
<br>> Please test !
<br><br>I start testing in a moment.
<br><br><br><br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372417&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26372417/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26372231Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-16T05:39:13Z2009-11-16T05:39:13ZKlaus Kaempf* Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372231&i=0" target="_top" rel="nofollow">kkaempf@...</a>> [Nov 12. 2009 16:11]:
<br>> * Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372231&i=1" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 12. 2009 15:53]:
<br>>
<br>> > Quick fix would be to pass the desired namespace to the
<br>> > filter_serialize-Method.
<br>> Exactly, thats what I've just done.
<br>> >
<br>> > Sure I'am willing to test the fix from svn.
<br>> Just go ahead, rev 3279 of openwsman should have it fixed.
<br>>
<br><br>After re-reading DSP0226 (WS-Management) again, we have to fix rev
<br>3279 once more.
<br><br>While wsman:Filter is correct for Enumeration, either wsman:Filter or
<br>wse:Filter (WS-Eventing) can be used for event subscription.
<br><br>However, section 10.2.2 of DSP0226 clearly says that wsman:Filter is
<br>correct for WS-Managment subscription.
<br><br>So following the 'be liberate in what you consume, be strict in what
<br>you generate', rev 3286 now accepts either Filter namespace for
<br>incoming requests.
<br><br>Please test !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26372231&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26370620Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-16T03:50:58Z2009-11-16T03:50:58ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26370620&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 16. 2009 12:30]:
<br>>
<br>> Am 12.11.2009 um 16:11 schrieb Klaus Kaempf:
<br>>
<br>> > Just go ahead, rev 3279 of openwsman should have it fixed.
<br>> Tested it now for a while, seems to work without a problem.
<br><br>Great !
<br><br>Thanks again for reporting the issue and for testing.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26370620&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26370401Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-16T03:30:11Z2009-11-16T03:30:11ZTill Steinbach-2<br>Am 12.11.2009 um 16:11 schrieb Klaus Kaempf:
<br><br>> Just go ahead, rev 3279 of openwsman should have it fixed.
<br>Tested it now for a while, seems to work without a problem.
<br><br>> I still wonder how Microsofts winrm implements this and what the
<br>> standard says. Its the usual interoperability vs. standard compliance
<br>> struggle ;-)
<br>Yea, that's on my todo list, testing compatibility with winrm.
<br><br><br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26370401&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26370401/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26332149Changeset 3174.2009-11-12T22:46:09Z2009-11-12T22:46:09ZSuresh Sundriyal-2I have mentioned this problem in one of my earlier emails. Changeset 3174 was
<br>introduced into the codebase to return fault messages from CIMOM to the
<br>client. The fix essentially uncommented a previously commented out code which
<br>strdup'ed strings however these duplicated strings are not free'd anywhere
<br>resulting in memory leaks. To make matters worse, the fix is incomplete since
<br>it will only return faults for the invokeMethod calls and not the rest of the
<br>intrinsic methods and as such is incomplete in its current form.
<br><br>The included patch contains the complete fix.
<br><br>The strdup happens in cim_to_wsman_fault method in sfcc-interface.c. Most of
<br>the sfcc wrapper methods in this file call this method and also call each other.
<br>There were a couple of places in the file itself where the fault_msg needed
<br>to be free'd. While I was at it, I cleaned up the code a bit as well.
<br><br>The wrapper methods in sfcc-interface.c are called by the callback methods in
<br>cim_data_stubs.c file. Some of the methods in this file are self-contained and
<br>are directly called'back and instantiate their own WsmanStatus variables and
<br>the fault_msg could be free'd from within the methods themselves. However,
<br>methods for Enumerate, Subscribe, Unsubscribe and Renew are called'back from
<br>wrapper methods defined in wsman-soap.c and the WsmanStatus variables are
<br>passed in as pointers and thus needed to be cleaned up in wsman-soap.c.
<br><br>I hope that makes sense. I have been working on this fix on and off for a while
<br>and it has been sitting in my queue for some time so my recollection of all
<br>the details is a bit fuzzy.
<br><br>In addition to the fix, it would be nice to document somewhere that in the
<br>future if any additions are made to the CIM plugin files, it should be kept
<br>in mind that the WsmanStatus.fault_msg needs to be explicitly free'd.
<br><br>--
<br>Regards,
<br>Suresh<br /><tt>[faults_memory_leak.diff]</tt><br /><hr align="left" width="300" /><tt>Index: src/plugins/cim/cim_data_stubs.c
<br>===================================================================
<br>--- src/plugins/cim/cim_data_stubs.c (revision 3279)
<br>+++ src/plugins/cim/cim_data_stubs.c (working copy)
<br>@@ -126,6 +126,7 @@
<br>
<br> if (!cimclient->cc) {
<br> CimResource_destroy(cimclient);
<br>+ u_free(status.fault_msg);
<br> return NULL;
<br> }
<br>
<br>@@ -165,6 +166,7 @@
<br> }
<br>
<br> u_free(show_extensions);
<br>+ u_free(status.fault_msg);
<br> return cimclient;
<br> }
<br>
<br>@@ -257,7 +259,7 @@
<br> if (wsman_check_status(&status) != 0) {
<br> ws_xml_destroy_doc(doc);
<br> doc = wsman_generate_fault( soap_get_op_doc(op, 1),
<br>- status.fault_code, status.fault_detail_code, NULL);
<br>+ status.fault_code, status.fault_detail_code, status.fault_msg);
<br> }
<br> if (doc) {
<br> soap_set_op_doc(op, doc, 0);
<br>@@ -267,6 +269,7 @@
<br>
<br> CimResource_destroy(cimclient);
<br> ws_destroy_context(cntx);
<br>+ u_free(status.false_msg);
<br> return 0;
<br> }
<br>
<br>@@ -321,7 +324,7 @@
<br> if (wsman_check_status(&status) != 0) {
<br> ws_xml_destroy_doc(doc);
<br> doc = wsman_generate_fault( soap_get_op_doc(op, 1),
<br>- status.fault_code, status.fault_detail_code, NULL);
<br>+ status.fault_code, status.fault_detail_code, status.fault_msg);
<br> }
<br> if ( doc ) {
<br> soap_set_op_doc(op, doc, 0);
<br>@@ -331,6 +334,7 @@
<br>
<br> CimResource_destroy(cimclient);
<br> ws_destroy_context(cntx);
<br>+ u_free(status.fault_msg);
<br> return 0;
<br> }
<br>
<br>@@ -397,6 +401,7 @@
<br>
<br> ws_destroy_context(cntx);
<br> CimResource_destroy(cimclient);
<br>+ u_free(status.fault_msg);
<br> return 0;
<br> }
<br>
<br>@@ -629,7 +634,7 @@
<br> if (wsman_check_status(&status) != 0) {
<br> ws_xml_destroy_doc(doc);
<br> doc = wsman_generate_fault( soap_get_op_doc(op, 1),
<br>- status.fault_code, status.fault_detail_code, NULL);
<br>+ status.fault_code, status.fault_detail_code, status.fault_msg);
<br> }
<br>
<br> if ( doc ) {
<br>@@ -640,6 +645,7 @@
<br>
<br> CimResource_destroy(cimclient);
<br> ws_destroy_context(cntx);
<br>+ u_free(status.fault_msg);
<br> return 0;
<br> }
<br>
<br>@@ -701,7 +707,7 @@
<br> if (wsman_check_status(&status) != 0) {
<br> ws_xml_destroy_doc(doc);
<br> doc = wsman_generate_fault( indoc,
<br>- status.fault_code, status.fault_detail_code, NULL);
<br>+ status.fault_code, status.fault_detail_code, status.fault_msg);
<br> }
<br>
<br> if ( doc ) {
<br>@@ -712,6 +718,7 @@
<br>
<br> CimResource_destroy(cimclient);
<br> ws_destroy_context(cntx);
<br>+ u_free(status.fault_msg);
<br> return 0;
<br> }
<br> #ifdef ENABLE_EVENTING_SUPPORT
<br>Index: src/plugins/cim/sfcc-interface.c
<br>===================================================================
<br>--- src/plugins/cim/sfcc-interface.c (revision 3279)
<br>+++ src/plugins/cim/sfcc-interface.c (working copy)
<br>@@ -905,7 +905,6 @@
<br> int match = 0;
<br> CMPIEnumeration *enumeration;
<br> CMPIObjectPath *result_op = NULL;
<br>- WsmanStatus statusPP;
<br> CMPIArray *enumArr = NULL;
<br>
<br> if (client->requested_class)
<br>@@ -931,7 +930,6 @@
<br>
<br> enumArr = enumeration->ft->toArray(enumeration, NULL);
<br> int n = CMGetArrayCount(enumArr, NULL);
<br>- wsman_status_init(&statusPP);
<br> if (n > 0) {
<br> while (enumeration->ft->hasNext(enumeration, NULL)) {
<br> CMPIData data = enumeration->ft->getNext(enumeration,
<br>@@ -939,7 +937,7 @@
<br> CMPIObjectPath *op = CMClone(data.value.ref, NULL);
<br> CMPIString *opstr = CMObjectPathToString(op, NULL);
<br> debug("objectpath: %s", (char *) opstr->hdl);
<br>- if (cim_verify_keys(op, client->selectors, &statusPP) != 0) {
<br>+ if (cim_verify_keys(op, client->selectors, statusP) != 0) {
<br> if (opstr)
<br> CMRelease(opstr);
<br> if (op)
<br>@@ -961,8 +959,6 @@
<br> if (op)
<br> CMRelease(op);
<br> }
<br>- statusP->fault_code = statusPP.fault_code;
<br>- statusP->fault_detail_code = statusPP.fault_detail_code;
<br> } else {
<br> statusP->fault_code = WSA_DESTINATION_UNREACHABLE;
<br> statusP->fault_detail_code =
<br>@@ -1591,16 +1587,14 @@
<br> {
<br> CMPIObjectPath *objectpath;
<br> CMPIStatus rc;
<br>- WsmanStatus statusP;
<br> CMCIClient *cc = (CMCIClient *) client->cc;
<br> WsXmlNodeH method_node = NULL;
<br>
<br> memset(&rc, 0, sizeof(CMPIStatus));
<br>- wsman_status_init(&statusP);
<br> if (client->resource_uri
<br> && strstr(client->resource_uri, XML_NS_CIM_CLASS) != NULL) {
<br> /* uri specifies class */
<br>- objectpath = cim_get_op_from_enum(client, &statusP);
<br>+ objectpath = cim_get_op_from_enum(client, status);
<br> } else {
<br> debug("no base class, getting instance directly with getInstance");
<br> objectpath = newCMPIObjectPath(client->cim_namespace,
<br>@@ -1612,6 +1606,8 @@
<br> if (objectpath != NULL) {
<br> CMPIArgs *argsin = NULL, *argsout = NULL;
<br> argsin = newCMPIArgs(NULL);
<br>+ u_free(status.fault_msg);
<br>+ wsman_status_init(status);
<br>
<br> if (client->method_args && hash_count(client->method_args) > 0) {
<br> debug("adding method arguments");
<br>@@ -1669,9 +1665,6 @@
<br> CMRelease(argsin);
<br> if (argsout)
<br> CMRelease(argsout);
<br>- } else {
<br>- status->fault_code = statusP.fault_code;
<br>- status->fault_detail_code = statusP.fault_detail_code;
<br> }
<br>
<br> if (objectpath)
<br>@@ -1689,24 +1682,21 @@
<br> {
<br> CMPIObjectPath *objectpath = NULL;
<br> CMPIStatus rc;
<br>- WsmanStatus statusP;
<br> CMCIClient *cc = (CMCIClient *) client->cc;
<br>
<br> if (!cc) {
<br> goto cleanup;
<br> }
<br>- wsman_status_init(&statusP);
<br>
<br>- if ((objectpath = cim_get_op_from_enum(client, &statusP)) != NULL) {
<br>+ if ((objectpath = cim_get_op_from_enum(client, status)) != NULL) {
<br>+ u_free(status->fault_msg);
<br>+ wsman_status_init(status);
<br> rc = cc->ft->deleteInstance(cc, objectpath);
<br> if (rc.rc != 0) {
<br> cim_to_wsman_status(rc, status);
<br> }
<br> debug("deleteInstance rc=%d, msg=%s", rc.rc,
<br> (rc.msg) ? (char *) rc.msg->hdl : NULL);
<br>- } else {
<br>- status->fault_code = statusP.fault_code;
<br>- status->fault_detail_code = statusP.fault_detail_code;
<br> }
<br>
<br> debug("fault: %d %d", status->fault_code,
<br>@@ -1728,15 +1718,15 @@
<br> CMPIInstance *instance;
<br> CMPIObjectPath *objectpath;
<br> CMPIStatus rc;
<br>- WsmanStatus statusP;
<br> CMCIClient *cc = (CMCIClient *) client->cc;
<br>
<br> if (!cc) {
<br> goto cleanup;
<br> }
<br>- wsman_status_init(&statusP);
<br>
<br>- if ((objectpath = cim_get_op_from_enum(client, &statusP)) != NULL) {
<br>+ if ((objectpath = cim_get_op_from_enum(client, status)) != NULL) {
<br>+ u_free(status.fault_msg);
<br>+ wsman_status_init(status);
<br> instance = cc->ft->getInstance(cc, objectpath,
<br> CMPI_FLAG_IncludeClassOrigin,
<br> NULL, &rc);
<br>@@ -1751,9 +1741,6 @@
<br> (rc.msg) ? (char *) rc.msg->hdl : NULL);
<br> if (instance)
<br> CMRelease(instance);
<br>- } else {
<br>- status->fault_code = statusP.fault_code;
<br>- status->fault_detail_code = statusP.fault_detail_code;
<br> }
<br>
<br> debug("fault: %d %d", status->fault_code,
<br>@@ -1774,12 +1761,10 @@
<br> CMPIInstance *instance = NULL;
<br> CMPIObjectPath *objectpath;
<br> CMPIStatus rc;
<br>- WsmanStatus statusP;
<br> WsXmlNodeH resource = NULL;
<br> CMCIClient *cc = (CMCIClient *) client->cc;
<br> CMPIConstClass *class = NULL;
<br>
<br>- wsman_status_init(&statusP);
<br> objectpath = newCMPIObjectPath(client->cim_namespace,
<br> client->requested_class, NULL);
<br> if (!objectpath) {
<br>@@ -1854,14 +1839,12 @@
<br> CMPIInstance *instance = NULL;
<br> CMPIObjectPath *objectpath, *objectpath_r;
<br> CMPIStatus rc;
<br>- WsmanStatus statusP;
<br> CMPIConstClass *class;
<br> int fragment_flag;
<br> char *element = NULL;
<br> int index;
<br> WsXmlNodeH resource;
<br> WsXmlNodeH child = NULL;
<br>- wsman_status_init(&statusP);
<br> int numproperties = 0, i;
<br>
<br> CMCIClient *cc = (CMCIClient *) client->cc;
<br>Index: src/lib/wsman-soap.c
<br>===================================================================
<br>--- src/lib/wsman-soap.c (revision 3279)
<br>+++ src/lib/wsman-soap.c (working copy)
<br>@@ -959,7 +959,7 @@
<br> if (endPoint && (retVal = endPoint(epcntx, enumInfo, &status, opaqueData))) {
<br> debug("enumeration fault");
<br> doc = wsman_generate_fault( _doc, status.fault_code,
<br>- status.fault_detail_code, NULL);
<br>+ status.fault_detail_code, status.fault_msg);
<br> destroy_enuminfo(enumInfo);
<br> goto DONE;
<br> }
<br>@@ -1003,6 +1003,7 @@
<br> soap_set_op_doc(op, doc, 0);
<br> }
<br> ws_destroy_context(epcntx);
<br>+ u_free(status.fault_msg);
<br> return retVal;
<br> }
<br>
<br>@@ -1680,7 +1681,7 @@
<br> }
<br> if (endPoint && (retVal = endPoint(epcntx, subsInfo, &status, opaqueData))) {
<br> debug("Subscribe fault");
<br>- doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, NULL);
<br>+ doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, status.fault_msg);
<br> destroy_subsinfo(subsInfo);
<br> goto DONE;
<br> }
<br>@@ -1750,6 +1751,7 @@
<br> u_free(expiresstr);
<br> ws_serializer_free_all(epcntx->serializercntx);
<br> ws_destroy_context(epcntx);
<br>+ u_free(status.fault_msg);
<br> return retVal;
<br> }
<br>
<br>@@ -1814,7 +1816,7 @@
<br> pthread_mutex_unlock(&soap->lockSubs);
<br> if (endPoint && (retVal = endPoint(epcntx, subsInfo, &status, opaqueData))) {
<br> debug("UnSubscribe fault");
<br>- doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, NULL);
<br>+ doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, status.fault_msg);
<br> goto DONE;
<br> }
<br> pthread_mutex_lock(&subsInfo->notificationlock);
<br>@@ -1830,6 +1832,7 @@
<br> }
<br> ws_serializer_free_all(epcntx->serializercntx);
<br> ws_destroy_context(epcntx);
<br>+ u_free(status.fault_msg);
<br> return retVal;
<br> }
<br>
<br>@@ -1911,7 +1914,7 @@
<br>
<br> if (endPoint && (retVal = endPoint(epcntx, subsInfo, &status, opaqueData))) {
<br> debug("renew fault in plug-in");
<br>- doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, NULL);
<br>+ doc = wsman_generate_fault( _doc, status.fault_code, status.fault_detail_code, status.fault_msg);
<br> pthread_mutex_unlock(&subsInfo->notificationlock);
<br> goto DONE;
<br> }
<br>@@ -1927,6 +1930,7 @@
<br> }
<br> ws_serializer_free_all(epcntx->serializercntx);
<br> ws_destroy_context(epcntx);
<br>+ u_free(status.fault_msg);
<br> return retVal;
<br> }
<br>
<br></tt><hr align="left" width="300" /><br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26332149&i=0" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26320386Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-12T07:11:22Z2009-11-12T07:11:22ZKlaus Kaempf* Till Steinbach <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26320386&i=0" target="_top" rel="nofollow">till.steinbach@...</a>> [Nov 12. 2009 15:53]:
<div class='shrinkable-quote'><br>> Am 12.11.2009 um 15:48 schrieb Klaus Kaempf:
<br>> > * Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26320386&i=1" target="_top" rel="nofollow">kkaempf@...</a>> [Nov 12. 2009 15:43]:
<br>> >>
<br>> >>> But after looking into the Specification I think the Issue must be
<br>> >>> fixed in the client library
<br>> >>
<br>> >> Yeah. Let me find the serialization counterpart and fix it there also.
<br>> >
<br>> > Its in filter_serialize() of wsman-filter.c which creates the filter
<br>> > xml representation without taking enumerate vs. subscribe into account.
<br>>
<br>> Yes, there is no information about the action in the filter structure.
</div><br>> Quick fix would be to pass the desired namespace to the
<br>> filter_serialize-Method.
<br>Exactly, thats what I've just done.
<br>>
<br>> Sure I'am willing to test the fix from svn.
<br>Just go ahead, rev 3279 of openwsman should have it fixed.
<br><br>I still wonder how Microsofts winrm implements this and what the
<br>standard says. Its the usual interoperability vs. standard compliance
<br>struggle ;-)
<br><br>>
<br>> Thanks for your involvement!
<br>Thanks for your patience and testing !
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26320386&i=2" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26320094Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-12T06:53:49Z2009-11-12T06:53:49ZTill Steinbach-2Am 12.11.2009 um 15:48 schrieb Klaus Kaempf:
<br>> * Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26320094&i=0" target="_top" rel="nofollow">kkaempf@...</a>> [Nov 12. 2009 15:43]:
<br>>>
<br>>>> But after looking into the Specification I think the Issue must be
<br>>>> fixed in the client library
<br>>>
<br>>> Yeah. Let me find the serialization counterpart and fix it there also.
<br>>
<br>> Its in filter_serialize() of wsman-filter.c which creates the filter
<br>> xml representation without taking enumerate vs. subscribe into account.
<br><br>Yes, there is no information about the action in the filter structure. Quick fix would be to pass the desired namespace to the filter_serialize-Method.
<br><br>Sure I'am willing to test the fix from svn.
<br><br>Thanks for your involvement!
<br>Till<br /> <br />------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br />_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26320094&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>smime.p7s</strong> (3K) <a href="http://old.nabble.com/attachment/26320094/0/smime.p7s" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>tag:old.nabble.com,2006:post-26319989Re: Issues (Dispatcher Error/FilteringNotSupported)2009-11-12T06:48:38Z2009-11-12T06:48:38ZKlaus Kaempf* Klaus Kaempf <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26319989&i=0" target="_top" rel="nofollow">kkaempf@...</a>> [Nov 12. 2009 15:43]:
<br>>
<br>> > But after looking into the Specification I think the Issue must be
<br>> > fixed in the client library
<br>>
<br>> Yeah. Let me find the serialization counterpart and fix it there also.
<br><br>Its in filter_serialize() of wsman-filter.c which creates the filter
<br>xml representation without taking enumerate vs. subscribe into account.
<br><br>Klaus
<br>---
<br>SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
<br><br><br>------------------------------------------------------------------------------
<br>Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
<br>trial. Simplify your report design, integration and deployment - and focus on
<br>what you do best, core application coding. Discover what's new with
<br>Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_top" rel="nofollow">http://p.sf.net/sfu/bobj-july</a><br>_______________________________________________
<br>Openwsman-devel mailing list
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26319989&i=1" target="_top" rel="nofollow">Openwsman-devel@...</a>
<br><a href="https://lists.sourceforge.net/lists/listinfo/openwsman-devel" target="_top" rel="nofollow">https://lists.sourceforge.net/lists/listinfo/openwsman-devel</a><br><p>From forum: <a href="http://old.nabble.com/Openwsman---Development-f21691.html" embed="fixTarget[21691]" target="_top" >Openwsman - Development</a></p>