Hi, CMISProvider.getUriTemplates(Request r) does not work with jax-rs . String base(Path) is ever the path to the project without /servletPath/cmis . How can I fix this in a good way? Best regards Florian Roth in-integrierte informationssysteme GmbH Am Seerhein 8 • 78467 Konstanz http://www.in-gmbh.de/ • mailto:info@in-gmbh.de Telefon: +49 7531 8145-0 Telefax: +49 7531 8145-81 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. • Registernummer: HRB 380976 • Geschäftsführer: Siegfried Wagner
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth updated CMIS-72:
-----------------------------
Status: Patch Available (was: Reopened)
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
> Attachments: Patch jax-rs post objects.java.patch
>
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth reopened CMIS-72:
------------------------------
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
> Attachments: Patch jax-rs post objects.java.patch
>
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth updated CMIS-72:
-----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
> Attachments: Patch jax-rs post objects.java.patch
>
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth updated CMIS-72:
-----------------------------
Attachment: Patch jax-rs post objects.java.patch
patch improves tests and fixes the missing post methods in jax-rs binding
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
> Attachments: Patch jax-rs post objects.java.patch
>
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth updated CMIS-72:
-----------------------------
Comment: was deleted
(was: this patch includes tests and fixes the missing post methods in jax-rs binding)
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Roth updated CMIS-72:
-----------------------------
Status: Patch Available (was: Open)
this patch includes tests and fixes the missing post methods in jax-rs binding
> missing post objects in jax-rs binding
> --------------------------------------
>
> Key: CMIS-72
> URL: https://issues.apache.org/jira/browse/CMIS-72
> Project: Chemistry
> Issue Type: Improvement
> Components: server
> Reporter: Florian Roth
> Priority: Minor
>
> Currently there is no service method to post objects in a children collection in jax-rs
binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
missing post objects in jax-rs binding
--------------------------------------
Key: CMIS-72
URL: https://issues.apache.org/jira/browse/CMIS-72
Project: Chemistry
Issue Type: Improvement
Components: server
Reporter: Florian Roth
Priority: Minor
Currently there is no service method to post objects in a children collection in jax-rs binding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume reopened CMIS-13:
-----------------------------------
> Add empty constructor to CMISServlet
> ------------------------------------
>
> Key: CMIS-13
> URL: https://issues.apache.org/jira/browse/CMIS-13
> Project: Chemistry
> Issue Type: Improvement
> Components: atompub
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
> In order to deploy the atompub server to a servlet container, an empty constructor in
CMISServlet is required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi Jason,
The CmisSqlSimpleWalker has only been lightly tested, I can't say I'm
certain it works in all cases. From doing ANTLR work (based on the
same tree parser) in Nuxeo I remember that list management was a bit
tricky at first.
You haven't given an example of query that fails by the way.
The simplest way to help fixing this would be for you to provide me
with an updated unit test in Chemistry, for instance new query calls
in TestSimpleRepository.testBasicQuery. Could you open a JIRA issue
with that?
I would like to stress also that the goal of CmisSqlSimpleWalker is
not to be efficient, so you shouldn't use it in any production
project. Its goal is to be simple to understand so that unit tests can
be run with it on small in-memory databases. In particular, it will
probably get even slower when I get around to implementing JOIN
support in it, as the simplest way to code it will probably be to just
do the cross join and walk all possible solutions -- which is
expensive but correct. I can't guarantee efficiency without
reimplementing a SQL query engine, or bridging to a real one, and
that's not the goal of the "simple" implementation.
Cheers,
Florent
On Wed, Dec 2, 2009 at 9:51 PM, Jason Tesser <jasontesser@gmail.com> wrote:
> I am trying to use the CmisSimpleWalker in Chemistry to parse my SQL.
> It works until I pass 2 conditions within the where clause.
>
> Here is my code
> http://pastebin.com/f6ea1b90e
>
> It fails in the generated CmisSimpleWalker here on line 1596.
> for (boolean_factor_return t :
> (List<boolean_factor_return>) list_list) {
>
>
> The reason it is faling is list_list is a CommonTree. This makes no
> sense to me as the only things that get added to the list are from
>
> public static class boolean_factor_return extends TreeRuleReturnScope {
> public boolean matches;
> CommonTree tree;
> public Object getTree() { return tree; }
> };
>
> And here you can see where the generated code fills the list. Notice
> that getTree will always be a CommonTree.
>
> list=boolean_factor();
>
> state._fsp--;
> adaptor.addChild(root_1, list.getTree());
> if (list_list==null) list_list=new ArrayList();
> list_list.add(list.getTree());
>
>
> My question is is the grammer file in Chemistry wrong that generates
> this? I wouldn't think this is a bug with ANTLR. I was looking here
> at the grammer http://svn.apache.org/viewvc/incubator/chemistry/trunk/chemistry/chemistry-commons/src/main/antlr3/org/apache/chemistry/impl/simple/CmisSqlSimpleWalker.g?revision=825570&view=markup
>
> Thanks,
> Jason Tesser
> dotCMS Lead Development Manager
> 1-305-858-1422
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
[ https://issues.apache.org/jira/browse/CMIS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785202#action_12785202
]
Serge Huber commented on CMIS-13:
---------------------------------
It looks like this issue needs to be re-opened as the constructor is no longer present since
revision 787180.
> Add empty constructor to CMISServlet
> ------------------------------------
>
> Key: CMIS-13
> URL: https://issues.apache.org/jira/browse/CMIS-13
> Project: Chemistry
> Issue Type: Improvement
> Components: atompub
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
> In order to deploy the atompub server to a servlet container, an empty constructor in
CMISServlet is required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
I am trying to use the CmisSimpleWalker in Chemistry to parse my SQL.
It works until I pass 2 conditions within the where clause.
Here is my code
http://pastebin.com/f6ea1b90e
It fails in the generated CmisSimpleWalker here on line 1596.
for (boolean_factor_return t :
(List<boolean_factor_return>) list_list) {
The reason it is faling is list_list is a CommonTree. This makes no
sense to me as the only things that get added to the list are from
public static class boolean_factor_return extends TreeRuleReturnScope {
public boolean matches;
CommonTree tree;
public Object getTree() { return tree; }
};
And here you can see where the generated code fills the list. Notice
that getTree will always be a CommonTree.
list=boolean_factor();
state._fsp--;
adaptor.addChild(root_1, list.getTree());
if (list_list==null) list_list=new ArrayList();
list_list.add(list.getTree());
My question is is the grammer file in Chemistry wrong that generates
this? I wouldn't think this is a bug with ANTLR. I was looking here
at the grammer http://svn.apache.org/viewvc/incubator/chemistry/trunk/chemistry/chemistry-commons/src/main/antlr3/org/apache/chemistry/impl/simple/CmisSqlSimpleWalker.g?revision=825570&view=markup
Thanks,
Jason Tesser
dotCMS Lead Development Manager
1-305-858-1422
Want to expand atompub-server with an postFolder Test. Similar to the Query post test.
Im getting Parsing errors. Can you help me out? This is the xml
(Name and type are class members)
public void writeTo(StreamWriter sw) {
sw.startDocument();
sw.startElement("entry", CMIS.CMIS_NS, CMIS.CMIS_PREFIX);
sw.startElement("id").writeElementText(
"urn:uuid:00000000-0000-0000-0000-000000000000").endElement();
sw.startElement("title").writeElementText(name).endElement();
sw.startElement("updated").writeElementText("2009-01-01T00:00:00Z").endElement();
sw.startElement("author").writeElementText("component test").endElement();
sw.startElement("link").writeAttribute("rel", "alternate").writeAttribute(
"href", "").endElement();
sw.startElement("summary").writeElementText("test (summary)").endElement();
sw.startElement("object", CMIS.CMIS_NS,
"cmisra");
sw.startElement("properties", CMIS.CMIS_NS, CMIS.CMIS_PREFIX);
sw.startElement("propertyId", CMIS.CMIS_NS, CMIS.CMIS_PREFIX).writeAttribute(
"propertyDefinitionId", "cmis:objectTypeId");
sw.startElement("value", CMIS.CMIS_NS, CMIS.CMIS_PREFIX).writeElementText(
type).endElement();
sw.endElement();// propertyId
sw.endElement();// properties
sw.endElement();// object
sw.endElement();// entry*/
sw.endDocument();
}
chears
in-integrierte informationssysteme GmbH
Am Seerhein 8 • 78467 Konstanz
http://www.in-gmbh.de/ • mailto:info@in-gmbh.de
Telefon: +49 7531 8145-0
Telefax: +49 7531 8145-81
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht
der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. • Registernummer: HRB 380976 •
Geschäftsführer: Siegfried Wagner
:D I figgured it out. Do it like this:
protected Response getAbderaPostEntry(int skipSegments) {
RequestContext requestContext = getRequestContext(skipSegments);
CollectionAdapter adapter = getAbderaCollectionAdapter(requestContext);
if (adapter == null) {
return Response.status(Response.Status.NOT_FOUND).build();
}
ResponseContext responseContext = adapter.postEntry(requestContext);
URI uri = null;
try {
uri = requestContext.getUri().toURI();
} catch (URISyntaxException e) {
log.error("Error: Could not get uri from requestContext", e);
e.printStackTrace();
}
return Response.created(uri).entity(responseContext).build();
}
Chears
Florian
-----Ursprüngliche Nachricht-----
Von: Florian Roth [mailto:Florian.Roth@in-gmbh.de]
Gesendet: Mittwoch, 2. Dezember 2009 15:23
An: chemistry-dev@incubator.apache.org
Betreff: How to return 201 jax-rs on posing new object
Hi,
want to implement jax-rs post object. How do I return 201 I tried this but does not work.
Ends in some parsing exceptions. Can you help me?
protected Response getAbderaPostEntry(int skipSegments) {
RequestContext requestContext = getRequestContext(skipSegments);
CollectionAdapter adapter = getAbderaCollectionAdapter(requestContext);
if (adapter == null) {
return Response.status(Response.Status.NOT_FOUND).build();
}
ResponseContext con=adapter.postEntry(requestContext);
try {
URI uri=con.getLocation().toURI();
return Response.created(uri).build();
} catch (URISyntaxException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
//return Response.ok(con).build();
return Response.status(Response.Status.BAD_REQUEST).build();
}
Best regards
Florian Roth
in-integrierte informationssysteme GmbH
Am Seerhein 8 . 78467 Konstanz
http://www.in-gmbh.de/ . mailto:info@in-gmbh.de
Telefon: +49 7531 8145-0
Telefax: +49 7531 8145-81
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht
der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
Sitz der Gesellschaft: Konstanz . Amtsgericht Freiburg i.B. . Registernummer: HRB 380976 .
Geschäftsführer: Siegfried Wagner
Hi,
want to implement jax-rs post object. How do I return 201 I tried this but does not work.
Ends in some parsing exceptions. Can you help me?
protected Response getAbderaPostEntry(int skipSegments) {
RequestContext requestContext = getRequestContext(skipSegments);
CollectionAdapter adapter = getAbderaCollectionAdapter(requestContext);
if (adapter == null) {
return Response.status(Response.Status.NOT_FOUND).build();
}
ResponseContext con=adapter.postEntry(requestContext);
try {
URI uri=con.getLocation().toURI();
return Response.created(uri).build();
} catch (URISyntaxException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
//return Response.ok(con).build();
return Response.status(Response.Status.BAD_REQUEST).build();
}
Best regards
Florian Roth
in-integrierte informationssysteme GmbH
Am Seerhein 8 • 78467 Konstanz
http://www.in-gmbh.de/ • mailto:info@in-gmbh.de
Telefon: +49 7531 8145-0
Telefax: +49 7531 8145-81
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht
der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. • Registernummer: HRB 380976 •
Geschäftsführer: Siegfried Wagner
[ https://issues.apache.org/jira/browse/CMIS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784793#action_12784793
]
Florent Guillaume commented on CMIS-59:
---------------------------------------
I think the spec is wrong, see http://tools.oasis-open.org/issues/browse/CMIS-605 for my reasoning.
> ContentStream PUT success should be 201
> ---------------------------------------
>
> Key: CMIS-59
> URL: https://issues.apache.org/jira/browse/CMIS-59
> Project: Chemistry
> Issue Type: Bug
> Components: tck
> Reporter: Norrie Quinn
> Priority: Minor
>
> The TCK tests for 200 and fails for 201. See CMIS 1.0 draft4 section 3.10.7.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi,
you are right. getTypes(typeid,..) speaks for a result that includes the type with typeid.
I have to remove the type in services.
Chears
Florian
-----Ursprüngliche Nachricht-----
Von: Florent Guillaume [mailto:fg@nuxeo.com]
Gesendet: Mittwoch, 2. Dezember 2009 12:14
An: chemistry-dev
Betreff: Re: TODO in SimpleTypeManager with spec 1 clear now
Hi,
Yes the spec is now clear that getTypeChildren and getTypeDescendants
never return the type itself, just children at various depth. I'll
make sure the clients/servers behave well.
However in the Java API I find this not very useful. I try to provide
in the API the best user experience possible, and at the moment I have
two methods:
Collection<Type> getTypes(String typeId);
Collection<Type> getTypes(String typeId, int depth, boolean
returnPropertyDefinitions);
I think a Java programmer seeing these method signatures would expect
to see the type itself returned along its children. What do you think?
Florent
On Thu, Nov 12, 2009 at 4:36 PM, Florian Roth <Florian.Roth@in-gmbh.de> wrote:
> Hi,
>
> In my opinion the //TODO: in SimpleTypeManager is clear now with spec 1.0 getTypes(typeId,-1,.)
returns all descendants without Type=typeId
> For me I changed TestSimpleRepository getTypes() and uncommented in SimpleTypeManager.
What do you think? I did It like that also for JcrTypeManager.
>
>
> //if (depth < 0) {
> // list.add(types.get(typeId));
> //}
>
> Chears
>
> frh
>
>
> in-integrierte informationssysteme GmbH
> Am Seerhein 8 . 78467 Konstanz
> http://www.in-gmbh.de/ . mailto:info@in-gmbh.de
>
> Telefon: +49 7531 8145-0
> Telefax: +49 7531 8145-81
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie
nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren
Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
> This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender immediately
and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
>
> Sitz der Gesellschaft: Konstanz . Amtsgericht Freiburg i.B. . Registernummer: HRB 380976
. Geschäftsführer: Siegfried Wagner
>
>
>
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Hi,
Yes the spec is now clear that getTypeChildren and getTypeDescendants
never return the type itself, just children at various depth. I'll
make sure the clients/servers behave well.
However in the Java API I find this not very useful. I try to provide
in the API the best user experience possible, and at the moment I have
two methods:
Collection<Type> getTypes(String typeId);
Collection<Type> getTypes(String typeId, int depth, boolean
returnPropertyDefinitions);
I think a Java programmer seeing these method signatures would expect
to see the type itself returned along its children. What do you think?
Florent
On Thu, Nov 12, 2009 at 4:36 PM, Florian Roth <Florian.Roth@in-gmbh.de> wrote:
> Hi,
>
> In my opinion the //TODO: in SimpleTypeManager is clear now with spec 1.0 getTypes(typeId,-1,.)
returns all descendants without Type=typeId
> For me I changed TestSimpleRepository getTypes() and uncommented in SimpleTypeManager.
What do you think? I did It like that also for JcrTypeManager.
>
>
> //if (depth < 0) {
> // list.add(types.get(typeId));
> //}
>
> Chears
>
> frh
>
>
> in-integrierte informationssysteme GmbH
> Am Seerhein 8 • 78467 Konstanz
> http://www.in-gmbh.de/ • mailto:info@in-gmbh.de
>
> Telefon: +49 7531 8145-0
> Telefax: +49 7531 8145-81
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie
nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren
Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
> This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender immediately
and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
>
> Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. • Registernummer: HRB 380976
• Geschäftsführer: Siegfried Wagner
>
>
>
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Here's what I'm using in my JAX-RS based implementation of CMIS on top
of Nuxeo:
@POST
@Path("node/{uuid}/children")
@Consumes("application/atom+xml;type=entry")
@Produces("application/atom+xml;type=entry")
public Response createObject(@PathParam("uuid") String uuid)
throws Exception {
...
}
S.
On Dec 2, 2009, at 9:53 AM, Florian Roth wrote:
> Hi,
>
> can someone give me an example how to implement a doCreateFolder
> with jax-rs?
>
> @POST
> @Consumes(?)
> @Produces(?)
> @Path("/{objectid}/children?)
> public Response doCreateFolder()
> {
> ????
> }
>
> Best regards
>
> Florian Roth
>
>
> in-integrierte informationssysteme GmbH
> Am Seerhein 8 • 78467 Konstanz
> http://www.in-gmbh.de/ • mailto:info@in-gmbh.de
>
> Telefon: +49 7531 8145-0
> Telefax: +49 7531 8145-81
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
> E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
> Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren
> sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail
> in error) please notify the sender immediately and destroy this e-
> mail. Any unauthorised copying, disclosure or distribution of the
> material in this e-mail is strictly forbidden.
>
> Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. •
> Registernummer: HRB 380976 • Geschäftsführer: Siegfried Wagner
>
>
>
--
Stefane Fermigier, Founder and Chairman, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
Web: http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87
New: follow me on Twitter: http://twitter.com/sfermigier
Hi,
can someone give me an example how to implement a doCreateFolder with jax-rs?
@POST
@Consumes(?)
@Produces(?)
@Path("/{objectid}/children?)
public Response doCreateFolder()
{
????
}
Best regards
Florian Roth
in-integrierte informationssysteme GmbH
Am Seerhein 8 • 78467 Konstanz
http://www.in-gmbh.de/ • mailto:info@in-gmbh.de
Telefon: +49 7531 8145-0
Telefax: +49 7531 8145-81
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht
der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
Sitz der Gesellschaft: Konstanz • Amtsgericht Freiburg i.B. • Registernummer: HRB 380976 •
Geschäftsführer: Siegfried Wagner
[ https://issues.apache.org/jira/browse/CMIS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-71:
------------------------------
Status: Patch Available (was: Open)
> Query parameters aren't taken into account
> ------------------------------------------
>
> Key: CMIS-71
> URL: https://issues.apache.org/jira/browse/CMIS-71
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-71.txt
>
>
> None of query parameters but the statement one are taken into account
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-71:
------------------------------
Attachment: patch-CMIS-71.txt
> Query parameters aren't taken into account
> ------------------------------------------
>
> Key: CMIS-71
> URL: https://issues.apache.org/jira/browse/CMIS-71
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-71.txt
>
>
> None of query parameters but the statement one are taken into account
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Query parameters aren't taken into account
------------------------------------------
Key: CMIS-71
URL: https://issues.apache.org/jira/browse/CMIS-71
Project: Chemistry
Issue Type: Bug
Components: server
Reporter: Amélie Avramo
None of query parameters but the statement one are taken into account
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-70:
------------------------------
Status: Patch Available (was: Open)
> Query POST success should be 201
> --------------------------------
>
> Key: CMIS-70
> URL: https://issues.apache.org/jira/browse/CMIS-70
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-70.txt
>
>
> Query POST should return a 201 HTTP status code when success. (see §3.7.2.1 CMIS-cd04
spec)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-70:
------------------------------
Attachment: patch-CMIS-70.txt
CMISQueryFeed modified to return 201 HTTP status code when POST is successful.
Tests are separated relative to CMIS-69 issue.
> Query POST success should be 201
> --------------------------------
>
> Key: CMIS-70
> URL: https://issues.apache.org/jira/browse/CMIS-70
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-70.txt
>
>
> Query POST should return a 201 HTTP status code when success. (see §3.7.2.1 CMIS-cd04
spec)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-70:
------------------------------
Description: Query POST should return a 201 HTTP status code when success. (see §3.7.2.1
CMIS-cd04 spec)
Environment: (was: Query POST should return a 201 HTTP status code when success. (see
§3.7.2.1 CMIS-cd04 spec))
> Query POST success should be 201
> --------------------------------
>
> Key: CMIS-70
> URL: https://issues.apache.org/jira/browse/CMIS-70
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
>
> Query POST should return a 201 HTTP status code when success. (see §3.7.2.1 CMIS-cd04
spec)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Query POST success should be 201
--------------------------------
Key: CMIS-70
URL: https://issues.apache.org/jira/browse/CMIS-70
Project: Chemistry
Issue Type: Bug
Components: server
Environment: Query POST should return a 201 HTTP status code when success. (see §3.7.2.1
CMIS-cd04 spec)
Reporter: Amélie Avramo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-42:
------------------------------
Attachment: patch-CMIS-42.txt
Throws a ResponseContextException(409) when contentStream is null.
I've add a specific test for the AbderaServlet, since it doesn't works with Jaxrs because
of the CMIS-69 issue.
> Use specialized CMIS-related exceptions to deal with error cases
> ----------------------------------------------------------------
>
> Key: CMIS-42
> URL: https://issues.apache.org/jira/browse/CMIS-42
> Project: Chemistry
> Issue Type: Task
> Components: api
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Attachments: patch-CMIS-42.txt
>
>
> We should use specialized exceptions (following what's defined in the spec's domain model)
to treat error cases.
> First pass on the CMIS exception list:
> General:
> - invalidArgument -> java.lang.IllegalArgumentException
> - notSupported -> java.lang.UnsupportedOperationException
> - runtime -> java.lang.RuntimeException
> - objectNotFound
> - permissionDenied
> Specific:
> - constraint
> - contentAlreadyExists
> - filterNotValid
> - nameConstraintViolation
> - storage
> - streamNotSupported
> - updateConflict
> - versioning
> At least for the general CMIS exceptions I propose to use Java unchecked exception. Even
for the specific ones I think we should minimize the number of checked exceptions (JCR showed
that having too many of those on a single method is painful).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Jaxrs always returns a 200 HTTP status code when getting content
----------------------------------------------------------------
Key: CMIS-69
URL: https://issues.apache.org/jira/browse/CMIS-69
Project: Chemistry
Issue Type: Bug
Components: server
Reporter: Amélie Avramo
Priority: Minor
The AbderaResource.doGetFile() wrapp the ResponseContext so that the status code is always
200.
It seems to be the same for other requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-68:
------------------------------
Component/s: tck
> GET an empty content stream should throw a 409 error instead of a 404 one
> -------------------------------------------------------------------------
>
> Key: CMIS-68
> URL: https://issues.apache.org/jira/browse/CMIS-68
> Project: Chemistry
> Issue Type: Bug
> Components: tck
> Reporter: Amélie Avramo
> Priority: Minor
>
> Constraint CMIS Services Exceptions are mapped with 409 HTTP Status Code (see §3.2.4.2
CMIS-cd04 spec)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
GET an empty content stream should throw a 409 error instead of a 404 one
-------------------------------------------------------------------------
Key: CMIS-68
URL: https://issues.apache.org/jira/browse/CMIS-68
Project: Chemistry
Issue Type: Bug
Reporter: Amélie Avramo
Priority: Minor
Constraint CMIS Services Exceptions are mapped with 409 HTTP Status Code (see §3.2.4.2 CMIS-cd04
spec)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782906#action_12782906
]
Amélie Avramo edited comment on CMIS-42 at 11/26/09 2:44 PM:
-------------------------------------------------------------
Trying to get an empty content stream should throw a 409 HTTP error.
For now it returns a response 200.
was (Author: aavramo):
Trying to get an empty content stream should throw a 404 HTTP error.
For now it returns a response 200.
> Use specialized CMIS-related exceptions to deal with error cases
> ----------------------------------------------------------------
>
> Key: CMIS-42
> URL: https://issues.apache.org/jira/browse/CMIS-42
> Project: Chemistry
> Issue Type: Task
> Components: api
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
>
> We should use specialized exceptions (following what's defined in the spec's domain model)
to treat error cases.
> First pass on the CMIS exception list:
> General:
> - invalidArgument -> java.lang.IllegalArgumentException
> - notSupported -> java.lang.UnsupportedOperationException
> - runtime -> java.lang.RuntimeException
> - objectNotFound
> - permissionDenied
> Specific:
> - constraint
> - contentAlreadyExists
> - filterNotValid
> - nameConstraintViolation
> - storage
> - streamNotSupported
> - updateConflict
> - versioning
> At least for the general CMIS exceptions I propose to use Java unchecked exception. Even
for the specific ones I think we should minimize the number of checked exceptions (JCR showed
that having too many of those on a single method is painful).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782906#action_12782906
]
Amélie Avramo commented on CMIS-42:
-----------------------------------
Trying to get an empty content stream should throw a 404 HTTP error.
For now it returns a response 200.
> Use specialized CMIS-related exceptions to deal with error cases
> ----------------------------------------------------------------
>
> Key: CMIS-42
> URL: https://issues.apache.org/jira/browse/CMIS-42
> Project: Chemistry
> Issue Type: Task
> Components: api
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
>
> We should use specialized exceptions (following what's defined in the spec's domain model)
to treat error cases.
> First pass on the CMIS exception list:
> General:
> - invalidArgument -> java.lang.IllegalArgumentException
> - notSupported -> java.lang.UnsupportedOperationException
> - runtime -> java.lang.RuntimeException
> - objectNotFound
> - permissionDenied
> Specific:
> - constraint
> - contentAlreadyExists
> - filterNotValid
> - nameConstraintViolation
> - storage
> - streamNotSupported
> - updateConflict
> - versioning
> At least for the general CMIS exceptions I propose to use Java unchecked exception. Even
for the specific ones I think we should minimize the number of checked exceptions (JCR showed
that having too many of those on a single method is painful).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-67:
------------------------------
Component/s: commons
> NullPointerException when creating empty content document
> ---------------------------------------------------------
>
> Key: CMIS-67
> URL: https://issues.apache.org/jira/browse/CMIS-67
> Project: Chemistry
> Issue Type: Bug
> Components: commons, server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-67.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-67:
------------------------------
Status: Patch Available (was: Open)
> NullPointerException when creating empty content document
> ---------------------------------------------------------
>
> Key: CMIS-67
> URL: https://issues.apache.org/jira/browse/CMIS-67
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-67.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-67:
------------------------------
Attachment: patch-CMIS-67.txt
> NullPointerException when creating empty content document
> ---------------------------------------------------------
>
> Key: CMIS-67
> URL: https://issues.apache.org/jira/browse/CMIS-67
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-67.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
NullPointerException when creating empty content document
---------------------------------------------------------
Key: CMIS-67
URL: https://issues.apache.org/jira/browse/CMIS-67
Project: Chemistry
Issue Type: Bug
Components: server
Reporter: Amélie Avramo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-66:
------------------------------
Status: Patch Available (was: Open)
> Getting object with request parameters throws a 404 error
> ---------------------------------------------------------
>
> Key: CMIS-66
> URL: https://issues.apache.org/jira/browse/CMIS-66
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-66.txt
>
>
> Parameters aren't taken into account for object request
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/CMIS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amélie Avramo updated CMIS-66:
------------------------------
Attachment: patch-CMIS-66.txt
TargetResolver fixed in CMISProvider and parameters taken into account in CMISObjectCollection
> Getting object with request parameters throws a 404 error
> ---------------------------------------------------------
>
> Key: CMIS-66
> URL: https://issues.apache.org/jira/browse/CMIS-66
> Project: Chemistry
> Issue Type: Bug
> Components: server
> Reporter: Amélie Avramo
> Attachments: patch-CMIS-66.txt
>
>
> Parameters aren't taken into account for object request
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Getting object with request parameters throws a 404 error
---------------------------------------------------------
Key: CMIS-66
URL: https://issues.apache.org/jira/browse/CMIS-66
Project: Chemistry
Issue Type: Bug
Components: server
Reporter: Amélie Avramo
Parameters aren't taken into account for object request
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.