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"
Line 46: | Line 46: | ||
<TD width="289">When Expanding the Collpased Property, error throws up</TD> | <TD width="289">When Expanding the Collpased Property, error throws up</TD> | ||
<TD width="216">182307</TD> | <TD width="216">182307</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation - Workaround: This problem comes up only when user imports properties of Complex data types.</TD> |
</TR> | </TR> | ||
Line 54: | Line 54: | ||
<TD width="289">when renaming mcap file , its asking to remove xsd and rmd files</TD> | <TD width="289">when renaming mcap file , its asking to remove xsd and rmd files</TD> | ||
<TD width="216">179958</TD> | <TD width="216">179958</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 61: | Line 61: | ||
<TD width="289">Could not set values for Operation parameter arrays through MAX</TD> | <TD width="289">Could not set values for Operation parameter arrays through MAX</TD> | ||
<TD width="216">181221</TD> | <TD width="216">181221</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 119: | Line 119: | ||
<TD width="289">Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed</TD> | <TD width="289">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="216">181770</TD> | ||
− | <TD width="202">Known Limitation - Workaround: | + | <TD width="202">Known Limitation - Workaround:</TD> |
</TR> | </TR> | ||
Line 157: | Line 157: | ||
</TR> | </TR> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</TABLE> | </TABLE> | ||
Line 180: | Line 174: | ||
<TD width="289">When codegeneration is successful, at present we have to replace existing javafiles with other javafiles.</TD> | <TD width="289">When codegeneration is successful, at present we have to replace existing javafiles with other javafiles.</TD> | ||
<TD width="216">176593</TD> | <TD width="216">176593</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 199: | Line 193: | ||
<TD width="289">Client proxy generation not working for relationships capability</TD> | <TD width="289">Client proxy generation not working for relationships capability</TD> | ||
<TD width="216">181912</TD> | <TD width="216">181912</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 207: | Line 201: | ||
<TD width="289">Axis2 Location is not updated in the User Preferences</TD> | <TD width="289">Axis2 Location is not updated in the User Preferences</TD> | ||
<TD width="216">185305</TD> | <TD width="216">185305</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
<TR> | <TR> | ||
<TD width="191"></TD> | <TD width="191"></TD> | ||
<TD width="289">Codgen window does not comes up to do codegeneration with SUN/IBMJava142</TD> | <TD width="289">Codgen window does not comes up to do codegeneration with SUN/IBMJava142</TD> | ||
<TD width="216">185320</TD> | <TD width="216">185320</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<TR> | <TR> | ||
<TD width="191"></TD> | <TD width="191"></TD> | ||
Line 282: | Line 263: | ||
<TD width="289">Unsubscribe image doesnot shows up on the Property in MAX</TD> | <TD width="289">Unsubscribe image doesnot shows up on the Property in MAX</TD> | ||
<TD width="216">179923</TD> | <TD width="216">179923</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
<TR> | <TR> | ||
Line 314: | Line 295: | ||
<TD width="289">Could not Remove the Relationship Property in Relationship participant</TD> | <TD width="289">Could not Remove the Relationship Property in Relationship participant</TD> | ||
<TD width="216">179440</TD> | <TD width="216">179440</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
<TR> | <TR> | ||
Line 320: | Line 301: | ||
<TD width="289">Able to Add duplicate Relationship Definition</TD> | <TD width="289">Able to Add duplicate Relationship Definition</TD> | ||
<TD width="216">181582</TD> | <TD width="216">181582</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 337: | Line 318: | ||
<TD width="289">error throws up in error log On Selecting classe names of selected Jar files</TD> | <TD width="289">error throws up in error log On Selecting classe names of selected Jar files</TD> | ||
<TD width="216">181604</TD> | <TD width="216">181604</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Line 344: | Line 325: | ||
<TD width="289">UCD: Jar file text box should be editable, so that user manually can add path or delete path</TD> | <TD width="289">UCD: Jar file text box should be editable, so that user manually can add path or delete path</TD> | ||
<TD width="216">184378</TD> | <TD width="216">184378</TD> | ||
− | <TD width="202"></TD> | + | <TD width="202">Known Limitation</TD> |
</TR> | </TR> | ||
Revision as of 07:04, 1 June 2007
Place content here.
Feature | Limitation | Bug Reference | Remarks |
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. | Known Limitation - Workaround: Before Importing any wsdl or xsd file in to the existing capability or while creating new capability please make sure that Network is enabled Internet access Enabled | ||
Unable to see the existing Properties in the properties tab | 190433 | Known Limitation - Workaround: Create all default properties without changing the metadata and save the editor, Again reopen the editor and update the metadata | |
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 |
185144 | Known Limitation - Workaround: Create a New project with out spaces in the project name | |
When Expanding the Collpased Property, error throws up | 182307 | Known Limitation - Workaround: This problem comes up only when user imports properties of Complex data types. | |
when renaming mcap file , its asking to remove xsd and rmd files | 179958 | Known Limitation | |
Could not set values for Operation parameter arrays through MAX | 181221 | 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 | 182979 | Known Limitation - Workaround: It is a Muse bug |
MRT Editor |
Redmark shows up for the mrt file when Capability is removed from the Project | 167374 | Known Limitation - Workaround: Before deleting the capability file from the project, please makesure that has been removed from the MRTs | |
Standard and Custom capabilities are repeating in the mrt editor | 181202 | Known Limitation - Workaround: Please restart the Eclipse so that it goes away. | |
Service Group and Relationship capabilities should expose the topics and related rmd files have to be changed | 181770 | Known Limitation - Workaround: | |
Router Entries are not created in Proper folder | 189401 | Known Limitation - Workaround: If user wants to change the mrt file, start editing Manageable Endpoint Type name so that it automatically edits File name also |
Deployment Descriptor Editor |
Custom Serializers shows up even when the related mrt is removed from the dd file | 176009 | 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 | |
Could not see any Custom Serializers in the dd file, which got created when generating code from MRT | 174594 | 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 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. | 176593 | Known Limitation |
Code Generation |
Client proxy generation not working for relationships capability | 181912 | Known Limitation | |
Axis2 Location is not updated in the User Preferences | 185305 | Known Limitation | |
Codgen window does not comes up to do codegeneration with SUN/IBMJava142 | 185320 | Known Limitation | |
Java files are not getting generated when doing codegen after updating operation name in capability editor | 179713 | ||
Compilation Errors shows up for the java files after codegeneration | 185520 | 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 | |
Topics provided in RMD file leads to failure of initialization of resource | 183804 | Known Limitation - Workaround: 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 | 185297 | Known Limitation - Workaround: Restart the Workspace so that this problem will go away | |
Duplicate projects are getting generated when doing codegen for AXIS 2 on J2EE | 185766 | Known Limitation - Workaround: When Generating code for MRT or DD file, please provide non existent project name |
Managed Agent Explorer |
Unsubscribe image doesnot shows up on the Property in MAX | 179923 | Known Limitation | |
noticed that Updated Custom Operation name doesnt reflect in operations list, instead old Custom Operation name shows up | 174474 | Known Limitation - Workaround: Updation of Operation cannot be done,instead please create a new capability and add the new operation. | |
Confused which Property belogs to which Capability In MAX | 183152 | known Limitation |
Relationships Editor |
Could not Remove the Relationship Property in Relationship participant | 179440 | Known Limitation | |
Able to Add duplicate Relationship Definition | 181582 | Known Limitation |
Import Java classes a Capability |
error throws up in error log On Selecting classe names of selected Jar files | 181604 | Known Limitation | |
UCD: Jar file text box should be editable, so that user manually can add path or delete path | 184378 | Known Limitation |