You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/10/26 13:02:27 UTC

[jira] [Updated] (ISIS-945) Exception by restful different than shown by Wicket viewer

     [ https://issues.apache.org/jira/browse/ISIS-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-945:
-----------------------------
    Fix Version/s: 1.14.0

> Exception by restful different than shown by Wicket viewer
> ----------------------------------------------------------
>
>                 Key: ISIS-945
>                 URL: https://issues.apache.org/jira/browse/ISIS-945
>             Project: Isis
>          Issue Type: Bug
>          Components: Core: Viewer: RestfulObjects
>    Affects Versions: core-1.7.0
>            Reporter: Erik de Hair
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 1.14.0
>
>
> Hi,
> I have a service method that I only want to expose via restful. I suppressed the method from showing up in the Wicket viewer so I didn't try to call it with the Wicket viewer.
> Now restful throws an error (which is not very useful) when calling the method:
> org.apache.tomcat.util.http.parser.TokenMgrError: Lexical error at line 1, column 29.  Encountered: ":" (58), after : ""
> 	org.apache.tomcat.util.http.parser.HttpParserTokenManager.getNextToken(HttpParserTokenManager.java:434)
> 	org.apache.tomcat.util.http.parser.HttpParser.jj_ntk(HttpParser.java:300)
> 	org.apache.tomcat.util.http.parser.HttpParser.MediaType(HttpParser.java:21)
> For some reason I now also exposed the action via Wicket. That way I get another exception with more useful information about my problem:
> javax.jdo.JDOUserExceptionInvalid operator "=". Did you mean to use "=="?    org.datanucleus.api.jdo.NucleusJDOHelper#getJDOExceptionForNucleusException(NucleusJDOHelper.java:549)
>     org.datanucleus.api.jdo.JDOQuery#execute(JDOQuery.java:299)
>     nl.pocos.dom.workflow.WorkFlowStatusses#checkNumberOfPGSMLicences(WorkFlowStatusses.java:55)
>     sun.reflect.NativeMethodAccessorImpl#invoke0(NativeMethodAccessorImpl.java:-2)
>     sun.reflect.NativeMethodAccessorImpl#invoke(NativeMethodAccessorImpl.java:57)
>     sun.reflect.DelegatingMethodAccessorImpl#invoke(DelegatingMethodAccessorImpl.java:43)
>     java.lang.reflect.Method#invoke(Method.java:606)
> After fixing this error the restful call works fine. I had this behaviour before but couldn't reproduce it. It looks like the TokenMgrError is thrown when some exception occurs in an action called via restful and the real reason/exception can't be found in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)