Re: CIMOM refuses EmbeddedObject with unknown class

> Technically, it can work. I need
to create lot of classes, but if it's

> the price I must pay, I can do it. 'Lot of' = 10-15 for now + more
in

> future as the OpenLMI evolves. It's just copy-paste from each method,

> that could be even automated, so I wouldn't worry much about it.

As a circumvention for right now(so
this does not holds up development) that's okay. As a long-term solution
I do not really like it because we would clutter up the class repository.

> What troubles me a bit is description
of

> CIM_InstMethodCall.MethodParameters property:

>

> The parameters of the method, formatted as an EmbeddedObject

> (with a predefined class name of "__MethodParameters".

>

> I interpret it as the classname must be literally "__MethodParameters"

> and not a subclass of it. Am I reading it wrong?

I read it the same way.

Thanks a lot everyone for the responses,
ideas and suggestion! Much appreciated.

Right now I think we should go with
hard-coded classes __MethodParameters,
__JobInParameters and __JobOutParameters to
fix the current problem with JCP. For the future, having a qualifier to
enable the dynamic behavior would be great (Andy's fourth idea).

Kind regards,

Marek Szermutzky

Software Engineer / OpenPegasus Maintainer (PMC)

IBM Systems &Technology Group, Systems Software Development / z/OS
Capacity Management and Support

-------------------------------------------------------------------------------------------------------------------------------------------

IBM Deutschland

Schoenaicher Str. 220

71032 Boeblingen

Phone: +49-7031-16-5182

E-Mail: [email protected]

-------------------------------------------------------------------------------------------------------------------------------------------

IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats:
Martina Koederitz

Geschäftsführung: Dirk Wittkopp

Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294