Re: Get the contentId of a remotely created content

"Bogeblad Mattias" <[email protected]>
Newsgroups gmane.comp.cms.infoglue.devel
Message-ID <[email protected]>
Hi,

I understand your dilemma. We can perhaps solve it by returning multiple
variables. We could keep the current status flag but also implement a
different variable in which the newly created contentId is stored. Would
that help you?

Regards
Mattias Bogeblad

-----Original Message-----
From: sbalbous [mailto:[email protected]] 
Sent: den 23 december 2008 10:20
To: [email protected]
Subject: [Infoglue-developer] Get the contentId of a remotely created
content


Hi all,

To complete my previous post (remotely create a folder), I'd like to
know if
there a way to retreive the contentID just created with
'remoteContentService' tag. I tried using 'matchingContents' with a
restrictive @freeText but I had 2 issues : this tag is not returning
folders, this tag seems to work only with content attributes and not
with
the core field 'Container name'.

I suppose that if remoteContentService could return the created
contentId or
0 in case of error would really help but I imagine that would be a pain
for
people who already implement this tag as they may test true/false.

Any idea ?
-sb
-- 
View this message in context:
http://www.nabble.com/Get-the-contentId-of-a-remotely-created-content-tp
21141577p21141577.html
Sent from the Infoglue - Dev mailing list archive at Nabble.com.


------------------------------------------------------------------------
------
_______________________________________________
Infoglue-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/infoglue-developer

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.