Switch to standard view 
  Sybase logo
 
 
 



Release Bulletin Sybase® WorkSpace Version 1.5 for Microsoft Windows

 

Document ID: DC00348-01-0150-02

Last revised: August 2006



Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase® Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site
  1. Go to Product Manuals.

  2. Follow the links to the appropriate Sybase product.

  3. Select the Release Bulletins link.

  4. Select the Sybase product version from the Release Bulletins list.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.



Product summary

This release bulletin provides information on the following products:

Note:This release bulletin provides information on the Unwired Orchestrator Developer Edition. For information about issues concerning the Unwired Orchestrator Production Edition, see the Release Bulletin for Unwired Orchestrator 5.1.



Special installation instructions

Before installing Sybase WorkSpace and Sybase Developer Edition Servers review the following information.


Support for Internet Explorer

CR # 438841

Description: Sybase WorkSpace supports Eclipse 3.1.2, which does not support Internet Explorer 7.0

Workaround: Use Internet Explorer 5.x or 6.x.


Cannot create services

CR #430809

Description: After a fresh install or reinstall of Sybase WorkSpace, no service-related items are available in project context menus.

Workaround: Before starting Sybase WorkSpace for the first time after the install, run the clean command, and exit from Eclipse. Run this command from the eclipse directory under your Sybase WorkSpace installation or from an existing eclipse directory that has been assigned during WorkSpace installation. The clean command should be invoked as follows:

eclipse.exe -clean

Note:This command is required only once. The second time you launch Sybase WorkSpace, you do not need to run the clean command.


Extending a Sybase WorkSpace evaluation license

If your Sybase WorkSpace evaluation license has not expired, you can extend the license for an additional 30 days using the Preferences dialog in the Sybase WorkSpace tooling. See the Sybase WorkSpace Online Help for more information.

If the evaluation license has already expired, contact your Sybase representative for extension information.


Installing Sybase WorkSpace outside the default directory

CR # 429980, 430037

Description: When Sybase WorkSpace is installed in a directory other than the default directory (C:\Sybase\WorkSpace), the tooling is unable to find the Java Message Service (JMS) driver definitions.

Workaround: Manually edit the JMS driver definitions.

Editing the JMS driver definitions
  1. Open the Driver Definitions window. Select Window | Preferences from the Sybase WorkSpace main menu bar.

  2. Edit the driver definitions:

    1. In the left pane, select Sybase, Inc. | Driver Definitions.

    2. In the right pane, select the driver definition that you want to edit, and click Edit to open the Edit Driver Entry dialog.

  3. Edit the required JARs for each driver definition:

    1. Select each of the following files and click Edit Jar/Zip in the Edit Driver Entry dialog box to browse for the new location:

      <installation directory>\sybase_workspace\services\eclipse\plugins \com.sybase.easclient_5.3.0\lib\easclient.jar

      <installation directory>\sybase_workspace\services\eclipse \plugins\com.sybase.easclient_5.3.0\lib\easj2ee.jar

    2. Select each file and click Open to update the path in the driver definition.

    3. Click OK to complete the driver definition update.

      See the Sybase WorkSpace online bookshelf for more information on driver definitions.


Possible invalid host name for EAServer

CR # 417395

Description: When you run VPN while installing EAServer as part of the Sybase Developer Edition Servers installation, the installation could result in an invalid host name. In this case, EAServer, Unwired Orchestrator, and Unwired Accelerator (EAServer) fail to start, and all listener host names are replaced with “localhost” at start-up.

Workaround: Shut down VPN before installing EAServer as part of the Sybase Developer Edition Servers installation.


Setting up the Oracle JDBC driver

To use the Oracle JDBC™ Driver for database services, you must set up the Oracle JDBC driver.

Setting up the Oracle JDBC driver
  1. Add the Oracle JDBC driver JAR file to the following directory:

    <installation directory>\EAServer\java\lib<filename>

  2. Unzip and extract the files to:

    <installation directory>\EAServer\java\classes


Sybase WorkSpace incorrectly identifies the resource bundle

CR #406310

Description: A bug in the javaw.exe in jdk1.4.2 file causes Sybase WorkSpace to reference the system locale instead of the user locale, resulting in the incorrect identification of the resource bundle.

Workaround: Edit the SybaseWorkspace.bat file to execute the java.exe file to launch Sybase WorkSpace.

Editing the SybaseWorkSpace.bat file
  1. Search for javaw.exe in the following start statement and replace it with with java.exe:

    start "Sybase WorkSpace" /MIN "%ECLIPSE_ROOT%\eclipse.exe" -vm "%JDK_ROOT%"\bin\javaw.exe -vmargs -Djava.endorsed.dirs="%ECLIPSE_ROOT%"\endorsed -Xmx384M -XX:MaxPermSize=128m -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -DSampleObject=true -DPureJava=PureJava -Declipse.product=com.sybase.stf.pifbase.SWSproduct -Dosgi.splashPath=platform:/base/../sybase_workspace/doc/eclipse/plugins/com.sybase.stf.pifbase



Special upgrade instructions

If you have an existing installation of Sybase WorkSpace 1.0, you may need to complete the following additional setup for mobile, service, and database development.


Database service setup


Database setup

CR # 427317

Description: The Database Development feature in Sybase WorkSpace 1.5 runs with jConnect 6.05. If you plan to use any external Sybase databases as your target databases, you may experience problems if they run on jConnect 5.5 or lower.

Workaround: Verify that your external Sybase databases are set up to run on jConnect 6.05.


Migration issues

CRs #419443, 426015

Description: The migration of existing Sybase ASA, ASE, and ASIQ drivers and connection profiles are automatically updated to jConnect 6.0 from jConnect 5.5 when you launch Sybase WorkSpace 1.5.

However, if you have a database service with a custom endpoint that does not reference a connection profile, you need to edit the database service endpoint to update the jConnect information.

Workaround: Edit the JDBC endpoint using the JDBC Endpoint wizard.

Editing the database service endpoint
  1. Open the database service that you want to edit.

  2. Edit the service endpoint.

    See Editing a Service Endpoint on the Sybase WorkSpace online bookshelf for more information.

  3. In the Connection Profiles page, update the following jConnect information:

    Table 1: Connection Profiles Page

    Field

    Description

    Driver Class

    com.sybase.jdbc3.jdbc.SybDriver

    Driver Classpath

    <installation directory>\sybase_workspaceservices\eclipse\plugins\com.sybase.jconnect60_6.0.0 \lib\jconn3.jar


Unwired Accelerator setup

CR #426643

Description: If you have an existing installation of Unwired Accelerator from a Sybase WorkSpace 1.0 installation, and you choose to install Unwired Accelerator with your Sybase WorkSpace 1.5 installation, you must edit the JDBC driver information. Failure to do so will disable the SQL dialog when editing an existing database in a mobile application.

Workaround: Edit the JDBC driver information.

Editing the JDBC driver information
  1. Reset the JDBC driver information from com.sybase.jdbc2.jdbc.SybDriver to com.sybase.jdbc3.jdbc.SybDriver.

  2. Copy the jconn3.jar file into the following directory:

    <installation directory>\DevRuntimes\UA\tomcat\tomcat \webapps\onepage\WEB-INF\lib



Changed functionality in this version

For information on changed functionality and new features, see the What’s New guide on the Sybase WorkSpace online bookshelf.



Sybase WorkSpace issues

The following are known issues for Sybase WorkSpace features.


Connection profiles

CR # 420574

Description: If a machine name contains hyphens, Sybase WorkSpace cannot establish a connection with the following connection profiles when using the Enterprise Explorer:

Workaround: Do not install Sybase WorkSpace on a machine the contains hyphens in its name.


Database Development


Creating computed columns in Database Explorer

CR #417942

Description: You cannot create a computed column in Database Explorer. If you create a computed column elsewhere, such as in SQL Editor, and export the syntax in the Database Explorer, the syntax is not correct.

Workaround: Avoid any use of computed columns in Database Explorer.


Running SQL statements

CR #428135

Description: When you execute a SQL statement to create a table in an Adaptive Server Anywhere database, open the table in Database Explorer, and then expand the Columns folder, the datatype does not display for columns of type uniqueidentifier.


System procedures always display for ASIQ 12.6

CR #424147

Description: Database Explorer displays system procedures in the Procedures & Functions folder for ASIQ 12.6 even if the “Show System Procedures” option has not been selected.


SQL Debugger malfunction

CR #428601

Description: The SQL Debugger may not function properly for connection profiles that have been modified in online mode.

Workaround: If you need to modify the connection profile for an ASE, ASA, or ASIQ database, disconnect from the profile first. When you have finished modifying the profile, reconnect and proceed with whatever tasks require SQL Debugger.


Message Designer


Copying custom JAR files

CR #420812

Description: When you copy and paste a message definition (.wfim file) from one project to another using the copy/paste functionality in the tooling, the process does not copy the custom class JAR files that the message definition references.

Workaround: After copying and pasting a message definition (.wfim file) from one project to another using the copy/paste functionality in the tooling, you must also manually copy and paste the custom class JAR files into the MessageDesigns\CustomClasses directory of the target project.


String data with nonprintable ASCII characters

CR #419448

Description: Testing a message definition parser with string data may result in the following error message:

Cannot display results
Parse succeeded, but cannot display results.  Invalid XML document.

This error indicates that the test data contains ASCII non-printable characters that are not supported by the String datatype for this release.

Workaround: If your message definition must be able to parse ASCII non-printable characters, change the datatype of the appropriate field from String to Binary.


Mobile Development


SAP element is not working as designed

CR #427880, 427882

Description: On the SAP Element wizard page, you can select Direct Connection and supply the connection properties by editing the Direct Connection Properties table.

When you click Search in the Method field, Unwired Accelerator incorrectly queries the server using the default connection properties instead of the specified properties.


Working with Web Studio

CR: 429763

Description: If a string to be replaced is a substring of the replacing string and exactly half the size of the replacing string, it runs into a loop.


Service Development


Service editors

CR #428397

Description: Markers are not cleared in the Problem view if they are added when a service editor is open but resolved when an editor is closed. This becomes a problem when the service editor and the builder attempt to report problems of a similar nature.

For example, if a business process service is opened in the service editor at the same time a service referenced by the business process is edited, the referenced service becomes invalid. This causes the business process service editor to add a problem marker indicating that the referenced service has become invalid.

Workaround: To resolve the problem, open the service editor, edit the service, and save your changes.


Business process service


Using math expressions inside index predicates

CR #429800

Description: The business process service does not support math expressions inside index predicates.


Testing a SOAP service with a public WSDL

CR #429145

Description: If you are using an element that occurs more than once under two different namespaces in a public WSDL, you may have problems if you use the Test dialog.

Workaround: Use the SOAP Inspection dialog.


Using count variables in nested loops

CR #428930

Description: When you create a looping complex activity, a count variable is automatically created to facilitate development. The default count variable name is counter, causing a problem with nested loops. When you create a loop within a loop, all the count variables have the same name.

Workaround: If you plan to use count variables in a nested loop, change the default name of the count variable to a meaningful name within the context of the business process, for example, orderCounter or lineItemCounter.


Expression editor availability

CR #428910

Description: The expression editor is disabled for an assign activity if the source and target have not been specified or, in a Prune, the target has not been specified. The expression editor is available if the source is a literal, but the editor contains the target node only, and nothing can be added.


Deploying two packages that listen for messages on the same input queue

CR #424055

Description: If you deploy two separate packages that listen for messages on the same input queue, you could have problems with the routing of messages to the appropriate business process service. Because each package installs its own JMS listener, this process works intermittently when the message is grabbed by the correct listener, but fails when listener A grabs a message intended for listener B and vice versa.

Workaround: Install both business process services in the same package and use a single JMS input endpoint to expose the services. In this case, one JMS listener is registered that routes messages to one of two business processes.


Business process fails to clean up if it sends correlation values beginning with a space

CR #426619

Description: A stateful business process may fail to be cleaned up after the business process completes if the business process uses correlation values that begin with a space. This problem is due to an error in the interaction between the server and the transaction manager.

Workaround: When running a business process, do not send correlation values that begin with a space. There is no known solution to the problem at this time.


Variable references inside XPath index predicates not supported in assign target

CR #401250

Description: The target (Finish) node of an assign activity does not support variable references inside of XPath index predicates, such as in the following example:

/PurchaseOrder/LineItems/Item[/counter]/PartNum

Workaround: Use the getVariableData pseudofunction to retrieve the value of the variable, as shown in the following example:

/PurchaseOrder/LineItems/Item[getVariableData(‘counter’)]/PartNum


Problem with two stateful business processes in the same package

CR # 403833

Description: Deadlocks can occur when stateful business process #1 invokes stateful business process #2. This occurs when the invocations are in the same package (the same transaction) and multiple threads invoke the services.

Workaround: Break the transaction between business process #1 and business process #2 by wrapping business process #2 with a SOAP service.


XPath number function

CR # 390946

Description: The XPath number function does not return the numeric value of the given argument if it is a Boolean type. For example, if you create an input parameter, connect it to number function, and connect this to an output parameter in an assign, you do not see the expected results.

Workaround: Use the following method to produce the correct results for the above example.

Converting a Boolean argument to a number in an assign activity
  1. Create an input Boolean parameter.

  2. Create an output Float parameter.

  3. Activate the Tool Palette.

    • Click inside the editor.

    • Click the Tool Palette icon on the Fast View shortcut bar, and select the Activities tool palette.

  4. Drag and drop an assign activity onto the canvas.

  5. From the Business Process Variables section, drag the parameter you want to use as the source, and drop it into the Source cell of the assign properties.

  6. From the Business Process Variables section, drag the parameter you want to use as the target, and drop it into the Target cell of the assign properties.

  7. Click the Assign tab in the Properties Panel for the assign.

  8. Click in the expression editor to activate the Tool Palette.

  9. Select the Boolean Functions tool palette, drag IsEqualTo, and drop it onto the expression editor.

  10. From the Generic Variable and Constants tool palette, drag String Constant, and drop it onto the expression editor.

  11. Highlight String Constant in the editor, and change the Logical name property to True. Select the check box next to Source text to keep the Logical name and Source name the same.

  12. Change the datatype to Boolean.

  13. From the Number Functions tool palette, drag number and drop it onto the expression editor.

  14. Connect the following to create the flow:

    1. Connect the input variable to IsEqualTo.

    2. Connect True to IsEqualTo.

    3. Connect IsEqualTo to the number.

    4. Connect the number to the output variable.


Substring-after and substring-before function arguments with leading zeros

CR # 399122

Description: The substring-after and substring-before functions do not always give the correct output if the argument strings have leading zeroes. The leading zeroes are deleted.

Workaround: Perform the operations using a map.


DateTime comparisons

CR # 401270

Description: When comparing the value of a dateTime field to the dateTime constant or a variable, Sybase WorkSpace does not always return True even when the condition is True. For example:

getVariableData('BP11243231409382', 'newParameter1', '/ns0:CT/ns0:dateTime') &lt; '2005-08-17T18:00:00'

Workaround: Convert the dateTime field values to ISO dates or times. The ISO format puts the number in a sequence (such as YYYYMMDDHHMMSS) without any of the annotations that are present in the format used by XSD Schema types. When dates and times are in this format, you can compare the two integers to identify which dates are newer or older.

For example, if you have a dateTime format of 2005-08-17T18:00:00, you can perform the following operations on that string to convert it to an ISO dateTime, where dateTime = 2005-08-17T18:00:00:

result = concat( concat( concat( substring(dateTime, 1, 4), substring(dateTime, 6, 2) ), concat( substring(dateTime, 9, 2), substring(dateTime, 12, 2) ) ), concat( substring(dateTime, 15, 2), substring(dateTime, 18, 2)))

This operation would yield result = 20050817180000. Convert this string to an integer using number and round functions, round(number(result)), which could then be used as an integer in a comparison.


Corruption of looping expressions copied from a complex activity

CR # 431557

Description: If the looping expression of a complex activity is collapsed and the complex activity also contains an assign having a collapsed expression, the looping expression is corrupted when the complex activity is cut and pasted into another complex activity.

Workaround: Expand the looping expression of a complex activity before cutting and pasting the complex activity.


WorkSpace hangs on copy or cut of assign activity with multiple rows and collapsed expression

CR # 431554

Description: Sybase WorkSpace hangs when an assign activity containing multiple rows, at least one of which contains a collapsed expression, is copied or cut. Sybase WorkSpace must then be killed from the Windows task manager.

Workaround: Expand any collapsed expressions within an assign activity containing multiple rows before attempting to copy or cut the activity.


Cannot delete target in assign expression editor

CR #408108

Description: If you attempt to delete a target in the expression editor, the action is ignored.


Cannot drag and replace target in assign expression editor

CR #408088

Description: If you attempt to replace an expression target in the expression editor by dragging and dropping the new variable onto the existing variable, the new variable is only placed onto the canvas but does not replace the existing variable.

Workaround: Use the Assign Overview tab to replace expression targets.


Multiple Send Response operations cause delete conflict

CR #398913

Description: Deleting a Send Response operation when the response variable is set to a fault parameter can result in errors.

Workaround: Before deleting a Send Response operation, change the Response variable from the fault parameter to "Normal Response".


Database service


Managing ServiceName warnings

CR #428432

Description: You may receive one of the following ServiceName warnings:

Workaround: Ignore each warning.


Connecting to Avaki EII

CR #418155

Description: If you plan to create a database service that interacts with Avaki EII, you may have problems executing the database service operation.

Workaround: Install EBF #13291 for Avaki EII 6.2.1 to install the JDBC drivers required for runtime connectivity to Avaki from a database service.

See “Sybase EBFs and software maintenance” for more information.


Select statement sometimes returns an update count for each row

CR # 380113

Description: When a stored procedure or SQL statement executes a select * statement, an update count is sometimes returned for each row.

Workaround: Ignore the update counts if they are not necessary for your result.


Problems using JDBC and DB2 version 7

CR # 389255

Description: You may experience problems using JDBC and DB2 version 7.

Workaround: Check the DB2 product documentation for more information.


Using an Oracle database

CR # 401643

Description: When using Oracle, the database provides time zone information in the TIMESTAMP datatype; however, JDBC does not provide for time zone information, so a class cast exception results.

Workaround: You may want to use a third-party driver, such as the DataDirectJDBC driver for Oracle, if database operations have result sets with a TIMESTAMP column.


Using a stored procedure that returns an update count from an Oracle database

CR # 389565

Description: A problem occurs when you use a stored procedure that returns an update count from an Oracle database. When the database service runs, it returns an update count for any operation. Combined with the known problem concerning how Oracle handles update counts, this problem results in the procedure running in an infinite loop.

Workaround: Use a SQL statement instead of a stored procedure to perform work in the database service.

See the Oracle product documentation for additional information regarding this issue.


EJB service

CR #429724

Description: When testing a service using the Dialog Service Test Wizard, if you click Next on the Options page, and then return to that page and edit the Enable support for "wrapped" document/literal style operations setting, the service test fails.

Workaround: To edit the Enable support for "wrapped" document/literal style operations setting, click Cancel, exit the wizard, and restart it.


Java service


Building a package

CR #431465

Description: If you create a Java service with space in the name and attempt to create a Sybase Services Package Profile from the Java service, the package build fails with an error indicating that the package name contains invalid characters.

Workaround: Package names cannot contain spaces. To avoid this error, make sure the name of your Java service contains no spaces.


Creating a Java service

CR #417426

Description: When importing a project from Sybase WorkSpace version 1.0 into 1.5, you may receive the following error:

Project UCDMP4IV is missing required library: 
<installation directory>\Eclipse\sybase_workspace_1.0\services\eclipseplugins\com.sybase.psesp_4.5.0\lib\services.jar

Workaround: Launch Sybase WorkSpace 1.5, and in the WorkSpace Navigator, right-click the imported Sybase project, and select Update WorkSpace Build Path Entries from the context menu.


Creating a proxy for a Java service

CR #419892

Description: When a proxy for a service with an array type parameter (such as Integer[ ]) is generated, a holder class for the parameter is also generated, in this case, ArrayOfJavaLangInteger. This holder class may require a different array type in the constructor (new ArrayOfJavaLangInteger(int[])).

Workaround: Examine the source generated for the holder class and ensure that any datatype conversions are done before creating an instance of the holder class.


Transformation service


Packaging fails after XSD file name is changed

CR #417509

Description: When the name of an XSD file used in a transformation service is changed, the .map, .rules, .gem, and the svc_trans_rules.gem files fail to update and do not allow you to package the service.

Workaround: Open the transformation service, and make a minor change to the map, such as moving one of the content models on the Map page. Save the minor change to restore the transformation service to a consistent state.


getTimeZoneID() function always returns 0000

CR #401702

Description: When you use the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID function, the Dialog Service Test wizard may send the incorrect time zone to the getTimeZoneID function, resulting in an incorrect value of “0000” every time you call the getTimeZoneID function.

Workaround: Instead of using the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID function, use the SOAP Request/Response Service Test wizard or the Create Web Service Client wizard.


Comparing hexBinary values in a Java transformation service

CR #423065

Description: When defining a transformation rule in a Java Transformation Service using the expression editor, a problem arises when comparing hexBinary values.

Workaround: Convert each hexBinary value to a string.

Comparing hexBinary values in a Java transformation service
  1. Convert each hexBinary value to a string.

    The result is a string of hexBinary characters (0-f).

  2. Compare the results to another string.


Cannot define rules in conditional logic functions

CR #429723

Description: After rules are defined in a conditional logic function, error messages appear in the Problems View of the Service Development perspective, and the corresponding transformation service cannot be deployed.

Workaround: Delete all if-then links, and then redraw the links.


Package creation failure

CR #430935

Description: A Java Transformation does not compile if it contains a literal in the map.

Workaround: Use expression constants instead of map literals.

Using expression constants instead of map literals
  1. Delete the literal, and map a source field to the target field.

  2. In the transformation rule, delete the source field.

  3. Add to the rule a constant with a type matching the datatype of the target field.

  4. Set the value of the constant to the desired value.

  5. Add a number or string function to the rule:

    • Use a string function for String, Binary, Custom Date & Time, Date & Time, Date, and Time datatypes.

    • Use a number function for all other datatypes.

  6. Connect the constant to the string or number function.

  7. Connect the string or number function to the target field.


WorkSpace Navigator


Path validation fails for specified WSDL and BPEL files

CR #429546

Description: An attempt to extract WSDL and BPEL from a service package file in WorkSpace Navigator fails if the path specified for the target directory is located in your Sybase WorkSpace installation.


Project copies and internal references to resources

CR #384009

Description: When you copy a project, the project resources are not actually copied, but are a reference to the original resource. If you make a change to a resource in the project (for example, a service), the resource is changed both in the original and in the copy. If you want a copy of a project as an archive, you must use the workaround below. If you want only a copy of the service in a project, you must copy the entire project using the workaround below. If you only copy the individual service, you are copying the selected file, but not the associated hidden files required to run the service.

Workaround: The project owner must export the project. Use the Import wizard to import the project.


Deployment framework

CR #403020

Description: If an apostrophe is entered in the literal of a business process service assign activity, the business process service fails during deployment and displays the following error:

XPATH expression error; Native Expression: 'Shouldn't get here'; Parsed expression: 'Shouldn't get here'; Native message: Unexpected 't get here''.

Workaround: The BPEL translator has been modified to examine the literal string and replace apostrophes with “&apos;”. However, the translator does not fix this problem for literal values that are developed in the Assign Expression Builder.


Web Application Development


Building database connections to a JSF DataWindow

CR #428108

Description: If you use onLoadHandler to build a database connection to a JavaServer Faces (JSF) DataWindow, turn on the enableDataCache option, bind the Java-side DataWindow component function retrieve to a JSF button, and call the function at runtime, the JSF DataWindow loses all its rows.

Workaround: Disable the enableDataCache option when using onLoadHandler to build a database connection to JSF DataWindow.


Configuring native drivers for DataWindow objects

CR #429820

Description: For production systems with a large number of concurrent users (200 or more), Sybase recommends using native drivers, which provide the advantage of using the ConnectionCache. JDBC can be used in production systems with fewer than 200 concurrent users.

For additional information, see the online help topic called JSF DataWindow Database Driver Support.

To improve performance, one option is to implement connection information sharing among multiple DataWindow objects across the Web application using the onLoadHandler attribute of the JSF DataWindow. Java coding is required.

Implementing connection information sharing
  1. Define a common class that implements the DataWindowOnLoadListener:

    //For DataWindow Data Retrieval with no retrieval argumentspublic class CommonOnLoadHandler implements DataWindowOnLoadListener{	public TestODBC() {		super();	}	public void onLoadDataWindow(DWLoadedEvent arg0) {				//1. Get the DataWindowComponent from the ViewRoot		DataWindowComponent dwc = (DataWindowComponent)arg0.getComponent();				//2. Create JSFDW Transaction object		Transaction ts = new Transaction();		try {						//=================================================				//ODBC Transaction object				//ODBC Driver needs to be installed				ts.setDbms("ODBC");				ts.setDbparm("ConnectString='DSN=TestODBC;UID=sa;PWD=sa'");						//=================================================				//ASE Native Transaction object				//Need to have ASE Open Client Installed on the EAServer machine				 //ts.setDbms("SYC Adaptive Server Enterprise");				//ts.setDatabase("jsfdwtest");				//ts.setLogpass("sa");				//ts.setServername("TestASEOC"); //Created using DSEdit Utility				//ts.setLogid("sa");			//=================================================						ts.connect();		} catch (TransactionException e) {			ServletContext sc = (ServletContext)FacesContext.getCurrentInstance().getExternalContext().getContext();			sc.log("TestODBCJava " + e.getMessage());					} catch (MethodFailureException e) {					}                //Cache JS files for performance improvement                FacesContext fc = FacesContext.getCurrentInstance();    	String contextPath = fc.getApplication().getViewHandler().getActionURL(fc,"/");    	int first = contextPath.indexOf("/");    	int last = contextPath.lastIndexOf("/");    	String refinedcontextPath= contextPath.substring(first,last+1);    	        try {	dwc.modify("DataWindow.HtmlGen.ResourceBase='" + refinedcontextPath + "'");        	dwc.modify("DataWindow.HtmlGen.CommonJSFile='common.js'");        	dwc.modify("DataWindow.HtmlGen.DateJSFile='date.js'");        	dwc.modify("DataWindow.HtmlGen.NumberJSFile='number.js'");        	dwc.modify("DataWindow.HtmlGen.StringJSFile='string.js'");		} catch (ArgumentNullException e) {					} 				//3. Attach the Transaction object to the DataWindowComponent		dwc.setTransaction(ts);				//4. Do Data Retrieval		try {			dwc.retrieve();		} catch (DbErrorException e) {			ServletContext sc = (ServletContext)FacesContext.getCurrentInstance().getExternalContext().getContext();			sc.log("TestODBCJava " + e.getSqlErrorText());		}				//5. Disconnect the connection		dwc.getTransaction().disconnect();				//6. Null reference		ts=null;	}}
    
  2. Share the common handler among all the DataWindow objects in the Web application.

    For Page1.jsp:

    <syb:dataWindow onLoadHandler="CommonOnLoadHandler" dataWindowObject="dept"			libraryList="/WEB-INF/pb/test.pbl" id="dept1" enableLog="true">			<syb:objectlink linkname="dept_id" linkurl="/usingonloadhandler.faces">				<syb:linkargs value="dept_id" type="DW Column" name="dept"></syb:linkargs>			</syb:objectlink></syb:dataWindow><syb:dataWindow onLoadHandler="CommonOnLoadHandler" dataWindowObject="dept"			libraryList="/WEB-INF/pb/test.pbl" id="dept2" enableLog="true">			<syb:objectlink linkname="dept_id" linkurl="/usingonloadhandler.faces">				<syb:linkargs value="dept_id" type="DW Column" name="dept"></syb:linkargs>			</syb:objectlink></syb:dataWindow>
    

    For Page2.jsp:

    <syb:dataWindow onLoadHandler="CommonOnLoadHandler" dataWindowObject="cust"			libraryList="/WEB-INF/pb/test.pbl" id="cust1" enableLog="true">			</syb:dataWindow>
    

Cutting, copying and pasting DataWindow objects

CR #426090

Description: An error occurs when you expand a .pbl file in the WorkSpace Navigator, click any DataWindow in the list, and then attempt to cut, copy, or paste using the hot keys (Ctrl+C, Ctrl+V, or Ctrl+X).

Workaround: Do not use the hot keys (Ctrl+C, Ctrl+V, or Ctrl+X) to cut, copy, or paste a DataWindow in the WorkSpace Navigator.


Deploying a JSP page to a runtime environment

Description: You may encounter problems in deployment to a runtime environment because the runtime server may not be able to recognize changes in your development environment.

Workaround: Stop and restart the runtime server before running a test on your JSF page.


EAServer crashes with multiple client access to JSF DataWindow

CR #410157

Description: If you are using an ASE 12.5 native client and an ASE 12.5 server, EAServer may crash when multiple clients access a JSF DataWindow.

Workaround: Use ASE 15.0 for both client and server.


JSF DataWindow database driver support

CR #429809

You can use the jndiDataSource or connectString JSF DataWindow attribute to connect to a database. See “JSF DataWindow Database Driver Support” in the Sybase WorkSpace Development, Web Application Development online collection for further details.

Sybase recommends that you use a native database driver where adequate performance and scalability are required.


Unsupported DataWindow options

Description: The following DataWindow options are not supported at runtime:

Workaround: Do not use any of the above options when creating a DataWindow in Sybase WorkSpace. If you import a DataWindow object that has any of above options, be aware that the options will not be supported at runtime.


Unsupported DataWindow Painter option

CR #421697

Description: The DataWindow Painter option InkEdit style type in the Edit tab of the column properties view in the DataWindow Painter is not supported at runtime.

Workaround: Do not use this option when creating a DataWindow in Sybase WorkSpace. If you import a DataWindow object that has the above option, be aware that the option will not be supported at runtime.



Sybase Developer Edition Server issues

The following are known issues for the Sybase Developer Edition Servers.


Adaptive Server Anywhere


Displaying ASA 9.0.x and Sybase IQ 12.5 stored procedures

CR #426349

Description: Enterprise Explorer and Database Explorer may show stored procedures as user-defined functions when you create a new Sybase IQ 12.5 or Adaptive Server Anywhere 9.0.2 database from an existing database server.

Workaround: After you create the database, and before you run any existing stored procedures or functions, run asa_sql.sql to correct the display. This script is in the directory where jConnect 6 is installed.

Correctly displaying IQ 12.5 or ASA 9.0.2 stored procedures and functions
  1. In Database Explorer, right-click the newly created Sybase ASIQ or ASA connection profile, and choose Connect from the context menu.

  2. From the main menu bar choose Window | Preferences, expand Sybase, Inc. and Database Development in the left frame of the Preference dialog box, and choose Connection Level Options.

  3. In the Sybase IQ_12.6.x or Adaptive Server Anywhere_9.x tab, click the Quoted identifier check box, then click Apply and OK.

  4. Click on the main toolbar in the Database Development perspective.

  5. In the Choose a .sql File to Execute dialog box, browse to the appropriate sql_asa.sql script:

    • For IQ, browse to: <jConnect-6_installation_directory>\sp, and open sql_asa.sql.

    • For ASA, browse to: <sybase_installation_directory>\WorkSpace\DevRuntimes\ASA \scripts, and open sql_asa.sql.

  6. In the Select Profile for the Editor dialog box, enter the appropriate database type:

    • For IQ, enter Sybase IQ_12.6.x for Database type.

    • For Adaptive Server Anywhere, enter Adaptive Server Anywhere_9.x for database type.

    Enter the newly created ASIQ or ASA profile name for the connection profile name, and click OK.

  7. Ignore any error dialogs that indicate tables are in use or already exist, and click OK to continue executing the SQL file. Database Explorer and Enterprise Explorer show stored procedures and user-defined functions correctly.

  8. Choose Window | Preferences, expand Sybase, Inc. and Database Development, and choose Connection Level Options. In the Sybase IQ_12.6.x or Adaptive Server Anywhere_9.x tab, click the Quoted identifier check box to restore its original setting. Click Apply and OK.


Input parameters interpreted as output parameters

CR #427654

Description: Output parameters for ASA stored procedures written with Watcom-SQL syntax are treated as input parameters.

Workaround: Use Transact-SQL™ syntax in all ASA stored procedures used in database services.


Adaptive Server Enterprise


Cannot load TIBCO JMS dynamic load libraries

CR #415816

Description: ASE versions 12.5.3 and later dynamically load the JMS libraries needed for real-time messaging services (RTMS). Some versions of the TIBCO EMS do not include the necessary libraries, and configuration of the RTMS feature for ASE may fail.

Workaround: After installing the TIBCO EMS, place the missing libraries in <tibco_install>\ems\clients\c\bin, where <tibco_install> is the path for your TIBCO EMS installation.


Command size limit on temp tables with database debugger

CR #428907

Description: Non-sharable temp tables are visible only for the current JDBC connection, and the database debugger must retrieve temp table data from the ASE debugger API thread. The debugger API limits command length to 255 characters.

Workaround: Limit command lengths to 255 characters or less when performing inserts or updates on temp tables and using the database debugger.


Unique data required in stored procedure tables

CR #422609

Description: If you create a business process service and invoke a database service with two stored procedures containing two tables, the business process fails and the transaction is rolled back when you insert duplicate data into one of the tables.

Workaround: Use unique data in all tables for stored procedures.


Unsigned integer datatypes not supported

CR # 409553

Sybase WorkSpace does not support Adaptive Server Enterprise 15.0 unsigned integer datatypes.


Unwired Orchestrator


Cursors in Oracle stored procedures not supported

The use of cursors as parameters in an Oracle database stored procedure is not supported for Unwired Orchestrator. If you attempt to discover a result set for an Oracle stored procedure that uses cursors as parameters, you may encounter errors.


Installing Sybase IQ with Unwired Orchestrator

CRs #393025, 424141

Description: When installing Sybase IQ with Unwired Orchestrator, if you first install Unwired Orchestrator and then install Sybase IQ, the EAServer plug-in may not be registered in Sybase Central™ 4.3.

Workaround: To resolve this issue, use the following procedure.

Installing Sybase IQ with Unwired Orchestrator
  1. Before you install Sybase IQ, back up the .scRepository file located in the <install_dir>\DevRuntime\Shared\Sybase Central 4.3 directory, where <install_dir> is the directory in which you have installed Sybase WorkSpace.

  2. Install Sybase IQ.

  3. Add the contents of the backed-up .scRepository file to the new .scRepository file.


Java exception when starting or stopping Unwired Orchestrator

CR #429756

Description: The following Java Remote Method Protocol (JRMP) exception may appear in a DOS window when you try to start or stop Unwired Orchestrator 5.1:

javax.naming.notfoundexception

This exception results from a difference in default port numbers between the SybAgent port used by Unwired Orchestrator and the Sybase IQ Agent port, which is 1099.

Workaround: To resolve this issue, do one of the following:

Changing the SybAgent port configuration
  1. Open the boot.xml file at <install_dir>\DevRuntimes\UO\install_data\eas\sysmgmt, where <install_dir> is the directory in which you have installed Sybase WorkSpace.

  2. Edit the boot.xml file as follows:

    1. Insert the following attribute on line 55:

      <attribute name="Port">xxxx</attribute>
      

      Where xxxx is the port value you want to use.

    2. Replace the port number in line 78 to the same port you used in line 55, for example:

      <param
      type="java.lang.Object">rmi://banglor:xxxx
      </param>
      
  3. Open the StopSybAgent.bat file at <install_dir>\DevRuntimes\EAServer\SysMgmt\bin.

  4. Edit the StopSybAgent.bat file. Replace the port number on line 24 with the port number you used in the boot.xml file.

For more information on managing ports, see the topic “Managing Ports,” which is in the Sybase WorkSpace Server Administration collection.


Log Viewer does not automatically update

CR #419209

Description: Newly generated logging information for Unwired Orchestrator is not updated in the Log Viewer component of the Profiling and Logging perspective.

Workaround: To ensure that logging information is shown in the Log Viewer, use the following procedure:

Setting up the Unwired Orchestrator logging agent
  1. Download the TPTP Agent Controller and Generic Log Adapter from the Eclipse downloads Web site.

  2. Configure the Agent Controller. Instructions are available in the getting_started.html document available with the Agent Controller download or on the Eclipse Web site.

  3. Launch the Agent Controller.

  4. Configure the Generic Log Adapter according to the instructions given in <gla_install>/bin/gla.bat, where gla_install is the installation directory for your Generic Log Adapter.

  5. In <install_dir>/DevRuntimes/UO/templates/runUOLogAdapter.bat, where <install_dir> is the directory in which you have installed Sybase WorkSpace, replace AC_HOME with the root directory of your Agent Controller installation and GLA_HOME with the root directory of your Generic Log Adapter installation.

  6. In <install_dir>/DevRuntimes/UO/templates/UOLogRuleParser.adapter, change the following lines to match the location of the log file on your machine:

    <pu:Property propertyName="directory" propertyValue="."/>
    <pu:Property propertyName="fileName"propertyValue="Unwired.log.0"/>
    <sensor:SingleFileSensor directory="." fileName="Unwired.log.0"/>
    

    For example, if <jaguar> indicates the root directory of your EAServer installation, change the lines to the following:

    <pu:Property propertyName="directory" propertyValue="<jaguar>\bin"/>
    <pu:Property propertyName="fileName"propertyValue="Unwired.log.0"/>
    <sensor:SingleFileSensor directory="<jaguar>\bin" fileName="Unwired.log.0"/>
    
  7. Start the Generic Log Adapter with the following command:

    <install_dir>/templates/runUOLogAdapter.bat <install_dir>/templates/UOLog_RuleParser.adapter
    

    Here, <install_dir> indicates the root directory of your Sybase WorkSpace installation.

  8. In Eclipse, open the preferences page at Windows | Preferences | Profiling and Logging. Make sure the Enable logging option is selected.

  9. In Eclipse, select Run | Profile, and select Attach - Java Process from the Profile wizard. Click New.

  10. Click the Host tab, and specify the host for your Agent Controller.

  11. Click the Agents tab, and specify UOLogAgentOutputter.

  12. Click Apply, Profile, and Close.

  13. If you need to start profiling, right-click the log entry in the Profiling and Logging perspective, and choose Start Profiling. To refresh the log, right-click the log entry in the Profiling and Logging perspective, and select Refresh Views.


Unwired Orchestrator errors occur for long PATH variable

CR # 429745

Description: Long global PATH variables cause the following problems:

Workaround: To recover from these errors, use the following procedure:

Recovering from long PATH errors
  1. Stop all servers.

  2. Modify your system PATH to reduce its length.

  3. Read Configuring_UO_standaloneEAS.doc at <sybase_install>\WorkSpace\DevRuntimes \UO\install_data\configurator.

  4. Run the configurator to reconfigure Unwired Orchestrator modules in EAServer.

  5. Start Unwired Orchestrator.

  6. Design and deploy services.


Unwired Accelerator


LDAP authentication failure after CSI configuration

CR #432800

Description: If you are using the Common Security Infrastructure (CSI) with LDAP, you cannot log into Unwired Accelerator if the LDAP security provider has been configured for authentication by Unwired Accelerator.

Workaround: Unwired Accelerator requires all authenticated users to have an “everybody” role. To use an LDAP server to store and authenticate users for Unwired Accelerator, you must create an "everybody" role and grant it to all users in the LDAP server.

For more information about configuring an LDAP security provider for use with CSI, see the Unwired Accelerator Installation Guide. This document is included on the Sybase Getting Started CD.



Documentation updates and clarifications


Sybase WorkSpace Development online help


Creating an ASIQ connection profile

CR # 400484

Description: The topic, “Creating an ASIQ connection profile,” which is in the Sybase WorkSpace Development, Getting Started collection, contains an error. In the table titled “Specify a Driver and Connection Details page,” the entry for “Other properties” reads:

In the text box, specify connection properties using the KEY=value format, and then click Add.

Workaround: The text should read:In the text box, specify connection properties using the KEY=value format, or choose from the drop-down list. Then, click Add.


Logging your work

CR # 428129

Description: The topic “Logging your work,” which is in the Sybase WorkSpace Development, Database Development online collection, contains an error. The text currently reads:

As you define a new table, for example, Sybase WorkSpace builds a SQL CREATE TABLE statement internally.

Workaround: The text should read:As you define a new table, for example, Sybase WorkSpace builds a CREATE TABLE statement internally.


Runtime Management Console online help

CR #420039

Description: In the Using LDAP Runtime Security topic, the note currently reads:

Note: See the CSI 2.0.1 Java LDAP Provider technical white paper located http://www.sybase.com/techdocs for a description of each property.

Workaround: The note should read:

Note: See the CSI 2.0.1 Java LDAP Provider technical note located http://www.sybase.com/techdocs for a description of each property.



Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.



Other sources of information

Use the Sybase Getting Started CD, the SyBooks™ CD, and the Sybase Product Manuals Web site to learn more about your product:


Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications
  1. Point your Web browser to Technical Documents.

  2. Click Certification Report.

  3. In the Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Certification Report title to display the report.

Finding the latest information on component certifications
  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance
  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.


Eclipse documentation

To access Eclipse 3.1 documentation on the Web, point your Web browser to the Eclipse SDK help page.



Accessibility features

This document is available in PDF format through which you can navigate using a screen reader.

You can get additional information about Sybase accessibility http://www.sybase.com/accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.

Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.



Back to Top
© Copyright 2010, Sybase Inc.