Description:
Symptoms
========
When using very long Concept/StateMachine names in a BE 2.0 project, this will result in an exception when building the Archive.

Impact
======
BE 2.0 Archive creation fails with following exception:

com.tibco.be.parser.codegen.CompilationFailedException: C:\DOCUME~1\tnguyen\LOCALS~1\Temp\BE\conceptSrc\be\gen\BusinessRules\Provisioning\PrivateRules\DecomposeAndSequence\Concepts\OBCUnsolicitedModificationCommandInstance.java:1261: error while writing be.gen.BusinessRules.Provisioning.PrivateRules.DecomposeAndSequence.Concepts.OBCUnsolicitedModificationCommandInstance.OBCUnsolicitedModificationCommandInstance$StateMachine.$00240_OBCUnsolicitedModificationCommandInstance_StateMachine_Transition_12_Rule.$0_OBCUnsolicitedModificationCommandInstance_StateMachine_Transition_12_gc: C:\DOCUME~1\tnguyen\LOCALS~1\Temp\BE\conceptSrc\be\gen\BusinessRules\Provisioning\PrivateRules\DecomposeAndSequence\Concepts\OBCUnsolicitedModificationCommandInstance$OBCUnsolicitedModificationCommandInstance$StateMachine$$00240_OBCUnsolicitedModificationCommandInstance_StateMachine_Transition_12_Rule$$0_OBCUnsolicitedModificationCommandInstance_StateMachine_Transition_12_gc.class (The filename, directory name, or volume label syntax is incorrect)
class $0_OBCUnsolicitedModificationCommandInstance_StateMachine_Transition_12_gc extends com.tibco.cep.kernel.model.rule.impl.ConditionImpl
^
1 error

Workaround
==========
The State machine archive building requires work around to shorten the function name.

Cause
=====
This is due to the 256 char filename limit. During BE archive building the temp file names when result in more than 256 chars it breaks. This issue is seen in BE 2.0.

Resolution
==========
This issue is targetted to be fixed in future BE 2.x updates.
Symptoms:

Cause: