Persistence Layer: get source of definition

CONTENTS DELETED

Hi Bruno,

I am not sure to understand your question. It seems to me that in general a
GET needs to check if the form is available and answer 404 if it isn't. But
a PUT (publish or republish) wouldn't need to do that check. Am I missing
something?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Hi Bruno,

If there is a GET for the form definition before the PUT, then it should be
find if that GET returns a 404. Off the top of my head, I think the GET is
made to check the description for the form, that users can enter when
publishing, and which isn't part of the metadata. But again, it should be
fine if the API returns a 404. You'll let me know what you see with 2017.2.

https://doc.orbeon.com/form-runner/api/persistence/forms-metadata.html

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Bruno,

What do you mean by "republish"? Are you using the "Upgrade local/remote
form definitions" on the Form Runner home page as an admin?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Bruno, got it, so the form had already been published in the past, but is
currently unavailable. So when you "publish it" from the home page (which
could also be called "make available"), Form Runner reads the form, and
writes it back as "available". You're saying that the reading part returns a
404; how so, if the form had already been published?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Hi Bruno,

Let me first clarify some terminology that might be confusing:

- A form can be published or not.
- A publish form can be available or not.

So far so good, I imagine. The confusing part is that what is called
"unpublish" in the Form Runner home page, doesn't "unpublish", it makes the
published form unavailable.

So if the Form Runner home page shows the form, a GET should succeed. If the
form is unavailable, then its metadata should say so. Does that make more
sense?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Hi Bruno,

The GET operation shouldn't return a 404 when the form is unavailable. It
should just return the form definition, but in its `fr-form-metadata` it
will have `<available>false</available>`.

In fact, there is nothing related to the availability of form definitions
that your implementation of the persistence API should worry about: this is
something implemented at the Form Runner level, and your implementation can
treat it as an opaque piece of information that is part of the form
metadata. Does this make sense?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

CONTENTS DELETED

Perfect Bruno! And for 2018.1, we've also change the terminology used on the
Form Runner home page to use "make unavailable" instead of "unpublish",
which I image, must have things confusing (why is an "unpublished" form
still "published"?!).

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].