Type information missing warning after upgrade to StreamBase 10
Article ID: KB0080617
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 10.3 |
Description
I have imported an project from StreamBase 7 into Streambase 10, but when I run it I get a warning "Type information missing. Upgrade module."
The warning looks like this:
default-engine-for-com.example.test_app:2018-08-16 11:40:58.150000-0300 [EventFlow Fragment] WARN com.streambase.sb.runtime.RuntimeUtil: At file C:\Users\user\Documents\StreamBase Studio 10.3 Workspace\.nodes\test_app.user\application\fragments\com.example.test_app\com\example\sample_interfaces \TopLevel.sbapp: Type information missing. Upgrade module.How do I upgrade a module?
Resolution
This warning will not affect the execution of the EventFlow fragment or application.
To suppress this warning, open the .sbapp file in an EventFlow editor (in the example above, TopLevel.sbapp) and make a minor change. The change could be as simple as adding a stream and then deleting it. When the .sbapp is then saved, the missing package information will be added to the file and this warning will no longer appear.
New in StreamBase 10.3.0 a module may have an additional annotation indicating what package it is in. This is to assist error reporting so that the error can be associated with a module path in the project. If this information is missing, a related error message will only have the runtime path (container.module.operator) and not also the project package path (com.example.filename).
In an upcoming release we expect Studio to detect and offer a Quick Fix option to resolve this issue.
To suppress this warning, open the .sbapp file in an EventFlow editor (in the example above, TopLevel.sbapp) and make a minor change. The change could be as simple as adding a stream and then deleting it. When the .sbapp is then saved, the missing package information will be added to the file and this warning will no longer appear.
New in StreamBase 10.3.0 a module may have an additional annotation indicating what package it is in. This is to assist error reporting so that the error can be associated with a module path in the project. If this information is missing, a related error message will only have the runtime path (container.module.operator) and not also the project package path (com.example.filename).
In an upcoming release we expect Studio to detect and offer a Quick Fix option to resolve this issue.
Issue/Introduction
Steps to resolve this runtime warning
Feedback
Yes
No
Powered by
