Well...here you are...
imt...@imtiaz-20100131 /cygdrive/d/temp
$ curl --dump-header headers -d "token=HEZTQKM525SAMIPN4EDVRUOGHI40AKBL"
http:/
/localhost:8080/esme-server-apache-esme-1.0-RC1-incubating/api2/session
<?xml version="1.0" encoding="UTF-8"?>
<api><session><user><id>3</id><nickname>imtiaz2</nickname><image>None</image><wh
ole_name>I A 2 H E</whole_name></user></session></api>
imt...@imtiaz-20100131 /cygdrive/d/temp
$ cat headers
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=28DBA5607A4D94C9E6E2BD1E61492EAD;
Path=/esme-server-apach
e-esme-1.0-RC1-incubating
Expires: Sat, 17 Jul 2010 15:58:22 UTC
Date: Sat, 17 Jul 2010 15:58:22 GMT
Pragma: no-cache
Cache-Control: no-cache; private; no-store
X-Lift-Version: 2.0-SNAPSHOT
Content-Type: text/xml;charset=utf-8
Content-Length: 178
imt...@imtiaz-20100131 /cygdrive/d/temp
$ curl -b headers -d
'message=test72&metadata=<metadata>"meta":[{"place":{"plac
e_type":"city","region":"CA+"}},{"song":{"artist":"Prince","songtitle":"Never+L
et+Me+Down"}}]</metadata>'
http://localhost:8080/esme-server-apache-esme-1.0-RC
1-incubating/api2/user/messages
<?xml version="1.0" encoding="UTF-8"?>
<api><message>
<id>10</id>
<date>Sat, 17 Jul 2010 15:58:44 UTC</date>
<source>api2</source>
<body>test72</body>
<metadata>"meta":[{"place":{"place_type":"c
ity","region":"CA
"}},{"song":{"artist&q
uot;:"Prince","songtitle":"Never Let Me
Down"}}]</
metadata>
<author><nickname>imtiaz2</nickname><id>3</id></author>
<tags></tags><replyto></replyto><conversation></conversation>
</message></api>
imt...@imtiaz-20100131 /cygdrive/d/temp
$
Imtiaz
----- Original Message -----
From: "Ethan Jewett" <[email protected]>
To: <[email protected]>; <[email protected]>
Sent: Saturday, July 17, 2010 8:30 PM
Subject: Re: Release planning
Re ESME-242 - I think you (and Vassil) are right, but I haven't been
able to independently confirm and I haven't seen a working API call
attached to the Jira issue, so I'm not willing to close it yet. If we
had working metadata examples using properly escaped XML and JSON, I
would be very happy :-)
Ethan
On Sat, Jul 17, 2010 at 4:32 PM, <[email protected]> wrote:
About ESME-242,
Per Vassil Dichev's mail to this group that http POST text used in the
shell curl command must not be quoted and must be url encoded or must be
quoted using single quotes, this Jira issue should be resolved to 'not a
bug', if I recall correctly, that is!
Imtiaz
Sent from BlackBerry® on Airtel
-----Original Message-----
From: Ethan Jewett <[email protected]>
Date: Sat, 17 Jul 2010 16:11:44
To: <[email protected]>
Reply-To: [email protected]
Subject: Re: Release planning
Thoughts on items remaining for this release:
ESME-225 - "need unit test for GET api2/users/actions don't retrieve
disabled actions" - I don't think this is required for release and
should be moved to the backlog.
ESME-242 - "The use of metadata in the api2 currently doesn't work" -
I think this is important but also not required for release and should
be moved to the backlog.
I agree that ESME-205 and ESME-212 are major. ESME-212 at least is a
blocker.
Regarding changes to be made to API2: I've created JIRA issues for all
the todos at the bottom of the file (except a couple that were already
done). It was lazy of me to put a todo-list in the file - I should
really avoid that and force myself to have everything in Jira. I will
be checking in a version of the file without the todo-list shortly.
Cheers,
Ethan
On Fri, Jul 16, 2010 at 12:40 PM, Richard Hirsch <[email protected]>
wrote:
I've been working on the JIRA items and we have 10 items left for this
release.
The following items are linked to IE 7:
* ESME-207
* ESME-239
* ESME-208
Some of these items are CSS-related (for example, 207) but the other
ones are javascript / jquery related.
I think the two main issues are:
* ESME-205 Search is broken (This only happens when you use a JDBC
based compass indexes - first noticed on Stax but it also is present
locally)
* ESME-212 Messages from pools aren't hidden
I'm going to be gone the next four weeks on vacation, so either
someone else can coordinate the release or we wait until I return to
continue with our release preparations.
If anyone wants to work on other items until the release, here are
other items that I consider important:
* ESME-108 - View my pools" functionality
* ESME-170 Pubsubhubbub support for Atom & RSS actions#
* ESME-214 Add container-based authentication
* ESME-213 Twitter API is out-of-date and API calls don't always
return the correct info
-- other api2 related changes - see the ToDos at the bottom of the
API2.scala page .
D.
