-
15. Re: TEIID31100 Parsing error: Encountered "null"
gioppoluca Sep 26, 2012 6:13 PM (in response to rareddy)I think you are missing the jndi name of the VBD.
In the WAR (I hope to have followed instruction correctly) I have to define the jndi datasource of TEIID:
the VDB uses a datasource whose jndi is named something like BookDB (if I remember well), than since the web service war behaves like a client to the VDB it should need its own datasource whose jndi name is the one you are getting.
So maybe the error means you do not have the jndi defined in standalone.xml
Could it be?
Luca
-
16. Re: TEIID31100 Parsing error: Encountered "null"
rareddy Sep 26, 2012 7:00 PM (in response to gioppoluca)Yes, that was it. Once I added the datasource I saw the same exception.
The query I saw when I executed the service was "call ()" it was missing the procedure name, thus the issue. Did you auto create the WAR file?
Ramesh..
-
17. Re: TEIID31100 Parsing error: Encountered "null"
gioppoluca Sep 27, 2012 2:54 AM (in response to rareddy)Yes I created the WAR using the wizard after creating the web service (again using the wizard from the phisical model).
The strange thing is that all the operations without input parameters throw that error, but the only one using an input parameter (the getauthors) works like a charm.
So or I did something wrong in the operations or the wizards does.
Luca
-
18. Re: TEIID31100 Parsing error: Encountered "null"
tejones Sep 27, 2012 9:05 AM (in response to gioppoluca)Luca,
Based on you trace it appears we are not building the query correctly when there are no parameters. Could you please log this against Teiid Designer and we will get it corrected in time for the Designer 8.0 release (which will work with Teiid 8.x).
Thanks,
Ted
-
19. Re: TEIID31100 Parsing error: Encountered "null"
gioppoluca Sep 28, 2012 5:38 PM (in response to tejones)Jira filed.
Is there a workaround?
Luca
-
20. Re: TEIID31100 Parsing error: Encountered "null"
rareddy Sep 28, 2012 10:33 PM (in response to gioppoluca)You could take .java file in the war and fix the issue yourself and rebuild the WAR file, or add a dummy parameter to the procedure. I recommend the first option to keep your signature to downstream applications consistent.
Ramesh..