Last time I was doing something along those lines (with XStream) I had
to provide it with the classloader to use.
That may need to be done with CGLib too, something that I'd expect to
have been nailed with dmServer/Virgo
On 20/05/2011 14:32, Peter Neubauer wrote:
> Hi there,
> any solution to t
El 22/05/11 13:38, Mattias Persson escribió:
> A transaction is typically done like this:
>
>Transaction tx = graphDb.beginTx();
>try
>{
>// Do stuff
>tx.success();
>}
>finally
>{
>tx.finish();
>}
>
> If you don't want that transaction committed j
Just saw that: http://blog.andrewvc.com/why-arent-you-using-messagepack
Quote from the intro:
JSON is a fantastic format, anywhere people in your organization want to reach
for XML, it's always a good thing to ask the question "Why not JSON?". The
question I'd like you to ask the next time you'r
A transaction is typically done like this:
Transaction tx = graphDb.beginTx();
try
{
// Do stuff
tx.success();
}
finally
{
tx.finish();
}
If you don't want that transaction committed just throw an exception in the
"Do stuff" block, or don't call tx.success(). You c
As Jim and Ian have suggested, a URL parameter or a URL pattern would both work.
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Peter Neubauer
Sent: Sunday, May 22, 2011 11:27 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] Comp
Ok,
Then all requests should be piped through a filter looking for non - domain,
generic, possibly reserved url parameters like "format "? Or is a reserved
url pattern a better way?
On May 22, 2011 5:14 PM, "Rick Bullotta"
wrote:
> The key here is that the *URI* is the determining factor on the ty
The key here is that the *URI* is the determining factor on the type of
representation (compact or not), and clearly the client, who will request a
specific URI, is aware of which type of request has been made.
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@li
Hi Peter,
> How does then the "compact" parameter work in other Accept headers than
> "application/json" work?
I think Ian's saying it's not to be used in the Accept header. He's saying
identify the *variant* through a different URI.
> Since this is a representation that compacts in
> JSON, may
Mmh,
How does then the "compact" parameter work in other Accept headers than
"application/json" work? Since this is a representation that compacts in
JSON, maybe the subformat is ok anyway?
Otherwise, how do we then name that return-format parameter so it doesn't
get mixed up with other, "normal"
9 matches
Mail list logo
