[
https://issues.apache.org/jira/browse/CMIS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay brown updated CMIS-630:
---------------------------
Attachment: ecblank.gif
graycol.gif
Thanks for fixing that so fast, wow. ( Verified. )
Definitely a good fix. Now if you are not doing any extensions you don't
have to do anything special to make the Json binding work.
I just realized that I can 'close' the issues that I have opened (like this
one). As a matter of process should I always be 'closing' my tickets once
I have verified them or is leaving them in fixed ok? It looks like I have
a few out there that are in 'fixed' state.
So are you getting in the vacation frame of mind yet?
Jay Brown
Senior Engineer, ECM Development
IBM Software Group
[email protected]
>-----------------------------------------------------------------------------------------------------------------------------------------------|
|Florian Müller (JIRA) <[email protected]>
|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
|Jay Brown/Costa Mesa/IBM@IBMUS,
|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
|02/16/2013 02:55 AM
|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
|[jira] [Resolved] (CMIS-630) NullPointerException
JSONConverter.convertExtension
|
>-----------------------------------------------------------------------------------------------------------------------------------------------|
[
https://issues.apache.org/jira/browse/CMIS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Müller resolved CMIS-630.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: OpenCMIS 0.9.0 beta 1)
OpenCMIS 0.9.0
Assignee: Florian Müller
OpenCMIS now ignores extension elements that are null.
with REST binding all along and everything working ok so far. Tried doing
a GET today for the first time on the browser binding service document
passing same credentials, etc. and I get this error. (see trace below)
the JSON binding, but seems like this should not happen. E.g. Something
that needs to be initialized but only for JSON.
org.apache.chemistry.opencmis.commons.impl.JSONConverter.convertExtension
(JSONConverter.java:2736) at
org.apache.chemistry.opencmis.commons.impl.JSONConverter.convert
(JSONConverter.java:239) at
org.apache.chemistry.opencmis.server.impl.browser.RepositoryService.getRepositories
(RepositoryService.java:78) at
org.apache.chemistry.opencmis.server.impl.browser.CmisBrowserBindingServlet.dispatch
(CmisBrowserBindingServlet.java:332) at
org.apache.chemistry.opencmis.server.impl.browser.CmisBrowserBindingServlet.service
(CmisBrowserBindingServlet.java:292) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:305) at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:210) at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:222) at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:123) at
org.apache.catalina.authenticator.AuthenticatorBase.invoke
(AuthenticatorBase.java:472) at
org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:171) at
org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:99) at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:118) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process
(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol
$AbstractConnectionHandler.process(AbstractProtocol.java:589) at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run
(JIoEndpoint.java:310) at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:897) at
java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:738) ",
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
> NullPointerException JSONConverter.convertExtension
> ---------------------------------------------------
>
> Key: CMIS-630
> URL: https://issues.apache.org/jira/browse/CMIS-630
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.9.0 beta 1
> Environment: <opencmis.version>0.9.0-beta-1</opencmis.version>
> Reporter: jay brown
> Assignee: Florian Müller
> Fix For: OpenCMIS 0.9.0
>
> Attachments: ecblank.gif, graycol.gif
>
>
> Have a simple server running based on 0.9.0-beta-1. Have been testing with
> REST binding all along and everything working ok so far. Tried doing a GET
> today for the first time on the browser binding service document passing same
> credentials, etc. and I get this error. (see trace below)
> Not sure if this is something special that needs to be done to support the
> JSON binding, but seems like this should not happen. E.g. Something that
> needs to be initialized but only for JSON.
> Please advise.
> Stack trace ------------------------
> {
> "message": null,
> "stacktrace": "java.lang.NullPointerException at
> org.apache.chemistry.opencmis.commons.impl.JSONConverter.convertExtension(JSONConverter.java:2736)
> at
> org.apache.chemistry.opencmis.commons.impl.JSONConverter.convert(JSONConverter.java:239)
> at
> org.apache.chemistry.opencmis.server.impl.browser.RepositoryService.getRepositories(RepositoryService.java:78)
> at
> org.apache.chemistry.opencmis.server.impl.browser.CmisBrowserBindingServlet.dispatch(CmisBrowserBindingServlet.java:332)
> at
> org.apache.chemistry.opencmis.server.impl.browser.CmisBrowserBindingServlet.service(CmisBrowserBindingServlet.java:292)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
> at java.lang.Thread.run(Thread.java:738) ",
> "exception": "runtime"
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
