On Fri, Jan 2, 2009 at 11:54 PM, Jordan Zimmerman <[email protected]> wrote:
> >Is there any more to the stack trace? This looks like a configuration > >problem, but the base exception seems to have been cut off so it's hard > to > >know what's missing. > > The rest of the exception goes into our application server. The > exception occurs during WAR initialization. If there's nothing else, your best bet is to walk the construction path from the servlet. The fact that the line right before the exception is reading the container configuration tells me that there's probably a problem locating the container configuration file. Check to make sure that the container configuration location is being set to a valid location. By default, we look for a resource in containers/default/container.js. You can override this in shindig.properties or by manually creating ContainerConfig. If it's not the container configuration, then there should be additional information in the stack trace indicating what class failed to construct. If not the container config, the most likely problem would be missing properties. Compare your properties file to the default and see if you're missing anything. > > > Jordan Zimmerman > Principal Software Architect > 831.647.4712 > 831.214.2990 (cell) > [email protected] > > SHOP*COMTM > All your favorite stores. > OneCart(r) convenience. > www.shop.com > > > This message (including any attachments) is intended only for > the use of the individual or entity to which it is addressed and > may contain information that is non-public, proprietary, > privileged, confidential, and exempt from disclosure under > applicable law or may constitute as attorney work product. > If you are not the intended recipient, you are hereby notified > that any use, dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify us immediately by telephone and > (i) destroy this message if a facsimile or (ii) delete this > message > immediately if this is an electronic communication. > > Thank you. >
