You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/01/23 02:20:44 UTC

[jira] Updated: (OODT-118) CAS Curator doesn't allow metadata update on file manager browser

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

Chris A. Mattmann updated OODT-118:
-----------------------------------

    Priority: Blocker  (was: Major)

> CAS Curator doesn't allow metadata update on file manager browser
> -----------------------------------------------------------------
>
>                 Key: OODT-118
>                 URL: https://issues.apache.org/jira/browse/OODT-118
>             Project: OODT
>          Issue Type: Bug
>          Components: curator
>    Affects Versions: 0.1-incubating
>         Environment: Testing out locally
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>            Priority: Blocker
>             Fix For: 0.2
>
>
> While fixing OODT-116 I found out that the curator doesn't allow metadata to be updated in the catalog. This is a direct result of porting over to Apache CXF from the old Jersey dependencies. As it turns out line 260 in MetadataResource gives an NPE which is the cause of the error. The root cause is trickier though -- it has to do with @FormParam("id") being null and @Consumes("application/x-www-form-urlencoded"). If you see this issue here http://osdir.com/ml/issues-cxf-apache/2010-03/msg00129.html I think what they are saying is that old versions of Apache CXF pre version 2.3 (we are currently on 2.2.7 in curator) don't support this correctly. So I am going to try upgrading to CXF 2.3.0 (which looks like the latest release for Jax RS) and see if that fixes it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.