Problem: Errors occur when packaging a service. Severe packaging errors appear in the console view as orange text.
Solution: Use the following sequence to troubleshoot errors during packaging:
Copy the contents of the console view display in a text file, and send this information to Tech Support.
The following information is an example of a severe error:
[package.artifacts] com.sybase.io.pkggen.kernel.BuilderException: The BPMN file C:\support\pecos\Bart\MyTest394214\.MyBPService.bpmn had a dangling namespace http://schemas.sybase.com/services/security/V1.0/
[package.artifacts] at com.sybase.io.pkggen.kernel.BPPostProcessor.processWSDL(BPPostProcessor.java:267)
[package.artifacts] at com.sybase.io.pkggen.kernel.PackageBuilder.complete(PackageBuilder.java:138)
[package.artifacts] at com.sybase.io.pkggen.kernel.BuilderFactory.invokeBuilder(BuilderFactory.java:44)
In rare circumstances, the packager may detect a non-fatal condition and issue a warning while continuing with the package operation. These messages again appear in orange. An example of such a warning is:
[package.artifacts] Dependency "C:/Sybase/or50Dt/Eclipse/workspace/.metadata/.plugins/com.sybase.stf.models.services.security/UOSecurity.svc_security" used by "/MyTest394214/MyBPService.svc_bpmn" does not exist.
2. If packaging succeeds but deployment errors are encountered, save a copy of the <package name>.svcpkg file that was produced during packaging, as Tech Support may request it.
If you use long names for service files and the services package file, packaging may fail when the path to an intermediate generated file exceeds operating system limits. In this case, try repackaging the services with a package that uses a shorter file name.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com