Sybase, Inc.
One Sybase Drive
Dublin, CA 94568
1-800-8-SYBASE (North America)
Web: http://www.sybase.com


Dear Customer:

Enclosed please find:

EBF 14254

for the following platform:

Windows x86 32-bit

This EBF is part of this release:

WorkSpace 1.6

This EBF contains updates for the following product(s):

WorkSpace Studio
WorkSpace Designer
WorkSpace Designer Studio
WorkSpace Designer Enterprise
WorkSpace Designer Studio Enterprise
WorkSpace Mobile Development
WorkSpace Database Development
WorkSpace Process Orchestration
WorkSpace Web Application Development
WorkSpace DataArchitect
WorkSpace DataArchitect Enterprise
WorkSpace Data Federation
WorkSpace Services Development

We recommend that you install this EBF as soon as possible.

Documentation for new and enhanced features is provided in the Sybase
WorkSpace
1.6 ESD #1 What's New available on the Sybase Product Manuals Web site
(http://sybooks.sybase.com/nav/base.do).

We appreciate your patience while we resolve problems in the product and
your
willingness to install this EBF. Please contact Technical Support if you
encounter any problems using this product and let them know that you are
using
this EBF.

This documentation includes these sections:

* Platform Specific Details

* Loading Instructions

* New Fixes in this EBF

* All Fixes Included in this EBF (EBF14254_Buglist.txt)

* List of Files in this EBF (EBF14254_Filelist.txt)

Sincerely,

Sybase Engineering

--------------------------------------------------------------------------------


Platform Specific Details
-------------------------

This section contains platform specific details of this EBF.

This EBF is applied to Sybase WorkSpace 1.6. It is compatible with Unwired
Orchestrator 5.1 ESD #6.


Loading Instructions
--------------------

This section contains instructions for loading the new software onto your
system.

Pre-requisites:
Install WorkSpace 1.6 GA Product first before applying this patch.

Note:
1. Make sure you backup your current files before applying the patch.
2. The location where the Sybase WorkSpace has been installed is referred to
as
the WorkSpace home directory (WORKSPACE_HOME) in this document. WorkSpace
home
directory could be C:\Sybase\WorkSpace.


1. Download EBF14254.zip to a temporary directory on your local machine.

2. Shut down WorkSpace, if it is running.

3. If you have installed DEServers from WorkSpace, then shut down all
Development Runtime Server applications.

4. Install the zip
Unzip the ws1.6_EBF1.zip to %WORKSPACE_HOME%.
(Say yes to replace the files)

5. Clear Eclipse Cache
Start a command prompt window and do the following:
cd %WORKSPACE_HOME%\Eclipse
eclipse -vm %WORKSPACE_HOME%/JDK1.4.2_06/bin/javaw.exe -clean

6. Shutdown Eclipse

7. If you have installed DEServers from WorkSpace:
Update the EAServer NamedClassLoader Configuration by running the
following
config utility:
change directory to %WORKSPACE_HOME%\DevRuntimes\UO\bin
run configprops.exe

8. The patch is installed and is ready to use.


New Fixes in this EBF
---------------------

The following is a list of fixes which are specific to this EBF. The list is
sorted
by the component in which the bug was fixed.

For a complete list of fixes in this EBF, see EBF14254_Buglist.txt.

Component BugID Description
---------------- ------ ----------------------------------------------
BP Engine 433999 Business processes with large numbers of
assignments were running very slowly. This was
showing up with business processes that invoked
other services, such as database services which
exposed multi-part parameters. To address this
problem we have made the following fixes: -
Improved caching of SAXParsers during
assignments.
- Fixed a bug in the converters whereby we were
retrieving cached converters using an improper
key. - Improved pooling of non-transactional
database connections. - Optimized the count
function in our Jaxen implementation. - Improve
string handling in xpath processing. - Improved
performance of XML to Java converter. - Lazy
instantiation of DOMXPath objects during node
building. - Modified the database service
provider
to accept aggregated (i.e. complex type)
parameters. -Optimized the process of two step
conversion (where a direct format converter
from
the source to the target is not available).
Created an object that holds the two converters
and facilitates the two step conversion. This
eliminates a number of format converter lookups
as
well as an error routine when a converter is
not
available. - Reduced reliance on the
MessageFormat
object to create simple XML strings, since
doing
so incurs an unnecessary parse operation. -
Optimized creation of the key used for variable
lookups. - Optimized processing in the
SybValue2XML converter by simplifying
conversion
steps for strings.

BPEL Service 447394 Complex Activity "windows" are now drawn on a
Editor separate "canvas layer" which has a higher
z-order
than simple BP activities. This prevents the
simple icons that are not contained within a
Complex Activity from being drawn on top of the
Complex Activity window. This has the
unfortunate
effect that a Complex Activity will obscure
simple
activity icons, however these can be located by
selecting from the outline view, or by
minimizing
the Complex Activity.

Creation Wizards 447423 Description: ASE Stored procedures that contain
parameters with 'univarchar' type do not run
correctly if the value of 'univarchar' is null.
This issue only happens in ASE 12.5.2.x.
Resolution/Workaround: Change the default value
of
univarchar to ' ' (space). Remaining issues:
If the user clicks on 'Null' checkbox in the
Configure Parameters dialog, the stored
procedure
will be running forever. Workaround:
User
should avoid clicking check box 'Null' for
univarchar in the Configure Parameters dialog,
otherwise the stored procedure will be running
forever; but the user can still click on the
Terminate button to terminate the running
stored
procedure in SQL Results view.

Creation Wizards 445165 Description: The Procedural Object creation
wizard
cannot list user-defined datatypes with spaces
in
the type name. Resolution: This issue has been
fixed.

Creation Wizards 436773 Problem: It took about 10 seconds to create a
stored procedure. Resolution: This performance
issue has been fixed.

Creation Wizards 436770 Problem: It took about 2 min. to create a
trigger
in a large database. Resolution: This
performance
issue has been fixed.

Database 443123 Problem: The Database Explorer view is very
slow
Explorer in expanding the 'Stored Procedure' node for a
large database. Resolution: This performance
issue has been fixed.

Service - 451711 Problem: Examples are needed for the XPath
Business Process Expression Editor. Resolution: Included with
the
Sybase WorkSpace 1.6 ESD #1 download is a
document
and sample project that help you to understand
this feature. After installing the ESD, locate
the
document, Comparative Use of the Expression
Builder and XPath Editor, in the folder named
ExpBldrXPathEdrdoc_samplePrj at the root of
%WORKSPACE_HOME% where the default is
C:\Sybase\WorkSpace. To build an assignment,
open
the following business process service in the
Service Editor: AssignExample.svc_bpmn To
build
a single rule expression with a condition, open
the following business process service in the
Service Editor: SingleRuleExample.svc_bpmn To
build an expression for a complex activity with
a
loop condition, open the following business
process service in the Service Editor:
ComplexExample.svc_bpmn

Service - 451687 Problem: The Business Process editor allows the
Business Process user to create a local variable with a space,
but
an error is reported when using the local
variable
in XPath Expression Editor. Problem
Resolution/Workaround: For local variables, do
not
use spaces in the local variable name.

Other 451376 Problem Description: If you are importing
database
connection profiles from a sql.ini file and the
service type value contains "_" (underscore),
this
service entry will not be retrieved by the
Import
Connection Profile wizard. All other valid
entries
will be retrieved. For example: [ABC]
master=TCP,abc,4104 query=TCP,abc,4104
win3_query=TCP,abc,4104 Workaround: modify
sql.ini file, remove "_" (underscore) from
service
type name.

Database 448598 Problem: An overflow error occurs after the
user
Development expands and clicks the subscription node under
a
Replication Server connection profile.
Resolution: This issue has been fixed.

Database 447947 Description: When using Sybase WorkSpace with
ASE
Development 12.5.3, an error occurs after a database and
user
are created and the user attempts to log in.
The
error states, "Catalog tables could not be
created
and are not available for use." Workaround:
The
error message occurs during an attempt to
establish attribute-related tables for a
DataWindow. To prevent this from occurring,
deselect the 'Use Extended Attributes' checkbox
in
the Database Preferences dialog. Click the
drop-down
menu for the Database Explorer perspective and
select Design | Options to open the Database
Preferences dialog.

Other 446524 Problem: A "save failed: null" dialog message
occurs. Resolution: A rule in the file
serializer
has been relaxed so that "dangling" model
objects
(orphans) are ignored instead of causing a
fatal
error. This was caused by objects that had been
deleted and removed from the model hierarchy,
but
had not been disposed correctly, causing the
mysterious "save failed: null" dialog message.

Database 441896 Problem: Cannot create procedural objects on
ASE
Development 12.5.3 when logged in as a user who is aliased
to
'dbo'. Resolution: This issue has been fixed.

Service - 432196 Description: When a parameter is defined as a
Business Process Complex data type and has the same name as the
root of the Complex type, the XPaths of the
assign
target variables are erased. Resolution: This
problem has been fixed and the XPaths of assign
target variables are no longer erased.

Runtime 440350 In a stateful business process the value of
variables could be lost in specific scenarios.
This loss in the value of the variable
manifests
itself as a premature end of file error in the
log
file. This can only occur for variables whose
values are set prior to the saving of the
business
process state and then accessed again after the
state is restored. This problem is most likely
to
manifest itself when servers are configured in
a
cluster. This change fixes the problem.

Runtime - 443454 When a Java Service was invoked from within a
Service Business Process Service, the output from the
Java
Invocation Service could be mapped in an assignment, but
the
assignment failed at runtime. This was due to a
bug in the way Java Service namespaces were
being
registered in the runtime type registry. This
problem has been fixed.

SQL Debugger 440308 Problem: Failed to load trigger definition
during
debugging when the quoted identifier preference
is
'ON'. Resolution: This issue has been fixed.

SQL Debugger 440285 Problem: Cannot step into system stored
procedure
during debugging. Resolution: This issue has
been
fixed.

SQL Debugger 436774 Problem: It took 30 sec. to start SQL Debugger.
Resolution: This performance issue has been
fixed.

SQL Editor 447292 Problem: Enterprise Explorer view throws
exception
when importing sql.ini and converting them into
connection profiles. Resolution: This issue
has
been fixed.

SQL Editor 439880 Problem Details: The content assist in SQL
Editor gives the user the incorrect syntax when
typing in "create index index_name on
table_name
(". The content assist gives
table_name.column_name, which doesn't fit the
ASE
index. If user select one column from content
assist and try to save, error will occur.

SQL Editor 433862 Problem: SQL Debugger should prevent the user
from
setting breakpoints for long-named procedural
objects in ASE. Problem Details: The user
failed setting a breakpoint in an ASE stored
procedure with long name, the breakpoint would
not
be adjusted to the nearest valid SQL statement,
stack tracke were displayed in ASE's error log
file, and the user will not able to debug any
ASE
stored procedures from that point on until they
perform the following steps: 1. Delete all
the
breakpoints from the Breakpoint view of SQL
Debugger. 2. Shut down WorkSpace 3.
Shut
down and reboot ASE Server. 4. Restart
WorkSpace 5. Do not set breakpoint in
stored
procedures or trigger with name longer than ~22
bytes. The problem is caused by a debugging
related ASE server problem. Solutions:
Database Development Tooling adds a safeguard
mechanism that prevents the user from setting
breakpoint for ASE long-named procedural object
(SPs and triggers). In additon, there's a new
debugger preference for the user to turn off
the
safeguard so that when the user installed ASE
debugger patches in the future, we don't need
to
take out the safeguard mechanism, and the user
only need to disable the safeguard from the
preference page.

SQL Editor 433444 Problem: Temp table wizard considers any object
name prefixed with '#' as a temp table.
Details:
Temp table wizard considers any object name
prefixed with '#' as a temp table. For example,
with the following statement referencing a
stored
procedure 'pbcatcol', temp table wizard still
popped up: create index #abc on pbcatcol
(pbcatcol.pbc_case)

Service - 451801 Problem: When using the XPath Expression
Editor,
Business Process it is possible to create local variables with
same
name but different scopes (different complex
activities). However, when you do this, local
variables with the parent scope will disappear
and
not show in the Local Variable list when mouse
is
focused on the nested complex activity.
Problem
Resolution/Workaround: Do not create local
variables with the same name, even with a
different scope.

Service - 451255 Problem: When using the XPath Expression
Editor,
Business Process the Copy/Paste/Cut subitems of the Edit menu do
not work. Resolution/Workaround: Set to
"Properties Panel" (not "Properties" Session),
and
use shortcuts Ctrl-C/Ctrl-V/Ctrl-X for
Copy/Paste/Cut.

Service - 450022 Problem: In some cases, cleaning a project
Business Process (Project -> Clean...) may introduce false error
messages/decorators to some services.
Resolution/Workaround: Make a minor change to
the
service (e.g. move an icon on the Business
Process
canvas), then save it.

Service - 441455 When a one-way business process service throws
a
Business Process fault which is not caught by a fault handler,
the
runtime engine should write the original
message
that initiated the service along with a stack
trace to the MONITORQ. This functionality was
not
working correctly: neither the original message
nor the stack trace was being written to the
MONITORQ. This problem has been fixed.

Service - 440546 The wire format properties of a message service
Business Process allow the user to set the encoding of the
outbound
message for both text and bytes messages in the
UO
tooling. Prior to this change all XML messages
were output as UTF-8 regardless of the selected
encoding. This fix encodes the output XML
message
based on the encoding selection of the user for
both text and bytes messages. Note: It is
strongly recommended that all XML messages be
output as bytes messages.

Service - 436263 Problem: Assigning an integer datatype to int
Business Process datatype in a business process will prevent the
packaging and deployment of the process.
Solution. A new property as been added to the
preferences selection that allows the user to
turn
off the reporting of type mismatches as errors.
To stop the GUI from checking for type
mismatches
go to
Windows->Preferences->Services->Expression
Builder and deselect "Treat Type Mismatches as
Errors".

Service - 434315 Problem: This bug was in the BP/Rule editor's
Business Process handling of XPaths coming from schemas which
import other schemas. In the rule editor,
XPaths
are converted between a format with
{namespaceURI}
before the element names and sy<n>: namespace
prefixes between them. The original code only
handled the targetNamespace for the XPath, but
if
the XPath comes from a schema which imports
other
schemas, there may be other namespaces
references
in the XPath. Fix: Rule Editor conversion of
XPaths with {ns} to/from XPaths with sy<n>: The
fix is to sourceTextToXPath and
xpathToSourceText
in RuleModelUtil.java which is in
com.sybase.stf.editor.rule. I also had to make
getNamespaceManger public. This is in
XSDElement
which is in com.sybase.stf.sxi (in suadeframe).

Service - 433276 Description: There was a bug with using
predicates
Business Process (square bracketed expressions) in XPaths. For
example "/a/b/c[x]/d". It would cause the XPath
expression to be lost. Resolution: This has
been
fixed. There remains however a problem with
predicates that do arithmetic, for example,
"/a/b/c[x + 1]/d". The workaround is to compute
the value of the predicate in a previous
assign,
then use the resulting local variable in the
predicate.

Service - 432653 Description: Potential problems existed with
Business Process business process performance when saving,
selecting an assign activity, or building
incrementally. Resolution: A fix was made to
alleviate all potential business process
performance problems.

Service - 448942 Description: Sybase Workspace may be unable to
Database accurately generate database stored procedure
metadata. Specifically, when using Enterprise
Explorer to browse ASE stored procedures, the
parameters for these stored procedures are not
visible, nor can Workspace create services for
these procedures.

Service - 437809 There is a new feature implemented to support
Database aggregation parameter for DB service. The
related
GUI changes are following: 1) Aggregation
parameter option check box added at
workbench(Window->Preferences->Services->Database
Service Editor), service and operation
level(Properties Panel) 2) Aggregation
parameter
display at service explorer and variables panel
for BP service editor Also please check
attached
file for use case.

Service - 432952 Description: Certain scenarios present a
potential
Framework for corruption of a business process.
Resolution:
To prevent potential corruption of a business
process, these following capabilities have been
added: 1) Modifications to the Diagram Model
mapper to detect inconsistencies and attempt
recovery on load of models. The new preference
option is found under Sybase Inc | Graphic
Editors: Perform model validation and recovery.
Set this option to cause the model mapper to
attempt recovery. See the Sybase WorkSpace
bookshelf for more information on setting
preferences. 2) Automatic backup of the
Business
Process temp folder prior to model
serialization.
3) New business process preferences found under
Sybase Inc | Services | Business Process
Service
Editor: . Generate EMF Model diagnostics - Set
this option to perform diagnostics on the
business
process and diagram models when saving your
work.
Diagnostics are written to the error log. .
Log
debugging messages - Set this option to track
user
gestures and in-memory model changes when
editing.
. Restore to last valid state on failure - Set
this option to automatically recover the
business
process service to its last valid state if
model
serialization fails when saving your work. When
this option is off, you can still recover the
business process to the last valid state by
copying the backup from the temp folder. To
manually restore a BP from a temporary backup
in
your file system: 1) Find your windows "temp"
folder. Ex. c:\WINDOWS\Temp 2) Find a folder
with
your project name. Ex.
c:\WINDOWS\Temp\MyProject
3) Navigate the subfolder hierarchy of your
project to the folder containing the BP. Ex.
C:\WINDOWS\Temp\MyProject\Services\BusinessProcess
4) Find your BP Service file with an extension
svc_bpmn. Find a corresponding file with a name
of
"." + %BPServiceName% + .bpmn. Copy these 2
files
back to the corresponding folder in your
project.
5) Navigate back to the project level and find
a
folder called ".metadata". Ex.
C:\WINDOWS\Temp\MyProject\.metadata 6)
Navigate
within the .metadata folder to the same folder
structure until you find the following files:
"."
+ %BPServiceName% + .bpmn.gem %BPServiceName% +
.rules (these may not exist if you did not
develop
any rules in your service) %BPServiceName% +
.rules.gem (these may not exist if you did not
develop any rules in your service) Copy these
files back to the corresponding folder in your
project.

Service - 443667 With logging turned on the business process
engine
Message was outputting XML messages to message services
without any XML prologs. (The XML prolog looks
like--<?xml version="1.0"
encoding="UTF-8"?> --and
appears at the beginning of the message.) This
problem has been resolved so that all XML
messages
are output by the Business Process Engine with
XML
prologs regardless of whether logging is set.

Service - 431847 Description: SMTP service not handling
multi-byte
Message characters correctly. The wrong characters
sometime appear in the subject and body of
multi-
byte messages, such as Japanese or Chinese
encoded
messages, transmitted using the email service.
Resolution: A Subject Encoding attribute was
added
to email service operation context properties.
The
business process service now allows you to
specify
encoding for both message subject and body,
enabling proper handling during email
transmission. This specific SMTP service fix
requires an additional Sybase WorkSpace 1.5 EBF
download: EBF 13749.

Service - XSL 434231 Description: If you use an XML Schema whose
Transformation filename includes the '-' character in a
Transformation Service, the service will run
design time tests correctly, but when you use
the
service at run-time, there will be an error.
Workaround: There are 2 alternative
workarounds:
i) Rename schema files which include '-' so
that
they do not include this character. Ideally you
should do this before creating the
transformation
service. ii) If you do not rename the schema
files
with '-' in their names, after creating the
transformation service, you should go to the
Map
page, make sure either the Properties Panel
view
is open or you have opened the Properties
section
on the map page, select the title bar of each
content model which comes from a schema with
'-'
in its filename and remove the '-' character
from
the Logical Name of the content model.

Service Palette 440139 In a business process service, assignments
involving variables defined by non-namespaced
schemas occasionally resulted in invalid XPath
expressions. These schemas are now handled
correctly.