Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

BtM WSDM TPTP 4.4 Limitations

Revision as of 15:08, 29 June 2007 by (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Known problem or limitation


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: XSD property removed from capability cannot be imported again

Do not remove imported properties but instead create a new capability

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

Known problem. If you wish to use a specific namespace for a capability, format it such that it ends with x.y. i.e. and are incorrect; 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

Back to the top