Issues with RestKit and responses with namespaces
I'm developing an app that should communicate with our server application. I can retrieve both XML and JSON documents from the server. However, I'm having problems because of (I imagine) namespaces. The server responds either an XML like:

    <emsman:packages xmlns:ems="http://www.mycompany.com/ems"     xmlns:emsman="http://www.mycompany.com/ems/managing">
      <ems:link href="http://devserver02/services/rest/packages" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
      <emsman:package id="1">
        <ems:link href="http://devserver02/services/rest/packages/1" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
        <emsman:artifactCount>36</emsman:artifactCount>
        <emsman:name>Public</emsman:name>
        <emsman:owner id="06d57bf5-0ce1-4a84-abba-b8019b16fb1c">
          <ems:link href="http://devserver02/services/rest/users/06d57bf5-0ce1-4a84-abba-b8019b16fb1c" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
          <emsman:email>helpdesk@mycompany.com</emsman:email>
          <emsman:firstName>Administrator</emsman:firstName>
          <emsman:lastName>User</emsman:lastName>
          <emsman:locale>en</emsman:locale>
          <emsman:userName>admin</emsman:userName>
        </emsman:owner>
      </emsman:package>
    </emsman:packages>

or a JSON like:

    {
        "ns1.packages": {
            "ems.link": {
                "@href": "http:\/\/devserver02\/services\/rest\/packages",
                "@rel": "self",
                "@type": "application\/vnd.mycompany.com.ems.managing+xml"
        },
        "ns1.package": {
            "@id": "1",
            "ems.link": {
                "@href": "http:\/\/devserver02\/services\/rest\/packages\/1",
                "@rel": "self",
                "@type": "application\/vnd.mycompany.com.ems.managing+xml"
            },
            "ns1.artifactCount": 36,
            "ns1.name": "Public",
            "ns1.owner": {
                "@id": "06d57bf5-0ce1-4a84-abba-b8019b16fb1c",
                "ems.link": {
                    "@href": "http:\/\/devserver02\/services\/rest\/users\/06d57bf5-0ce1-4a84-abba-b8019b16fb1c",
                    "@rel": "self",
                    "@type": "application\/vnd.mycompany.com.ems.managing+xml"
                },
                "ns1.email": "helpdesk@mycompany.com",
                "ns1.firstName": "Administrator",
                "ns1.lastName": "User",
                "ns1.locale": "en",
                "ns1.userName": "admin"
            }
        }
    }
}
I modified a test version of the server to hide the namespace specification. Then RestKit worked fine, mapping my objects (package in this example) correctly. However, with the namespaces turned on, I'm always getting "Adding mapping error: Could not find an object mapping for keyPath:" errors. I imagine that the problem could be with the colon between the namespace and the element name in XML, and with the dot between the namespace and the element name in JSON.

Moreover, the conversion from XML to JSON performed by the CXF framework, which we're using on the server application, specifies that XML attributes are converted to JSON sub-elements by adding an @ sign (as can be seen in package id attribute). 

Is there any way to setup RestKit to deal with the namespace prefix on the elements? Is it possible that RestKit parses correctly elements with an @ sign embedded on their names or do I have to hardcode it?
Issues with RestKit and responses with namespaces
===

I'm developing an app that should communicate with our server application. I can retrieve both XML and JSON documents from the server. However, I'm having problems because of (I imagine) namespaces. The server responds either an XML like:

    <emsman:packages xmlns:ems="http://www.mycompany.com/ems"     xmlns:emsman="http://www.mycompany.com/ems/managing">
      <ems:link href="http://devserver02/services/rest/packages" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
      <emsman:package id="1">
        <ems:link href="http://devserver02/services/rest/packages/1" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
        <emsman:artifactCount>36</emsman:artifactCount>
        <emsman:name>Public</emsman:name>
        <emsman:owner id="06d57bf5-0ce1-4a84-abba-b8019b16fb1c">
          <ems:link href="http://devserver02/services/rest/users/06d57bf5-0ce1-4a84-abba-b8019b16fb1c" rel="self" type="application/vnd.mycompany.ems.managing+xml"/>
          <emsman:email>helpdesk@mycompany.com</emsman:email>
          <emsman:firstName>Administrator</emsman:firstName>
          <emsman:lastName>User</emsman:lastName>
          <emsman:locale>en</emsman:locale>
          <emsman:userName>admin</emsman:userName>
        </emsman:owner>
      </emsman:package>
    </emsman:packages>

or a JSON like:

    {
        "ns1.packages": {
            "ems.link": {
                "@href": "http:\/\/devserver02\/services\/rest\/packages",
                "@rel": "self",
                "@type": "application\/vnd.mycompany.com.ems.managing+xml"
        },
        "ns1.package": {
            "@id": "1",
            "ems.link": {
                "@href": "http:\/\/devserver02\/services\/rest\/packages\/1",
                "@rel": "self",
                "@type": "application\/vnd.mycompany.com.ems.managing+xml"
            },
            "ns1.artifactCount": 36,
            "ns1.name": "Public",
            "ns1.owner": {
                "@id": "06d57bf5-0ce1-4a84-abba-b8019b16fb1c",
                "ems.link": {
                    "@href": "http:\/\/devserver02\/services\/rest\/users\/06d57bf5-0ce1-4a84-abba-b8019b16fb1c",
                    "@rel": "self",
                    "@type": "application\/vnd.mycompany.com.ems.managing+xml"
                },
                "ns1.email": "helpdesk@mycompany.com",
                "ns1.firstName": "Administrator",
                "ns1.lastName": "User",
                "ns1.locale": "en",
                "ns1.userName": "admin"
            }
        }
    }
}
I modified a test version of the server to hide the namespace specification. Then RestKit worked fine, mapping my objects (package in this example) correctly. However, with the namespaces turned on, I'm always getting "Adding mapping error: Could not find an object mapping for keyPath:" errors. I imagine that the problem could be with the colon between the namespace and the element name in XML, and with the dot between the namespace and the element name in JSON.

Moreover, the conversion from XML to JSON performed by the CXF framework, which we're using on the server application, specifies that XML attributes are converted to JSON sub-elements by adding an @ sign (as can be seen in package id attribute). 

Is there any way to setup RestKit to deal with the namespace prefix on the elements? Is it possible that RestKit parses correctly elements with an @ sign embedded on their names or do I have to hardcode it?