Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "BtM WSDM TPTP 4.4 Limitations"

Line 3: Line 3:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ff80ff" width="340"><B>Limitation</B></TD>
+
<TD bgcolor="#ff80ff" width="500"><B>Limitation</B></TD>
<TD bgcolor="#ff80ff" width="206"><B>Workaround</B></TD>
+
<TD bgcolor="#ff80ff" width="500"><B>Workaround</B></TD>
 
</TR>
 
</TR>
 
 
Line 11: Line 11:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Capability Editor</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Capability Editor</B></TD>
 
</TR>
 
</TR>
 
 
Line 18: Line 18:
 
         
 
         
 
               <TR>
 
               <TR>
<TD width="191"></TD>
+
<TD width="289">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">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="216"></TD>
+
<TD width="202">Known Limitation - Workaround: 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">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>
 
</TR>
 
</TR>
  
 
                                
 
                                
 
               <TR>
 
               <TR>
<TD width="191"></TD>
+
<TD width="289">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">When Creating the capability/creating by importing WSDL/Creating by impporting java classes as capabilities under the Project i,e "Test 1" (Project Name
 
having space) redmark shows up for the capability file when opening capability
 
having space) redmark shows up for the capability file when opening capability
 
file noticed all the fields are empty</TD>
 
file noticed all the fields are empty</TD>
<TD width="216">185144</TD>
+
<TD width="202">Known Limitation - Workaround: Create a New project with out spaces in the project name</TD>
+
<TD width="500">Create a New project with out spaces in the project name</TD>
 
</TR>
 
</TR>
  
Line 37: Line 37:
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289">when renaming mcap file , its asking to remove xsd and rmd files</TD>
+
<TD width="500">when renaming mcap file , its asking to remove xsd and rmd files</TD>
<TD width="216">179958</TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
 
                                  
 
                                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Could not set values for Operation parameter arrays through MAX</TD>
+
<TD width="500">Could not set values for Operation parameter arrays through MAX</TD>
<TD width="216">181221</TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
 
                  
 
                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">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">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="216"></TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
  
Line 60: Line 60:
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Topics provided in RMD file leads to failure of initialization of resource</TD>
+
<TD width="500">Topics provided in RMD file leads to failure of initialization of resource</TD>
<TD width="216"></TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">RuntimeException throws up when deploying Javacode on Tomcat</TD>
+
<TD width="500">RuntimeException throws up when deploying Javacode on Tomcat</TD>
<TD width="216">182979</TD>
+
<TD width="202">Known Limitation -  Workaround: It is a Muse bug </TD>
+
<TD width="500">Known Limitation(It is a Muse bug) </TD>
 
</TR>
 
</TR>
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Could not see the XSD property to import</TD>
+
<TD width="500">Could not see the XSD property to import</TD>
<TD width="216">190969</TD>
+
<TD width="202">Known Limitation -  Workaround: Do not remove imported properties but instead create a new capability</TD>
+
<TD width="500">Do not remove imported properties but instead create a new capability</TD>
 
</TR>
 
</TR>
 
                
 
                
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">When the property is removed from the capability editor, the related fields are disabled but not getting Empty</TD>
+
<TD width="500">When the property is removed from the capability editor, the related fields are disabled but not getting Empty</TD>
<TD width="216"></TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
 
                  
 
                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Could not generate code when capability having property as writable and mutability as constant</TD>
+
<TD width="500">Could not generate code when capability having property as writable and mutability as constant</TD>
<TD width="216">193087</TD>
+
<TD width="202">Known Limitation - Workaround: When user wants to select mutability as constant then make sure that property is read only</TD>
+
<TD width="500">When user wants to select mutability as constant then make sure that property is read only</TD>
 
</TR>
 
</TR>
  
Line 101: Line 101:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>MRT Editor</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>MRT Editor</B></TD>
 
</TR>
 
</TR>
 
 
Line 109: Line 109:
 
                
 
                
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289">Redmark shows up for the mrt file when Capability is removed from the Project</TD>
+
<TD width="500">Redmark shows up for the mrt file when Capability is removed from the Project</TD>
<TD width="216">167374</TD>
+
<TD width="202">Known Limitation -  Workaround: Before deleting the capability file from the project, please makesure that has been removed from the MRTs </TD>
+
<TD width="500">Before deleting the capability file from the project, please makesure that has been removed from the MRTs </TD>
 
</TR>
 
</TR>
 
                  
 
                  
Line 118: Line 118:
 
                  
 
                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed</TD>
+
<TD width="500">Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed</TD>
<TD width="216">181770</TD>
+
<TD width="202">Known Limitation </TD>
+
<TD width="500">Known Limitation </TD>
 
</TR>
 
</TR>
  
Line 131: Line 131:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Deployment
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Deployment
 
Descriptor Editor</B></TD>
 
Descriptor Editor</B></TD>
 
</TR>
 
</TR>
Line 139: Line 139:
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289">Custom Serializers shows up even when the related mrt is removed from the dd file</TD>
+
<TD width="500">Custom Serializers shows up even when the related mrt is removed from the dd file</TD>
<TD width="216">176009</TD>
+
<TD width="202">Known Limitatin -    Workaround: 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">Open the DD file in Text editor and remove all the <custom-serializer> Elements that were being used by Removed resource type </TD>
 
</TR>
 
</TR>
 
 
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289">Could not see any Custom Serializers in the dd file, which got created when generating code from MRT</TD>
+
<TD width="500">Could not see any Custom Serializers in the dd file, which got created when generating code from MRT</TD>
<TD width="216">174594</TD>
+
<TD width="202">Known Limitatin -    Workaround: 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">User can right click the mrt file and generate a dd template, custom serializer will show up in the dd template and
 
then user can do the codegen from that dd file.</TD>
 
then user can do the codegen from that dd file.</TD>
 
</TR>
 
</TR>
Line 160: Line 160:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Service Group Editor</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Service Group Editor</B></TD>
 
</TR>
 
</TR>
 
 
Line 168: Line 168:
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289">When codegeneration is successful, at present we have to replace existing javafiles with other javafiles.</TD>
+
<TD width="500">When codegeneration is successful, at present we have to replace existing javafiles with other javafiles.</TD>
<TD width="216">176593</TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
 
                  
 
                  
Line 180: Line 180:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Code Generation</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Code Generation</B></TD>
 
</TR>
 
</TR>
 
 
Line 189: Line 189:
 
                  
 
                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Compilation Errors shows up  for the java files after codegeneration</TD>
+
<TD width="500">Compilation Errors shows up  for the java files after codegeneration</TD>
<TD width="216">185520</TD>
+
<TD width="202">Known Limitation -  Workaround: 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">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>
 
</TR>
 
</TR>
 
                  
 
                  
 
                
 
                
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Topics provided in RMD file leads to failure of initialization of resource </TD>
+
<TD width="500">Topics provided in RMD file leads to failure of initialization of resource </TD>
<TD width="216">183804</TD>
+
<TD width="202">Known Limitation -  Workaround: After generation of code please remove the java files, build the project and can be deployed successfully</TD>
+
<TD width="500">After generation of code please remove the java files, build the project and can be deployed successfully</TD>
 
</TR>
 
</TR>
  
 
                  
 
                  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Could not GenerateJavacode when Entering duplicate Project name and Checking in Overwrite Files necessary checkbox</TD>
+
<TD width="500">Could not GenerateJavacode when Entering duplicate Project name and Checking in Overwrite Files necessary checkbox</TD>
<TD width="216">185766</TD>
+
<TD width="202">Known Limitation -  Workaround: When Generating code for MRT or DD file, please provide non existent project name</TD>
+
<TD width="500">When Generating code for MRT or DD file, please provide non existent project name</TD>
 
</TR>
 
</TR>
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">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">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="216">182751</TD>
+
<TD width="202">Known Limitation -  Workaround: 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">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>
 
</TD>
 
</TR>
 
</TR>
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">Could not do Codegeneration when started eclipse with Java 1.4.2</TD>
+
<TD width="500">Could not do Codegeneration when started eclipse with Java 1.4.2</TD>
<TD width="216"></TD>
+
<TD width="202">Known Limitation</TD>
+
<TD width="500">Known Limitation</TD>
 
</TR>
 
</TR>
  
Line 233: Line 233:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Managed Agent Explorer</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Managed Agent Explorer</B></TD>
 
</TR>
 
</TR>
 
                
 
                
Line 241: Line 241:
 
         
 
         
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">noticed that Updated Custom Operation name doesnt
+
<TD width="500">Noticed that Updated Custom Operation name doesnt
 
reflect in operations list, instead old Custom Operation name shows up</TD>
 
reflect in operations list, instead old Custom Operation name shows up</TD>
<TD width="216">174474</TD>
+
<TD width="202">Known Limitation -  Workaround: Updation of Operation cannot be done,instead please create a new capability and add the new operation.</TD>
+
<TD width="500">Updation of Operation cannot be done,instead please create a new capability and add the new operation.</TD>
 
</TR>
 
</TR>
  
 
                 <TR>
 
                 <TR>
<TD width="191"></TD>
+
<TD width="289">subscribe image shows up even when selecting unsubscribe on the Property in MAX</TD>
+
<TD width="500">subscribe image shows up even when selecting unsubscribe on the Property in MAX</TD>
<TD width="216">179923</TD>
+
<TD width="202">Known Limitation -  Workaround: This is related to Muse bug</TD>
+
<TD width="500">Known Limitation(This is related to Muse bug)</TD>
 
</TR>
 
</TR>
 
                  
 
                  
Line 262: Line 262:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Relationships Editor</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Relationships Editor</B></TD>
 
</TR>
 
</TR>
 
 
Line 269: Line 269:
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289"></TD>
+
<TD width="500"></TD>
<TD width="216"></TD>
+
<TD width="202"></TD>
+
<TD width="500"></TD>
 
</TR>
 
</TR>
 
                
 
                
Line 280: Line 280:
 
 
 
<TR>
 
<TR>
<TD bgcolor="#ffdcb9" height="20" width="904"><B>Import Java classes a Capability</B></TD>
+
<TD bgcolor="#ffdcb9" height="20" width="1000"><B>Import Java classes a Capability</B></TD>
 
</TR>
 
</TR>
 
 
Line 287: Line 287:
 
 
 
<TR>
 
<TR>
<TD width="191"></TD>
+
<TD width="289"></TD>
+
<TD width="500"></TD>
<TD width="216"></TD>
+
<TD width="202"></TD>
+
<TD width="500"></TD>
 
</TR>
 
</TR>
 
                  
 
                  

Revision as of 02:52, 22 June 2007

Place content here.

Limitation Workaround
Capability Editor
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. 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
When Creating the capability/creating by importing WSDL/Creating by impporting java classes as capabilities under the Project i,e "Test 1" (Project Name

having space) redmark shows up for the capability file when opening capability

file noticed all the fields are empty
Create a New project with out spaces in the project name
when renaming mcap file , its asking to remove xsd and rmd files Known Limitation
Could not set values for Operation parameter arrays through MAX Known Limitation
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 Known Limitation
Topics provided in RMD file leads to failure of initialization of resource Known Limitation
RuntimeException throws up when deploying Javacode on Tomcat Known Limitation(It is a Muse bug)
Could not see the XSD property to import Do not remove imported properties but instead create a new capability
When the property is removed from the capability editor, the related fields are disabled but not getting Empty Known Limitation
Could not generate code when capability having property as writable and mutability as constant When user wants to select mutability as constant then make sure that property is read only
MRT Editor
Redmark shows up for the mrt file when Capability is removed from the Project Before deleting the capability file from the project, please makesure that has been removed from the MRTs
Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed Known Limitation
Deployment Descriptor Editor
Custom Serializers shows up even when the related mrt is removed from the dd file Open the DD file in Text editor and remove all the <custom-serializer> Elements that were being used by Removed resource type
Could not see any Custom Serializers in the dd file, which got created when generating code from MRT User can right click the mrt file and generate a dd template, custom serializer will show up in the dd template and then user can do the codegen from that dd file.
Service Group Editor
When codegeneration is successful, at present we have to replace existing javafiles with other javafiles. Known Limitation
Code Generation
Compilation Errors shows up for the java files after codegeneration 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
Topics provided in RMD file leads to failure of initialization of resource After generation of code please remove the java files, build the project and can be deployed successfully
Could not GenerateJavacode when Entering duplicate Project name and Checking in Overwrite Files necessary checkbox When Generating code for MRT or DD file, please provide non existent project name
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 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
Could not do Codegeneration when started eclipse with Java 1.4.2 Known Limitation
Managed Agent Explorer
Noticed that Updated Custom Operation name doesnt reflect in operations list, instead old Custom Operation name shows up Updation of Operation cannot be done,instead please create a new capability and add the new operation.
subscribe image shows up even when selecting unsubscribe on the Property in MAX Known Limitation(This is related to Muse bug)
Relationships Editor
Import Java classes a Capability

Back to the top