Difference between revisions of "BtM WSDM TPTP 4.4 Limitations"

Revision as of 15:00, 29 June 2007

Known problem or limitation	Workaround
Project with spaces: When creating a capability in a project that has spaces in its name (for example, Test 1), a redmark shows up next to the capability file and when it is opened, all the fields are empty.	Create capabilities only in projects that do not have a space in the name
Capability definition import: Import of any XSD or WSDL which imports another XSD or WSDL using a HTTP URI, requires a network connection to resolve the imported XSD or WSDL file.	Before importing any WSDL or XSD file into an existing capability or while creating a new capability make sure that an internet connection is available.
Capability definition import:<i>XSD property removed from capability cannot be imported again</TD>	Do not remove imported properties but instead create a new capability</TD> </TR>
<i>Capability definition editor:When a property is removed from the capability editor, the related fields are disabled but still show values	Known Limitation
Renaming capability definitions: When renaming a capability definition file (.mcap), a confirmation dialog requesting confirmation for removal of the corresponding XSD and RMD files is shown.	Known Limitation. This will be addressed in the next release by providing a "Package Explorer" like view that hides the different files that compose a capability definition.
Capability Definition: Changes to operation name are not reflected	Known limitation. Only workaround is to create a new capability.
Creating a new project: In some cases, Cannot create new WSDM capability or managed resource type definition from File menu	When creating new Capability/managed resource type from the File menu, Select the target Project i.e. Project1 using browse button; if it shows up in the corresponding text field as \Project1 update it to /project1 before proceeding.
Array return type for operations in capability definition: If user selects to return array values for an operation, then the generated WSDL file is marked invalid in the generated project	Known Limitation. This is a WSDL validation issue and does not affect the generated endpoint's operation.
Notification Topics:Topics provided in capability definition may lead to failure of resource initialization on endpoint deployment	In the generated project, you will find an extra package called org.eclipse.tptp.wsdm.runtime.capability. Delete this package before deploying the generated endpoint.
Manageable Resource Type:When a capability definition that is used in one or more Manageable resource type (.mrt) files is removed, the corresponding .mrt files fail validation	Before deleting the capability definition from the project, remove it from the Manageable Resource Type definitions that use the capability. Unfortunately, once a resource type definition has been marked invalid, the reference to the missing capability can be removed only by opening the file in a text editor and manually removing the entry.
Deployment descriptor editor: Custom Serializers shows up even when the related manageable resource type is removed from the deployment descriptor template file	Known limitation. Open the .dd file in a text editor and remove all the <custom-serializer> elements that were used by removed resource type
Code Generation: On Java 1.4, code generation dialog does not show J2EE option	Known Limitation. J2EE based endpoints cannot be created on Java 1.4 since Web tools project requires Java 1.5 or above.
Code generation: Generated deployment descriptor file (in the generated project) does not contain any custom serializers	Known problem. Generate the deployment descriptor template from the manageable resource type definition (right click on the .mrt file). Associate custom serializer in the generated deployment descriptor template and then generate java code from the deployment descriptor file (right click on the .dd file)
Code generation: When codegeneration is successful for manageable resource type definition that has Relationship, Service group and/or Notification producer Capabilities additional packages are generated	Known Limitation. Remove the additional packages from the generated project. Keep only the packages that correspond to the namespaces of the custom capability used in the resource type definition.
Code generation: Generasted Java code has compilation problems if the namespace provided for capability does not end in a format such as test2.org	Known problem. If you wish to use a specific namespace for a capability, format it such that it ends with x.y. i.e. http://test1.org/test2 and http://test1.org/test2/test3 are incorrect; http://test1.test2.org is correct
Code generation: Could not generate code when capability has a property defined as writable and as constant for mutability	A constant property cannot be writable. Ensure that constant properties are defined as read only.
Code Generation: Could not generate code if an existing project name is specified as target event if the "Overwrite Files" checkbox is checked	When Generating code, provide a non-existent project name
Generated Endpoint:RuntimeException throws up when deploying Javacode on Tomcat	Known Limitation. There are no side effects and the endpoint will function normally.
Spec compliance::Service Group and Relationship capabilities do not provide topics as defined by the specification	Known Limitation. The topics can be manually added to the corresponding files after code generation.
Generated endpoint:Generated OSGI project is not valid	Export these packages: org.apache.muse.core.platform.osgi, org.apache.muse.core.platform.osgi.descriptor, org.apache.muse.core.platform.osgi.internal, org.apache.muse.ore.platform.osgi.routing and org.apache.muse.core.platform.osgi.util from 'org.apache.muse.osgi.core' plugin as a jar to the created OSGI project. Add it as an additional jar to the project.
Managed Agent Explorer: Unsubscribe does not work	The resource you are introspecting with the Managed Agent Explorer must support WS-RL for unsubscribe to be supported
Managed Agent Explorer: Can not set values for Operation parameter arrays through MAX	Known Limitation

@@ Line 2: / Line 2: @@
                  <TR>
-			<TD bgcolor="#ff80ff" width="500"><B>Limitation</B></TD>
+			<TD bgcolor="#0099FF" width="500"><B>Known problem or limitation</B></TD>
-			<TD bgcolor="#ff80ff" width="500"><B>Workaround</B></TD>
+			<TD bgcolor="#0099FF" width="500"><B>Workaround</B></TD>
 		</TR>
                 <TR>
-			<TD width="500">If user imports any XSD or WSDL which imports another XSD or WSDL using Http uri, then user might need Network connection to resolve the imported XSD or WSDL file.</TD>
+			<TD width="500"><i>Project with spaces:</i> When creating a capability in a project that has spaces in its name (for example, Test 1), a redmark shows up next to the capability file and when it is opened, all the fields are empty.</TD>
-			<TD width="500">Before Importing any wsdl or xsd file into the existing capability or while creating new capability please make sure that Network and Internet access Enabled</TD>
+			<TD width="500">Create capabilities only in projects that do not have a space in the name</TD>
 		</TR>
+	 <TR>
-               <TR>
-			<TD width="500">When Creating the capability/creating by importing WSDL/Creating by impporting java classes as capabilities under the Project i,e "Test 1" (Project Name
+			<TD width="500"><i>Capability definition import:</i> Import of any XSD or WSDL which imports another XSD or WSDL using a <i>HTTP URI</i>, requires a network connection to resolve the imported XSD or WSDL file.</TD>
-having space) redmark shows up for the capability file when opening capability
-file noticed all the fields are empty</TD>
-			<TD width="500">Create a New project with out spaces in the project name</TD>
+			<TD width="500">Before importing any WSDL or XSD file into an existing capability or while creating a new capability make sure that an internet connection is available.</TD>
 		</TR>
+	<TR>
-		<TR>
-			<TD width="500">when renaming mcap file , its asking to remove xsd and rmd files</TD>
+			<TD width="500"><i>Capability definition import:<i>XSD property removed from capability cannot be imported again</TD>
-			<TD width="500">Known Limitation</TD>
+			<TD width="500">Do not remove imported properties but instead create a new capability</TD>
 		</TR>
                  <TR>
-			<TD width="500">Could not set values for Operation parameter arrays through MAX</TD>
+			<TD width="500"><i>Capability definition editor:</i>When a property is removed from the capability editor, the related fields are disabled but still show values</TD>
 			<TD width="500">Known Limitation</TD>
 		</TR>
-                <TR>
-			<TD width="500">Array return type for operations - If user selects to return the array values for an operation, then the generated smashed wsdl file will be invalid and marked         as red in the generated project</TD>
-			<TD width="500">Known Limitation</TD>
-		</TR>
+		<TR>
-                <TR>
-			<TD width="500">Topics provided in RMD file leads to failure of initialization of resource</TD>
+			<TD width="500"><i>Renaming capability definitions:</i> When renaming a capability definition file (.mcap), a confirmation dialog requesting confirmation for removal of the corresponding XSD and RMD files is shown.</TD>
-			<TD width="500">Known Limitation</TD>
+			<TD width="500">Known Limitation. This will be addressed in the next release by providing a "Package Explorer" like view that hides the different files that compose a capability definition.</TD>
 		</TR>
                  <TR>
-			<TD width="500">RuntimeException throws up when deploying Javacode on Tomcat</TD>
+			<TD width="500"><i>Capability Definition:</i> Changes to operation name are not reflected</TD>
-			<TD width="500">Known Limitation(It is a Muse bug) </TD>
+			<TD width="500">Known limitation. Only workaround is to create a new capability.</TD>
 		</TR>
-                <TR>
+		<TR>
-			<TD width="500">Could not see the XSD property to import</TD>
+			<TD width="500"><i>Creating a new project:</i> In some cases, Cannot create new WSDM capability or managed resource type definition from File menu </TD>
-			<TD width="500">Do not remove imported properties but instead create a new capability</TD>
+			<TD width="500">When creating new Capability/managed resource type from the File menu, Select the target Project i.e. Project1 using browse button; if it shows up in the corresponding text field as <i>\Project1</i> update it to <i>/project1</i> before proceeding.</TD>
 		</TR>
                  <TR>
-			<TD width="500">When the property is removed from the capability editor, the related fields are disabled but not getting Empty</TD>
+			<TD width="500"><i>Array return type for operations in capability definition:</i>  If user selects to return array values for an operation, then the generated WSDL file is marked invalid in the generated project</TD>
-			<TD width="500">Known Limitation</TD>
+			<TD width="500">Known Limitation. This is a WSDL validation issue and does not affect the generated endpoint's operation.</TD>
 		</TR>
                  <TR>
-			<TD width="500">Could not generate code when capability having property as writable and mutability as constant</TD>
+			<TD width="500"><i>Notification Topics:</i>Topics provided in capability definition may lead to failure of resource initialization on endpoint deployment</TD>
-			<TD width="500">When user wants to select mutability as constant then make sure that property is read only</TD>
+			<TD width="500">In the generated project, you will find an extra package called <i>org.eclipse.tptp.wsdm.runtime.capability</i>. Delete this package before deploying the generated endpoint.</TD>
 		</TR>
-                <TR>
+		<TR>
+			<TD width="500"><i>Manageable Resource Type:</i>When a capability definition that is used in one or more Manageable resource type (.mrt) files is removed, the corresponding .mrt files fail validation</TD>
-			<TD width="500">Redmark shows up for the mrt file when Capability is removed from the Project</TD>
+			<TD width="500">Before deleting the capability definition from the project, remove it from the Manageable Resource Type definitions that use the capability. Unfortunately, once a resource type definition has been marked invalid, the reference to the missing capability can be removed only by opening the file in a text editor and manually removing the entry.</TD>
-			<TD width="500">Before deleting the capability file from the project, please makesure that has been removed from the MRTs </TD>
 		</TR>
-                 <TR>
+		<TR>
-			<TD width="500">Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed</TD>
+			<TD width="500"><i>Deployment descriptor editor</i>: Custom Serializers shows up even when the related manageable resource type is removed from the deployment descriptor template file</TD>
-			<TD width="500">Known Limitation </TD>
+			<TD width="500">Known limitation. Open the .dd file in a text editor and remove all the <custom-serializer> elements that were used by removed resource type</TD>
 		</TR>
 		<TR>
-			<TD width="500">Custom Serializers shows up even when the related mrt is removed from the dd file</TD>
+			<TD width="500"><i>Code Generation:</i> On Java 1.4, code generation dialog does not show J2EE option</TD>
-			<TD width="500">Open the DD file in Text editor and remove all the <custom-serializer> Elements that were being used by Removed resource type </TD>
+			<TD width="500">Known Limitation. J2EE based endpoints cannot be created on Java 1.4 since Web tools project requires Java 1.5 or above.</TD>
 		</TR>
 		<TR>
-			<TD width="500">Could not see any Custom Serializers in the dd file, which got created when generating code from MRT</TD>
+			<TD width="500"><i>Code generation</i>: Generated deployment descriptor file (in the generated project) does not contain any custom serializers</TD>
-			<TD width="500">User can right click the mrt file and generate a dd template, custom serializer will show up in the dd template and
+			<TD width="500">Known problem. Generate the deployment descriptor template from the manageable resource type definition (right click on the .mrt file). Associate custom serializer in the generated deployment descriptor template and then generate java code from the deployment descriptor file (right click on the .dd file)</TD>
-then user can do the codegen from that dd file.</TD>
 		</TR>
@@ Line 118: / Line 108: @@
 		<TR>
-			<TD width="500">When codegeneration is successful for MRT,DD having Relationship/Service group/Notification producer Capabilities. At present we have to remove the related javafiles</TD>
+			<TD width="500"><i>Code generation:</i> When codegeneration is successful for manageable resource type definition that has Relationship, Service group and/or Notification producer Capabilities additional packages are generated</TD>
-			<TD width="500">Known Limitation</TD>
+			<TD width="500">Known Limitation. Remove the additional packages from the generated project. Keep only the packages that correspond to the namespaces of the custom capability used in the resource type definition.</TD>
 		</TR>
@@ Line 126: / Line 116: @@
                  <TR>
-			<TD width="500">Compilation Errors shows up  for the java files after codegeneration</TD>
+			<TD width="500"><i>Code generation:</i> Generasted Java code has compilation problems if the namespace provided for capability does not end in a format such as test2.org</TD>
-			<TD width="500">When Creating the new custom capability dont change the namespace of the capability or if user still wants to change the name space please edit the namespace in these formats i,e http://test1.org/test2 or http://test1.org/test2/test3 but edit to http://test1.test2.org </TD>
+			<TD width="500">Known problem. If you wish to use a specific namespace for a capability, format it such that it ends with x.y. i.e. http://test1.org/test2 and http://test1.org/test2/test3 are incorrect; http://test1.test2.org is correct</TD>
 		</TR>
+<TR>
-                <TR>
-			<TD width="500">Topics provided in RMD file leads to failure of initialization of resource </TD>
+			<TD width="500"><i>Code generation:</i> Could not generate code when capability has a property defined as writable and as constant for mutability</TD>
-			<TD width="500">After generation of code please remove the java files, build the project and can be deployed successfully</TD>
+			<TD width="500">A constant property cannot be writable. Ensure that constant properties are defined as read only.</TD>
 		</TR>
+		<TR>
-                <TR>
-			<TD width="500">Could not GenerateJavacode when Entering duplicate Project name and Checking in Overwrite Files necessary checkbox</TD>
+			<TD width="500"><i>Code Generation:</i> Could not generate code if an existing project name is specified as target event if the "Overwrite Files" checkbox is checked</TD>
-			<TD width="500">When Generating code for MRT or DD file, please provide non existent project name</TD>
+			<TD width="500">When Generating code, provide a non-existent project name</TD>
 		</TR>
-                <TR>
+<TR>
-			<TD width="500">Redmark shows on the Generated Axis2 on OSGI Code when started eclipse with SUNJava1.4.2/1.5.0 or IBMJava1.4.2/1.5.0</TD>
+			<TD width="500"><i>Generated Endpoint:</i>RuntimeException throws up when deploying Javacode on Tomcat</TD>
-			<TD width="500">Export the packages org.apache.muse.core.platform.osgi, org.apache.muse.core.platform.osgi.descriptor, org.apache.muse.core.platform.osgi.internal, org.apache.muse.ore.platform.osgi.routing and org.apache.muse.core.platform.osgi.util from 'org.apache.muse.osgi.core' plugin as a jar to the created OSGI project. Add it as an additional jar to the project. The 2 errors of src folder were gone from the problem view
+			<TD width="500">Known Limitation. There are no side effects and the endpoint will function normally. </TD>
-</TD>
 		</TR>
-                <TR>
+		<TR>
-			<TD width="500">Could not do Codegeneration when started eclipse with Java 1.4.2</TD>
+			<TD width="500"><i>Spec compliance:</i>:Service Group and Relationship capabilities do not provide topics as defined by the specification</TD>
-			<TD width="500">Known Limitation</TD>
+			<TD width="500">Known Limitation. The topics can be manually added to the corresponding files after code generation.</TD>
 		</TR>
                  <TR>
-			<TD width="500">Noticed that Updated Custom Operation name doesnt
+			<TD width="500"><i>Generated endpoint:</i>Generated OSGI project is not valid</TD>
-reflect in operations list, instead old Custom Operation name shows up</TD>
-			<TD width="500">Updation of Operation cannot be done,instead please create a new capability and add the new operation.</TD>
+			<TD width="500">Export these packages: org.apache.muse.core.platform.osgi, org.apache.muse.core.platform.osgi.descriptor, org.apache.muse.core.platform.osgi.internal, org.apache.muse.ore.platform.osgi.routing and org.apache.muse.core.platform.osgi.util from
+			'org.apache.muse.osgi.core' plugin as a jar to the created OSGI project. Add it as an additional jar to the project.</TD>
 		</TR>
                  <TR>
-			<TD width="500">subscribe image shows up even when selecting unsubscribe on the Property in MAX</TD>
+			<TD width="500"><i>Managed Agent Explorer:</i> Unsubscribe does not work</TD>
-			<TD width="500">Known Limitation(This is related to Muse bug)</TD>
+			<TD width="500">The resource you are introspecting with the Managed Agent Explorer must support WS-RL for unsubscribe to be supported</TD>
 		</TR>
-                 <TR>
+		<TR>
-			<TD width="500">Could not create WSDM Tooling Artifacts from File menu to selected WSDM Tooling Project</TD>
+			<TD width="500"><i>Managed Agent Explorer:</i> Can not set values for Operation parameter arrays through MAX</TD>
-			<TD width="500">At the time of creating new Capability/MRT from File->New->Other->Tooling for WSDM, Select the Project i,e Project1 using browse button, When selected it shows as \Project1 then update it to /project1 and proceed to create new capability/MRT </TD>
+			<TD width="500">Known Limitation</TD>
 		</TR>

Breadcrumbs

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Difference between revisions of "BtM WSDM TPTP 4.4 Limitations"

Revision as of 15:00, 29 June 2007