Assembly Gallery
User login
Navigation
Cape Clear Studio 7.5.1 Release Notes
This page lists the known issues in Cape Clear 7.5.1 and the issues fixed since 7.5.0.
Known Issues in Cape Clear Studio 7.5.1
The following table lists the known issues in Cape Clear Studio 7.5.1:
|
Issue Summary: |
Migrating Assembly Projects from Cape Clear Studio 7.5 to 7.5.x |
| ID: | WTP-4655 |
| Status: | Open |
| Component: | Migration |
| Description: |
Since Cape Clear 7.5, a number of attribute changes have been made to Cape Clear assembly schema. This migration should be done using the Automatic Migration Utility packaged with Studio. Note: Do not attempt to open a 7.5 assembly.xml file in the 7.5.x Assembly Editor without first running the migration utility against the project. This is because the Assembly Editor will delete any invalid elements completely from the file before they can be properly migrated. Start the automatic migration utility by either right-clicking on the Cape Clear assembly.xml requires migration problem marker and selecting the Quick Fix option, which will migrate the assembly file accordingly. Alternatively, you can perform the migration by right-clicking on the assembly.xml itself and selecting CapeClear> Migrate Assembly.xml to latest version. Once each problem marker has been resolved, save the assembly file and close the assembly editor, then re-open the assembly file to ensure that no problem markers exist. In some cases, the updated assembly might not render itself properly in the editor - you can resolve this by deleting the assembly-diagram.xml file and reopen the assembly in the editor once again. |
|
Issue Summary: |
Adding the Cape Clear Assembly facet to J2EE Modules |
| ID: | WTP-4361 |
| Status: | Unresolved |
| Component: | Mediation |
| Description: | J2EE modules (e.g. WAR and EAR projects) do not support Cape Clear's Assembly facet even though the facet can be added to these projects using Cape Clear Studio. The assembly facet is for use with Cape Clear Web service projects only. |
|
Issue Summary: |
Workspaces created with the Cape Clear 7.5 Technical Preview will not open in the 7.5 GA |
| ID: | WTP-4346 |
| Status: | Unresolved |
| Component: | Welcome - Samples Page |
| Description: | Eclipse Workspaces created within the Cape Clear 7.5 Technical Preview will not open in the 7.5 GA. To overcome this problem, create a new workspace in Cape Clear 7.5 GA and import the older projects into this new workspace. |
|
Issue Summary: |
Antivirus worm detection option may interfere with Cape Clear Web Service Browser |
| ID: | WTP-4320 |
| Status: | Unresolved |
| Component: | View - Web Service Browser |
| Description: | Enabling worm detection within antivirus software has been found on occasion to cause errors when refreshing the Cape Clear Web Service Browser. Cape Clear processes are not identified as a worm by the antivirus software and no security breach occurs or is logged. |
|
Issue Summary: |
Attempting to deploy a project before the Cape Clear Server has started may cause its service to fail to deploy properly |
| ID: | WTP-4268 |
| Status: | Unresolved |
| Component: | Project Actions |
| Description: | We recommend you start the Cape Clear server before deploying a service using "Run on Server". On occasion deploying a project using the "Run On Server" option to a Cape Clear Server that is not already started may cause the project's Web service to not deploy properly when the server is eventually started. |
|
Issue Summary: |
Invalid elements and attributes added in the source view are silently discarded by the Assembly Editor |
| ID: | WTP-4236 |
| Status: | Unresolved |
| Component: | Editor - Assembly |
| Description: | When editing an assembly using the "Source" view of the Assembly Editor, any added attributes or elements that are not defined in the assembly schema are silently discarded when the assembly is saved in the editor. They are also silently discarded if added within the "Design" view and then the user switches back to the "Source" view. Note that while this behavior can be confusing when editing, no useful information is being lost because the attributes and elements would make the assembly invalid and would have to be removed manually in any case. |
|
Issue Summary: |
PartnerLink-application-client.xml files are not renamed when a BPEL PartnerLink is renamed |
| ID: | WTP-3771 |
| Status: | Unresolved |
| Component: | Editor - BPEL Editor |
| Description: | When a BPEL PartnerLink is renamed using the Manage Partner Links dialog, if there is a corresponding PartnerLink-application-client.xml file defined in the project, it is not renamed. The workaround is to be manually rename the the PartnerLink-application-client.xml file appropriately if one exists. |
|
Issue Summary: |
Full path instead of relative path needs to be used in the document() function |
| ID: | WTP-3693 |
| Status: | Unresolved |
| Component: | Builder - Transform WS |
| Description: | When using document() function in XSLT, the full path to an external file should be specified instead of a relative path. A relative path to the file will just return an empty node. For example, use <xsl:variable name="Translation" select="document('file:///c:/MyProject/WSAR-INF/externalFile.xml')/node"/> instead of <xsl:variable name="Translation" select="document('externalFile.xml')/node"/> |
|
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. The workaround is that the sample_database project should be deleted with default option: 'Do not delete contents' or to restart Studio in order to delete the projects contents also. |
|
Issue Summary: |
Stored procedures do not support cursors and records |
| ID: | WTP-3272 |
| Status: | Unresolved |
| Component: | Hibernate Tools Integration |
| Description: | Cape Clear's facility for exposing stored procedures as Java Web services does not include support for cursors and records. A workaround is to process a cursor manually and close it before the transaction commits. In the case of records being passed as an argument of a procedure/function the workaround is to create a wrapper procedure which eliminates the record parameters. The following is an example of procedure which will cause an exception at runtime (opened cursor):
Create Procedure GetNameInfoById |
|
Issue Summary: |
Migration of BPEL project from 6.X to 7.0 results in errors for missing settings |
| ID: | WTP-3123 |
| Status: | Unresolved |
| Component: | Other |
| Description: | When a BPEL project is migrated the following errors may display in the problem view:
Severity and Description Path Resource Location Creation Time Id The errors go away after cleaning the project. |
|
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: |
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: |
A combined WSDL to Java Web Service and Java Web Service Client project implementing and invoking on the same WSDL will not 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: |
The "Enforce compatibility with only the current workbench default JRE" option in the Cape Clear > Java Project Settings > preferences does not work |
| ID: | WTP-2969 |
| Status: | Unresolved |
| Component: | Wizard/Property Pages - New Java Client |
| Description: | The Cape Clear > Java Project Settings preferences page has an option "Enforce compatibility 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. This property has no effect when enabled. Instead the Cape Clear wizards create projects that are compatible with any JRE. |
|
Issue Summary: |
Error when importing samples |
| ID: | WTP-2847 |
| Status: | Unresolved |
| Component: | Other |
| Description: | Each time a sample project is imported from the Studio Samples the following error is recorded 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: |
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: |
The context sensitve help button on the New Update Site dialog does not work |
| ID: | WTP-2574 |
| Status: | Unresolved |
| Component: | Samples - Implementation |
| Description: | If using the Update Manager to specify a new update site to point at the Cape Clear Studio Update Site, clicking the help button does nothing. |
|
Issue Summary: |
The XSLT Mapper's "add parameter" button incorrectly permits mapping to a disabled branch |
| ID: | WTP-2437 |
| Status: | Unresolved |
| Component: | Editor - XSLT |
| Description: | The XSLT Mapper incorrectly allows mappings to parent nodes of disabled branches when created using the "add paramater" button. |
|
Issue Summary: |
The vertical scroll bar periodically fails to appear in the Transformation Builder "before" panel |
| ID: | WTP-2430 |
| Status: | Unresolved |
| Component: | Editor - Transform Builder |
| Description: | The vertical scroll bar within the transformation builder's "before" panel sometimes fails to appear. A workaround is to click in the panel and use the page-up / page-down keys to scroll through the panel's details. |
|
Issue Summary: |
Java to WSDL web services generate unnecessary backup WSDL files |
| ID: | WTP-2299 |
| Status: | Unresolved |
| Component: | Java2WSDL |
| Description: | When rebuilding a Java to WSDL Web Service project, the WSDL file is always regenerated. A backup of the old WSDL file that is not really needed is also created. Eclipse has a local history system so the backup is unnecessary. |
|
Issue Summary: |
Occasionally publish to the server fails with error "cannot find deserializer for class (none)" |
| ID: | WTP-1436 |
| Status: | Unresolved |
| Component: | Servers - Local |
| Description: | Occasionally publish / deployment to a server may fail with an error message that states "cannot find deserializer for class (none)". If this happens, it can be corrected by shutting down Studio, removing the following file, and restarting:
<WORKSPACE_ROOT>/.metadata/.plugins/org.eclipse.wst.server.core |
|
Issue Summary: |
Disabling the launch client option when deploying Web applications |
| ID: | WTP-867 |
| Status: | Unresolved |
| Component: | Builder - Java WS |
| Description: | Deploying a web application to JBoss using the "Run On Server" option brings up a Web browser whose location is a WSDL that does not exist. This is displayed before the server has finished publishing the application. The workaround is to disable the Web browser from appearing by include the Web browser view as a standard view in the Cape Clear perspective. |
Issues Fixed Since Cape Clear Studio 7.5.0
The following table lists the issues fixed since Cape Clear Studio 7.0.3:
|
Issue Summary: |
The "REST-style Web Service Tutorial" described in the Samples Guide contains an incorrect step |
| ID: | WTP-4482 |
| Status: | Unresolved |
| Component: | Documentation - Studio Samples Guide |
| Description: | The BPEL code provided for the second <assign> activity in the "REST-style Web Service Tutorial" is incorrect. The line <bpws:to variable="YahooSearchResponse" part="output" query="/ns2:ResultSet/ns2:Result"/> in the third <copy> references the wrong response message and should read <bpws:to variable="WebSearchResponse" part="results" query="/ns2:ResultSet/ns2:Result"/>. The entire BPEL code for this <assign> activity should be as follows:
<bpws:assign> <bpws:to variable="WebSearchResponse" part="results" /> <bpws:copy> <bpws:copy> |
Subscribe to Feeds
Developer News
Forums
Blogs
Search
Active forum topics
