I have not changed anything in the component property file,
nor the IDL that is being generated. It's like something in
my environment has changed that is causing the Jaguar
Manager to act differently. I've uninstalled and reinstalled
EAServer and it still generates the new code.

The component Instance Property checkboxes that are checked
are Concurrency, Pooling, and Sharing. The new code that is
generated has a "_singleton" member and a "getInstance()"
method to return it.

This makes sense to me, as the property file has
"sharing=true". However, the code that was generated prior
to Friday never had this member nor method. I've compared my
property file against the one that we use on our Solaris
build platform, and they are identical. The generated code
on the Solaris platform does not have the member nor method.
Both generated files (new and old) have a reference to the
property file - stating that it was generated from it.

I am certain that my Windows XP client did not generate this
new code prior to Friday. So, what would make the code
generation do this? It is possible that our PC
administrators pushed out some OS changes that might be
affecting this.

The underlying problem is that the implemenation file throws
an exception in the constructor that the skeleton doesn't
catch. I could change the baseline code to not do this, but
I want to know why things have changed and how to get back
to our original baseline. I'm working on a major software
release and I don't want to make changes to code that has
been working for years and is not part of the release.
That's too risky at this point.

Any ideas?

Thanks,

-Donnie
EAServer 5.0

Try changing the "sharing" property to false and regenerating the skeleton.