RESTEASY001185: Could not find resource for relative

[rflesken]

Hi,

Just to test i was following JB450 documentation about creating a REST service in Teiid Designer.

i have deployed a VDB that includes 1 working oracle source and trying to deploy a REST service procedure.

Everything went OK, but after deploying the REST WAR, i do get the 'teiid interface gui', but when i want to test/try a service i get the error below.

When i try to preview the data, or call the procedure from SQuirrel it works fine. the JNDI is also there, so kind of stuck now.

Who can help me with this, and what would you need?

I use:

Jboss DV 6.2

Developer studio 8.1

Teiid 9.0.7

JBWEB000065: HTTP Status 404 - RESTEASY001185: Could not find resource for relative : /AddressService/getAddress of full path: http://su0env1003:8080/PostcodeCheckv7/AddressService/getAddress/

---

JBWEB000309: type JBWEB000067: Status report

JBWEB000068: message RESTEASY001185: Could not find resource for relative : /AddressService/getAddress of full path: http://su0env1003:8080/PostcodeCheckv7/AddressService/getAddress/

JBWEB000069: description JBWEB000124: The requested resource is not available.

Also this error on the 'home api screen':

schemaValidationMessages
0
level	"error"
message	"Can't read from file http://su0env1003:8080/PostcodeCheckv7/api-docs/AddressService"

[shawkins]

Can you provide the generated REST war?

[rflesken]

Hi Steven,

Thanks! Please see the project and war in the ZIP below:

PostcodeCheck.zip - Box

Regards,

Ruud

[rflesken]

Just fixed it by removing a forward slash in the URI parameter of the virtual procedure...

The JB540 manuals showed a prefix slash there, but it shouldn't be there in Teid 9.

De application Java showed:

@Path( "//getAddress/{Postcode},{BuildingNr}

(notice 2 forward slashes)

[shawkins]

Can you point to where the documentation needs updated?

[rflesken]

Hi Steven,

I got it out of the JB450 documentation.

Red Hat JBoss Data Virtualization Development - JB450

Chapter 10:

Selecting the virtual procedure name in the Model Explorer shows the properties for the procedure. There are several extension properties that begin with REST:. In this example, we set two of them:

    REST:Rest Method = GET

   REST:URI = /GetFirstName/{custId}

Note the use of the input parameter, custId, in the URI.

In this virtual procedure, the result, an XMLLITERAL, is built using a series of XML functions: XMLELEMENT, XMLAGG, and XMLFOREST.