[NXP-21330] Fix usage of aliases with Java Automation Client - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 7.10
Fix Version/s: 7.10-HF20, 8.10-HF01, 9.1
Component/s: Automation

Tags:
- SupCom
- nxfitcurrent
Backlog priority:
700
Upgrade notes:

Hide

Operation documentation can now be export for each alias using the `nuxeo.automation.export.aliases` configuration parameter. Default to false.

```
<extension target="org.nuxeo.runtime.ConfigurationService" point="configuration">
<property name="nuxeo.automation.export.aliases">true</property>
</extension>
```

Show
Operation documentation can now be export for each alias using the `nuxeo.automation.export.aliases` configuration parameter. Default to false. ``` <extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <property name="nuxeo.automation.export.aliases">true</property> </extension> ```
Sprint:
nxfit 9.1.3
Story Points:
5

Description

Calls to operations like UserWorkspace.Get, Document.Fetch, Collection.GetCollections, Document.Query will fail because they are aliases of existing operations.

Code snippet which fails:

        Document doc = (Document) getNuxeoSession().newRequest("UserWorkspace.Get")
                .setHeader(Constants.HEADER_NX_SCHEMAS)
    }

Attachments

Activity

People

Assignee:

Thomas Roger

Reporter:

Thierry Martins

Participants:

Jenkins, Thierry Martins, Thomas Roger

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

2016-12-14 17:26

Updated:

2016-12-28 13:31

Resolved:

2016-12-27 14:44

Time Tracking

Estimated:

Not Specified

Remaining:

Logged: