Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to rest service failed #30

Closed
chrisw14 opened this issue Jun 10, 2018 · 11 comments
Closed

Connecting to rest service failed #30

chrisw14 opened this issue Jun 10, 2018 · 11 comments

Comments

@chrisw14
Copy link

Hi,

I tried to connect to the rest-service over the imixs-admin console and get the following error in the logs:
16:02:30,541 WARN [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-18) RESTEASY002142: Multiple resource methods match request "GET /documents/configuration". Selecting one. Matching methods: [public org.imixs.workflow.xml.XMLDataCollection org.imixs.workflow.jaxrs.DocumentRestService.getDocument(java.lang.String,java.lang.String), public org.imixs.workflow.xml.XMLDataCollection org.imixs.workflow.jaxrs.DocumentRestService.getConfiguration() throws java.lang.Exception]

How can I solve this issue?

@rsoika
Copy link
Member

rsoika commented Jun 10, 2018

Please check your deployment artifact. It sounds like there are two versions of imixs-jax-rs included.
We also updated the Rest-API a little bit in the last releases. So it is recommended to use the latest build of Imixs-Admin Client. Also make sure your browser cache is cleared. This is because the admin-client is based on java script and there is also a new java script library included. But the error message sounds more that there are two version deployed. Note: wildfly and glassfish are both caching deployed aretefacts.

@chrisw14
Copy link
Author

Thank you! I solved it by updating imixs-admin.

@chrisw14
Copy link
Author

Okay, it seems that it doesn't solve the problem.

The two methods
public org.imixs.workflow.xml.XMLDataCollection org.imixs.workflow.jaxrs.DocumentRestService.getDocument(java.lang.String,java.lang.String)
public org.imixs.workflow.xml.XMLDataCollection org.imixs.workflow.jaxrs.DocumentRestService.getConfiguration() throws java.lang.Exception

I thinks it's because the following path can match both:
@path("/{uniqueid}")
@path("/configuration")

See https://stackoverflow.com/questions/46081787/resteasy002142-multiple-resource-methods-match-request

So I can't rebuild the index over the imixs-admin...

@chrisw14 chrisw14 reopened this Jun 11, 2018
@rsoika
Copy link
Member

rsoika commented Jun 11, 2018

This is interesting.... I did not run into this problem and I use the version in Wildfly (RestEasy) and also in Glassfish/Payara (Jersey).
But it is true, the path is not unique after all.

@rsoika
Copy link
Member

rsoika commented Jun 11, 2018

I opened a new bug report:
imixs/imixs-workflow#390

@rsoika
Copy link
Member

rsoika commented Jun 11, 2018

As we have this non-unique path pattern since several versions, please try to undeploy your application completely and restart your wildfly server. After that deploy your new version once again. I guess this will work. But of course we need to find a solution.

@rsoika rsoika added the bug label Jun 11, 2018
@chrisw14
Copy link
Author

Okay, I tried it again and it doesn't work for me :-(
The log always appears when I connect to the rest service on the "Home" link in imixs-admin.

@rsoika
Copy link
Member

rsoika commented Jun 12, 2018

We need to change the rest api and also the admin client code for this.
Which version of Wildfly are you using?

@chrisw14
Copy link
Author

The product version is 10.1.0.Final

@rsoika
Copy link
Member

rsoika commented Jun 12, 2018

Just to make it more clear for me. You problem is the warning message in the log file - right?
But you can still work with the admin client? Means - you can see the index list if you click on 'configuration'

image

@rsoika
Copy link
Member

rsoika commented Jun 12, 2018

I think the problem is now fixed in the master branch by adding a regex.
See issue imixs/imixs-workflow#390

Thanks for your finding Chris!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants