Hi Jeff ; I do not think that we need to do that . In the meantime if we can do that that will be great as well , then we can minimize the number of issues users are getting when they trying to create a ConfigurationContext.
Thanks Deepal >Howdy Deepal, > >Since you took out the initalization of the instance variables in >ConfigurationContext and moved it to the ConfigurationContextFactory, >shouldn't the ConfigurationContext constructor change be package protected >instead of public to force the use of the factory, and thus get those >instance variables initialized? > >Thanks, >Jeff > >IBM Software Group - WebSphere Web Services Development >Phone: 512-838-4587 or Tie Line 678-4587 >Internet e-mail and Sametime ID: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
