Apama 10.15.1 | Other Resolved Issues | Release 10.0.0 | Software AG Designer
 
Software AG Designer
*PAM-27151
The command engine_deploy --outputDeployDir <relative path> fails only when DES is enabled.
YAML generation was failing when a project with Digital Event Services (DES) enabled was exported to an output directory specified with a relative path.
This issue is fixed now.
*PAM-27177
ApamaDoc export fails when the Apama project contains query files.When ApamaDoc is generated for an Apama project containing query files, the operation fails. This issue has been fixed.
*PAM-27039
Ant run fails if a project has a parent excluded folder and a child folder has a jar.
If an Apama project contains an excluded parent folder and an included inner child folder which contains a jar file, Ant failed with this error:
"IllegalStateException: Workspace is closed"
This issue has been fixed whereby any included folders, inside the excluded folder, will have their files injected correctly into the correlator.
*PAM-27012
Ant exported build.xml has absolute path for the standard-codecs.yaml configuration file.
When a Software AG Designer project containing connectivity plug-ins was exported to an Ant script, the resulting build.xml used an absolute path to refer to some of the YAML files. This may have prevented the script from running correctly on other machines and operating systems.
This issue was fixed in 10.0.0.1.
*PAM-26942
Exporting CDP to the same (exported earlier) location is showing an error dialog in Designer.
If a CDP file was exported to an already existing file, then the CDP export wizard showed a warning and after clicking Finish, it failed with the exception “File already exists”. This has been fixed to just show a warning, but no exception will be thrown. Also, if there are multiple projects with the scenario file using project blocks and if the user tries to do a CDP export without opening the scenario file, then the export failed with an exception.
This issue was fixed in 10.0.0.1.
*PAM-26189
Invalid stream query inputs in combination with equi-join can crash the correlator/Designer.
An EPL stream query that uses an equi-join and has an invalid input item will cause the correlator to crash upon injection, or cause a fatal error in Software AG Designer when built inside an Apama project. For example:
from e1 in noSuchVariable join e2 in all E() on e1.i equals e2.i
select
f(e1, e2)
This has now been fixed in both the correlator and Software AG Designer.