BuilderTroubleshooting

Visual Mashup Builder

AppliBuilder User Documentation

Troubleshooting Tips

AppliBuilder is built on a number of technologies, products, libraries, and moving parts. And being a new product, has been tested for a limited number and types of applications or combinations of these piece parts. We will try to document issues to watch for and other tips on this page as they arise.

We have not put much energy as yet into performance optimization. We'll get to that soon. Meanwhile, here are some issues we have encountered.

Basic Operations

We have faced issues when combining Scriptaculous and Rico widgets on the same page, due to incompatible versions of the same prototype library used by these libraries.

Web Services

There are often namespace issues when using the WSDL/SOAP Wizard with specific WSDL files and corresponding services. The requested output will not be found with the generated XPath values. You may need to insert the appropriate namespace prefix (or remove a namespace prefix) to get it working. Try adding tns: prefix to output XPath entries and test the web service requests. You cannot assume the generated values will work for any WSDL file.

Performance Issues

It may not surprise you that theis product will need a very high speed connection between your browser and server. Without that, the tool will be unusable.

When using AppliBuilder with DataCaster, a major potentail performance issue is when the database is started/stopped with each request. Since DataCaster is designed to function as an embedded database, it supports this model - which is turned off by default. When using AppliBuilder make sure the db.delayed_shutdown_after_disconnect parameter is set to true in your serverprefs.xml in the conf dir.