I'm been thinking about this integration and I think we need some way to publish the information that is return from a HTTP post action. For example, posting to 12sprints leads to a response that contains the activity ID. Without surfacing this ID, it is impossible to get the ID except by going directly to 12Sprints.
To deal with this issue, I think it would useful for the HTTP Post Action to post a message with the result. I've created a JIRA item to deal with this: https://issues.apache.org/jira/browse/ESME-143 On Wed, Dec 2, 2009 at 3:05 PM, Richard Hirsch <[email protected]> wrote: > Then you would probably have a problem in that it would the tags > wouldn't be unencoded. > > D. > > On Wed, Dec 2, 2009 at 2:31 PM, Vassil Dichev <[email protected]> wrote: >> Great, does this issue still make sense? I think you are relying on >> the fact that there's a single tag in there. What if you use several? >> They would be separated with spaces. >> >> On Wed, Dec 2, 2009 at 3:25 PM, Richard Hirsch <[email protected]> wrote: >>> Fixed this myself:-> >>> >>> The integration with 12sprints is now based on dynamic information >>> based on message tags. I set the activity ID in the action through the >>> message tag. >>> >>> D. >>> >>> On Tue, Dec 1, 2009 at 4:28 PM, Richard Hirsch <[email protected]> >>> wrote: >>>> Unfortunately, I'm stuck now, because I can't use %t in the HTTP Post >>>> action URL. :-< >>>> >>>> I've created a Jira item ( >>>> https://issues.apache.org/jira/browse/ESME-141 ) describing the >>>> problem >>>> >>>> D. >>>> >>>> On Tue, Dec 1, 2009 at 12:24 PM, Richard Hirsch <[email protected]> >>>> wrote: >>>>> I'm asking first on a 12sprints discussion if I can provide details >>>>> about using the REST API. >>>>> >>>>> D. >>>>> >>>>> On Tue, Dec 1, 2009 at 12:13 PM, Vassil Dichev <[email protected]> wrote: >>>>>>> Just created a 12sprints activity via an ESME action. >>>>>>> >>>>>>> Took a bit of time to get the formatting right but it works now. >>>>>> >>>>>> Great! Can you share an approximate syntax for the header/body? It is >>>>>> always better to have more info we could document. >>>>>> >>>>> >>>> >>> >> >
