Assembly Gallery
User login
Navigation
Cape Clear Studio 7.0.3 Release Notes
Issues Fixed in Cape Clear Studio 7.0.3
The following table lists the issues fixed in Cape Clear Studio 7.0.3:
| Issue Summary: | WSDL to Java project fails silently to regenerate java-gen code |
| ID: | WTP-3748 |
| Status: | Fixed |
| Component: | Builder - Java WS |
| Description: | WSDL to Java projects (web service and client) sometimes fail to regenerate the Java code in the java-gen folder when the project is rebuilt. |
Known Issues in Cape Clear Studio 7.0.3
The following table lists the known issues in Cape Clear Studio 7.0.3:
| Issue Summary: | Deploying multiple projects when running with WTP 1.5.4 |
| ID: | WTP-3578 |
| Status: | Unresolved |
| Component: | Other |
| Description: | When the Cape Clear Studio plug-ins are installed in an Eclipse installation not provided by Cape Clear and where that installation is using WTP 1.5.4, adding multiple projects to the right side of the Add and Remove Projects page of the Run On Server wizard results in only the project selected initially being deployed. You must deploy each project separately. |
| Issue Summary: | Cannot drag onto a BPEL diagram that has "empty" instead of "sequence" at its root |
| ID: | WTP-3059 |
| Status: | Unresolved |
| Component: | Editor - BPEL Editor |
| Description: | If a BPEL has an "empty" element but no surrounding "sequence" element, then the drag and drop logic in the BPEL editor does not allow activities to be dropped onto the diagram. A workaround is to delete the empty activity, which results in an empty sequence being created, and then proceed as normal by adding activities to the sequence. |
| Issue Summary: | Incorrect XPath generated for attribute in property alias |
| ID: | WTP-3280 |
| Status: | Unresolved |
| Component: | View - BPEL Properties |
| Description: | The Property Alias editor generates an incorrect XPath query for mesage attributes. For example /root/element@attname is generated rather than /root/element/@attname - there is a missing / between the element and attribute parts of the path. The problem can be worked around by manually correcting the generated XPath expression. |
| Issue Summary: | Error deleting Hibernate Sample "sample_database" project |
| ID: | WTP-3321 |
| Status: | Unresolved |
| Component: | Samples - Implementation |
| Description: | The following error appears when a user attempts to delete the Hibernate Sample projects (ticking the box to remove the resources from the file system):
Problems encountered while deleting resources. |
| Issue Summary: | Workbench preference page Cape Clear Java Project Settings has no effect |
| ID: | WTP-2969 |
| Status: | Unresolved |
| Component: | Wizard/Property Pages - New Java Client |
| Description: | The workbench preference page Cape Clear -> Java Project Settings has a property titled "Enforce compatability with only the current workbench JRE" which causes new projects to specify the exact (current) JRE version in the .classpath file. When not checked, the project can be compiled with any JRE version. The preferences check box has been noted to have no effect and when this happens the Cape Clear wizards create projects that are compatible with any JRE. |
| Issue Summary: | Error in error log when importing samples |
| ID: | WTP-2847 |
| Status: | Unresolved |
| Component: | Other |
| Description: | Each time a sample project is imported from the Studio Samples this error is seen in the error log:
java.lang.NullPointerException This problem has been raised with Eclipse.org, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=175562 |
| Issue Summary: | WSDLs with schemas using xsd:include cannot be processed by the Java Web Service and Java Web Service Client wizards |
| ID: | WTP-3065 |
| Status: | Unresolved |
| Component: | Wizard/Property Pages - New Java Client |
| Description: | If a WSDL contains an embedded schema that xsd:include's another schema both the WSDL->Java web service wizard and Java web service client wizards are unable to process the WSDL. A workaround for this is to edit the WSDL such that the embedded schema targets a different namespace and then use xsd:import's to import the physical-item.xsd rather than including them. |
| Issue Summary: | Uninstall only works for one installation, others Studio installs cannot then be uninstalled |
| ID: | WTP-2805 |
| Status: | Unresolved |
| Component: | Installer |
| Description: | If more than one Cape Clear Studio is installed using the Installer e.g.
Studio installed into "C:\CapeClearA" with start menu "Cape Clear 7 A" After uninstalling one of the installations, the other cannot be uninstalled. |
| Issue Summary: | A combined WSDL to Java Web Service and Java Web Service Client project implementing and invoking on the same WSDL won't compile if default options used |
| ID: | WTP-3041 |
| Status: | Unresolved |
| Component: | Builder - Java WS |
| Description: | If a WSDL to Java Web service that invokes other web services is created with the default source folders settings and default namespace to package mappings, and the same WSDL is used for the implementing service and for the client, when code is generated it does not compile and problem markers are seen on the project. This happens because classes are generated for both the client and service into the same source folders that have the same name but different implementations, and one overwrites the other. There are two workarounds for this: (1) generate the service and client code into different source folders, or (2) change the package names for one of either the service or client in the namespace to package mapping table. |
| Issue Summary: | Help -> Software Updates -> Manage Configuration shows error markers for the Web Standard Tools (WST) feature |
| ID: | WTP-3094 |
| Status: | Unresolved |
| Component: | Other |
| Description: | Use Help -> Software Updates -> Manage Configuration to open the "Product Configuration" view, open the tree and notice that the "Web Standard Tools (WST)..." node and child nodes have error markers. Right click on the nodes, and select Properties -> Status to see the problem description.
The root cause is this error: Plug-in "org.eclipse.wst.wsdl.validation" version "1.1.101.v200701260245" referenced by this feature is missing. Cape Clear has patched this plug-in and so distributes the plug-in with a different version stamp e.g. "1.1.101.v200702211200-CCPATCH-154684-169427", where the numbers after "CCPATCH" are the Eclipse bug numbers for the problems addressed by the patching. The error markers appear because the feature descriptions specify the un-patched version number but Cape Clear Studio is supplied with and runs with the patched plug-in. The error markers can be ignored. |
| Issue Summary: | Whitespace in paths is not handled by the Buckminster command script as shown in the help |
| ID: | WTP-3112 |
| Status: | Unresolved |
| Component: | Headless Build |
| Description: | Whitespace in paths is not handled by the Buckminster command script as shown in the help. The Buckminster Automated Build will not correctly handle whitespace as shown in the help unless the paths are surrounded with double quotes. For example, specifying this path for the project.dir property
<property name="project.dir" value="C:/Documents and Settings/jdoe/myworkspace/" /> will cause the build to fail at the ccimport step e.g. ccimport --clean @project.dir@ To workaround this, surround the project.dir with double quotes e.g. ccimport --clean "@project.dir@" |
| Issue Summary: | Changes to Transform service WSDL outputData part of transformResponse are not preserved |
| ID: | WTP-3076 |
| Status: | Unresolved |
| Component: | Builder - Transform WS |
| Description: | The BPEL engine in Cape Clear 7.0 performs more stringent type checking on assignments that the 6.x server. This means that a technique of using a transform service to produce the XML for some elements of a variable/message no longer works because the xsd:base64Binary to element assignment will generate a MismatchedAssignmentFailure. To work around this, the WSDL for the transform service can be modified so that the outputData part of transformResponse is set to be the desired element. The mime:content of the binding for the output must also be customized to be text/xml. However, if the transformation serquence is modified or if the project is restored to the workspace from a ZIP the WSDL is rewritten and the changes are lost. A workaround is to stop the WSDL from being re-written by disabling the Cape Clear Transform Web Service Builder (via Project Properties->Builders). Such changes to builders are persisted to the .project file so a zipped and re-imported projects will continue to work. |
| Issue Summary: | HTTPS Restart Workbench button does not apply changes |
| ID: | WTP-3114 |
| Status: | Unresolved |
| Component: | Other |
| Description: | The Cape Clear HTTPS preferences page includes a "Restart Workbench" button, because the workbench must be restarted for the changes to take effect. However, if Restart Workbench is clicked before the "Apply" button has been clicked, the changes will be lost. The workaround is to Apply the changes before restarting the workbench. |
| Issue Summary: | "Problems occurred while trying to save the state of the workspace" error dialog when shutting down Studio workbench on JDK 1.4 |
| ID: | WTP-3012 |
| Status: | Unresolved |
| Component: | Hibernate Tools Integration |
| Description: | When you close Eclipse while using JDK 1.4 an error message is displayed saying "Problems occurred while trying to save the state of the workspace". However the workspace is saved, so this is error not fatal. . The recommended workaround is to use JDK 1.5.
The error is caused by a shutdown failure in the HibernateTools plugins that are shipped in Cape Clear Studio - it fails to persist the Console Configuration at exit as the HibernateTools implementation requires JDK 1.5 APIs to complete this task. Note this error occurs even if you have not used the HibernateTools plugins. A consequence of this failure to persist the console configuration data is that when the workbench restarts, Java to WSDL project (with Hibernate persistence support) will not have a valid HibernateTools Console Configuration until the project is rebuit. This is reported to the user as errors every time Console Configuration is used for projects had been created in previous sessions. There are three potential places where this can happen: To avoid this, perform a clean re-build of the Hibernate projects once before attempting any of the above tasks in a workbench. The HibernateTools Console Configuration will be re-created as part of the rebuild. |
| Issue Summary: | The BPEL Copy Dialog (Property View) does not display enumeration types correctly |
| ID: | WTP-2737 |
| Status: | Unresolved |
| Component: | View - BPEL Properties |
| Description: | Schema elements that are defined using enumeration type restrictions are not displayed correctly in the BPEL Copy Dialog (Property View). The workaround for this is to switch to the BPEL XML view and create the copy "from" and "to" contents manually. |
| Issue Summary: | Stored procedures with arguments maped to Types.OTHER are not generated |
| ID: | WTP-3271 |
| Status: | Unresolved |
| Component: | Hibernate Tools Integration |
| Description: | Stored procedures with arguments are maped to jdbc type Types.OTHER are not generated. If jdbc driver reports procedure column with type OTHER it means that the result is dynamic (ResultSet). Only simple types are supported in stored procedures signature. |
| Issue Summary: | Sqlserver: procedure/function which opens a cursor and return a value cause runtime error. |
| ID: | WTP-3272 |
| Status: | Unresolved |
| Component: | Hibernate Tools Integration |
| Description: | Procedure or function which returns cursor causes runtime exception.
Example: |
| Issue Summary: | Headless build commands ccdeploy and ccundeploy are documented but not present in the 7.0.1 Release |
| ID: | WTP-3361 |
| Status: | Unresolved |
| Component: | Documentation - Studio User Guide |
| Description: | The ccdeploy and ccundeploy headless build commands are described in the Cape Clear Studio 7.0.1 documentation but are not present in the software. They will be available in a future release |
| Issue Summary: | Removing a mapping in the XSLT Mapper doubles the nodes when two nodes are mapped to the parent |
| ID: | WTP-2593 |
| Status: | Unresolved |
| Component: | Editor - Mapper |
| Description: | Removing a mapping in the XSLT Mapper doubles the nodes when two nodes are mapped to the parent. This can be illustrated using the following steps: 1) Create an new XSLT file and load in the mapper. 2) Map a parent node to activate its children 3) Map one of its child nodes 4) Right click on the child node and select Remove. Only one mapping is listed. 5) Map another node to the parent 6) Richt click on the child node and select Remove. The mapping is listed twice. |
| Issue Summary: | Dependency on Eclipse HibernateTools feature |
| ID: | WTP-3449 |
| Component: | Hibernate Tools Integration |
| Description: | Cape Clear Studio has a dependency on the HibernateTools Eclipse feature that affects deployment of Web Services if the HibernateTools feature is not installed.
The HibernateTools feature is used primarily by our Java Web Service database integration and should have been declared as a required feature when installing the Cape Clear Studio 7.0.0 and 7.0.1 feature. Unfortunately the WTP Server runtime framework, on which our Web Service deployment infrastructure is built, requires that all features referenced by the Cape Clear project facet implementations be present in order to function correctly. If you have installed Cape Clear 7.0.0 (or 7.0.1) via our Update Site, you must ensure that you have the HibernateTools 3.2.0.beta9a feature installed or you will not be able to deploy your Web Service projects onto Cape Clear servers from within the Studio workbench. We are already hosting this feature on our update site. To install:
In future releases, Cape Clear Studio 7.0.2 and beyond, the product will declare a dependency on this feature ensuring that the Update Manager will prompt users to resolve the dependency before installing the Cape Clear Studio feature. |
Subscribe to Feeds
Developer News
Forums
Blogs
Search
Active forum topics
