output of enumerateClassNames

[Prash_blah]

Hi,

I am trying to use the intrinsic method enumerateClassNames in wsman and comparing the output to the test_ecn in the sfcc test source folder. I noticed that the output is different. Wsman enumerateClassNames shows more than double the number of class names shown by sfcc directly. Can someone tell me why???

# wsman invoke -a EnumerateClassNames -h <hostname> -P <port> -u <user> -p <pass> -y basic --namespace root/cimv2 http://schemas.openwsman.org/wbem/wscim/1/intrinsic | grep name | wc -l

1271



# ./test_ecn | wc -l

104


The above test_ecn enumerates the class names from root/cimv2 by default.


Thanks
Prashanth

[Prash_blah]

After looking at the sources, i noticed that wsman calls enumerateClassNames with the DEEP_INHERITANCE flag. Is there a way to disable this?

-Prash

Prash_blah wrote:

Hi,

I am trying to use the intrinsic method enumerateClassNames in wsman and comparing the output to the test_ecn in the sfcc test source folder. I noticed that the output is different. Wsman enumerateClassNames shows more than double the number of class names shown by sfcc directly. Can someone tell me why???

# wsman invoke -a EnumerateClassNames -h <hostname> -P <port> -u <user> -p <pass> -y basic --namespace root/cimv2 http://schemas.openwsman.org/wbem/wscim/1/intrinsic | grep name | wc -l

1271



# ./test_ecn | wc -l

104


The above test_ecn enumerates the class names from root/cimv2 by default.


Thanks
Prashanth

[Klaus Kaempf]

Hi Prash,

* Prash_blah <prashanth.venky@...> [Sep 30. 2009 10:28]:
>
> After looking at the sources, i noticed that wsman calls enumerateClassNames
> with the DEEP_INHERITANCE flag.

right, I used this flag since sfcc does not report the parent class.
So there is no other way to get a complete class list.


> Is there a way to disable this?

Not in the current version (2.2.0), I'm sorry. But I gladly take your
mail as an enhancement request for 2.2.1 ;-)

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Prash_blah]

Thanks Klaus. I will wait for 2.2.1 :-)

Klaus Kaempf wrote:

Hi Prash,

* Prash_blah <[e-mail]> [Sep 30. 2009 10:28]:
>
> After looking at the sources, i noticed that wsman calls enumerateClassNames
> with the DEEP_INHERITANCE flag.

right, I used this flag since sfcc does not report the parent class.
So there is no other way to get a complete class list.


> Is there a way to disable this?

Not in the current version (2.2.0), I'm sorry. But I gladly take your
mail as an enhancement request for 2.2.1 ;-)

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openwsman-devel mailing list
[e-mail]
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Prash_blah <prashanth.venky@...> [Oct 01. 2009 08:37]:
>
> Thanks Klaus. I will wait for 2.2.1 :-)

You're welcome :-)

Now this raises the question on how to pass this flag to opewsman.

I see three options to implement this in openwsman

1. pass it as 'flags' in the client_opt_t structure. This is easy to
   implement but would rule out the 'wsman' cli tool as it doesn't
   support setting the client options (afaik).

2. pass it via the 'selectors' array. This is how e.g. the cim
   namespace (setting the '__cimnamespace' selector) is set.
   Selector are appended to the resource URI.
   
3. pass it via the 'properties' array. Properties are method
   arguments and look like a 'natural' way to pass flags to
   EnumerateClassNames.
   Properties are passed as --prop=<key=val> to wsman.

Comments, suggestions, preferences anyone ?

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Prash_blah]

I think option 3 would be a good way as it would be compatible with both the wsman client and the api.

-Prash

On Thu, Oct 1, 2009 at 1:26 PM, Klaus Kaempf <kkaempf@...> wrote:

* Prash_blah <prashanth.venky@...> [Oct 01. 2009 08:37]:
>
> Thanks Klaus. I will wait for 2.2.1 :-)

You're welcome :-)

Now this raises the question on how to pass this flag to opewsman.

I see three options to implement this in openwsman

1. pass it as 'flags' in the client_opt_t structure. This is easy to
  implement but would rule out the 'wsman' cli tool as it doesn't
  support setting the client options (afaik).

2. pass it via the 'selectors' array. This is how e.g. the cim
  namespace (setting the '__cimnamespace' selector) is set.
  Selector are appended to the resource URI.

3. pass it via the 'properties' array. Properties are method
  arguments and look like a 'natural' way to pass flags to
  EnumerateClassNames.
  Properties are passed as --prop=<key=val> to wsman.

Comments, suggestions, preferences anyone ?

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Prashanth Venky <prashanth.venky@...> [Oct 01. 2009 11:01]:

> On Thu, Oct 1, 2009 at 1:26 PM, Klaus Kaempf <kkaempf@...> wrote:
> >
> > I see three options to implement this in openwsman
> >
> > 1. pass it as 'flags' in the client_opt_t structure. This is easy to
> >   implement but would rule out the 'wsman' cli tool as it doesn't
> >   support setting the client options (afaik).
> >
> > 2. pass it via the 'selectors' array. This is how e.g. the cim
> >   namespace (setting the '__cimnamespace' selector) is set.
> >   Selector are appended to the resource URI.
> >
> > 3. pass it via the 'properties' array. Properties are method
> >   arguments and look like a 'natural' way to pass flags to
> >   EnumerateClassNames.
> >   Properties are passed as --prop=<key=val> to wsman.
> >

> I think option 3 would be a good way as it would be compatible with both the
> wsman client and the api.
> -Prash
>

Looking more closely at the code, option 2 evolves as the most natural
way to pass cim namespace information to the enumerateClassNames calls.

Passing it via selectors (adding it to the resource URI) is supported
in a generic way and should work out-of-the-box for all CIM operations.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel